Call it fifteen. File it in thirty.

A combination product inherits its reporting duties from its constituent parts, not from whichever center reviewed it. 21 CFR Part 4, Subpart B, finalized in 2016, spells out exactly which postmarketing safety reports attach to a device constituent and which attach to a drug constituent — a sponsor running both gets both lists, not an averaged one. Buried in the drug-constituent list is a substitution that changes a report’s deadline without changing its name, and it applies to only one of the two reports sitting right next to each other in the same subsection.

Two constituents, two report lists

Under 21 CFR 4.102(c)(1), a combination product with a device constituent owes FDA five-day reports, malfunction reports, and correction-or-removal reports — the same Part 803 and Part 806 clocks a device-only manufacturer already runs, malfunction reports standard at thirty calendar days under 21 CFR 803.50. Under 21 CFR 4.102(c)(2), a combination product with a drug constituent owes two different reports: field alert reports and fifteen-day reports as described in 21 CFR 314.80. Named side by side in the same paragraph, the two drug-constituent reports do not share a clock.

The substitution written into the name

The fifteen-day report is defined by cross-reference to Section 314.80, and an ordinary drug application owes it within fifteen calendar days of the applicant learning of a serious, unexpected adverse reaction. Part 4.102(c)(2) adds one clause: the report must be submitted within thirty calendar days instead of fifteen if the combination product received its marketing authorization under a device application — a 510(k) or a PMA leading the product to market rather than an NDA or BLA. Nothing about the report’s trigger, its content, or its format changes. Only the clock does, and only because of which application type led. The report keeps the name a drug-only sponsor would recognize while running on a deadline that sponsor would not.

Two reports, one subsection, one substitution clause. It reaches the fifteen-day report and stops there.

The clock next to it that never moves

Field alert reports, required under 21 CFR 314.81(b)(1) for a drug quality or labeling problem serious enough to warrant one, run on their own clock: within three working days of the applicant receiving the information, regardless of which application led the combination product to market. Part 4.102 does not touch that deadline anywhere. A device-led combination product’s drug constituent files its field alert report exactly as fast as a drug-only application would, and its fifteen-day report twice as slowly — two reports, drawn from the same subsection of the same rule, moving on two different premises.

One filing instead of two, when the facts line up

The rule does not ask for the same event reported twice under two different names. If a report already submitted for an event satisfies the content, manner, and deadline another constituent’s report would otherwise require, Part 4.102(c) does not require the second filing. FDA phased enforcement in after the 2016 final rule rather than switching it on at once — compliance for applicants using FAERS and eMDR took effect July 31, 2020, and for applicants using VAERS, January 31, 2021 — but the underlying obligation, and its one clock substitution, has not changed since.

Why this sits outside a device-only watch

FDA Radar watches the device side of the FD&C Act — Federal Register device rules, CDRH warning letters, device recalls, and 510(k) clearances. A device constituent’s malfunction and correction-or-removal reports overlap with exactly that world; a device-only compliance calendar already tracks Part 803 and Part 806. The drug-constituent half of Part 4 — field alert reports, and the fifteen-day report that isn’t always fifteen days — runs through a pharmacovigilance system a device-only regulatory function was never built to watch. A combination-product sponsor who inherited that duty without a counterpart on the drug side is the one most likely to miss it, not because the rule is obscure, but because it lives one CFR part away from the one a device team already reads every day. Which systems to build, and which reports Part 4.102(c)’s duplicate-filing exception lets you consolidate, is a combination-product compliance judgment for your own regulatory and quality team to make on your own product — this describes what the rule requires, never a substitute for that judgment.