Why device functionality matters in combination product stability:

Drug-device combination products—such as prefilled syringes, inhalers, autoinjectors, and nasal sprays—must not only maintain chemical stability but also deliver accurate, reproducible doses throughout their lifecycle. Functional components like actuators, plungers, and valves may degrade, stiffen, or fail under long-term storage. Without integrated device performance checks within the stability protocol, a product may chemically remain stable but mechanically become unusable or unsafe.

Risks of excluding device checks from stability testing:

If device function is not monitored:

• Delivery failures (e.g., dose misfire, blockage) may go undetected
• User interface components may degrade and impair usability
• Regulatory agencies may challenge product reliability
• Post-market complaints and recalls may increase

Functional stability is as important as chemical stability for patient-centric combination products.

Regulatory and Technical Context:

Guidance from ICH, WHO, and FDA on combination product performance:

ICH Q1A(R2) and WHO TRS 1010 require that all properties affecting product quality and performance be evaluated throughout shelf life. The FDA’s Combination Product Quality Guidance further mandates that both constituent parts—drug and device—must retain functionality. CTD Module 3.2.P.8.3 and 3.2.R should include device functionality data to support approval.

What auditors and reviewers may request:

Inspectors often ask for:

• Device function test protocols and results at each stability time point
• Actuation force, spray pattern, dose accuracy, or priming studies
• Evidence of interaction between drug formulation and device material (e.g., plunger glide, silicone migration)

Absence of these data may lead to conditional approvals or post-approval testing obligations.

Best Practices and Implementation:

Design an integrated drug-device stability protocol:

Include:

• Chemical testing (e.g., assay, impurity, pH)
• Physical inspection (e.g., appearance, leakage)
• Device testing (e.g., dose delivery, actuator functionality, user interface integrity)

Test entire drug-device units—not just drug content—under ICH stability conditions (long-term, intermediate, accelerated).

Use validated functional test methods tailored to the device type:

Define device-specific metrics such as:

• Spray angle and plume geometry for nasal/oral sprays
• Injection force and glide testing for autoinjectors
• Dose reproducibility and priming effort for inhalers

Conduct tests at relevant stability intervals (e.g., 0M, 3M, 6M, 9M, 12M) and under stress conditions if required.

Document device performance trends and correlate with product usability:

Summarize:

• Functional pass/fail rates across time points
• Correlation between device drift and environmental exposure (e.g., cold chain, humidity)
• Any user feedback simulations from human factors testing

Reference all findings in CTD and maintain device-lot traceability throughout the study.

Aligning drug-device combination stability protocols with periodic device functionality testing ensures that the product is not only chemically intact but also mechanically reliable—delivering the right dose, in the right way, every time until expiry.

Why separate API testing is essential in combination products:

Combination products contain two or more active pharmaceutical ingredients (APIs) within a single dosage form. Each API may have a distinct chemical profile, degradation behavior, and interaction risk. Evaluating their stability individually—alongside the combined formulation—is crucial for identifying which component may degrade first or drive incompatibility issues.

This helps protect product efficacy, informs shelf-life assignments, and meets regulatory expectations for component-level quality control.

Consequences of lump-sum stability testing:

Testing only the final product without resolving the contribution of each API can mask early degradation signals, skew impurity trends, and complicate root cause analysis during OOS investigations. This can delay regulatory approval or lead to unanticipated product recalls if one API proves unstable during real-world conditions.

Applicability to various dosage forms:

This principle applies to fixed-dose combinations (FDCs), co-packaged regimens, dual-layer tablets, and multi-chamber devices. Whether APIs are co-formulated or compartmentalized, each requires its own stability profile and impurity threshold analysis.

Regulatory and Technical Context:

ICH guidance and combination product expectations:

ICH Q1A(R2) requires stability studies to detect any changes in a drug product’s quality over time. In the case of combination products, this extends to each active moiety. Assay methods must be specific, stability-indicating, and able to quantify each API and its respective degradation products independently.

ICH M4Q and WHO TRS guidance also require individual API profiles to support CTD submissions, especially when component APIs come from separate manufacturing sources.

CTD documentation and audit visibility:

Module 3.2.P.8.3 must present time-point data and trend summaries for each API within the combination. Missing or combined-only data may trigger questions on assay specificity or stability interpretation during dossier reviews or GMP inspections.

Analytical validation reports must confirm that each assay can accurately differentiate APIs and their degradation products under forced and real-time conditions.

Drug-drug and drug-excipient interactions:

Component-specific testing also helps reveal interactions that may not be evident in single-agent products—e.g., pH shift from one API degrading the other, moisture uptake by one drug affecting the second, or cross-reactivity due to excipient-induced stress.

Best Practices and Implementation:

Develop and validate API-specific assay methods:

Each API in the combination product should have a validated, stability-indicating assay method capable of detecting degradation independently of the other components. Use high-resolution chromatographic techniques such as HPLC or UPLC with peak resolution criteria (Rs > 2).

Validate methods for specificity, linearity, accuracy, precision, and robustness under both standalone and combined stress testing scenarios.

Design parallel stability studies:

Run real-time and accelerated stability studies for: (1) the full combination product, (2) individual APIs in placebo matrix, and (3) each API in isolation. This approach provides a holistic picture of which ingredient contributes to degradation and how formulation context affects stability.

Ensure sample pulls align with ICH intervals and that test parameters cover assay, impurities, dissolution, and appearance per component.

Document findings for shelf life and labeling strategy:

Use component-level data to determine whether the shelf life should be based on the most sensitive API or whether mitigation strategies (e.g., packaging upgrades, reformulation) can harmonize degradation profiles. Include justification in Module 3.2.P.8.1 and 3.2.P.8.3 for regulatory transparency.

Apply findings to labeling such as storage conditions, in-use timelines, and usage sequence (e.g., “Use within 14 days of mixing components.”)