Derivative works

Defensive Disclosure and Prior Art Generation for U.S. Patent 12,161,628

Publication Date: May 10, 2026
Subject: Derivatives and obvious improvements of combination therapy involving enzalutamide and CYP3A4 inducers.
Purpose: To place into the public domain a series of technical disclosures that anticipate potential future patent claims related to the subject matter of U.S. Patent 12,161,628, thereby rendering them non-novel or obvious under 35 U.S.C. § 102 and § 103.

---

Axis 1: Therapeutic Agent & Component Substitution

Derivative 1.1: Dose Adjustment of Enzalutamide with Alternative Strong CYP3A4 Inducers

• Enabling Description: The core principle of U.S. Patent 12,161,628 is the dose increase of enzalutamide (a CYP3A4/2C8 substrate) from its standard 160 mg dose to 240 mg to counteract the metabolic induction by rifampin. This principle is extended to other strong CYP3A4 inducers. Based on the known relative induction potential of these agents compared to rifampin, a skilled clinician can determine an adjusted dose of enzalutamide. For example, when co-administered with carbamazepine, which has a similar induction strength to rifampin, a daily dose of 240 mg of enzalutamide is administered. For phenytoin or phenobarbital, which can also be strong inducers, a dose titration starting at 200 mg and escalating to 240 mg based on serum PSA levels and patient tolerance is implemented. This method is applicable to any condition requiring treatment with enzalutamide in a patient who must take a strong CYP3A4 inducer for a co-morbidity such as epilepsy or other infections.

graph TD
    A[Patient with Prostate Cancer on Standard 160mg Enzalutamide] --> B{Initiation of Strong CYP3A4 Inducer for Co-morbidity};
    B --> C1[Inducer: Carbamazepine];
    B --> C2[Inducer: Phenytoin];
    B --> C3[Inducer: St. John's Wort];
    C1 --> D1[Increase Enzalutamide Dose to 240mg/day];
    C2 --> D2[Titrate Enzalutamide Dose from 200mg to 240mg/day];
    C3 --> D3[Increase Enzalutamide Dose to 240mg/day];
    D1 & D2 & D3 --> E[Monitor PSA and Safety];

Derivative 1.2: Use of Deuterated Enzalutamide with a Strong CYP3A4 Inducer

• Enabling Description: A deuterated analog of enzalutamide is developed where one or more hydrogen atoms are replaced by deuterium, specifically at metabolically active sites. This substitution can reduce the rate of metabolism by CYP3A4 and CYP2C8, leading to a longer half-life and altered pharmacokinetic profile. When a patient treated with this deuterated enzalutamide (e.g., standard dose of 120 mg/day) is also administered rifampin, the required dose increase is proportionally smaller than that for standard enzalutamide. A clinical protocol would increase the deuterated enzalutamide dose by 50%, to 180 mg/day, to maintain therapeutic exposure, mirroring the proportional adjustment logic of the parent invention.

sequenceDiagram
    participant P as Patient
    participant D as Deuterated Enzalutamide (120mg)
    participant R as Rifampin
    participant M as Metabolic Pathway (CYP3A4)

    P->>D: Administer standard dose
    loop Treatment Period 1
        D->>M: Slower metabolism (due to D-substitution)
        M->>P: Stable therapeutic concentration
    end
    P->>R: Administer Rifampin
    R->>M: Induce CYP3A4 activity
    loop Treatment Period 2
        D->>M: Increased rate of metabolism
        M->>P: Sub-therapeutic concentration
    end
    Note right of P: Dose Adjustment Needed
    P->>D: Administer adjusted dose (180mg)
    loop Treatment Period 3
        D->>M: Increased metabolism counteracted by higher dose
        M->>P: Restore therapeutic concentration
    end

---

Axis 2: Dosing & Patient Population Parameter Expansion

Derivative 2.1: Genotype-Guided Dosing for CYP2C8/CYP3A4 Polymorphisms

• Enabling Description: The metabolism of enzalutamide is mediated by both CYP3A4 and CYP2C8. Genetic polymorphisms in these enzymes affect a patient's metabolic capacity. This disclosure describes a method wherein patients are genotyped for CYP2C8 (e.g., for the *3 allele, a poor metabolizer) and/or CYP3A4 (e.g., for the *22 allele) prior to treatment. When a strong CYP3A4 inducer like rifampin is co-administered, the enzalutamide dose is adjusted based on this genetic profile. For a normal metabolizer, the dose is increased to 240 mg as per the base invention. For a CYP2C8 poor metabolizer, whose clearance of enzalutamide is already reduced, the dose increase is attenuated to 200 mg/day to avoid excessive exposure and toxicity. Conversely, an ultra-rapid metabolizer might require a dose of 280-320 mg/day.

flowchart TD
    subgraph Pre-Treatment
        A[Patient requiring Enzalutamide + Rifampin] --> B(Genotype for CYP2C8 & CYP3A4);
    end
    subgraph Dosing Algorithm
        B --> C{Metabolizer Status};
        C -- CYP2C8 Poor Metabolizer --> D[Adjust Enzalutamide Dose to 200mg/day];
        C -- Normal Metabolizer --> E[Adjust Enzalutamide Dose to 240mg/day];
        C -- Ultra-Rapid Metabolizer --> F[Adjust Enzalutamide Dose to 280mg/day];
    end
    subgraph Monitoring
        D --> G(Monitor for Toxicity);
        E --> H(Monitor for Efficacy & Safety);
        F --> I(Monitor for Efficacy);
    end

Derivative 2.2: Dosing Based on Therapeutic Drug Monitoring (TDM)

• Enabling Description: Rather than a fixed 240 mg dose, this method employs a TDM-based approach. After a patient on enzalutamide starts rifampin, the enzalutamide dose is initially increased to 200 mg/day. A trough plasma concentration (Cmin) of enzalutamide and its active metabolite (N-desmethyl enzalutamide) is measured after 7-14 days. The dose is then titrated to achieve a target Cmin range known to be associated with clinical efficacy (e.g., 8-15 µg/mL for the combined active moiety). The dose may be adjusted up to 320 mg/day or down to 180 mg/day based on the TDM results and individual patient tolerance, creating a personalized, exposure-matched therapy.

stateDiagram-v2
    [*] --> InitialDose: Patient starts Rifampin
    InitialDose: Enzalutamide set to 200mg/day
    InitialDose --> MeasureTrough: After 7-14 days

    MeasureTrough --> EvaluateTrough
    state EvaluateTrough {
        [*] --> Cmin_Low: Trough < 8 µg/mL
        Cmin_Low --> IncreaseDose: Increase dose to 240mg
        [*] --> Cmin_Target: Trough 8-15 µg/mL
        Cmin_Target --> MaintainDose: Continue current dose
        [*] --> Cmin_High: Trough > 15 µg/mL
        Cmin_High --> DecreaseDose: Decrease dose to 180mg
    }

    IncreaseDose --> MeasureTrough
    MaintainDose --> Stable: Monitor monthly
    DecreaseDose --> MeasureTrough
    Stable --> [*]

---

Axis 3: Cross-Domain Application

Derivative 3.1: Application in HIV Management

• Enabling Description: Patients with HIV are often treated with protease inhibitors (e.g., darunavir, atazanavir), which are potent CYP3A4 substrates. If such a patient contracts tuberculosis (TB), they require treatment with rifampin, a cornerstone of anti-TB therapy. Co-administration of rifampin drastically reduces protease inhibitor concentrations, leading to virologic failure. This disclosure applies the dose-escalation principle: the daily dose of the protease inhibitor is increased by 50-100% (e.g., darunavir/cobicistat dose is modified or boosted differently) to counteract the induction by rifampin. The specific adjustment is guided by TDM to maintain effective antiretroviral activity while monitoring for liver toxicity.

graph TD
    A[Patient with HIV on Protease Inhibitor (CYP3A4 Substrate)] --> B{Diagnosed with Tuberculosis};
    B --> C[Initiate Rifampin-based TB Therapy];
    C --> D{Drug-Drug Interaction: Reduced PI Exposure};
    D --> E[Risk of HIV Virologic Failure];
    E --> F[Action: Increase Protease Inhibitor Dose by 50-100%];
    F --> G[Implement Therapeutic Drug Monitoring (TDM)];
    G --> H[Maintain HIV Suppression & Treat TB];

Derivative 3.2: Application in Organ Transplantation

• Enabling Description: Organ transplant recipients rely on lifelong immunosuppression with calcineurin inhibitors like tacrolimus or cyclosporine. These drugs are narrow therapeutic index CYP3A4 substrates. If a transplant patient develops a seizure disorder requiring treatment with a strong inducer like carbamazepine or phenytoin, their immunosuppressant levels can fall precipitously, risking acute organ rejection. This method describes increasing the daily tacrolimus dose by 200-300% upon initiation of the enzyme-inducing anti-epileptic. Dosing is aggressively managed using frequent trough level monitoring to keep the immunosuppressant within its target therapeutic range.

sequenceDiagram
    participant P as Transplant Patient
    participant T as Tacrolimus (CYP3A4 Substrate)
    participant C as Carbamazepine (CYP3A4 Inducer)
    participant O as Transplanted Organ

    P->>T: Takes stable daily dose
    T->>O: Maintains immunosuppression (No Rejection)
    P->>C: Starts Carbamazepine for seizures
    C-->>T: Induces rapid metabolism of Tacrolimus
    T-->>O: Levels drop, risk of Acute Rejection
    P->>T: Administer 3x increased daily dose
    T->>O: Therapeutic levels restored, immunosuppression maintained

Derivative 3.3: Application in Oncology with Targeted Therapies

• Enabling Description: Many oral targeted cancer therapies, such as tyrosine kinase inhibitors (TKIs) (e.g., erlotinib, pazopanib), are CYP3A4 substrates. If a patient with lung cancer on erlotinib develops an infection requiring treatment with rifampin, erlotinib exposure can decrease by over 60%, leading to loss of anti-tumor effect. This method involves increasing the erlotinib dose from 150 mg/day to 300 mg/day or higher when co-administered with rifampin, with careful monitoring for side effects like rash and diarrhea, to maintain the necessary plasma concentration for tumor control.

flowchart LR
    A[Cancer Patient on TKI (e.g. Erlotinib 150mg)] --> B(Concurrent Infection);
    B --> C{Requires Rifampin};
    C --> D(CYP3A4 Induction);
    D --> E(Sub-therapeutic TKI Levels);
    E --> F(Risk of Tumor Progression);
    F --> G(Intervention: Increase TKI Dose to 300mg);
    G --> H(Monitor for Efficacy & Toxicity);

---

Axis 4: Integration with Emerging Tech

Derivative 4.1: AI-Driven Personalized Dosing Platform

• Enabling Description: A machine learning model is developed, trained on real-world data (RWD) encompassing patient genomics (CYP2C8/3A4 status), co-medications, liver function tests, body weight, and reported outcomes. When a patient is prescribed enzalutamide and rifampin, the platform integrates their specific data to predict an optimal starting dose (e.g., 220 mg, 240 mg, or 260 mg). The system then uses real-time data from an IoT wearable (monitoring activity levels, sleep patterns for signs of fatigue) and patient-reported outcomes via a mobile app to suggest dose adjustments, creating a dynamic, closed-loop therapeutic system.

classDiagram
    class Patient {
        +genomicData
        +coMedications
        +labValues
        +wearableData
        +reportedOutcomes
    }
    class AI_DosingEngine {
        -ML_Model
        +predictOptimalDose()
        +suggestDoseAdjustment()
    }
    class IoTSensor {
        +activityLevel
        +sleepData
        +streamData()
    }
    class ClinicianDashboard {
        +viewPredictions()
        +approveAdjustments()
    }
    Patient "1" -- "1" AI_DosingEngine : provides data
    Patient "1" -- "1" IoTSensor : wears
    IoTSensor --|> AI_DosingEngine : streams data
    AI_DosingEngine --|> ClinicianDashboard : displays recommendations

Derivative 4.2: Blockchain for Treatment Adherence and Verification

• Enabling Description: A private blockchain ledger is used to track the prescription and administration of high-cost, high-interaction drug combinations like enzalutamide and rifampin. When a clinician prescribes the adjusted 240 mg dose, the order is recorded as an immutable transaction on the blockchain. The specialty pharmacy dispensing the drug records the fulfillment. The patient's smart pill bottle (an IoT device) records each time the dose is taken. This creates an auditable trail for payers to verify adherence for value-based care contracts and for researchers to collect high-fidelity RWD for pharmacovigilance.

flowchart TD
    A[Clinician Prescribes 240mg Enzalutamide] --> B(Create Transaction on Blockchain);
    B --> C[Pharmacy Dispenses & Updates Ledger];
    C --> D[Patient Takes Dose from IoT Pill Bottle];
    D --> E(Pill Bottle Writes to Ledger);
    E --> F{Data is Immutable & Auditable};
    F --> G[Payers for Value-Based Reimbursement];
    F --> H[Researchers for Pharmacovigilance];

---

Axis 5: The "Inverse" or Failure Mode

Derivative 5.1: Toxicity-Based De-Escalation Protocol

• Enabling Description: This method describes a protocol for managing adverse events in patients on the 240 mg adjusted dose of enzalutamide with rifampin. If a patient develops a pre-defined toxicity, such as Grade 3 fatigue, severe hypertension, or a seizure, the enzalutamide dose is immediately reduced to the standard 160 mg/day. TDM is performed to ensure the level does not fall below a minimal therapeutic threshold. If the toxicity resolves to Grade 1 or less within 14 days, the dose can be re-escalated to 200 mg/day. This protocol prioritizes patient safety over maintaining maximum theoretical exposure in the event of severe side effects.

stateDiagram-v2
    OnTreatment: At 240mg Dose
    [*] --> OnTreatment

    OnTreatment --> ToxicityEvent: Grade >= 3 Adverse Event
    ToxicityEvent --> DoseReduction: Reduce Dose to 160mg
    DoseReduction --> Monitoring: Monitor for 14 days
    Monitoring --> Resolved: Toxicity <= Grade 1
    Monitoring --> Persistent: Toxicity > Grade 1
    Resolved --> ReEscalate: Increase Dose to 200mg
    Persistent --> StopTherapy: Discontinue Enzalutamide
    ReEscalate --> OnTreatment

Derivative 5.2: Use in Neoadjuvant (Pre-Surgery) Setting with Intermittent Dosing

• Enabling Description: For patients with high-risk localized prostate cancer, a neoadjuvant (pre-prostatectomy) regimen is described. The patient receives enzalutamide at the adjusted 240 mg dose while on rifampin (for a concurrent condition) for a fixed period of 3-6 months. The goal is to shrink the tumor and reduce micrometastatic disease before surgery. The therapy is intermittent and not for chronic treatment of metastatic disease. This application represents a "limited-functionality" mode, as the goal is short-term tumor response rather than long-term disease suppression. This method reduces the total duration of drug exposure and potential for long-term side effects.

graph TD
    A[High-Risk Localized Prostate Cancer] --> B(Concurrent Condition Requiring Rifampin);
    B --> C[Initiate Neoadjuvant Therapy];
    C --> D[3-6 month course of Enzalutamide 240mg/day];
    D --> E[Goal: Tumor Volume Reduction];
    E --> F[Definitive Surgery (Prostatectomy)];
    F --> G[End of Combination Therapy];

---

Combination Prior Art with Open-Source Standards

1. Combination with OMOP Common Data Model: The dosing algorithm described in Derivative 2.1 (Genotype-Guided Dosing) is implemented within a Real-World Evidence (RWE) study. Patient data from electronic health records (EHRs) are ETL'd into the Observational Medical Outcomes Partnership (OMOP) Common Data Model. A cohort of patients on enzalutamide and strong CYP3A4 inducers is identified. The outcomes (PSA response, adverse events) for patients dosed according to a genotype-guided algorithm versus a standard fixed-dose adjustment are compared, demonstrating the clinical utility of the disclosed method within a standardized, open-source data framework for observational research.

2. Combination with FHIR (Fast Healthcare Interoperability Resources): The AI-driven dosing platform from Derivative 4.1 is integrated into a clinician's EHR workflow using FHIR APIs. The AI engine is encapsulated as a Clinical Decision Support (CDS) Hook. When a physician prescribes enzalutamide for a patient already on rifampin, the EHR triggers the CDS Hook. The hook service reads relevant patient data (labs, meds) via FHIR resources (e.g., Patient, MedicationRequest, Observation) and returns a "card" to the EHR interface recommending the specific 240 mg dose, along with links to the supporting evidence. This demonstrates the invention's implementation using open, interoperable health data standards.

3. Combination with CDISC (Clinical Data Interchange Standards Consortium): A clinical trial protocol is designed to validate the TDM approach from Derivative 2.2. The protocol specifies that all pharmacokinetic and clinical outcome data must be collected and structured according to CDISC standards, specifically the Study Data Tabulation Model (SDTM) for raw data and the Analysis Data Model (ADaM) for analysis datasets. This ensures the data are ready for regulatory submission (e.g., to the FDA) and can be easily aggregated with other trial data for meta-analyses, demonstrating the invention's application within the open standards governing clinical research.