Glossary
Device malfunction
Device malfunction is one of the three reportable outcome types in a medical device report, alongside injury and death, meaning the device failed to perform as intended without necessarily harming a patient. Malfunction-only reports make up a large share of the 25,711,469 records in the openFDA Device Adverse Events (MAUDE) API.
What is device malfunction?
A device malfunction is the reportable outcome type in which a device failed to perform as intended - one of the three outcomes a medical device report (MDR) can record, alongside injury and death. A malfunction report does not assert patient harm; it asserts the device did not do what it was supposed to do.
In the catalog the term is structural, not descriptive. The openFDA Device Adverse Events (MAUDE) API record describes its coverage as 'covering device malfunctions, injuries and deaths', with one record per adverse event report and nested arrays per device and per patient involved.
Because malfunctions do not require harm, they dominate the volume - and they are the earliest signal.
Why does Device malfunction matter when choosing a dataset?
Malfunction reports are the largest and noisiest part of device safety data, and mishandling them cuts both ways:
- Volume without harm is easy to over-read. A malfunction count is not an injury count; summing all 25.7M MAUDE records inflates apparent risk.
- Filtering to injuries hides signal. The record's tags include 'recalls' and 'device-safety' because malfunctions often trigger them; injuries-only views remove the early warning.
- Event-level records need device-level joins. Coverage is 'one record per adverse event report with per-device detail' - a report can involve multiple devices, so naive row counts misstate device exposure.
How do you evaluate Device malfunction in a data source?
Use the report type as your first filter, deliberately:
- Filter by event type explicitly. The MAUDE record covers malfunctions, injuries and deaths as distinct outcomes; state which your analysis includes before quoting a count against the 25,711,469-record total.
- Respect the nested structure. One record per adverse event report with arrays per device and per patient means device-level analysis needs array expansion, not row counts.
- Pair with the recall record. The openFDA Device Recalls API holds the enforcement actions that malfunction clusters often precede - the two together are the surveillance loop.
Related terms
These entries cover the reporting and enforcement records malfunctions feed into:
- MAUDE - the FDA's Manufacturer and User Facility Device Experience database of adverse event reports, exposed through the openFDA Device Adverse Events API with 25,711,469 records as of the 2026-08-11 data load.
- Medical Device Report (MDR) - the mandatory report filed with the FDA when a device may have caused or contributed to a death, serious injury or malfunction; each MDR is one MAUDE record.
- Device recall - a correction or removal action addressing a violation of FDA law, cataloged in the openFDA Device Recalls API as the enforcement-side counterpart to adverse event reporting.
Frequently asked questions
What counts as a device malfunction?
A device failing to perform as intended, reported as one of three MDR outcome types alongside injury and death. No patient harm is required for a malfunction report to be filed.
How many device malfunction records exist?
The openFDA Device Adverse Events (MAUDE) API held 25,711,469 records as of the 2026-08-11 data load, covering malfunctions, injuries and deaths, with several hundred thousand new reports added per year.
Are malfunction reports a signal of device risk?
Yes, as an early one. Malfunctions often precede recalls - the openFDA Device Recalls API holds the enforcement actions - but a malfunction count alone is not an injury count and should not be presented as one.
Datasets containing this field
Datasets containing Device malfunction
6 datasets carry device malfunction in the catalog. Open one, count the fields, judge for yourself.
openFDA Device Adverse Events (MAUDE) API
mdr_report_key · event_type · date_of_event …+16 more
openFDA Device Registration & Listing API Data
registration.registration_number · registration.fei_number · registration.status_code …+13 more
WHO Medical Devices – Definitions and Policy Repository
IndicatorCode · IndicatorName · SpatialDim …+6 more
ClinicalTrials.gov API v2 - Studies Database
FDA Medical Devices Portal
database_title · description · updated …+3 more
Hugging Face Datasets Hub
Every listing shows the field dictionary, sample rows, and coverage before you commit. API, files, or your warehouse. Daily, weekly, or hourly.
Get sample rows