The Complete Guide to MDR Reporting for Medical Devices: From Awareness to Submission

Who must file MDRs and under what timelines

FDA 21 CFR Part 803 assigns reporting obligations to three groups. Manufacturers must report events involving death or serious injury within 30 calendar days under Section 803.50. Events requiring remedial action to prevent unreasonable risk of substantial harm must be reported within 5 business days. Malfunctions that could cause death or serious injury if they recurred are reportable within 30 days.

Importers must report deaths and serious injuries to both the FDA and the manufacturer within 30 calendar days under Section 803.40. Malfunctions are reported to the manufacturer only.

Device user facilities (hospitals, nursing homes, and similar institutions) must report deaths to both the FDA and the manufacturer within 10 business days. Serious injuries are reported to the manufacturer only.

The "becomes aware" trigger under Section 803.50(a) is where compliance risk concentrates. A manufacturer becomes aware when any employee receives information that reasonably suggests a reportable event has occurred. This includes sales representatives, field service engineers, customer service agents, and distributors. The clock does not start when the Regulatory department receives the complaint. It starts when anyone at the company learns about the event.

EU MDR Article 87 imposes shorter timelines on manufacturers for serious incidents reported through the manufacturer incident report (MIR). Serious public health threats must be reported within 2 days. Events involving death or unanticipated serious deterioration in health require reporting within 10 days. Other reportable events require reporting within 15 days. These reports are submitted to the competent authority in the Member State where the incident occurred.

Health Canada requires mandatory problem reporting: 10 days for events involving death or serious deterioration, 30 days for other incidents. The MHRA in the UK uses its own adverse incident reporting system post-Brexit. The TGA in Australia, PMDA in Japan, and ANVISA in Brazil each maintain jurisdiction-specific reporting requirements.

For manufacturers selling globally, a single complaint event can trigger simultaneous reporting obligations in four or more jurisdictions, each with different forms, fields, timelines, and submission channels.

What goes into an FDA Medical Device Report

FDA Form 3500A contains over 50 fields organized across five sections. Patient information includes age, sex, weight, and outcome (death, serious injury, malfunction, other). Device identification requires brand name, model number, catalog number, serial number, lot number, manufacturer name and address, manufacturing date, and expiration date. Event information covers the event date, event description narrative, and reporter details. Manufacturer information documents the date of awareness, report source, and any remedial action taken.

The event description narrative is the most scrutinized field in any MDR. Regulators expect a factual, specific account of what happened, what the device was doing, what the patient outcome was, and what corrective action the manufacturer has taken or plans to take. This narrative must be consistent with the complaint record, the investigation findings, and the IMDRF codes assigned to the event. Inconsistencies between the narrative and the underlying complaint file are among the most common findings during FDA inspections.

Each field draws data from a different source system. Device identification comes from the device master record (typically in the ERP or PLM system). Patient and event information come from the complaint record (typically in the eQMS). Reporter information may be in the CRM or in the complaint record. Assembling this data manually is where the majority of elapsed time in the MDR process is consumed.

Why MDR submission quality and timeliness matter

The FDA actively monitors MDR submission patterns. Late submissions are visible in the MAUDE database, where the gap between the date of awareness and the submission date is documented for every report. Consistent late reporting can result in warning letters, 483 observations during inspections, and formal enforcement action under the CDRH compliance program.

Incomplete submissions are rejected or flagged for follow-up, adding days to a process already running against a deadline. The most commonly missing fields across the industry are device product code, event type classification, and initial reporter contact information.

Data inconsistency between the complaint record and the MDR is a separate risk. When IMDRF codes on the complaint do not match the codes on the MDR, when the event description differs between systems, or when the patient outcome is characterized differently in the complaint file versus the regulatory submission, it creates audit exposure that can take weeks to resolve. One Smarteeva customer identified a 9% mismatch rate before implementation.

From a broader public health perspective, MDR submissions are the data layer that regulators use for signal detection across the entire device population. When manufacturers submit accurate, timely reports with consistent coding, the FDA's ability to identify emerging safety patterns improves. When submissions are late, incomplete, or inconsistently coded, safety signals are delayed or missed.

How Smarteeva processes MDR reporting end to end

Automatic reportability assessment across jurisdictions

When a complaint enters Smarteeva, country-driven decision trees evaluate the event against the regulatory criteria for every applicable jurisdiction. A complaint involving a serious injury at a hospital in Germany is simultaneously assessed against FDA Part 803 (if the manufacturer sells in the US), EU MDR Article 87 (MIR to the German competent authority BfArM), and any other applicable frameworks. All reportable routes are identified from a single complaint event without the Regulatory team manually checking each jurisdiction.

Pre-populated forms from connected data

Because complaint records, device master records, customer records, and reporter information exist in the same Salesforce environment, the MDR form fields are populated from connected data. The Regulatory team does not search multiple systems. They review pre-populated fields, edit where needed, and approve.

AI-drafted narratives

The event description narrative is generated as a draft from the complaint description, investigation findings, and IMDRF codes. The AI does not write the final submission. It eliminates the blank-page problem so the Regulatory professional starts with a source-grounded draft rather than starting from scratch.

Direct FDA submission via ESG NextGen API

Smarteeva submits MDRs directly to the FDA through the Electronic Submissions Gateway NextGen API. The submission is validated against field requirements, transmitted electronically, and confirmed with receipt acknowledgment. Average submission time: 3 minutes. One customer manages over 300,000 MDRs on the platform.

Bidirectional IMDRF code sync

IMDRF codes confirmed on the complaint automatically populate the MDR. Changes to codes on either the complaint or the report propagate to the other. The 9% mismatch rate at one customer dropped to less than 0.001% after implementation.

Complete audit trail

Every submission is documented: who submitted, when, what was included, what the FDA acknowledged, and any supplemental reports filed subsequently. Follow-up reports auto-populate fields from the original submission.

35% of all Medical Device Reports submitted to the FDA are filed through Smarteeva. This includes manufacturers of every size, from single-product companies to global enterprises managing device portfolios across 80+ countries. The platform handles the same regulatory obligation whether the manufacturer files 10 MDRs per year or 10,000.

What the MDR triggers beyond the submission

Filing the MDR is not the end of the process. It is the start of several operational workflows that most manufacturers handle outside the reporting system.

The reporter expects communication. The person or facility that reported the event wants to know what happened. Was a report filed? Is an investigation underway? What was the outcome? At most manufacturers, this communication happens through email threads that are never linked to the MDR or the complaint record. If an FDA inspector asks "how did you follow up with the reporter?", the documentation trail is often incomplete.

The sales team needs visibility. When a reportable event involves a key account, the account manager needs to know before their next visit. A serious injury at a hospital that represents significant annual revenue is both a patient safety event and a commercial relationship issue. Both need to be managed, and both should be traceable to the same complaint.

The risk management file needs updating. Every reportable event should trigger a review of the device's risk profile under ISO 14971. Does this event represent a new hazard? Does it change the probability or severity of a known risk? The risk assessment should reference the complaint data and the MDR submission, but when these live in separate systems, the connection is manual.

The event may trigger a field safety corrective action. If the MDR reveals a pattern or a severity level that warrants a recall or field correction, the MDR is the starting point for the FSCA workflow. The complaint data, the MDR submission, and the recall notification should all link together.

The MDR data feeds into the next PSUR. Every MDR filed during a reporting period contributes to the adverse event summary and trend analysis in the periodic safety update report. When MDRs are submitted through a separate tool, someone has to manually count and categorize them for the PSUR. When they are filed from the same platform where complaints and investigations live, the PSUR data is already connected.

Smarteeva handles all of these downstream workflows because the MDR is not a separate document. It is a regulatory output generated from the same complaint record that drives investigation, customer communication, and risk assessment. 35% of FDA MDRs filed through the platform means these connections are not theoretical. They run in production at scale.

‍