Published on 17/12/2025
ACTD Strategy for Device–Drug Combos: Where to Place Content, What to Prove, and How to Localize
What Counts as a Device–Drug Combination—and Why ACTD Placement Matters More Than You Think
A device–drug combination is any product in which a medical device and a medicinal product are physically or functionally integrated to achieve the intended clinical effect—think prefilled syringes (PFS), autoinjectors/pen injectors, on-body delivery systems, drug-eluting stents, medicated plasters/patches, inhalers with dose counters, and ophthalmic droppers with valve systems. Scientifically, your CTD core already contains the right building blocks—drug substance/product quality (Module 3), study reports (Modules 4–5), and Module 2 summaries. The challenge in ACTD markets is not reinventing science but placing device-led evidence and keeping traceability intact once language, packaging, and national templates enter the picture. If reviewers cannot verify a claim (dose accuracy, leachables control, or usability) in one to two clicks, expect a query—even when your data are sound.
Start with a lead component mindset. In most US/EU programs the combination is “drug-led” (primary mode of action is pharmacological), so the dossier skeleton follows CTD logic. Device evidence—design controls, risk management per ISO 14971, biocompatibility per ISO 10993, sterilization/aseptic validation,
Decide early how you’ll present system safety and performance across three threads: (1) the delivery system (materials, manufacturing, sterilization, packaging, shelf life, robustness), (2) the drug product (potency, purity, stability, particulate control), and (3) the interface (dose accuracy under use conditions, extractables/leachables, container-closure integrity, device-drug compatibility). Then map each claim to a precise anchor (figure/table ID) in the CTD core and mirror that map in ACTD leaves. When placement is done well, assessors can follow the dose-delivery story without guessing whether a number came from a bench study, a validation protocol, or a clinical HF report.
Mapping CTD → ACTD: Exactly Where to Put Device Evidence, and How to Keep Click-Through Traceability
Think of ACTD as “same dossier, different wrapper.” Use a simple mapping grid that links each ACTD quality heading to a CTD leaf and names the device evidence bundle it consumes. Effective patterns include:
- Drug–container interface (Module 3.2.P): primary container description, container-closure integrity (CCI) methods and sensitivity (e.g., helium leak LOD), extractables/leachables strategy and thresholds (toxicological assessment), lubricant/stopper/needle shields, silicone levels for PFS, and dose accuracy verification for metered pumps/inhalers.
- Manufacturing & controls (3.2.P.3): device assembly steps, in-process controls (e.g., plunger force, crimp dimensions), vision/functional testing, sterilization modality and validation linkage (EO per ISO 11135, gamma per ISO 11137, moist heat), and environmental/cleanliness classification where drug exposure exists.
- Validation (3.2.P.3.5): equipment/process validation relevant to device assembly, packaging validation (ISO 11607 seal strength, dye/microbial ingress), transport simulation (ISTA/ASTM) tied to dose delivery and CCI after distribution stresses.
- Stability (3.2.P.8): zone-appropriate (IVa/IVb) stability with dose delivery through shelf life (spray pattern/APS for OINDP, delivered dose for injectors), in-use stability where the device allows multiple actuations or openings.
Place human factors/usability summaries (formative/validation) where ACTD accepts clinical or “other studies,” and cross-link them from Module 2.5 with caption-level anchors to the HF report figures/tables (task analyses, critical use errors, residual risk tables). Keep a Navigation Charter: H2/H3 bookmarks plus named destinations on captions for every test table/figure referenced by Module 2 claims. The small craft details—embedded fonts, searchability, ASCII-safe filenames, stable leaf titles—are what make ACTD feel like eCTD to a reviewer even without an XML backbone.
Finally, reserve a compact Device Annex in Module 1 for country specifics (local UDI/2D codes, language-dependent IFUs, national form fields). The annex points back to unchanged science; it shouldn’t duplicate validation or stability data. When you must include a localized IFU, put a one-line evidence hook beneath critical warnings or dose instructions (“HF-VAL-03 Table 6; Misload mitigation validated in elderly cohort”). That hook saves days of ping-pong when reviewers verify that the translated instruction aligns with your validated use scenario.
The Evidence Stack You’ll Need: Biocompatibility, Sterilization, Packaging/Transport, Extractables/Leachables, and Performance
Combination products live or die on five evidence pillars. First, biocompatibility per ISO 10993 series tailored to contact type/duration (e.g., ISO 10993-1/-5/-10/-11 for cytotoxicity, sensitization, irritation, systemic tox; 10993-7 for EO residuals; 10993-18 for chemical characterization). Map test selection via a risk-based biocomp matrix and tie conclusions to patient contact and drug compatibility (e.g., silicone oil droplets, tungsten residues). Second, sterilization and microbial control: declare the modality, SAL target, cycle development (half-cycles, BI placement), EO residuals with aeration validation, or radiation dose mapping. If aseptic assembly is used, present media fills, intervention risk analysis, and environmental monitoring trending where drug exposure occurs.
Third, packaging & distribution: use ISO 11607 to validate seals and package integrity, then add distribution simulation (drop/vibration, thermal cycling) linked to dose delivery and CCI post-ship. For PFS/autoinjectors, include plunger movement after cold chain, break-loose/glide force, and spring performance at temperature extremes; for inhalers, connect valve performance, dose counters, and APS to transport stresses. Fourth, extractables and leachables (E&L): design studies based on worst-case solvent/temperature/time, simulate real contact conditions, and present toxicological thresholds (e.g., AETs, TTC) with identification/qualification summaries. Align leachables monitoring with stability; reviewers look for congruence between the E&L plan and long-term data.
Fifth, performance and dose accuracy: show delivered dose uniformity, priming/repriming behavior, misuse resilience (off-axis actuation, shallow injection), and end-of-content accuracy. For autoinjectors, include needle extension and dwell time controls; for topical patches, adhesive wear and drug residue after removal; for on-body pumps, occlusion alarms and flow rate accuracy across back-pressure scenarios. Every claim in Module 2 should cite a caption-level anchor in these test reports. Where platform devices serve multiple SKUs, present matrixed testing that shows representativeness across strengths/viscosity ranges. This organized stack—biocomp, sterilization, packaging/transport, E&L, performance—is the universal language assessors understand across ACTD authorities, regardless of how a national checklist is worded.
Human Factors & Usability: From Task Analysis to Validation—And Where It Lives in an ACTD Dossier
Usability is often the fastest path to either a clean review or a long delay. Build HF evidence along three stages. Context of use & task analysis: define users (patients, caregivers, HCPs), environments, and critical tasks (dose dialing, needle shield removal, injection trigger, patch placement, priming). Map potential use errors to severity and probability, then design mitigations (mechanical interlocks, feedback clicks, clear windows). Formative studies: iterate design and IFU with representative users, collecting error patterns and comprehension issues; document design changes and residual risks. Validation studies: under simulated clinical conditions with final design/IFU, show that intended users can perform critical tasks successfully without prior training beyond the IFU—cover age, dexterity/vision limitations, and language literacy where relevant.
In ACTD, locate HF validation where the authority expects “clinical” or “other studies,” then cross-anchor it from Module 2.5. Place IFU excerpts in Module 1 country annexes with language localization, but keep the HF report in the science stack so reviewers can verify IFU statements against validated user behavior. Tie residual risks to design controls and to labeling mitigations; if a critical task persists with non-zero risk, cite the exact IFU step that addresses it and the validation figure showing comprehension. For combination inhalers and complex injectors, include training-effect analyses and first-time use success rates; some ACTD authorities weigh naïve-user performance heavily when deciding if additional risk communications are needed.
Pay attention to elderly and pediatric subgroups, frequent in diabetes and asthma platforms: grip strength, thumb reach, or inspiratory flow capability may threaten dose delivery. If your US/EU program includes human factors work aligned to contemporary practice, you rarely need new ACTD-specific studies; you need bridges that clarify user populations, languages, and environments, and that place the proof so it is instantly visible. As ever, use harmonized language from ICH in Module 2, and keep FDA/EMA HF guidance at hand as interpretive anchors when a national checklist is silent on method details.
Labeling, IFU Localization, UDI/Barcodes, and Country Annexes Without Changing the Science
Combination product labeling blends medicinal content with device instructions. In ACTD markets, IFUs, leaflets, and artwork usually live in Module 1 and are often bilingual. Engineer a copy deck that ties every instruction and warning to an evidence hook (HF figure/table ID, performance test, or stability/CCI data). Enforce terminology parity (e.g., “click,” “twist,” “press and hold,” “priming”) across languages with a bilingual glossary; small wording drift can re-introduce use errors you eliminated during validation. Align UDI/2D barcodes and human-readable text; verify scan quality at proof stage; and ensure the encoded data do not contradict strength/lot/expiry strings shown on cartons or pens.
Use country annexes for purely administrative differences: national application forms, local MAH/agent details, language templates, and specific artwork panel orders. Keep science invariant across countries: dose accuracy, CCI, sterilization, and E&L data remain in Quality and HF reports. If a national template requires additional pictograms or layout changes, confirm they do not obscure critical steps; attach a quick “HF impact note” if the visual flow changes (e.g., relocating a warning box). Where cold chain or protection from light is critical, make the same storage statement appear on cartons, IFU, and leaflets and point to Module 3 stability/packaging anchors. For inhalers, synchronize dose counter descriptions and end-of-life indicators with performance test data; mismatches here are a common, preventable query.
Finally, separate global copy control from local formatting. Maintain a single, versioned English copy deck and glossary; local teams propose phrasing bridges to fit templates, but cannot change numbers, sequence of critical steps, or validated terms. This hub-and-spoke model keeps labeling consistent across ASEAN markets and simplifies post-approval updates when you revise an HF mitigation or a storage instruction downstream.
Sterile and Parenteral Combos: Aseptic Interfaces, CCI, Cold Chain, and Shelf-Life in Hot/Humid Zones
Sterile combination products—PFS, cartridges for pens, on-body pumps with prefilled reservoirs—face an extra layer of scrutiny in ACTD markets. Present a tight chain from aseptic/sterilization validation to CCI to stability through shelf life. If final assembly is aseptic, include media fill studies that reflect true interventions (device assembly steps, stopper placement, needle shield application), and show environmental monitoring trends at the interfaces where drug meets device. If terminal sterilization is used, tie cycle development to material compatibility (e.g., radiation effects on polymer embrittlement, EO residues on elastomers) with post-sterilization performance tests (plunger forces, valve function).
For ACTD’s climatic expectations, design zone IVa/IVb stability with dose delivery and CCI over time. Include shipping simulation that incorporates temperature cycling reflective of regional logistics and test post-ship dose accuracy and CCI immediately and over time. For cold-chain products, define excursion studies and reconcile them with labeling (“remove from refrigerator 30 minutes before use; do not freeze”) using clear anchors to stability and device performance plots. Where proteins are involved, link silicone control (for PFS) and agitation sensitivity to device motions (spring snap, priming) and present visible/ subvisible particulate data appropriate to USP/Ph. Eur. chapters.
In Module 3, make CCI methods explicit (e.g., helium leak with acceptance at X sccm, vacuum decay sensitivity) and discuss microbial ingress correlation if you rely on deterministic tests. For on-body systems, add occlusion detection and alarm reliability tests and user-removal scenarios validated in HF. Because many ACTD queries stem from the interface of transport-temperature-mechanical stress, ensure your evidence tells a continuous story: pack integrity → dose delivery → label statements. When that chain is visible and caption-anchored, sterile combination reviews move quickly even with country-specific annexes layered on top.
Lifecycle & Change Control: Platform Devices, Software/Firmware Updates, and Post-Approval Variations Across ACTD
Combination platforms multiply change vectors—drug concentration changes, viscosity shifts, spring force adjustments, firmware updates, label/IFU edits. Build a governance model that classifies changes by impact on dose accuracy, safety, and usability, then aligns them to US supplement types and analogous ACTD variation buckets. Where you’ve adopted ICH Q12 thinking, declare Established Conditions for dose-delivery-critical parameters (e.g., plunger forces, needle extension, counter accuracy) versus controls that remain within PQS. For device software/firmware, keep a software change log and verification/validation (V&V) summaries; if an update touches user interface cues (LEDs, beeps, error codes), run HF re-verification and update the copy deck/IFU bridges.
Operationally, simulate eCTD lifecycle in ACTD with a leaf-title catalog (stable names for replacement) and a one-page What Changed note per sequence listing the affected leaves, exact paragraphs/figures adjusted, and hashes of old vs new files. For platform devices serving multiple SKUs or regions, maintain a matrix that shows which combination of drug strength/viscosity and device variant has which data; reviewers appreciate seeing coverage at a glance. When a change affects only local annexes (e.g., artwork re-layout, language tweak), create a micro-correction protocol to avoid unnecessary re-legalization of the full Module 1 pack.
Finally, keep post-market surveillance aligned across geographies. Feed complaint trends, device malfunction investigations, and field safety corrective actions into your variation strategy and HF risk file. If a pattern emerges (e.g., miscap, partial dose), show the closed-loop fix: design tweak → V&V → HF check → labeling update → stability/performance reconfirmation where relevant. This lifecycle discipline lets you file confident, risk-proportional variations in ACTD markets without fracturing the core science that underpins your US/EU approvals.