The Workbench · Craft
A combination product reports safety through its parts
This blog has already covered how a Request for Designation settles which FDA center holds primary jurisdiction over a combination product, and how a drug-primary quality system still borrows specific device clauses once that jurisdiction is settled. Both posts describe how a combination product gets built and reviewed. Neither describes what happens once it's on the market and something goes wrong. 21 CFR Part 4 Subpart B, in force since December 20, 2016, answers that question with a routing rule rather than a new combination-product-specific report: it names which of FDA's existing postmarketing safety systems apply, based on how each constituent part actually got its own marketing authorization — and a combination product built from more than one kind of part can owe more than one of those systems at once.
The rule routes; it doesn't invent a new report
21 CFR 4.102 doesn't create a combination-product-specific adverse event form the way a reader might expect from a regulation titled Postmarketing Safety Reporting for Combination Products. It answers a narrower, prior question: which reports must you submit to FDA for your combination product or constituent part. Where a device application backs the product or a constituent part, the applicable requirements are parts 803 and 806. Where an NDA or ANDA backs it, the applicable requirements are in part 314. Where a BLA backs it, the applicable requirements are parts 600 and 606. There is no fourth, combination-specific track — the regulation's whole function is pointing an applicant at the tracks that already existed before Part 4 Subpart B was written.
One application, more than one regime
The routing matters most for a single-entity or co-packaged combination product — one built and marketed under a single application covering every constituent part it contains. 4.102 requires that applicant to comply with the postmarketing safety reporting requirements tied to each constituent part's own type, not just the requirements that follow the lead center that reviewed the application. A drug-led autoinjector cleared through CDER because the drug carries the primary mode of action still contains a device constituent, and the applicant still owes that constituent's own duties under parts 803 and 806, on top of whatever alert and periodic reporting part 314 requires for the drug side. Reviewing center and reporting duty are two different questions Part 4 keeps from collapsing into one.
Cross-labeled products keep duties that were already separate
A cross-labeled combination product — one whose constituent parts are marketed under their own distinct applications, potentially held by different companies — runs closer to how postmarketing safety reporting worked before Subpart B existed. Each constituent part applicant complies with the requirement tied to that part's own application type, under its own existing regulation, without a combination-specific overlay layered on top. The rule's real effect on this category is naming the obligation explicitly rather than leaving it to be inferred; the underlying reporting duty for each part was already running on its own terms.
The three destinations aren't interchangeable
Parts 803 and 806 run on the device side's own machinery — this blog has already covered how a medical device report runs two separate clocks, one for becoming aware of a reportable event and one for the report itself. Part 314's drug adverse-event framework runs on its own alert-report and periodic-report structure, timed and formatted differently, filed to a different review division. Parts 600 and 606 run the biologics equivalent. A combination-product safety team that funnels every complaint through whichever intake process the company happens to have built first — often the device side's, because that's where complaint handling already lived — is running two of the three regimes through a process that was only ever built for one of them.
Where this meets the file
A combination-product postmarketing safety worksheet needs each constituent part listed against its own marketing-authorization type and its own resulting reporting regime — 803/806, 314, or 600/606 — as separate, explicit fields, not a single “safety reporting: complete” line sitting on top of whichever regime the file happened to build first. A determination record built around that structure, alongside the jurisdiction memo a Request for Designation already produces and the borrowed-GMP mapping this blog has already covered, is previewed in the launch catalog. If your program routes this determination differently, the shelf takes that correction directly.
The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.