Why API-specific testing is crucial in FDC stability programs:

Fixed-dose combinations (FDCs) involve two or more active pharmaceutical ingredients (APIs) formulated together into a single dosage unit. While convenient for patient compliance, these formulations introduce complexities in stability testing. Each API may degrade differently, exhibit varying sensitivities to temperature or moisture, and potentially interact with other components in the formulation. Testing individual API stability ensures that degradation pathways are understood and controlled throughout the shelf life.

Risks of evaluating only the total formulation:

If stability tests only measure total potency or do not track each API independently:

• Early degradation of a single API may go undetected
• Degradation products may be misattributed or missed
• Incorrect shelf-life assignments may occur
• Regulatory questions may arise during filing or audits

This risk is heightened in FDCs where APIs differ in chemical class, stability profile, or pharmacopoeial status.

Regulatory and Technical Context:

ICH and WHO guidance on FDC stability requirements:

ICH Q1A(R2) and WHO TRS 1010 emphasize that each API in an FDC must retain its stability over the claimed shelf life. WHO guidelines for multisource products (Annex 10) clearly state that each active should be individually tested using validated, stability-indicating methods. The CTD Module 3.2.P.8.3 must include time-point assay data for each API along with impurity profiling and degradation trend analysis.

Expectations during inspections and submissions:

Regulators will expect:

• Separate assay results for each API at every time point
• Individual impurity and degradation tracking
• Data showing no cross-degradation or incompatibility

Missing or pooled data may lead to queries, data rejection, or delayed approvals—especially in global markets like the EU, US, or WHO PQ program.

Best Practices and Implementation:

Develop and validate API-specific analytical methods:

Use HPLC or UPLC methods capable of resolving each API and its impurities. Ensure:

• Method validation for linearity, specificity, and accuracy per ICH Q2(R2)
• Robustness under stress conditions (acid, base, oxidation, light, heat)
• Adequate resolution and tailing factors

Document method validation and include results in Module 3.2.S.4 and P.5.2 of the dossier.

Monitor degradation behavior under all study conditions:

Include each API in:

• Assay and related substances testing at each time point
• Impurity profiling and trending across accelerated and long-term studies
• Photostability and stress studies (as applicable)

Compare degradation rates between APIs to identify any significant imbalance or potential interaction, particularly under high-humidity or thermal stress conditions.

Report individual API stability in regulatory documents:

Include:

• Time-point assay results for each API
• Impurity tables highlighting each compound’s behavior
• Conclusion on compatibility or interaction risk

Address findings in CTD Modules 3.2.P.5.5 (Characterization) and 3.2.P.8.3 (Stability), and ensure that shelf life is assigned based on the most sensitive API’s stability data.

Evaluating individual API stability in FDCs ensures clarity, confidence, and compliance—allowing your formulation to meet therapeutic expectations and global regulatory benchmarks throughout its lifecycle.