Services Combination Products Approach Industries Insights About Book a consultation

Prefer email? info@dpdynamicsol.com

Combination Products

21 CFR Part 4: One Quality System for a Combination Product

A prefilled syringe is not a drug that happens to ship in a device, nor a device that happens to contain a drug. It is one product that must satisfy two bodies of cGMP. Part 4 exists so you can meet both obligations with a single, coherent quality system instead of two that argue with each other.

Key takeaways

  • Both constituent parts' cGMP obligations apply — Part 4 governs how you satisfy them, not whether.
  • The streamlined approach lets you operate one base system and add a defined set of provisions from the other.
  • PMOA determines your lead centre and marketing application; it does not dictate which base system you choose.
  • The failures are almost never in the base system. They are at the seams: design controls, risk, change control, and suppliers.
  • Write a Part 4 rationale document. If it is not written down, an investigator will conclude the decision was never made.

What Part 4 solves

Before Part 4, a manufacturer producing a drug-device combination faced two complete regulatory frameworks — the drug cGMPs in 21 CFR Parts 210 and 211, and the device quality system requirements in Part 820 — with no instruction on how they fit together. The common outcome was two parallel quality systems, two sets of procedures, two document control systems, and a set of interfaces nobody owned.

Part 4 confirms that both sets of requirements apply, then provides a mechanism to satisfy them through one operating system. That mechanism is the streamlined approach, and it is the single most useful provision in the regulation.

First, know what you actually have

The regulatory treatment depends on how the constituent parts are combined:

  • Single-entity. The parts are physically or chemically combined into one article — a prefilled syringe, an autoinjector, a drug-eluting stent, a drug-coated balloon.
  • Co-packaged. Separate articles supplied together in one package — a vial with a dedicated delivery device, a procedure kit.
  • Cross-labeled. Articles provided separately but labelled for use with each other, sometimes manufactured by different companies at different sites.

The streamlined approach is directed at single-entity and co-packaged products manufactured together. Where constituent parts are made separately at different facilities, each facility generally operates under the cGMP applicable to what it makes — and the interface obligations shift into supplier controls, agreements, and labelling.

PMOA, lead centre, and a persistent confusion

The primary mode of action is the single mode of action that provides the most important therapeutic effect. Under 21 CFR Part 3 it determines which FDA centre leads your review — CDRH, CDER, or CBER — and therefore what kind of marketing application you file. Where the PMOA is genuinely unclear, a Request for Designation gives you a binding determination rather than a guess.

Here is the confusion worth eliminating early: PMOA determines your review pathway. It does not determine your cGMP base system. A device-led combination product can perfectly well operate under a drug cGMP base with device provisions added, and vice versa. The streamlined approach gives you the choice.

In practice, choose the base system that matches where the manufacturing risk and organisational competence actually sit — not what the lead centre implies. A sterile injectable produced in a fill-finish plant with an established Part 211 system should usually keep that system and add the device provisions. A device manufacturer adding a small drug coating should usually do the reverse.

Two ways to comply

Part 4 offers two routes:

  1. Demonstrate compliance with all applicable requirements of both frameworks. Legitimate, and occasionally the right answer for large organisations with genuinely separate operations — but it means maintaining both systems in full.
  2. Use the streamlined approach. Operate under one complete base system, and comply with a specified subset of provisions from the other. This is what most combination product manufacturers do.

How the streamlined approach works

You pick a base and add the named provisions from the other side. The provisions are not arbitrary — each fills a gap the base system does not address for the other constituent type.

Operating under a device quality system

If your base is the device quality system, you must additionally comply with the drug cGMP provisions covering:

  • Testing and approval or rejection of components, containers, and closures
  • Calculation of yield
  • Tamper-evident packaging, where applicable to OTC products
  • Expiration dating
  • Testing and release for distribution
  • Stability testing
  • Special testing requirements
  • Reserve samples

Read that list as a theme rather than a checklist: it is everything a device quality system does not naturally do because devices do not degrade, expire, or require retained samples the way drug products do.

Operating under a drug cGMP system

If your base is the drug cGMP system, you must additionally comply with the device-side provisions covering:

  • Management responsibility
  • Design controls
  • Purchasing (supplier) controls
  • Corrective and preventive action (CAPA)
  • Installation, where applicable
  • Servicing, where applicable

The theme here is equally clear: a drug cGMP system controls manufacturing superbly but has no native concept of designing a product against user needs, or of a formal CAPA system in the device sense. Of these, design controls is consistently the hardest for drug-native organisations, because it demands a structured design history that pharmaceutical development does not naturally produce.

Note on citations: when the FDA's Quality Management System Regulation took effect, the device-side citations referenced by Part 4 were conformed to the restructured regulation. The underlying obligations are preserved, but if your Part 4 rationale names old Part 820 section numbers, the references need updating. See our article on the QMSR transition.

The integration work that actually matters

Choosing a base system and listing added provisions is the easy half. The hard half — and where audits find problems — is the set of processes that must span both constituents.

Design controls across the whole product

The most common structural error is scoping design controls to the device constituent only. Your user needs are not "the autoinjector shall deliver a dose"; they are about a patient receiving the correct dose of the correct drug safely. Design inputs must therefore capture drug-device interactions: container closure integrity, extractables and leachables, dose accuracy across the formulation's viscosity range, needle compatibility, and the effect of the drug on device materials over shelf life.

Risk management spanning both constituents

A device ISO 14971 risk file that stops at the device boundary misses the hazards that matter most: incorrect dose delivery, drug degradation from device materials, particulates from a stopper, occlusion from formulation precipitation. Combined-use hazards are exactly the hazards that only exist because the parts were combined — and therefore exactly the ones a partitioned analysis will not find.

Change control that crosses the boundary

A formulation change alters viscosity, which alters injection force, which alters delivery time and can alter human factors performance. A change to a device polymer alters the leachables profile, which touches drug stability. Your change control process must force assessment across the boundary. Systems that route drug changes to drug reviewers and device changes to device reviewers will miss these connections by design.

Supplier controls

Device purchasing controls and drug component testing solve overlapping problems in different vocabularies. Whichever base you choose, satisfy both intents: qualified suppliers with defined requirements and monitored performance, and defined testing and acceptance of incoming components.

Human factors for the combined product

Users do not interact with a constituent part; they interact with the whole product. Usability evaluation should reflect real handling of the real product — the actual formulation with its actual viscosity, the actual device, the actual instructions — because injection force, hold time, and viscosity-driven confusion are combination-product failure modes that device-only testing will not reveal.

Where programmes go wrong

  • Two systems wearing one name. A "single" quality system that is really two sets of procedures with a shared cover page. The tell is that no single person can describe end-to-end how a change is assessed.
  • No written rationale. The base system choice and added provisions exist in people's heads. Nothing to show an investigator.
  • Design controls scoped to the device only. Extremely common, and it produces a design history that cannot support the combined-use claims in the labelling.
  • Stability that ignores the device. Testing the drug in a glass vial when it ships in a polymer syringe with an elastomeric stopper.
  • Unassigned interfaces. Container closure integrity, particulates, and dose accuracy sit between two organisations, and each assumes the other owns it.
  • Stale citations. Rationale documents pointing at superseded regulation text after the QMSR conforming amendments.

Write the rationale document

One controlled document, referenced from the quality manual, that records: what kind of combination product this is; the PMOA determination and its basis, including any RFD; the compliance route chosen and why; the base system selected; each added provision, where it is implemented, and by which procedure; and how cross-constituent processes — design controls, risk management, change control, supplier controls, complaints — operate across the boundary.

Two or three pages, maintained as the product changes. It is the first thing a knowledgeable investigator asks for, and having it ready changes the character of the entire inspection: you are demonstrating a considered system rather than reconstructing a rationale under pressure.

This article is general information, not regulatory advice. Combination product requirements depend on your specific product, constituent parts, and manufacturing arrangement — verify the current regulation text and applicable FDA guidance before making compliance decisions.

David Plescia, Founder & Principal Consultant, DP Dynamic Solutions David Plescia Founder & Principal Consultant, DP Dynamic Solutions · 25+ years in medtech quality

DP Dynamic Solutions integrates quality, risk, and data across drug and device constituents — Part 4 operating models, combined-constituent risk management, design controls, and supplier and change controls that span the boundary.

Combination product services
Let's talk

One system, both constituents — done right.

We build Part 4 operating models that hold together: base system selection, added provisions mapped to real procedures, and the cross-constituent processes that audits actually probe.