The hospital's duty runs to the maker, not FDA.

A hospital sees a problem with a device and the assumption, from the device side, is usually the same one: the facility reports it to FDA, FDA’s record picks it up, and a monitoring feed watching that record eventually sees it too. 21 CFR 803.30 doesn’t work that way for most of what a user facility actually files. The duty forks on the outcome, and only one branch of it points at FDA directly.

What 803.30 actually requires

When a device user facility becomes aware of information that reasonably suggests a device has or may have caused or contributed to a death, it has to report that event to FDA, and to the manufacturer if the manufacturer is known, no later than 10 work days after becoming aware. A serious injury runs on the same 10-work-day clock, but to a different address: the report goes to the manufacturer, and only reaches FDA directly if the facility doesn’t know who the manufacturer is. Deaths are the rare event. Serious injuries are the one a facility files far more often — and that is the one whose first stop, by rule, is not the agency.

Which rooms owe this duty at all

21 CFR 803.3 defines “user facility” as a hospital, ambulatory surgical facility, nursing home, or outpatient diagnostic or treatment facility — and specifically excludes a physician’s office, a school nurse’s office, and an employee health unit. Severity doesn’t move that line. A serious injury that happens in a physician’s own office carries no mandatory 10-day duty on that site at all, from anyone. It reaches FDA, or the manufacturer, only if someone there chooses to file a voluntary MedWatch report on their own initiative.

A death reaches FDA because the rule points there. A serious injury reaches the manufacturer because the rule points there instead — and reaches FDA only because the manufacturer is separately required to pass it on.

Where the facility’s clock hands off to the manufacturer’s

Once a serious-injury report lands with the manufacturer, the facility’s 10 days are the end of its own obligation, not the start of the public record. What happens next runs on 21 CFR 803.50, the manufacturer’s own reporting clock, triggered by when the manufacturer becomes aware — which can be later than the facility’s 10 days already closed. FDA’s own MDR data files keep the two reporter types apart rather than merging them on receipt: manufacturer reports run back to August 1996, user-facility reports to 1991, each its own file, because each follows a different rule with a different trigger.

The practice

A quiet stretch in a public device-event record can mean nothing happened. It can also mean a user facility already reported a serious injury — to the manufacturer, on its own 10-day clock, exactly as required — and the event is sitting inside that manufacturer’s complaint file waiting on the manufacturer’s own 803.50 clock to turn it into something public. The facility’s job ended the moment it notified the maker. For a device manufacturer’s own regulatory team, the complaint-handling file is not a backup to the public record; for this category of event, it is frequently the first place the event exists at all. This is regulatory intelligence about how the reporting duty is structured, never regulatory advice about any specific facility’s or manufacturer’s compliance — that determination belongs with whoever holds the actual complaint file.