What does it take to develop and manufacture a Combination Product / Device drug?
A combination product lives in two regulatory worlds at once. You have a drug or biologic that has to behave like a drug (stability, potency, sterility, the full CMC package), and you have a device that has to behave like a device (design controls, mechanical reliability, biocompatibility, usability). An autoinjector, a prefilled syringe, a dry-powder inhaler, an on-body injector, a transdermal patch, a drug-eluting stent: each pairs a molecule with a delivery system, and the FDA assigns a primary mode of action (PMOA) that decides which center leads the review and which framework dominates. Getting the PMOA call right early shapes everything downstream, because it determines whether you are running a drug program with device elements bolted on or a device program with a drug inside.
The work that trips up first-time combination-product sponsors is rarely the molecule. It is the integration. The drug and the device interact, and you have to prove they play well together. Extractables and leachables from the device materials can contaminate the drug; the drug formulation can degrade an elastomer seal or corrode a needle; the device has to deliver the right dose, every time, across the product's shelf life and across the temperatures it will see in a patient's bag. That means container-closure integrity work, material compatibility studies, functional and dose-accuracy testing on the assembled product, and stability run on the finished combination, not just the drug substance. None of it is optional, and most of it cannot start until the device design is reasonably locked.
Two regulatory pillars sit underneath all of it. Design controls under 21 CFR 820.30 (and the ISO 13485 quality system the device side runs on) require a documented chain from user needs to design inputs, outputs, verification, validation, and a design history file. Human factors and usability engineering, covered by IEC 62366 and the FDA's human-factors guidance, requires that you study real users handling the device and run a validation study showing they can use it safely without critical use errors. A self-injecting patient who misreads the device is a safety signal, and the agency will ask for the data. 21 CFR Part 4 is the rule that ties the drug GMP and the device quality system together into one coherent set of obligations.
This is exactly where specialist combination-product CDMOs separate from generalists. A pure fill-finish CDMO can fill your prefilled syringe; it usually cannot run device design controls, build a usability lab, or own the design history file. A pure contract device manufacturer can mold and assemble an autoinjector; it often does not hold the drug GMP, sterility assurance, or CMC depth your molecule needs. The strongest partners do both under one roof, or you assemble a device-development house, a drug fill-finish site, and a human-factors CRO and make them work to one integrated plan. Whichever route you pick, someone has to own the seams between them, because the FDA reviews the product as one thing.
How do you choose a CRO or CDMO for Combination Product / Device?
The selection problem here is harder than for a single-modality program, because you are scoring two competencies and the bridge between them. A vendor that is brilliant at injectable fill-finish but treats the device as an afterthought will leave you holding the design controls and human-factors risk. A vendor that is a strong device shop but light on aseptic processing puts your sterility assurance at risk. Score candidates against the same written scope, and weight the integration capability heavily, not just the headline manufacturing rate.
Work through the checklist below before you sign anything.
- Relevant platform and track record: ask for finished combination products in your delivery format (autoinjector, prefilled syringe, pen, inhaler, on-body injector, transdermal, drug-eluting device) and your route, not generic device or generic fill-finish experience. A team that has shipped your exact format has already solved problems you have not seen yet.
- Drug-device integration depth: confirm they can run material compatibility, extractables and leachables, container-closure integrity, dose-accuracy and functional testing on the assembled product, and stability on the finished combination, not only on the drug substance. This is the work that fails late and expensively if it is skipped early.
- Design controls and quality systems: verify a working design controls process under 21 CFR 820.30, an ISO 13485 quality system on the device side, and the drug GMP on the pharma side, governed together under 21 CFR Part 4. Ask who owns the design history file and where it lives.
- Human factors and usability capability: check for in-house or partnered human-factors engineering, formative studies, and the ability to run a validation usability study to IEC 62366 and FDA human-factors guidance. For a self-administered product this is a gating deliverable, not a nice-to-have.
- Analytical and GxP capability for this modality: confirm the analytical methods for your finished product, biocompatibility testing per ISO 10993, sterility assurance and aseptic fill where relevant, and GLP-grade work where the submission needs it.
- Capacity and scale: match clinical-supply capability to commercial intent. A vendor that can build a few hundred devices for a Phase 1 study may not have the automated assembly and fill capacity to support launch. Ask about scale-up path, second-source strategy for critical device components, and lead times on tooling.
- Regulatory experience: prefer teams that have actually supported a combination-product submission, can speak to PMOA and the request-for-designation process, and understand which center (CDER, CBER, or CDRH) is likely to lead. A clean FDA inspection history on both the drug and device sides matters more than the lowest bid.
- IP and ownership: settle device design IP, tooling ownership, and the design history file in writing before work starts. With a platform device (a vendor's proprietary autoinjector, for instance) be precise about what you license versus what you own, and how you exit if you change partners.