What is 21 CFR Part 4 and which programs does it apply to?

21 CFR Part 4 is the FDA regulation governing CGMP requirements for combination products. Subpart A (the 'streamlined CGMP' framework) applies to single-entity and co-packaged combination products and lets a manufacturer demonstrate compliance with both the device QSR (21 CFR Part 820) and drug CGMP (21 CFR Part 211) through one integrated quality system, rather than running two parallel ones. Per 21 CFR 4.3, a combination product is two or more regulated components — drug, device, biological product — that are physically combined, co-packaged, or cross-labeled. If your product includes both a drug and a device constituent, Part 4 is in play.

What is the primary mode of action (PMOA) and why does it matter so early?

The primary mode of action is the single mode of action that provides the most important therapeutic effect of the combination product, per 21 CFR 3.2(m). The PMOA determines which FDA center has primary jurisdiction (CDER for drug-led, CDRH for device-led, CBER for biologic-led) and therefore which submission pathway, which review division, and which baseline regulatory framework the program will operate under. PMOA matters early because changing it midway through development is expensive — submission strategy, evidence package, and quality-system anchor all reset.

How is 'streamlined CGMP' under 21 CFR 4.4 different from running both Part 820 and Part 211 in full?

Per 21 CFR 4.4, a manufacturer that operates under 21 CFR Part 820 (the device QSR) can demonstrate compliance with the drug CGMP requirements of 21 CFR Part 211 by additionally implementing a specified subset of Part 211 provisions — listed in 21 CFR 4.4(b)(1). Conversely, a manufacturer operating under Part 211 can demonstrate compliance with Part 820 by additionally implementing a specified subset of Part 820 provisions, listed in 21 CFR 4.4(b)(2). The 'streamlined' approach lets one quality system serve as the anchor; the practical work is integrating the additional specified provisions cleanly without creating a parallel shadow system.

What's the most common stall point in combination-product programs?

The most common stall is at the interface between device design controls and drug CGMP — specifically, the integration of design control change-management with drug CGMP change-control. A device-led program can have a fully compliant 21 CFR 820.30 design controls process and a fully compliant Part 211 process, and still be non-compliant under Part 4 if a change to the device constituent that affects the drug constituent (or the drug-device interface) is not evaluated under both frameworks. This is the place inspections most often find gaps.

How does combination-product change control differ from device or drug change control alone?

Combination-product change control has to evaluate, for any change, which constituent the change touches and which constituents the change affects. A change to the device constituent that does not modify the drug or its delivery is evaluated under 820.30(i) design changes alone. A change to the device that modifies fluid path geometry, dosing accuracy, or drug-product contact materials is also a change to the drug constituent and triggers Part 211 evaluation. Programs without a single change-control board that includes both device and drug functions tend to evaluate changes against only one framework and discover the gap during inspection or submission.

Insights · Combination Products

21 CFR Part 4 in practice: where combination-product programs actually stall

21 CFR Part 4 is one of the shortest regulations in the medical-product world — but it sits at the most architecturally complex intersection. Combination-product programs do not stall on the regulation; they stall on the interfaces between the device QSR and drug CGMP, on the constituent classification underneath that, and on change-control logic that spans both. A practitioner's view of where to architect carefully.

May 3, 202613 min readBy Hitmaker Engineering

21 CFR Part 4 is one of the shortest regulations in the medical-product world. Subpart A — the streamlined CGMP framework that governs how a combination product can comply with both the device Quality System Regulation and drug CGMP through one integrated system — runs to a few pages. The brevity is deceptive. Part 4 sits at the most architecturally complex intersection in regulated-product development: the place where two regulatory frameworks, two quality vocabularies, two inspection cadences, and two engineering disciplines have to be integrated into a single coherent system that survives a coordinated inspection.

Combination-product programs rarely stall on Part 4 itself. They stall in three predictable places. This is a practitioner's note on what those stall points are and how to architect around them.

Programs do not stall on Part 4. They stall on the interfaces — between device design controls and drug CGMP, between constituent classification and submission pathway, and between two change-control systems that should be one.

The regulation, in brief

21 CFR Part 4 has two subparts: Subpart A covers CGMP requirements for combination products (the streamlined framework), and Subpart B covers post-market safety reporting. The structural backbone is in Subpart A, §4.4:

A manufacturer can demonstrate compliance with Part 820 alone, with Part 211 alone, with both in full, or with one as the anchor and the additional specified provisions of the other added on top. The fourth option is the streamlined framework.
§4.4(b)(1) lists the specific Part 211 provisions a Part-820-anchored manufacturer must implement: 211.84 (component testing), 211.103 (yield calculation), 211.137 (expiration dating), 211.165 (testing and release), 211.166 (stability), 211.167 (special testing), and 211.170 (reserve samples).
§4.4(b)(2) lists the specific Part 820 provisions a Part-211-anchored manufacturer must implement: 820.20 (management responsibility), 820.30 (design controls), 820.50 (purchasing controls), 820.100 (CAPA), 820.170 (installation), and 820.200 (servicing).

Stall 1 — Primary mode of action

Constituent classification, and specifically the determination of the primary mode of action under 21 CFR 3.2(m), is the decision that anchors everything downstream. PMOA determines:

Which FDA center has primary jurisdiction (CDER for drug-led, CDRH for device-led, CBER for biologic-led);
Which submission pathway is primary (NDA, BLA, 510(k), de novo, PMA);
Which framework anchors the streamlined CGMP system under §4.4(a);
Which review division within the lead center handles the application.

Programs stall here when the PMOA argument is made too late, or made in a form that does not survive the FDA's Office of Combination Products review. The PMOA determination is not a marketing decision — it has to align with how the product actually achieves its primary therapeutic effect, supported by mechanism-of-action data and clinical evidence. A program that designs around a device-led PMOA and discovers during pre-submission that the agency views the product as drug-led pays the cost twice: in the submission strategy and in the already-implemented quality system that was anchored on Part 820.

Stall 2 — Streamlined CGMP integration

Once PMOA is set and the anchor framework is chosen, the next stall point is the integration of the additional specified provisions. The regulation lists the provisions; it does not specify how to integrate them. Programs frequently default to one of two patterns, and both produce inspection findings:

Anti-pattern: the shadow system

A device-anchored program implements 21 CFR 820 in full and stands up a parallel set of procedures for the additional Part 211 provisions — often with different document numbering, different review boards, and different training paths. The two systems coexist but do not integrate. When a deviation occurs in the drug constituent, the device QMS does not capture it; when a CAPA opens for a device issue that affects drug stability, the Part 211 system does not see it. Inspections find the gap.

Anti-pattern: the blended system without anchor

The opposite failure: a program tries to integrate Part 820 and Part 211 in equal weight, with no clear anchor. The result is procedures that try to address both frameworks at once and end up addressing neither cleanly. Inspectors arrive expecting either a 820-anchored or a 211-anchored streamlined system per §4.4(a), find neither, and write findings against both frameworks.

Streamlined CGMP works when the anchor is unambiguous and the additional specified provisions are integrated as procedures within the anchor system — not as a parallel system, and not as a hybrid without an anchor.

The pattern that does work is structural: pick the anchor explicitly (per §4.4(a)), implement the anchor framework as the primary QMS, and integrate the additional specified provisions as named procedures within that QMS — referenced by their §4.4(b) provision number, owned by the same management responsibility chain as the anchor framework, and subject to the same internal-audit cadence.

Stall 3 — Change control across the interface

The third stall is at the most expensive seam: change control that spans the device-drug interface. A change-control system that handles a device change correctly under 21 CFR 820.30(i) and a drug-process change correctly under Part 211 can still be non-compliant under Part 4 if a change that touches the device but affects the drug constituent is not evaluated under both frameworks.

Examples of cross-interface changes that frequently miss dual-framework evaluation:

A change to a fluid path component that is technically a device change, but alters drug-product contact materials and therefore extractables/leachables risk under Part 211 stability testing (§211.166).
A software change to a delivery device that is a device design change under 820.30(i), but modifies the delivered dose profile and therefore the drug-product specification.
A supplier change for a primary container-closure component that is a purchasing controls change under 820.50, but is also a drug-product contact-surface change under 211.84 (component testing).

How to stand up streamlined CGMP — six steps

The HowTo schema embedded in this article's structured data captures the full step sequence; the practitioner version is shorter:

Establish constituent classification and PMOA per 21 CFR 3.2(e) and 3.2(m). Document the rationale before any QMS decision is made.
Choose the anchor framework per §4.4(a). The choice usually aligns with the PMOA, but the existing QMS, the inspection cadence, and the team's expertise matter — make it a deliberate decision.
Map the additional specified provisions from §4.4(b) onto the anchor QMS as named procedures, owned by the same management chain as the anchor framework.
Stand up an integrated change-control system with one board, dual representation, and explicit dual-framework evaluation logic.
Integrate design controls with drug CGMP at the artifact level. Design inputs reference drug-product specifications they constrain; design validation references drug-delivery clinical evidence directly.
Train the team on the integrated system. Device engineers and drug-CGMP staff each learn the other framework well enough to evaluate cross-interface changes correctly. The system is only as integrated as the people running it.

Practitioner summary

21 CFR Part 4 is short. The architectural decisions it requires are not. The three places combination-product programs stall — constituent classification and PMOA, streamlined CGMP integration, and change control across the device-drug interface — are not regulatory ambiguities. They are points where the regulation defers to the program's own design choices, and programs that defer those choices pay the cost in submission delay, inspection findings, or both.

Programs that architect Part 4 deliberately — choosing the anchor framework explicitly, integrating §4.4(b) provisions cleanly, and running one change-control board across the interface — pass coordinated inspections without surprises and route their submissions through the right center the first time.

For the design-controls side of the work, see Regulatory, Quality & Design Controls. For where programs typically stall in the lifecycle more broadly, see Why medical device development breaks down between user needs, engineering, and manufacturing.

Frequently asked questions

What is 21 CFR Part 4 and which programs does it apply to?: 21 CFR Part 4 is the FDA regulation governing CGMP requirements for combination products. Subpart A (the 'streamlined CGMP' framework) applies to single-entity and co-packaged combination products and lets a manufacturer demonstrate compliance with both the device QSR (21 CFR Part 820) and drug CGMP (21 CFR Part 211) through one integrated quality system, rather than running two parallel ones. Per 21 CFR 4.3, a combination product is two or more regulated components — drug, device, biological product — that are physically combined, co-packaged, or cross-labeled. If your product includes both a drug and a device constituent, Part 4 is in play.
What is the primary mode of action (PMOA) and why does it matter so early?: The primary mode of action is the single mode of action that provides the most important therapeutic effect of the combination product, per 21 CFR 3.2(m). The PMOA determines which FDA center has primary jurisdiction (CDER for drug-led, CDRH for device-led, CBER for biologic-led) and therefore which submission pathway, which review division, and which baseline regulatory framework the program will operate under. PMOA matters early because changing it midway through development is expensive — submission strategy, evidence package, and quality-system anchor all reset.
How is 'streamlined CGMP' under 21 CFR 4.4 different from running both Part 820 and Part 211 in full?: Per 21 CFR 4.4, a manufacturer that operates under 21 CFR Part 820 (the device QSR) can demonstrate compliance with the drug CGMP requirements of 21 CFR Part 211 by additionally implementing a specified subset of Part 211 provisions — listed in 21 CFR 4.4(b)(1). Conversely, a manufacturer operating under Part 211 can demonstrate compliance with Part 820 by additionally implementing a specified subset of Part 820 provisions, listed in 21 CFR 4.4(b)(2). The 'streamlined' approach lets one quality system serve as the anchor; the practical work is integrating the additional specified provisions cleanly without creating a parallel shadow system.
What's the most common stall point in combination-product programs?: The most common stall is at the interface between device design controls and drug CGMP — specifically, the integration of design control change-management with drug CGMP change-control. A device-led program can have a fully compliant 21 CFR 820.30 design controls process and a fully compliant Part 211 process, and still be non-compliant under Part 4 if a change to the device constituent that affects the drug constituent (or the drug-device interface) is not evaluated under both frameworks. This is the place inspections most often find gaps.
How does combination-product change control differ from device or drug change control alone?: Combination-product change control has to evaluate, for any change, which constituent the change touches and which constituents the change affects. A change to the device constituent that does not modify the drug or its delivery is evaluated under 820.30(i) design changes alone. A change to the device that modifies fluid path geometry, dosing accuracy, or drug-product contact materials is also a change to the drug constituent and triggers Part 211 evaluation. Programs without a single change-control board that includes both device and drug functions tend to evaluate changes against only one framework and discover the gap during inspection or submission.

Related insights

Sustaining engineering for combination products: cost reduction vs. regulatory risk →
Sustaining engineering on a combination product is the most underestimated phase in the lifecycle. Cost-reduction opportunities are real but every change traverses 21 CFR 820.30(i) design changes, ISO 14971 risk re-evaluation, and 21 CFR Part 4 cross-constituent impact. A practitioner's framework for evaluating sustaining changes against the cost / risk frontier.
Why medical device development breaks down between user needs, engineering, and manufacturing →
Most medical-device programs do not fail on the technology. They fail at the seams — where user needs, engineering, design controls, and manufacturing should integrate but don't. A practitioner's anatomy of where, why, and how to architect around it.
From user research to verifiable requirements: a lifecycle framework for medical-device teams →
User research produces narrative; design controls require verifiable inputs. A practitioner's framework for translating user-research outputs into design inputs that satisfy 21 CFR 820.30(c), align with IEC 62366-1:2015 use specifications, and produce a verification plan that audits cleanly.

← All insights Start a product development conversation →