FDA MAUDE Database: Complete Guide to Medical Device Adverse Event Reports

The FDA's MAUDE database — Manufacturer and User Facility Device Experience — is the largest publicly accessible repository of medical device adverse event reports in the world. It contains millions of records spanning decades, covering device malfunctions, serious injuries, and deaths reported by manufacturers, healthcare facilities, importers, and voluntary reporters.

For regulatory affairs professionals, quality engineers, and post-market surveillance teams, MAUDE is an indispensable tool. It is also a deeply imperfect one. Understanding both its power and its limitations is essential for anyone who relies on it for safety signal detection, competitive intelligence, or regulatory compliance.

This guide covers everything you need to work with MAUDE effectively: the regulatory framework behind it, the database structure, practical search strategies, known limitations, and how to build an ongoing monitoring program.

What Is MAUDE and Why It Matters

MAUDE is maintained by the FDA's Center for Devices and Radiological Health (CDRH). It collects Medical Device Reports (MDRs) — individual adverse event reports submitted under 21 CFR Part 803. Each report describes an incident involving a medical device that resulted in, or may have contributed to, a death, serious injury, or device malfunction.

The database is publicly searchable at accessdata.fda.gov/scripts/cdrh/cfdocs/cfmaude/ and is also accessible programmatically through the openFDA API at the /device/event endpoint.

MAUDE matters for several reasons:

Post-market surveillance obligation. Manufacturers are required under 21 CFR Part 803 to monitor and report adverse events. MAUDE is where those reports live. If your competitor's device is generating a cluster of malfunction reports, that is regulatory intelligence. If your own device is generating reports, that demands investigation.

Early warning system for recalls. A spike in MAUDE reports for a specific device model or failure mode is frequently a precursor to an FDA recall action. Organizations that monitor MAUDE proactively can identify emerging safety signals before the FDA acts.

Regulatory submissions. MAUDE data is routinely referenced in 510(k) submissions, PMA applications, and De Novo requests — both to characterize the safety profile of predicate devices and to contextualize the clinical risk landscape for a device category.

Litigation and risk management. MAUDE reports are used in product liability litigation, insurance risk assessments, and hospital purchasing decisions. The data is public and searchable by anyone.

MDR Reporting Requirements: Who Must Report and When

Medical Device Reporting is governed by 21 CFR Part 803. The reporting obligations differ by entity type:

Reporter Type	What Must Be Reported	Reporting Deadline	Regulatory Basis
Manufacturers	Deaths, serious injuries, and malfunctions that could cause or contribute to death or serious injury	30 calendar days (5 days for events requiring remedial action)	21 CFR 803.50
Importers	Deaths and serious injuries	30 calendar days	21 CFR 803.40
Device User Facilities (hospitals, nursing homes)	Deaths (to FDA and manufacturer) and serious injuries (to manufacturer only)	10 work days	21 CFR 803.30
Voluntary Reporters (healthcare professionals, patients, consumers)	Any adverse event — no obligation, but encouraged	No deadline	MedWatch Form 3500

Key Definitions

Death: An event where the device may have caused or contributed to a death.

Serious Injury: An injury or illness that is life-threatening, results in permanent impairment or damage to body function/structure, or necessitates medical or surgical intervention to preclude such outcomes.

Malfunction: A failure of a device to meet its performance specifications or otherwise perform as intended. Manufacturers must report malfunctions only if the malfunction could cause or contribute to a death or serious injury if it were to recur.

The 5-Day Reporting Rule

Under 21 CFR 803.53, manufacturers must submit a 5-day report when they become aware of an event that requires remedial action to prevent an unreasonable risk of substantial harm to public health, or when the FDA has requested 5-day reports for a specific device type. This is a higher-urgency pathway than the standard 30-day timeline.

Supplemental Reports

When a manufacturer receives new information about a previously reported event, a supplemental report must be submitted within 30 days. This means a single incident can generate multiple MAUDE entries over time, which is important to understand when analyzing report counts.

MAUDE Database Structure: Key Data Fields

Each MAUDE record contains several categories of information. Understanding these fields is critical for effective searching and analysis.

Event Information

Field	Description
MDR Report Key	Unique identifier for each report
Event Date	Date the adverse event occurred
Report Date	Date the report was submitted to the FDA
Event Type	Death, Injury, Malfunction, or Other
Report Source	Manufacturer, User Facility, Importer, or Voluntary

Device Information

Field	Description
Brand Name	Commercial name of the device
Generic Name	Generic device description
Product Code	FDA three-letter product classification code
Manufacturer Name	Name of the device manufacturer
Model Number	Specific model or catalog number
Lot Number	Production lot identifier (when available)
Device Class	FDA device classification (I, II, or III)

Patient and Event Outcome

Field	Description
Patient Outcome	Death, life-threatening, hospitalization, disability, required intervention, other
Date of Event	When the incident occurred
Single Use Device?	Whether the device was a single-use product
Previous Use Code	Whether the device had been previously used

Narrative Fields

The Event Description and Manufacturer Narrative are free-text fields containing the details of what happened. These are often the most valuable — and most inconsistent — fields in the database. The event description is typically written by the initial reporter, while the manufacturer narrative contains the manufacturer's assessment, investigation findings, and any corrective actions.

How to Search MAUDE Effectively

The FDA Web Interface

The MAUDE search interface at accessdata.fda.gov allows searching by:

• Brand name
• Product code (three-letter FDA code)
• Manufacturer name
• Event type (death, injury, malfunction)
• Date range
• MDR report number

Practical tips for the web interface:

Use product codes, not brand names. Brand names are entered inconsistently by reporters — misspellings, abbreviations, and outdated names are common. Product codes are standardized. Look up the correct product code for your device type using the FDA's Product Classification Database before searching MAUDE.

Search broad, then filter. Start with the product code and a wide date range, then narrow by event type or manufacturer. Starting too narrowly risks missing relevant reports.

Read the narratives. The structured fields (event type, product code) give you the volume picture, but the free-text narratives contain the actual clinical detail. A "malfunction" event type could describe anything from a minor software glitch to a catastrophic device failure. Only the narrative tells you which.

Watch for date field distinctions. The "event date" (when the incident occurred) and "report date" (when the report was submitted) can differ by months or even years. When analyzing trends, decide which date field is appropriate for your analysis.

The openFDA API

For systematic analysis, the openFDA API (api.fda.gov/device/event) is far more powerful than the web interface. Key capabilities:

Structured queries. Filter by any combination of fields: product code, manufacturer, event type, date range, patient outcome, device class.

Aggregation (count). The API supports count queries that return the number of reports matching a filter, grouped by a specified field. For example, you can count the number of malfunction reports by product code over the last 12 months.

Pagination. The API returns up to 100 results per request with skip/limit pagination, allowing you to retrieve large datasets programmatically.

Example query — all death reports for a specific product code in 2025:

https://api.fda.gov/device/event.json?search=device.product_code:"ABC"+AND+event_type:"Death"+AND+date_received:[20250101+TO+20251231]&limit=100

Limitation: The openFDA API does not always contain the most recent reports. There is a lag — sometimes days, sometimes weeks — between when a report is submitted and when it appears in the API. For real-time monitoring, the API alone is insufficient.

Advanced Search Strategies

Trend analysis. Pull monthly report counts for your product code over a 3–5 year window. A sudden increase in malfunction reports — even without deaths or injuries — can indicate an emerging quality issue.

Competitive benchmarking. Compare adverse event volumes across competing devices in the same product code. Normalize by estimated installed base or units sold (if available from 510(k) summaries or company filings) to compare rates rather than raw counts.

Failure mode clustering. Export narrative text for a set of reports and look for recurring keywords: "battery," "software," "fracture," "leak," "alarm." Manual review is time-consuming but reveals patterns that structured fields miss.

Predicate device research. Before submitting a 510(k), search MAUDE for adverse events associated with your predicate device. FDA reviewers may ask about the safety history of your predicate — knowing that data in advance strengthens your submission.

Limitations of MAUDE Data

MAUDE is a powerful resource, but it has well-documented limitations that every user must understand:

Underreporting. Not all adverse events are reported. Voluntary reporters (healthcare professionals, patients) have no legal obligation to report. Even mandatory reporters (manufacturers, facilities) may underreport due to unawareness, misclassification of events, or judgment calls about whether a malfunction "could" cause harm. The FDA itself states that MAUDE data "cannot be used to establish rates of events" or "to compare event rates between devices."

No denominator. MAUDE contains numerator data only — the number of reports. It does not contain the number of devices in use, the number of procedures performed, or any other denominator that would allow calculation of event rates. A device with 500 malfunction reports and 2 million units in the field may be far safer than a device with 50 reports and 10,000 units in the field.

Data quality and consistency. Free-text narratives vary enormously in detail and accuracy. Product names are misspelled. Model numbers are missing. Event descriptions range from detailed clinical accounts to single-sentence summaries like "device malfunctioned." Manufacturer narratives sometimes contain substantive investigation findings; other times they state only "investigation ongoing."

Duplicate and supplemental reports. A single adverse event can generate multiple MAUDE entries — the initial report, supplemental reports with updated information, and reports from different entities (manufacturer and user facility reporting on the same incident). Without careful deduplication, raw report counts overstate event volume.

Reporting lag. The time between when an event occurs, when it is reported, and when it appears in MAUDE can span months. Mandatory reporters have 30-day deadlines, but investigations take time, and database updates are not instantaneous. MAUDE is not a real-time system.

Causation vs. correlation. A MAUDE report indicates that a device was involved in an adverse event — it does not establish that the device caused the event. Many reports describe incidents where patient comorbidities, user error, or other factors contributed to the outcome. The presence of a report does not equal a confirmed device defect.

Setting Up Ongoing MAUDE Monitoring

For organizations with post-market surveillance obligations — which includes every manufacturer of a marketed medical device — periodic MAUDE review is not optional. Here is how to structure an ongoing monitoring program:

Define Your Monitoring Scope

Identify the product codes, brand names, manufacturer names, and competitor devices that should be included in your monitoring. For most organizations, this includes:

• Your own marketed devices (all product codes)
• Predicate devices referenced in your 510(k) or PMA submissions
• Direct competitor devices
• Component or accessory devices used with your products

Set Monitoring Frequency

Device Risk Level	Recommended MAUDE Review Frequency
Class III (high risk)	Weekly
Class II (moderate risk)	Bi-weekly to monthly
Class I (low risk)	Monthly to quarterly
Competitor / predicate devices	Monthly

Build Alerting Criteria

Not every MAUDE report requires action. Define escalation thresholds:

• Immediate escalation: Any death or serious injury report involving your own device
• Priority review: Cluster of 3+ malfunction reports with the same failure mode within 30 days
• Routine review: Individual malfunction reports, reports involving competitor devices
• Trend watch: Month-over-month increase in total report volume exceeding 25%

Document and Integrate

MAUDE monitoring findings should feed into your:

• Post-market surveillance reports (required under EU MDR for CE-marked devices)
• Periodic Safety Update Reports (PSURs) where applicable
• CAPA system when trends suggest a corrective action is needed
• Management review as part of your QMS
• Risk management file per ISO 14971

The Manual Monitoring Challenge

Doing this manually — logging into the MAUDE web interface or running openFDA queries weekly, reviewing results, cross-referencing with your device portfolio, and documenting findings — is feasible for a single product. For organizations with dozens of product codes, multiple markets, and competitive monitoring requirements, the manual approach does not scale.

From MAUDE to Action: Integrating Adverse Event Data

MAUDE data becomes actionable when it is combined with other regulatory intelligence sources:

MAUDE + FDA Recalls: A MAUDE report cluster followed by a recall action confirms the safety signal. Monitoring both in parallel provides earlier warning than monitoring either alone.

MAUDE + FDA Enforcement Reports: Weekly enforcement reports may reference MAUDE data as the basis for a recall classification decision.

MAUDE + International Vigilance Data: Adverse events reported to other regulators (Health Canada, TGA, MHRA, Swissmedic) may describe the same failure modes seen in MAUDE. Cross-referencing across jurisdictions strengthens signal detection.

MAUDE + Field Safety Corrective Actions (FSCAs): For devices also marketed in the EU, MAUDE events may correspond to FSCA notifications filed through EUDAMED or national competent authority databases.

Conclusion

The FDA MAUDE database is the foundation of medical device adverse event surveillance in the United States. It provides unmatched visibility into device safety issues — but only for those who know how to navigate its structure, work around its limitations, and maintain consistent monitoring over time.

Effective MAUDE use requires understanding MDR reporting requirements, knowing which data fields to query and which to treat with caution, applying systematic search strategies, and integrating MAUDE findings into your broader post-market surveillance and quality systems.

---

MedFlux aggregates MAUDE data alongside adverse event reports, recalls, and safety alerts from 27 regulators worldwide — delivering filtered, device-specific intelligence to your team in real time. Instead of running manual MAUDE queries, let MedFlux surface emerging signals across every market where your devices are sold.