Glossary

Medical Device Reporting (MDR)

Medical Device Reporting (MDR) is the FDA's mandatory post-market surveillance mechanism requiring manufacturers and importers to report device-related deaths, serious injuries, and malfunctions.

Get in touch Learn more

Modern WeWork hardware lab area with product team collaborating around AI device prototypes, 3D printer in background, dramatic industrial lighting with product sketches on glass walls.

POST-MARKET SURVEILLANCE

What is Medical Device Reporting (MDR)?

Medical Device Reporting (MDR) is a regulatory mandate codified in 21 CFR Part 803 that compels manufacturers and importers to submit reports to the FDA within 30 days of becoming aware of a device-related death, serious injury, or malfunction. A malfunction is reportable if it is likely to cause death or serious injury upon recurrence, establishing a proactive risk identification loop.

MDR data feeds the FDA's Manufacturer and User Facility Device Experience (MAUDE) database, enabling signal detection for emerging safety issues. This mandatory reporting is a critical input for Post-Market Surveillance (PMS) and often triggers Corrective and Preventive Action (CAPA) investigations, directly linking field performance to the manufacturer's Quality Management System (QMS).

POST-MARKET SURVEILLANCE

Key Characteristics of MDR

The foundational elements of the FDA's Medical Device Reporting (MDR) regulation, which mandates the timely reporting of adverse events to monitor device performance and protect public health.

Mandatory Reporting Triggers

MDR requires manufacturers and importers to submit a report to the FDA within 30 days of becoming aware of an event where their device:

May have caused or contributed to a death.
May have caused or contributed to a serious injury.
Malfunctioned in a way that would likely cause death or serious injury if it recurred.

This is a legal obligation, not a voluntary program.

30 days

Standard Reporting Window

5 days

Death or Serious Injury (Manufacturer)

The 5-Day and 30-Day Rule

The FDA enforces strict timelines based on event severity:

5-Day Report: Required for events requiring remedial action to prevent an unreasonable risk of substantial harm, or for a death/serious injury designated by the FDA.
30-Day Report: The standard window for all other reportable deaths, serious injuries, and malfunctions.

Failure to meet these deadlines results in non-compliance findings during inspections.

5 days

Remedial Action Deadline

30 days

Standard Reporting Deadline

Electronic Submission via eMDR

The FDA requires manufacturers to submit MDR reports electronically using the eMDR (Electronic Medical Device Reporting) system. This structured data format replaces paper Form 3500A submissions.

Uses HL7 ICSR (Individual Case Safety Report) standards.
Enables automated ingestion into the MAUDE (Manufacturer and User Facility Device Experience) database.
Requires a valid FDA Establishment Identifier (FEI) and production account.

EXPLORE

MDR vs. Vigilance Reporting (EU MDR)

While both systems track adverse events, key differences exist:

FDA MDR: Focuses on individual events. Reports go to the MAUDE database.
EU MDR Vigilance: Governed by MEDDEV 2.12-1 rev 8 and EU MDR 2017/745. Requires trend reporting and Periodic Safety Update Reports (PSURs).
Timelines: EU requires a 15-day initial report for serious public health threats, differing from the FDA's 30-day standard.

Complaint Handling & MDR Evaluation

All complaints must be evaluated against MDR criteria. A robust Quality Management System (QMS) under 21 CFR Part 820 (or ISO 13485) must establish a procedure for:

Triage: Determining if a complaint involves a death, serious injury, or malfunction.
Investigation: Root cause analysis to determine device causality.
Decision Logic: Documenting the rationale if an event is determined not reportable.

This process is a primary focus of FDA quality system inspections.

User Facility & Importer Obligations

MDR obligations extend beyond the manufacturer:

User Facilities (hospitals, clinics): Must report device-related deaths to the FDA and the manufacturer, and serious injuries to the manufacturer (or FDA if unknown).
Importers: Must report deaths and serious injuries to the FDA and the manufacturer, and malfunctions to the manufacturer.
Both must establish written MDR procedures and retain records for 2 years.

REGULATORY REPORTING COMPARISON

MDR vs. Other Post-Market Surveillance Activities

Distinguishing mandatory adverse event reporting from proactive data collection and quality system processes

Feature	Medical Device Reporting (MDR)	Post-Market Surveillance (PMS)	Corrective and Preventive Action (CAPA)
Regulatory Trigger	Death, serious injury, or malfunction likely to cause death or serious injury if it recurred	Proactive, scheduled data collection plan defined in PMS Plan	Identification of a nonconformity, quality issue, or process failure
Primary Objective	Alert FDA and public to immediate safety risks; identify emerging device problems	Continuously verify device safety and performance using real-world data	Investigate root cause, correct the nonconformity, and prevent recurrence
Data Flow Direction	Manufacturer/Importer → FDA (mandatory push)	Market → Manufacturer (continuous pull of real-world data)	Internal QMS → Root Cause Analysis → Corrective Action (internal loop)
Submission Timeline	30 calendar days (death/serious injury); 5 work days (remedial action to prevent substantial public health harm)	Defined by PMS Plan; typically periodic (e.g., quarterly, annually)	No fixed regulatory deadline; driven by risk-based urgency within QMS
Regulatory Reference	21 CFR Part 803	21 CFR Part 822; ISO 14971; MEDDEV 2.12/2	21 CFR Part 820.100; ISO 13485 Section 8.5
Output Artifact	MedWatch Form FDA 3500A (eMDR submission)	Periodic Safety Update Report (PSUR); Post-Market Surveillance Report	CAPA Record; Root Cause Analysis Report; Effectiveness Check
Proactive vs. Reactive	Reactive (triggered by a specific adverse event)	Proactive (systematic, planned data collection and analysis)	Reactive (triggered by a detected nonconformity)
Confidentiality	Publicly available in MAUDE database (with patient/ reporter de-identification)	Confidential to manufacturer; summary reports submitted to notified body/FDA	Confidential internal QMS record; subject to FDA inspection

REGULATORY COMPLIANCE

Frequently Asked Questions

Clarifying the mandatory reporting obligations and procedural nuances of the FDA's Medical Device Reporting (MDR) regulation for software-enabled diagnostic tools.

Medical Device Reporting (MDR) is the FDA's mandatory post-market surveillance mechanism requiring manufacturers and importers to report device-related deaths, serious injuries, and malfunctions. Codified in 21 CFR Part 803, the process obligates manufacturers to submit a MedWatch Form 3500A within 30 calendar days of becoming aware of an adverse event. The reporting workflow involves internal complaint handling, investigation of the device's role in the incident, and a causality assessment. For Software as a Medical Device (SaMD), a reportable malfunction might include a diagnostic algorithm producing a false negative that leads to a delayed cancer diagnosis. The FDA uses this real-world data to identify emerging safety signals and trigger corrective actions, such as recalls or labeling changes.

Enabling Efficiency, Speed & Accuracy

Intelligent Analysis, Decision & Execution

We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.

Talk to Us

Search across company data

Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.

Useful when people spend too long searching or get different answers from different systems.

Enterprise searchRAGPermissions

Automate internal workflows

Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.

Useful when repetitive work moves across multiple tools and teams.

AI agentsWorkflow automationGovernance

Add AI to products and internal tools

Build assistants, guided actions, or decision support into the software your team or customers already use.

Useful when AI needs to be part of the product, not a separate tool.

AI integrationDecision supportModel routing

REGULATORY ECOSYSTEM

Related Terms

Medical Device Reporting (MDR) is a critical component of a broader post-market surveillance framework. Understanding these adjacent regulatory mechanisms is essential for maintaining a compliant and safe medical device lifecycle.

Post-Market Surveillance (PMS)

The proactive, systematic process of collecting and analyzing real-world data on a device's performance after market release. While MDR is a reactive, event-driven reporting mechanism, PMS is a continuous, planned activity designed to proactively identify trends, update risk-benefit analyses, and feed into Clinical Evaluation reports. Data from MDRs are a vital input into the broader PMS system.

21 CFR 822

PMS Regulation

Corrective and Preventive Action (CAPA)

A systematic process within a Quality Management System (QMS) for investigating nonconformities and preventing recurrence. An MDR report often triggers a CAPA investigation. The CAPA process is the operational bridge between identifying a device-related death or serious injury (the MDR) and implementing a design or manufacturing change to eliminate the root cause.

ISO 13485

Governing Standard

Adverse Event

Any untoward medical occurrence, unintended disease or injury, or undesirable clinical signs in patients, users, or other persons, whether or not related to the medical device. An MDR is the formal regulatory submission that reports a specific subset of these events—those involving death or serious injury where a device may have caused or contributed to the outcome.

30-Day Rule

Reporting Deadline

Quality Management System (QMS)

The formalized organizational structure, responsibilities, procedures, and resources for implementing quality management, typically aligned with ISO 13485. The MDR process is a mandated procedure within the QMS. A robust QMS ensures that reporting pathways, complaint handling, and escalation procedures are documented, trained, and auditable to guarantee timely MDR submissions.

21 CFR Part 820

FDA QS Regulation

Complaint Handling

The front-end process for receiving, reviewing, and evaluating any written, electronic, or oral communication that alleges deficiencies related to a device's identity, quality, durability, reliability, safety, effectiveness, or performance. Every MDR originates from a complaint. A critical regulatory function is the triage of complaints to determine if they meet the criteria for a reportable event under 21 CFR Part 803.

21 CFR 820.198

Complaint Files

21 CFR Part 803

The specific section of the Code of Federal Regulations that codifies the legal requirements for Medical Device Reporting. It defines who must report (manufacturers, importers, user facilities), what must be reported (deaths, serious injuries, malfunctions), and the strict timelines for submission. This regulation is the definitive legal source for all MDR obligations in the United States.

EXPLORE

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.

Limited slotsGet a Free AI Consultation

How We Work

Custom AI workflows for your Business

One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.