A user facility's MDR duty isn't a manufacturer's

This blog has already covered the manufacturer's own medical device reporting duty — the 803.50 reportability test, the standard 30-day filing window, and the 803.53 escalation that can shrink it to five. That post covers one of three reporters 21 CFR Part 803 regulates, and the other two don't inherit the manufacturer's rules by default. A hospital and an importer each carry their own subpart, with their own recipients and their own deadlines, and a single “MDR duty” checkbox that doesn't ask which kind of reporter is filing has already lost the distinction the regulation is built around.

A user facility's duty splits by outcome, not by event

21 CFR Part 803, Subpart C governs device user facilities — hospitals, nursing homes, ambulatory surgical facilities, and outpatient treatment or diagnostic facilities — and it doesn't ask a single question about whether an event is reportable the way the manufacturer's 803.50 does. It splits the duty by what happened. A device-related death has to be reported to both FDA and the manufacturer, if the manufacturer is known, no later than ten work days after the facility becomes aware of it. A device-related serious injury runs a narrower route: it goes to the manufacturer alone if the manufacturer is known, and only reaches FDA directly if the manufacturer isn't known. A user facility procedure built on the assumption that every reportable event goes to FDA is already wrong about roughly half of what the subpart actually requires.

The “if known” branch decides where the report goes

That manufacturer-known condition isn't a footnote — it's the fork the whole serious-injury pathway runs on. A facility that can identify the manufacturer owes that report to the manufacturer and stops there; a facility that can't owes it to FDA instead, because there's no other party left to receive it. A device-tracking system that can't answer, on a per-event basis, whether the manufacturer was identifiable at the time of filing hasn't kept the fact that actually determined where the report was legally required to go.

An annual report closes the loop the individual reports don't

Beyond the event-by-event duty, Subpart C also requires a device user facility to submit an annual report to FDA. That report isn't a re-filing of each individual death or serious injury already reported during the year — it's a separate, standing obligation on its own calendar, and a facility that files every individual report on time but never produces the annual summary has still left part of Subpart C undone.

An importer's duty runs on a single 30-day clock, split by severity

21 CFR Part 803, Subpart D covers importers, and it runs on a different structure than either the user facility's or the manufacturer's. A death or serious injury an importer becomes aware of goes to both FDA and the manufacturer, within 30 calendar days — not the user facility's 10 work days, and not the manufacturer's own 803.53 escalation to five. A malfunction, by contrast, goes to the manufacturer only, never directly to FDA, on that same 30-day clock. This blog has already covered the other duties an importer takes on once a device crosses the border; medical device reporting is a fourth one, running on its own subpart rather than borrowing either of the other two reporters' rules.

Three subparts, not one duty read three ways

The pattern across all three is the same shape with different numbers filled in: who the report reaches, how fast it has to get there, and whether the manufacturer's own knowledge of the event changes the answer. Subpart E's 803.50 through 803.53 answer that shape for a manufacturer. Subpart C answers it for a user facility, on a 10-work-day clock split by death versus serious injury. Subpart D answers it for an importer, on a 30-calendar-day clock split by severity versus malfunction. None of the three subparts defers to another for its own terms, and a compliance program that maintains one MDR procedure written from the manufacturer's subpart, then hands it to an importer or a user-facility partner as if it applied unchanged, has handed over rules that were never written for that reporter.

Where this meets the file

An MDR procedure library needs a separate document for each reporter category — manufacturer, importer, user facility — built from that reporter's own subpart, rather than one master procedure with a note that “other reporters may have different timelines.” A reporter-specific MDR tracking template set is previewed in the launch catalog. If your organization holds more than one of these roles and tracks the distinction differently, the shelf takes that correction directly.