A product that combines a device with a drug, biologic or other regulated constituent part is not simply two products in one package. Its performance and quality can depend on relationships across domains.
A material, coating, adhesive, polymer, container closure, formulation component or manufacturing condition may influence both the device and the constituent product. A change may require engineering assessment, analytical testing, stability/compatibility evidence, supplier review, manufacturing evaluation, risk analysis and quality-system action.
FDA's combination-product CGMP guidance explains the final rule codified in 21 CFR Part 4. The rule addresses current good manufacturing practice requirements and post-market safety reporting for combination products, including products composed of two or more regulated components.
The exact requirements depend on the product and its primary mode of action, constituent parts and markets. The operational challenge is broader: the relevant evidence must be connected enough for teams to assess a product lifecycle decision coherently.
Separate systems are normal. Separate evidence is the problem.
Device teams may work in requirements-management, PLM, CAD, test and QMS systems. Drug or formulation teams may use ELNs, LIMS, analytical systems, batch records, stability systems and quality platforms. Manufacturing and supplier-quality functions add further systems.
There is nothing inherently wrong with this specialist landscape. Each system may be appropriate for its domain.
The issue arises when a user cannot answer cross-domain questions: which product configurations use a given material or coating formulation, which risk controls and verification reports are affected by a change in supplier or process, which analytical, compatibility or stability studies apply to the current configuration, what manufacturing lots, quality events or customer complaints are associated with the affected component, and what was approved previously, and under what conditions.
The Connected Combination-Product Record
The point is not to force a formulation study into a device-design template, or a device verification report into a pharmaceutical batch record. It is to preserve each record's appropriate context while making relevant relationships visible.
.png)
Change control reveals whether the data model works
Consider a proposed change to a material, coating, adhesive or supplier. A complete impact assessment may need to identify the affected device configurations and markets, the design inputs and outputs involving the component, the hazards, risk controls and residual-risk decisions at stake, the verification and validation evidence generated using the current material or process, the relevant supplier, lot, manufacturing and process context, any analytical, compatibility, stability or delivery-performance evidence, related deviations, CAPAs, complaints and post-market signals, and the approval, implementation and post-change monitoring the change requires.
If this information must be assembled from disconnected folders and interviews, the organisation has a change-impact problem. The risk is not simply delay. It is that an important relationship will be missed.
Treat materials as lifecycle objects
For combination products, a material is rarely just a bill-of-materials line. It may carry relationships to the product configuration and design outputs it belongs to, its supplier, site, grade and lot identity, its material specifications and certificates, any biocompatibility, compatibility or extractables/leachables evidence where relevant, drug or product stability and delivery performance, the manufacturing process parameters that shaped it, quality events and supplier changes, and the risk controls and verification results tied to it.
A connected record makes the scope of these relationships visible before a decision is made.
Keep risk management connected to evidence
ISO 14971:2019 describes a systematic risk-management framework for medical devices that includes identifying hazards, estimating and evaluating associated risks, controlling risks and monitoring the effectiveness of controls throughout the device lifecycle.
Risk records should not become isolated matrices. When a material, device configuration, formulation or process changes, teams need to find the risk controls and evidence that may be affected. Likewise, a complaint, nonconformance or new supplier signal may require reassessment of controls and their supporting evidence.
Start with one cross-domain use case
Do not begin by trying to unify every device and formulation system. Choose one workflow that repeatedly crosses the boundary, whether that is material or supplier change control, compatibility or stability evidence management, complaint-to-risk-control investigation, transfer of a combination product to a new manufacturing site, or configuration-specific verification and validation traceability.
Define the objects, identifiers, authoritative sources and evidence links needed to answer that question. Then use the live workflow to test and improve the model.
The goal is usable evidence
A connected architecture does not make a product less complex. It makes the complexity more manageable. Teams can preserve specialist data where it belongs while connecting the evidence that determines product safety, quality, performance and lifecycle decisions.
That is what combination-product organisations need: not one data model for every discipline, but a governed way to connect the models that shape the same product.
.png)
.png)
.png)
