Combination Products for Device Buyers: Device Constituent, Co-Packaged and Cross-Labeled in Plain Terms
Published 2026-10-27 · Keywords: combination product device
Almost every autoinjector program is a combination product — drug and device in one therapeutic system — but “combination product” describes three different structures with three different documentation splits. Device buyers who can name which structure applies to their program know exactly which documents to demand from the device supplier, and which workstreams belong to their own regulatory team.
The three structures
| Structure | What it looks like | Device supplier’s documentation role |
|---|---|---|
| Single integral (device constituent) | Drug and device combined into one product — a prefilled autoinjector is the classic case | Device design controls, test reports, material data feeding the sponsor’s submission; the device is reviewed as a constituent of the drug product |
| Co-packaged | Drug and device shipped together in one package but not combined into one unit | Device specification and quality evidence; compatibility with the co-packaged drug |
| Cross-labeled | Separately shipped drug and device, used together per shared labeling | Device evidence supporting the labeled use; little physical integration |
In the United States this sits under FDA’s combination-product framework, with the quality-system side governed by the QMSR (the revised Quality Management System Regulation, effective 2026-02-02); in the EU, MDR (EU 2017/745) governs the device side and EUDAMED registration is mandatory from 2026-05-28. The device buyer’s practical takeaway: whichever structure applies, your device documentation must be complete enough to be handed into a drug submission — that is the standard against which a supplier’s “we support your regulatory process” claim should be tested.
What to demand from the device side, per structure
- Single integral: full design-controls evidence, per-part test reports (ISO 11608 series as applicable), biocompatibility data (ISO 10993-1), and configuration-specific performance results — your named container, not an assumed one.
- Co-packaged: device specification plus compatibility evidence with the packaged drug presentation.
- Cross-labeled: the device’s own evidence plus a clear statement of intended-use boundaries.
In all three, the dividing line is the same: the device supplier produces and stands behind device documentation; the sponsor owns the drug, the submission and the therapeutic claims. A supplier who blurs that line — implying their documents constitute an approval — is misdescribing the structure.
How to verify a supplier’s combination-product fluency
Ask them to state, in writing, which structure applies to your program and which documents they will hand over for it. A fluent answer names the structure correctly, lists device-side documents, and stops at the boundary. An answer that promises “approval support” without naming documents is a sentence from someone who has never fed a submission.
What this does not cover
Submission pathways, agency interactions and clinical evidence are the sponsor’s work and your regulatory advisor’s advice. This article maps the structures to the document split only.
Next step: tell us your program’s structure — we return the device-side document list for it within one working day. Start the inquiry.
Related reading
Talk to NOVIXPEN about your program
Send your container format, annual volume and target market — we reply with the platform match, documentation set and written quotation within one working day.
Start the inquiry