Medical Device Reporting Awareness
Medical Device Reporting, or MDR, is an important part of how device manufacturers respond to information about potentially serious product problems. The work begins with recognizing concerning information and getting it to the right people promptly.
This lesson focuses on manufacturer awareness. Watch for events that may need reporting, the difference between calendar days and work days, and the evidence needed for assessment. We will also look at what FDA's public adverse-event database can and cannot tell us.
Complaint handling and reporting are connected
MDR requirements are addressed in Title twenty-one of the Code of Federal Regulations, Part eight hundred three. They remain relevant alongside the Quality Management System Regulation in Part eight hundred twenty.
A complaint record and an MDR assessment serve related but different purposes. Receiving and investigating a complaint does not, by itself, complete the reporting assessment.
Manufacturers, importers, and device user facilities have mandatory duties with different details. Here we concentrate on recognizing manufacturer concerns and routing them to designated reporting personnel, who apply the current regulation and company procedure.
Recognize potentially reportable events
A manufacturer must report when information reasonably suggests that a device it markets may have caused or contributed to a death or serious injury.
Reporting also applies to a malfunction when that device, or a similar device the manufacturer markets, would be likely to cause or contribute to death or serious injury if the malfunction happened again.
An actual injury is therefore not required for every reportable malfunction. The threshold is also not final proof of causation. Concerning information needs prompt assessment while the technical investigation continues.
Know the reporting timeframes
The standard manufacturer reporting deadline is no later than thirty calendar days after the day the manufacturer receives or otherwise becomes aware of the information indicating a reportable event.
Certain circumstances require a report no later than five work days after the relevant day of awareness. These include a reportable event that requires remedial action to prevent an unreasonable risk of substantial harm to public health, and circumstances covered by FDA's written request for five-day reporting.
Calendar days and work days are different. Designated reporting personnel must apply the relevant rules, including any applicable exceptions or authorized arrangements.
Escalate without waiting for the investigation
Do not treat an outer reporting deadline as permission to delay internal escalation. Record when information was received, preserve the available evidence, and promptly involve the designated reporting lead.
An investigation may still be working out what happened. Reporting assessment should proceed alongside that work rather than waiting for a final root cause or a successful reproduction of the failure.
The company procedure supports recognition, communication, and follow-up. A foundation-course result does not grant independent authority to make every reportability determination.
Use the required reporting channel
Manufacturers generally submit MDRs electronically in the format FDA requires. The reporting lead needs to apply the relevant submission requirements and any authorized exception.
A patient's voluntary MedWatch report does not automatically satisfy the manufacturer's own reporting obligation. The manufacturer still needs to assess and meet its applicable duties.
Maintain evidence of the assessment, the information available, and reports made. This helps connect the original concern with the decisions and communications that followed, rather than leaving reporting separate from the event history.
Handle incomplete information honestly
A report may arrive without complete device details or a finished technical explanation. Bring those gaps to the reporting lead promptly so the applicable requirements can still be met.
The manufacturer has responsibilities to investigate and obtain reasonably available information. Where required information cannot be provided, the report explains why it is incomplete and what steps were taken to obtain it. Later information may require a supplemental report under the applicable rules.
Keep known facts and missing information distinct. Neither an invented answer nor an indefinite wait for complete information creates a reliable reporting record.
Use MAUDE with its limitations in mind
FDA's Manufacturer and User Facility Device Experience database, known as MAUDE, provides publicly accessible medical device reports. These reports can contribute useful information to a safety review.
A report does not, by itself, prove that a device caused the outcome. Reports may be incomplete, inaccurate, unverified, or affected by underreporting.
Raw report counts also cannot establish or compare adverse-event rates. For example, the information may not tell us how often each device was used. Without dependable reporting and exposure information, a count alone is not a valid measure of comparative risk.
Example: a shutdown reported by a clinician
Imagine a clinician reports that a device shut down during use. No injury was reported, but the circumstances suggest that a repeat event could have serious consequences. The cause is not yet known.
Capture the available device identity, event details, and timing of receipt. Preserve relevant evidence and promptly involve the reporting lead.
The lack of an actual injury and an unfinished investigation do not justify dismissing the concern. Designated personnel assess the event against the reporting criteria and applicable timing requirements. The Quality Manager helps ensure that the information and follow-up reach them.
What to carry into your work
Recognize potentially reportable events, preserve the available information, and escalate promptly. Keep the reporting assessment moving while technical work continues. Use MAUDE as one source of safety information, while respecting the limits of what individual reports and raw counts establish.
This lesson draws on FDA's reporting and MAUDE resources and Title twenty-one of the Code of Federal Regulations, Part eight hundred three. It is original educational content, not an official FDA course. Applicable requirements and your company's approved procedures govern actual work.
SOURCE CREDIT FDA mandatory reporting and MAUDE resources; 21 CFR Part 803. Original educational adaptation of the existing Medical Device Reporting Awareness course reading, with sources checked 29 October 2026. Not an official FDA course. Applicable requirements and company procedures govern actual work.