Open access · No login · Nothing leaves your browser

Twenty million FDA medical device
adverse event reports, analysable
by anyone.

MaudeDash turns the U.S. FDA's Manufacturer and User Facility Device Experience database — the national reporting system for medical devices that injure or kill patients — into an instrument any clinician, researcher, journalist or regulator can actually use. It is free, it requires no account, and every calculation runs on your own computer.

Reports
20,746,963
Years
1991–2024
Product codes
3,763
Manufacturers
26,344

Data current to 2024-12-31. Published in Surgical Neurology InternationalPubMed 42232423.

Why this exists

When a medical device fails — a pump that over-delivers insulin, a spinal screw that loosens, a monitor that misses an alarm — manufacturers, hospitals and patients file a report with the FDA. Those reports accumulate in MAUDE, a public database of more than twenty million records. It is one of the few windows the public has into how devices behave after approval.

In practice that window is nearly opaque. The FDA distributes MAUDE as a set of raw pipe-delimited text files totalling tens of gigabytes, split across several tables that must be joined correctly before any question can be answered. The official web search interface returns individual reports, not statistics. Researchers who want a rate, a trend, or a confidence interval must first spend weeks building a pipeline — and most of the published analyses that result are not reproducible, because the cohort definition lives in a script nobody else has.

MaudeDash removes that barrier. Define a cohort in a sidebar; get harm rates with confidence intervals, subgroup forest plots, trend tests, and disproportionality signal screening in seconds. Every analysis ships with the exact filter that produced it and an auto-generated methods paragraph, so the work is reproducible by construction.

Clinically meaningful outcomes

Patient harm is classified using the FDA's own seven categories under 21 CFR 803.3 — death, life-threatening, hospitalization, disability, congenital anomaly, required intervention, other — not just the coarse event type most tools stop at.

Statistics that survive review

Wilson score intervals, Cochran-Armitage and Mann-Kendall trend tests, Fisher's exact, and dual frequentist and Bayesian signal detection with false-discovery-rate control. Cross-validated against SciPy on every function.

Search by device, not by code

MAUDE identifies devices by opaque three-letter codes. Type “pedicle screw” or “infusion pump” and MaudeDash finds them, using the device names manufacturers actually recorded in the reports.

Reproducible by default

Every cohort has a shareable URL, an exact SQL filter, and a generated STROBE-style methods paragraph stating the data vintage — so a reviewer can reproduce your number, not just read it.

Honest about its limits

MAUDE is passive surveillance with no denominator. The tool says so on every rate it displays, flags unreliable strata, warns on partial years, and refuses to present proportions as incidence.

Free and open source

MIT licensed, no account, no paywall, no usage limits. The full build pipeline is published so anyone can rebuild the corpus from the FDA's own files and verify the numbers independently.

How it works

MaudeDash has no application server. The site serves static files; your browser does the analysis.

  1. 1

    The FDA's raw files are rebuilt into an analytic table

    Roughly 40 GB of pipe-delimited text is parsed, multi-line narratives are reassembled, and the tables are joined into one row per report. Patient outcome codes are decoded into the seven statutory harm categories.

  2. 2

    That table is compressed 53-fold

    The working database is about 73 GB, most of it a full-text index and duplicated columns no analysis reads. Stripping those leaves 1.4 GB of columnar Parquet — the complete corpus, narratives included, at one fifty-third the size.

  3. 3

    Your browser queries it directly

    A SQL engine compiled to WebAssembly runs inside the page and reads only the byte ranges a query needs. Filtering 2018–2024 never touches the other years; a query on product code never downloads the narratives. A typical session transfers about 14 MB, not 1.4 GB.

🔒
Nothing you do here is transmitted anywhere. Your cohort definition, search terms and results exist only in your browser tab. There is no account system, no database, no analytics script and no cookie. See the privacy statement.

Two editions

The tool on this site is the one most people want. A downloadable edition exists for work that needs the complete corpus on your own machine — and so that anyone can verify these numbers independently.

Browser Edition — nothing to install

Open it and query. All 20.7 million reports, every analysis, narratives to 4,000 characters, CSV export and shareable cohort URLs. Runs entirely in your browser; nothing you search is transmitted.

Open the tool

Research Edition — free download

A Streamlit application you run locally against the full corpus built from the FDA's own files. Adds untruncated multi-part narratives, unlimited cohort exports, and the entire build pipeline with its test suite — so any figure here can be reproduced from source.

How to get it

Both compute identically — the statistical engine exists in Python and in JavaScript, cross-validated against SciPy on every function. Compare the editions in detail →

What MAUDE can and cannot tell you

Stated plainly, because misreading this database is the most common error in the literature that uses it.

⚠️
MAUDE cannot produce a device failure rate. It records reports, not exposures. Nobody knows how many of a given device were implanted or used, so there is no denominator. A count of 500 reports is not a risk, a rate, or a probability — and any figure here expressed as a percentage is a share of reports, never a share of patients or devices.
  • Reporting is incomplete and uneven. Manufacturers must report; hospitals under-report; patients rarely report at all. Volume reflects who is watching as much as what is happening.
  • Publicity distorts the signal. A recall, a lawsuit or a news story reliably produces a spike in reports for a device whose real-world behaviour has not changed.
  • A report is not a finding of fault. A death report records that a death occurred and a device was involved. It is not an FDA determination that the device caused it.
  • Disproportionality signals are hypotheses. They indicate a code appears more often than expected in a cohort. That warrants investigation, never a clinical or legal conclusion.
  • Device-level data begins in 2015 in this build. Earlier reports exist but carry no product code, manufacturer, brand or narrative, so the tool defaults to 2015 onward and says so.
  • The most recent year is usually partial, because the FDA files are captured mid-cycle. The tool flags this rather than letting the drop-off read as a real decline.

MaudeDash is a research instrument. It is not medical advice, not a substitute for clinical judgement, and not a regulatory determination. See the terms of use.

Cite MaudeDash

If MaudeDash contributed to your work, please cite the paper and record the data vintage — MAUDE is revised retroactively, so the same query run later may return different counts.

Porwal M. MaudeDash: an open analytic platform for the FDA MAUDE medical device adverse event database. Surg Neurol Int. 2026. doi:10.25259/SNI_201_2026. Available from: https://maudedash.com (FDA data current to 2024-12-31).