Combination Product Jurisdiction: How FDA Decides Who Reviews Your Product

Few regulatory questions cause as much avoidable delay as jurisdiction. A device company assumes CDRH will review their product because it looks like a device; a pharma company assumes CDER will review theirs because the active ingredient is a drug. Both assumptions are frequently wrong once a product combines a drug, device, or biologic component — and resolving jurisdiction late in development is one of the most common, and most preventable, sources of costly regulatory rework.

What Counts as a Combination Product

FDA defines combination products under 21 CFR Part 3 as products composed of any combination of a drug, device, or biological product — whether physically or chemically combined as a single entity, packaged together as separate components in a single package, or even packaged separately but intended for use together, cross-labeled to reference each other’s use, when both are required to achieve the intended therapeutic effect. Familiar examples span a wide range: drug-eluting stents, prefilled drug-delivery injectors, transdermal patches combining a drug with a delivery device, and combination biologic-device products used in cell or gene therapy delivery.

The regulatory complexity isn’t abstract — it directly shapes clinical trial design, quality system requirements, manufacturing oversight, and which FDA center leads the review.

How FDA Determines the Lead Center

FDA’s Office of Combination Products (OCP) is responsible for assigning jurisdiction, and the central concept it applies is Primary Mode of Action (PMOA) — which component of the combination product provides the most important therapeutic action. If a drug-eluting stent’s primary therapeutic effect comes from the drug coating rather than the mechanical stent structure, that PMOA determination points toward CDER-led review with device-center consultation, even though the product includes a device component; if the mechanical function is primary, CDRH typically leads instead.

This determination isn’t always straightforward, particularly for products where multiple components contribute meaningfully to the therapeutic effect, or where the primary mode of action is genuinely ambiguous based on available data. In genuinely uncertain cases, FDA applies a hierarchy of considerations beyond PMOA alone, including which center has relevant review experience with similar products.

The Request for Designation (RFD) Process

When jurisdiction is unclear, sponsors can — and should — proactively request a formal determination through a Request for Designation (RFD) submitted to OCP, rather than guessing and building a development program around an assumption. FDA is required to respond to a complete RFD within 60 days, providing a binding jurisdictional determination that identifies the lead center and, where relevant, consulting centers for specific review disciplines.

The strategic value of an early RFD is significant: it removes a substantial source of downstream uncertainty before a sponsor commits to clinical trial design, quality system architecture, or manufacturing facility planning built around assumptions about the wrong center’s expectations. Sponsors who skip this step and proceed based on an internal assumption risk building an evidence package aligned with the wrong center’s typical requirements — a mismatch that surfaces during review, when it’s far more expensive to correct.

Why This Matters Beyond the Lead Center Assignment

Jurisdiction determines far more than which FDA office reviews the submission — it shapes:

Quality system requirements. A device-led combination product may need to demonstrate compliance with device Quality System requirements under QMSR, while a drug-led combination product must additionally satisfy current Good Manufacturing Practice (cGMP) expectations for drug components — and combination products frequently need to satisfy both, in an integrated way that a single-modality development team may not anticipate.

Clinical trial design. Drug-led review typically drives clinical evidence expectations closer to standard drug development (dose-finding, pharmacokinetic data, efficacy endpoints), while device-led review may emphasize functional performance testing and human factors validation more heavily. Combination products often require both, integrated into a single clinical program.

Post-market obligations. Adverse event and complaint reporting requirements differ between drug and device frameworks, and combination product sponsors need reporting systems capable of satisfying both sets of obligations — not just the lead center’s typical expectations.

Manufacturing and facility considerations. Drug component manufacturing may require different facility registration and inspection preparedness than device component manufacturing, and combination products frequently involve manufacturing partnerships across both domains that need to be coordinated from a compliance perspective, not just a supply chain perspective.

Common Missteps Sponsors Should Avoid

Assuming jurisdiction based on how the product “feels.” A product that looks and functions primarily like a device to a development team may still be drug-led under PMOA analysis if the drug component provides the dominant therapeutic effect — and vice versa. Internal assumptions are not a substitute for a formal determination when ambiguity exists.

Waiting until the marketing submission to resolve ambiguity. Jurisdiction should be resolved during early development planning, not discovered during premarket submission preparation, when clinical and manufacturing strategy is already largely locked in.

Treating consulting-center input as a formality. Even when one center leads, the consulting center’s requirements are not optional extras — a device-led combination product with a significant drug component still needs to satisfy applicable drug-related expectations, and sponsors that treat consulting-center feedback as secondary risk significant review delays.

Underestimating the integrated quality system burden. Combination product sponsors frequently underinvest in building a quality system that genuinely satisfies both device and drug expectations from the outset, instead retrofitting one framework onto the other after an initial gap is identified — usually during an audit or inspection.

A Practical Approach

For sponsors developing anything with more than one modality — drug, device, or biologic — the sequence that minimizes downstream risk is: assess PMOA honestly and early, ideally before major development investment; file an RFD proactively whenever genuine ambiguity exists, rather than assuming; build quality and clinical strategy around the confirmed lead-and-consulting-center structure from the start; and treat the consulting center’s requirements as binding, not advisory.

Jurisdiction is one of the few regulatory questions with a clear, formal mechanism for resolving ambiguity before it becomes expensive. Sponsors who use that mechanism early tend to build development programs that align with FDA’s actual expectations; sponsors who don’t tend to find out the hard way, later and at greater cost.

This article reflects FDA’s regulatory framework for combination products under 21 CFR Part 3 and is intended for general regulatory and educational purposes. It does not constitute regulatory or legal advice for a specific product or jurisdictional determination.