SMDA: User-Facility Reporting Duties

The Safe Medical Devices Act of 1990 (Pub. L. 101-629) is the law that first put a mandatory reporting duty directly on hospitals and other healthcare facilities that use medical devices, not just on the companies that make them. That duty survives today as the “device user facility” branch of FDA’s Medical Device Reporting (MDR) regulation, codified at 21 CFR Part 803. For a patient-safety officer, quality director, or risk manager, the practical question isn’t the Act’s legislative history — it’s three narrower questions: what has to be reported, to whom, and by when.

This guide is written for hospital patient-safety officers, quality directors, risk managers, and infection preventionists who own device-related event reporting and need the actual duty, not a summary of the whole MDR system. For the full manufacturer/importer/user-facility framework this guide deliberately does not re-explain end to end, see Medical Device Reporting (MDR).

What Counts as a “Device User Facility”

Part 803 defines device user facilities as hospitals, ambulatory surgical facilities, nursing homes, and outpatient diagnostic or treatment facilities. Physician offices are specifically exempt — a distinction that matters for any multi-site health system that includes both hospital-based and freestanding physician-office locations under one compliance umbrella. Individual clinicians and patients are not mandatory reporters under this regulation at all; they can report suspected device problems voluntarily through FDA’s MedWatch program on Form 3500, a separate channel from the mandatory-reporter duty described here.

The Three Duties at a Glance

Device-related death: report to both FDA and the device manufacturer, no later than 10 workdays after the facility becomes aware of it.
Device-related serious injury: report to the manufacturer only, within the same 10-workday window — unless the manufacturer is unknown, in which case the report goes to FDA directly.
Annual report: submit a summary report to FDA by January 1 of each year, but only if the facility filed at least one death or serious-injury report during that period.

Notice what is not on this list: user facilities do not have a mandatory duty to report device malfunctions that don’t rise to death or serious injury — that obligation sits with manufacturers and importers, not with the facility using the device.

Death Reports: FDA and the Manufacturer, Within 10 Workdays

A device-related death is one a facility has information reasonably suggesting a device may have caused or contributed to. This is a dual-report duty — both the manufacturer and FDA directly, not one or the other. Both reports are due within 10 workdays of the facility becoming aware of the event, and “becoming aware” is a lower bar than “concluded the device was at fault”: it starts the clock once any responsible facility employee has information reasonably suggesting the device may be implicated, not once an internal investigation confirms it.

Serious Injury Reports: The Manufacturer First

A device-related serious injury follows a different routing rule than a death. The report goes to the manufacturer, not to FDA, within the same 10-workday window. FDA only becomes a direct recipient of a serious-injury report if the manufacturer cannot be identified — an unlabeled or unmarked device, for example, or one from a source the facility can’t trace. This split (dual report for death, single report for serious injury) is the detail most often gotten wrong internally, since it’s easy to assume every reportable event follows the same routing.

Counting the 10-Workday Clock Correctly

Ten workdays means ten business days, not ten calendar days — weekends and the facility’s recognized holidays don’t count toward the total. The clock starts on the date the facility becomes aware of the event, which a compliance program should log explicitly and separately from the date the event itself occurred; those two dates are often different by days or weeks, and only the “became aware” date controls the deadline. A program that only tracks event dates will misjudge its own compliance window.

The Annual Report: Form FDA 3419, Due by January 1

Beyond the individual death and serious-injury reports, a user facility that filed at least one report during the year must also submit an annual report to FDA on Form FDA 3419, due by January 1 of the following year. It goes to FDA’s Center for Devices and Radiological Health, not to the manufacturer, and it summarizes the reports the facility filed during that period: the total number of reports, the range of report numbers, current facility and contact information, and, for each reportable event, the report number, the manufacturer and device identified, a description of the event, and where it was reported. Facilities that filed zero medical device reports during the period are not required to submit an annual report at all — the obligation is triggered by having something to summarize, not by the calendar alone.

Recordkeeping: The Two-Year MDR Event File

Independent of the reports themselves, a user facility must establish and maintain an MDR event file for each event it evaluates, documenting the facility’s own deliberation over whether the event was reportable, and retain it for two years from the date of the event. That two-year period is shorter than what applies to manufacturers and importers, who must keep their MDR event files for two years from the event or for the expected life of the device, whichever is longer — a user facility’s retention duty doesn’t scale with device lifespan the way a manufacturer’s does. Files must be clearly identified and organized so FDA can access, copy, and verify them on request during an inspection.

Building the Internal Program So the Clock Doesn’t Start Late

Because the reporting clock starts at “becomes aware,” not at “confirmed,” the practical failure mode isn’t usually a missed deadline after the fact — it’s a delayed internal handoff that eats into the 10 workdays before anyone starts the clock. A workable program typically has:

A single designated person or office (often risk management, biomedical/clinical engineering, or a quality department) with clear, published authority to receive device-event reports from any staff member and to make the reportability call.
A short escalation path from bedside staff, sterile processing, and biomedical engineering to that designated person, separate from — and faster than — the facility’s general incident-reporting workflow, so a device-related death or serious injury doesn’t wait behind a routine event queue.
A logged “became aware” date captured at first notice, not backfilled later, since that date — not the event date — is what the 10-workday clock actually runs from.
A tie-in to the facility’s existing root cause analysis process for events that also meet the threshold for a sentinel event review, since the two obligations run in parallel and share source information but serve different purposes.
A standing check, ahead of January 1 each year, for whether any reports were filed that year and, if so, who owns compiling Form FDA 3419.

How This Differs from Manufacturer and Importer Duties

Reporter	Death	Serious injury	Malfunction	Deadline
Device user facility	FDA and manufacturer	Manufacturer (FDA if unknown)	No mandatory duty	10 workdays
Manufacturer	FDA directly	FDA directly	FDA, if likely to cause death/serious injury if it recurred	30 calendar days (5 workdays if remedial action is needed)
Importer	FDA and manufacturer	FDA and manufacturer	Manufacturer only	30 calendar days

The practical takeaway for a hospital compliance program: your facility’s duty is narrower than a manufacturer’s in one sense (no mandatory malfunction reporting) and stricter in another (a shorter 10-workday clock instead of 30 calendar days). Don’t design an internal SOP around the manufacturer-facing timelines described elsewhere — they’re a different clock for a different reporter.

Frequently Asked Questions

Is a physician’s private office a “device user facility” under the Act?

No. Part 803 explicitly exempts physician offices from the device user facility definition, even though hospitals, ambulatory surgical facilities, nursing homes, and outpatient diagnostic or treatment facilities are all included.

What if we didn’t file any device reports this year — do we still owe FDA an annual report?

No. The annual-report duty is triggered only by having filed at least one death or serious-injury report during the period; a facility with zero reports for the year has nothing to submit.

Are the 10 workdays calendar days or business days?

Business days. Weekends and the facility’s recognized holidays don’t count toward the 10-workday total, and the clock starts from the date the facility became aware of the event, not the date the event occurred.

Do we ever report a malfunction to FDA ourselves?

Not as a mandatory user-facility duty under Part 803 — malfunction reporting is a manufacturer and importer obligation. A facility can still choose to notify a manufacturer of a malfunction it observes, which is good practice, but it isn’t the reporting duty this Act created for facilities.

Is this the same “MDR” as the EU’s Medical Device Regulation?

No, and the acronym collision is a real source of confusion. This page covers FDA’s Medical Device Reporting under 21 CFR Part 803; the EU’s Medical Device Regulation (2017/745) is an entirely different, premarket CE-marking framework. See Medical Device Reporting (MDR) for the disambiguation.

Who inside the hospital should actually own this duty?

There’s no single FDA-mandated title, which is exactly why it needs to be assigned deliberately rather than left implicit. Risk management, biomedical/clinical engineering, and quality departments most commonly hold it, provided the designation is published and staff know where to route a suspected device-related death or serious injury the moment they see one.

Safe Medical Devices Act Reporting Duties: The User-Facility Compliance Checklist

Ask about Safe Medical Devices Act Reporting Duties: The User-Facility Compliance Checklist