What this guide covers
What is MAUDE?
MAUDE (the Manufacturer and User Facility Device Experience database) is the FDA's store of medical device reports (MDRs) describing suspected device-associated deaths, serious injuries and malfunctions. Reports come from mandatory reporters (manufacturers, importers and device user facilities such as hospitals) and voluntary reporters (health professionals, patients and consumers). The FDA's data files go back to the early 1990s (the web search covers the last ten years), and openFDA shows 2.9 million reports received in 2025.
Why monitor it
For a medical device manufacturer, MAUDE monitoring serves several purposes at once:
- Post-market surveillance. It's a primary external data source for your PMS system under EU MDR, and a standard input to complaint handling and risk management under the FDA's quality system requirements (21 CFR 820). See our guide to EU MDR Articles 83–92.
- Signal detection. A cluster of similar reports can be the earliest warning of a problem with your device, or with a component or material you rely on.
- Competitor and category intelligence. Because reports are public, you can watch similar devices (by product code) for problems that may affect your own design.
- Evidence for your reports. MAUDE findings feed the analyses behind your PMS Report or PSUR and any trend reporting.
Three ways to access MAUDE
| Method | Best for | Update cadence |
|---|---|---|
| MAUDE web search (accessdata.fda.gov) | Ad-hoc lookups, reading individual narratives | Monthly |
| openFDA API (api.fda.gov/device/event.json) | Automated, repeatable queries and dashboards | Weekly |
| Bulk data downloads (zipped JSON) | Building your own database or bulk analysis | Periodic |
The web search is fine for the occasional lookup. For regular monitoring, use the openFDA API or the bulk files, because they can be queried on a schedule.
How to search the MAUDE database
The MAUDE search page on the FDA website has two modes.
Simple search looks for any word or phrase that appears in a report received in one year. You can type a single word, an exact phrase in quotes, or several words joined by "and" (for example balloon and leak). You can also paste a device's UDI into the box.
Advanced search lets you fill in specific fields over a date range. The fields that matter most for a manufacturer are:
- Product code, to find every device of the same type, from any maker
- Manufacturer and brand name, to narrow it to your own devices
- Model number, when you need one specific model
- Event type (death, injury, malfunction or other)
- Date report received by FDA, to set the window you're reviewing
Click a result to read the full report, including the event narrative and the manufacturer's response. That narrative is usually where the useful detail is.
Two limits catch people out. Both search modes return at most 500 results, so a broad search can be cut short without much warning. Narrow the date range or add a product code until you're under the limit. And the web search only covers the last ten years and is refreshed once a month, with reports received up to the end of the previous month. For older reports, or anything larger, use the FDA's MDR data files or the openFDA API below.
Step 1: Set your monitoring scope
The most common mistake is searching by one brand name and assuming you've covered everything. Define your scope in three ways:
- Brand and trade names, including old names, sub-brands and common misspellings. Small differences in a name change what a search returns.
- Manufacturer names, including legacy entities, acquired companies and distributor names that may appear on reports.
- FDA product codes. These three-letter classification codes are the most reliable way to find your device type, and to include similar devices from other makers.
A good scope covers both your own devices and the similar devices that share their product codes.
Step 2: Build a repeatable workflow
Monitoring means running the same steps every time. A workable routine looks like this:
- Query on a schedule. Because the API refreshes weekly, a weekly pull keyed to
date_receivedcatches new reports promptly. - De-duplicate. A single event can generate an initial report plus follow-ups; group them by report number so you don't count one event many times.
- Triage by event type. Separate deaths and serious injuries from malfunction-only reports, and read the narrative field for context.
- Assess for signals. Compare against your baseline. Is this a new failure mode, or a rise in an existing one?
- Document and route. Log findings into your complaint/PMS system, and where warranted, feed CAPA, trend reporting and your PSUR/PMSR.
Using the openFDA API
The device adverse-event endpoint is:
https://api.fda.gov/device/event.json
The most useful search fields are device.brand_name, device.manufacturer_d_name, device.device_report_product_code, event_type (Death / Injury / Malfunction), and date_received. A query for one manufacturer's reports received in a date window looks like:
https://api.fda.gov/device/event.json?search=
device.manufacturer_d_name:"ACME+MEDICAL"
+AND+date_received:[20260101+TO+20260630]&limit=100
To get counts instead of raw records (for example, reports by event type), use the count parameter (note the .exact suffix, required when counting text fields):
...&count=event_type.exact
date_received rather than date_of_event, which is often blank. The API returns at most 1,000 records per query, so split multi-year pulls into monthly or quarterly windows. The device.model_number and device.catalog_number fields are searchable, but they are free text as reported, so expect spelling variants; combining them with manufacturer and product code gives the cleanest results..exact rule, pagination past the 25,000-record limit, API keys and the common pitfalls.Limitations you must respect
MAUDE is a passive surveillance system, and the FDA is clear about its limits. Misreading it creates compliance risk of its own:
- It doesn't prove causation. A report existing is not an admission that the device caused the event.
- You can't calculate rates from it. There's no denominator (units in use), so raw counts can't establish incidence or be used to rank devices against each other.
- Data is often incomplete or unverified, and can be duplicated, delayed or biased. Some text is redacted as
(b)(4)or(b)(6). - There's reporting lag. Manufacturer MDRs arrive on FDA timelines (generally within 30 days, sooner for the most serious events), so recent weeks are always incomplete.
Common questions about MAUDE
What does MAUDE stand for?
Manufacturer and User Facility Device Experience. It is the FDA database of medical device reports: suspected deaths, serious injuries and malfunctions reported by manufacturers, importers, hospitals and the public.
Is the MAUDE database free to use?
Yes. The web search, the openFDA API and the bulk data files are all free. An openFDA API key is also free and raises the daily request limit.
How often is MAUDE updated?
The web search is updated monthly, with reports received up to the last day of the previous month. The openFDA device event data is refreshed weekly.
Can MAUDE reports show how often a device fails?
No. MAUDE has no figures for how many devices are in use, so you can't work out an incidence rate from it, and a report on its own doesn't show that the device caused the event. Use it to spot and investigate possible problems.
Why can't I find a report I know was submitted?
It may be too recent, since reports can take weeks to appear. It may be filed under a different brand or manufacturer name, or a misspelling. Searching by product code and a wider date range usually finds it.
From monitoring to compliance
MAUDE is one source among several. Recalls, clinical-trial registries, literature and the open market matter too, but MAUDE is one of the most useful. It also only covers the United States. If you sell into the UK, Canada, the EU or Switzerland, each of those regulators publishes information MAUDE never will (see our guide to monitoring the regulators beyond the FDA). Keeping all of this going is the difficult part: querying every source on a schedule, removing duplicates, checking each result against your portfolio, and keeping a timestamped record so you can answer when an auditor asks "how did you know, and when?"
When this is done by hand across separate tools, gaps appear. Automating it, with MAUDE and the other sources queried on a schedule, matched to your device lines and logged, gives you monitoring that stays current and feeds your PMS plan, PSUR or PMSR and trend reporting.
See what MAUDE is saying about your devices
Book a demo and we'll run MedFortis against your device lines to show you, live, what's being reported across FDA MAUDE, other regulator sources and the resale market. It's the routine in this guide, automated.
Book a Demo →Key takeaways
- MAUDE holds FDA medical device reports of suspected deaths, injuries and malfunctions with data files going back to the early 1990s.
- Access it three ways: the web search (monthly), the openFDA API (weekly) or bulk downloads. Use the API to automate.
- Scope by brand names, manufacturer names and product codes, and watch similar devices as well as your own.
- Run the same steps on a schedule: query, de-duplicate, triage, assess for signals, document and route.
- Never use raw MAUDE counts to calculate rates or rank devices. Use it to detect and investigate signals.