Guide · FDA MAUDE device reports
Understanding FDA Device Reports: What MAUDE Data Actually Shows
PlainHospital's device safety section draws on the FDA's MAUDE database, the largest collection of medical device adverse event reports in the world.
PlainHospital's device safety section draws on the FDA's MAUDE database, the largest collection of medical device adverse event reports in the world. But raw event counts can be deeply misleading without context. This guide explains how to interpret the data responsibly.
A device with 10,000 adverse event reports may be safer than one with 100 reports, if the first device is used in millions of patients and the second in only thousands. Raw report counts measure visibility, not risk. Always interpret MAUDE data relative to device usage volume and in consultation with your healthcare provider.
What MAUDE Is and What It Is Not
The MAUDE database is a passive surveillance system, it collects reports as they are submitted but does not actively investigate whether each reported event was actually caused by the device. A report that a patient died while using a device does not mean the device caused the death. The patient may have died from their underlying condition, from a surgical complication, or from an entirely unrelated cause. The report simply documents that an adverse event occurred in association with the device.
This distinction is critical. MAUDE is a signal detection tool, the FDA uses it to identify patterns that warrant further investigation. A sudden spike in reports for a specific device, or an unusual cluster of a specific problem type, may trigger the FDA to open a formal investigation, issue a safety communication, or require the manufacturer to conduct a study. But the MAUDE data itself does not constitute a safety finding.
How to Interpret Report Counts
What it tells you: Report counts provide a rough measure of the volume of adverse events associated with a device. On PlainHospital's device pages, you can see total reports, death reports, injury reports, and malfunction reports for each device. High-level breakdowns by event type, patient outcome, and product problem help characterize the nature of the reports.
What it doesn't tell you: Raw counts cannot be compared across devices without knowing how many of each device are in use. A device used in 1 million patients with 5,000 reports has a very different safety profile than one used in 10,000 patients with 5,000 reports, but the MAUDE summary for both shows "5,000 reports." The denominator (devices in use) is not included in MAUDE and is often not publicly available.
How to use it: Use MAUDE data as one input, not the final answer. Look at trends over time, a device with increasing annual reports may reflect growing usage or an emerging safety issue. Look at the types of problems reported, device malfunctions are different from patient injuries. Browse device profiles on PlainHospital and discuss any concerns with your healthcare provider.
Report Quality and Completeness
What it tells you: Manufacturer reports tend to be more detailed and consistent because manufacturers have regulatory obligations and established reporting processes. Voluntary reports from patients and providers vary widely in completeness and clinical detail.
What it doesn't tell you: Underreporting is a known limitation. Not all adverse events are reported, particularly for voluntary reporters. Healthcare professionals may not file reports for events they do not attribute to the device, or when the reporting process is burdensome. This means MAUDE captures a fraction of actual adverse events, the fraction that someone decided to report.
What This Means for You: A Practical Framework
Step 1, Look up the device. Search for any device on PlainHospital's device safety pages. Review the total report count, the breakdown by event type (death, injury, malfunction), and the trend over time.
Step 2, Look at problem types, not just counts. A device with 1,000 malfunction reports and 10 injury reports has a very different profile than one with 1,000 injury reports. The "Top Product Problems" section on each device page shows what types of issues are being reported.
Step 3, Check for FDA actions. If the FDA has identified a safety concern with a device, it issues safety communications, recalls, or labeling changes. Check the FDA Recalls and Safety Alerts page for any active actions on the device you are researching.
Step 4, Talk to your healthcare provider. MAUDE data provides context, not conclusions. Your healthcare provider can factor in clinical evidence, your specific medical situation, and device-specific studies that go far beyond what adverse event reports can show. Use the data to ask informed questions, not to make device decisions independently.
Frequently Asked Questions
What is the FDA MAUDE database?
MAUDE collects adverse event reports for medical devices, malfunctions, injuries, and deaths submitted by manufacturers, healthcare facilities, and patients. It contains millions of reports dating back to 1991.
Does a high number of reports mean a device is unsafe?
Not necessarily. Report counts reflect usage volume as much as safety. A widely used device generates more reports even if its failure rate is low. The FDA considers reporting rates relative to usage, not raw counts.
Who submits adverse event reports?
Manufacturers (legally required), user facilities like hospitals (required for deaths/injuries), and voluntary reporters (patients, healthcare professionals) via the FDA's MedWatch system.
Can I use MAUDE data to choose between medical devices?
MAUDE provides context but should not be the sole basis for decisions. The data reflects reported events, not safety rates or comparative effectiveness. Always discuss device options with your healthcare provider.
Sources: FDA, MAUDE Database; FDA, openFDA Device Events API.
Last updated: April 2026
Every figure on PlainHospital is rendered directly from federal source data, no number is typed in by an editor. This page draws directly on federal source data, no figure is typed in by an editor. See our editorial standards & corrections policy, the methodology behind these numbers, or report a data error.