Practical guide

FDA MAUDE Database: How to Search & Monitor Adverse Events

By Kieran Redington, Founder of MedFortis Updated 23 October 2026 ~8 min read

The FDA's MAUDE database is one of the best public sources of real-world information about how medical devices perform, and a standard input to post-market surveillance. It's also large, messy and easy to misread. This guide covers how to access it, how to scope and run a repeatable monitoring workflow, and the limitations you must respect.

Short on time? MedFortis automates this routine across MAUDE and other regulators in a single device lookup. See how it works →
Just need the database? You can run an FDA MAUDE database search directly at accessdata.fda.gov (updated monthly), or query it programmatically via the openFDA API. The rest of this guide covers turning one-off searches into a repeatable monitoring workflow.

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:

Three ways to access MAUDE

MethodBest forUpdate cadence
MAUDE web search (accessdata.fda.gov)Ad-hoc lookups, reading individual narrativesMonthly
openFDA API (api.fda.gov/device/event.json)Automated, repeatable queries and dashboardsWeekly
Bulk data downloads (zipped JSON)Building your own database or bulk analysisPeriodic

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.

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:

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:

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:

  1. Query on a schedule. Because the API refreshes weekly, a weekly pull keyed to date_received catches new reports promptly.
  2. 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.
  3. Triage by event type. Separate deaths and serious injuries from malfunction-only reports, and read the narrative field for context.
  4. Assess for signals. Compare against your baseline. Is this a new failure mode, or a rise in an existing one?
  5. Document and route. Log findings into your complaint/PMS system, and where warranted, feed CAPA, trend reporting and your PSUR/PMSR.
Prefer not to build this yourself? MedFortis automates this routine (scheduled queries, de-duplication, matching against your portfolio and a timestamped evidence log) across MAUDE and other regulator sources (including MHRA, Health Canada, Swissmedic and EUDAMED) in a single device lookup. See how the lookup works →

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
Practical tips: filter by 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.
Rate limits: without an API key, openFDA allows 240 requests per minute and 1,000 per day per IP address. A free API key raises the daily limit to 120,000 requests, so get one for any scheduled monitoring.
Going deeper on the API? Our openFDA Device Event API guide covers the full query language, counting and the .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:

In short: use MAUDE to detect and investigate signals, not to calculate event rates or compare the safety of devices.

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.
This article is provided for general information only and is not legal or regulatory advice. API details and data cadences reflect openFDA/FDA documentation at the time of writing and may change; always confirm against the current openFDA documentation and consult a qualified regulatory professional for your specific devices.