FDA MAUDE Medical Device Adverse Events & Malfunctions Scraper avatar

FDA MAUDE Medical Device Adverse Events & Malfunctions Scraper

Pricing

from $2.10 / 1,000 reports

Go to Apify Store
FDA MAUDE Medical Device Adverse Events & Malfunctions Scraper

FDA MAUDE Medical Device Adverse Events & Malfunctions Scraper

Scrape official FDA MAUDE medical device adverse event reports, malfunctions, patient outcomes, and manufacturer narratives from openFDA. Unverified submissions disclaimer applied.

Pricing

from $2.10 / 1,000 reports

Rating

0.0

(0)

Developer

Groundplane Labs

Groundplane Labs

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Features

Limited permissions

Share

Extract official FDA Manufacturer and User Facility Device Experience (MAUDE) medical device adverse event reports, device malfunctions, patient outcomes, and manufacturer narrative records from openFDA (https://api.fda.gov/device/event.json). Keyless, official FDA integration with optional free API key support.

FDA Regulatory & Legal Disclaimer: MAUDE reports are unverified submissions from manufacturers, health facilities, and voluntary reporters. The submission of an adverse event report does not establish that the device caused or contributed to the adverse event or malfunction. Report counts reflect filing volume only and must never be interpreted as verified defect rates or statistical proof of causation.

This actor is an independent product and is not affiliated with, endorsed by, or sponsored by the US Food and Drug Administration (FDA) or the US Department of Health and Human Services (HHS).

What it does

  • Adverse Event Classifications: Filter across Death, Injury, Malfunction, and Other events.
  • Manufacturer & Brand Intelligence: Search by manufacturer entity name (e.g. Medtronic, Abbott, Boston Scientific) or device brand / generic description.
  • Patient Outcomes & Device Problems: Captures documented clinical outcome codes (e.g. Hospitalization, Required Intervention) and device failure descriptions.
  • Multi-Device Handling: Flattens primary device and patient data while tracking total device counts (deviceCount) and flagging multi-device reports (hasMultipleDevices).
  • Narrative Extraction: Concatenates all FDA Freedom of Information (FOI) narrative text blocks in source order, after privacy scrubbing (see below).
  • Privacy Guard: Output is strictly limited to the fields in the Output table. No reporter, patient, or facility contact fields from the source record are emitted. FOI narrative text is additionally scrubbed before it ships: email addresses, phone numbers, SSNs, street addresses, titled personal names, and signature names that appear next to a phone number are redacted. FDA's own FOI text is already redacted at source for many identifiers (the (b)(6) markers), and the scrubber is a second, pattern-based layer on top of that, not a guarantee that every possible name mention in free text is caught.

Who it's for

  • MedTech Safety & Surveillance Teams: Monitor post-market surveillance signals and product failure trends.
  • Mass Tort & Product Liability Attorneys: Track report volume, adverse event descriptions, and manufacturer narrative disclosures for medical device litigation.
  • Healthcare Risk Managers: Review device operator types (e.g. Health Professional vs. Lay User/Patient) and clinical intervention codes.
  • Medical Device Competitor Analysts: Benchmark complaint filing patterns across competing product lines.

Input

FieldTypeDefaultDescription
eventTypesarray["Death", "Injury", "Malfunction"]Adverse event classifications. Empty array queries all event types.
manufacturerNameKeywordstring""Filter by manufacturer or sponsor name keyword (e.g. Medtronic).
brandOrGenericDeviceNamestring""Filter by commercial brand name or generic clinical device description.
dateReceivedFromstring60 days before run dateEarliest FDA receipt date (YYYY-MM-DD or YYYYMMDD).
dateReceivedTostringRun dateLatest FDA receipt date (YYYY-MM-DD or YYYYMMDD).
openFdaApiKeystring (secret)""Optional free openFDA API key for higher rate limits (240 req/min vs 40 req/min).
maxItemsinteger1000Maximum MAUDE report records to deliver.

Example input

{
"eventTypes": ["Injury", "Malfunction"],
"manufacturerNameKeyword": "Medtronic",
"brandOrGenericDeviceName": "defibrillator",
"maxItems": 1000
}

Output

One row per MAUDE Master Device Report (MDR).

FieldTypeDescription
mdrReportKeystringUnique FDA MAUDE Master Device Report (MDR) identifier.
reportNumberstring or nullOfficial FDA report tracking number.
dateReceivedstringDate report was received by the FDA (YYYY-MM-DD).
dateOfEventstring or nullDate adverse event or malfunction occurred (YYYY-MM-DD).
eventTypestring or nullEvent classification (Death, Injury, Malfunction).
adverseEventFlagstring or nullY if adverse clinical event occurred, otherwise N.
productProblemFlagstring or nullY if product malfunction occurred, otherwise N.
manufacturerNamestring or nullDevice manufacturer or corporate sponsor entity.
brandNamestring or nullCommercial / proprietary trade name of the device.
genericNamestring or nullGeneric clinical device descriptor.
modelNumberstring or nullDevice model or catalog number.
lotNumberstring or nullManufacturing lot or batch number.
deviceOperatorstring or nullOperator during event (HEALTH PROFESSIONAL, LAY USER/PATIENT).
deviceCountintegerTotal number of devices associated with this event report.
hasMultipleDevicesbooleanTrue if more than one device was documented in the report.
patientOutcomeCodesarray of stringsDocumented clinical outcomes (e.g. Hospitalization, Required Intervention).
deviceProblemDescriptionsarray of stringsDocumented device problems and failure modes.
foiNarrativeTextstring or nullConcatenated FDA FOI narrative descriptions.

Sample row (real, live openFDA data)

{
"mdrReportKey": "50555082",
"reportNumber": "2649622-2026-25953",
"dateReceived": "2026-09-02",
"dateOfEvent": "2026-08-13",
"eventType": "Injury",
"adverseEventFlag": "Y",
"productProblemFlag": "Y",
"manufacturerName": "Medtronic Puerto Rico Villalba",
"brandName": "Sprint Quattro Secure MRI SureScan",
"genericName": "IMPLANTABLE CARDIOVERTER DEFIBRILLATOR (NON-CRT)",
"modelNumber": "694765",
"lotNumber": null,
"deviceOperator": "LAY USER/PATIENT",
"deviceCount": 1,
"hasMultipleDevices": false,
"patientOutcomeCodes": [
"Required Intervention",
"H"
],
"deviceProblemDescriptions": [
"Over-Sensing"
],
"foiNarrativeText": "It was reported that the Right Ventricular (RV) lead triggered a Lead Integrity Alert (LIA) due to High Rate Non-Sustained episodes and Sensing Integrity Counter (SIC). The RV lead was capped and replaced. No patient complications have been reported as a result of this event."
}

Source and update cadence

Source: the official openFDA device adverse event endpoint (https://api.fda.gov/device/event.json), keyless with an optional free openFDA API key. MAUDE reports are not real-time. FDA receives reports continuously, but published records carry a lag of about one month: as of 2026-11-01, the newest date_received in the endpoint is 2026-09-30 and the endpoint metadata was last updated 2026-10-13. For that reason the default window is 60 days (not the 30 days a naive reading of the cadence would suggest): a 30-day window returns zero rows for much of each month. The actor also probes a trailing 90-day baseline on every run and fails loudly if that baseline is empty, so a source outage or schema change is never reported as a clean zero-match run.

Canary input

{
"eventTypes": ["Injury"],
"manufacturerNameKeyword": "Medtronic",
"maxItems": 5
}

Expected: 5 rows, status Complete, every row with a Medtronic manufacturer name and a populated mdrReportKey and dateReceived.

Troubleshooting

  • Zero matches: a narrow filter (an exact manufacturer or brand spelling, or a short recent window) can legitimately match nothing, especially given the publication lag above. The run reports Complete: 0 rows matched buyer criteria. Widen the date window before assuming breakage.
  • PARTIAL about the 25,000-result ceiling: openFDA paging stops at 25,000 results. That reason appears only when you requested more than 25,000 rows (maxItems above 25,000) and the query matched more than that. Narrow the date window to page the remainder in a second run.
  • PARTIAL about skipped records or unparseable event dates: the source returned records whose core fields or event dates did not parse. The status states how many. If this keeps happening, please open an issue on this actor's Issues tab and we'll fix it fast.
  • Rate limits: keyless runs share openFDA's lower per-IP limits. Supplying your own free openFDA key raises them. The actor retries 429 and 5xx responses with backoff.

Changelog

  • 0.1.1 (2026-11-01, review fixes): FOI narratives are privacy-scrubbed before shipping (emails, phones, SSNs, street addresses, titled and signature names redacted). The 25,000-result ceiling now produces a PARTIAL only when the requested row count actually exceeds the ceiling (previously any query matching over 25,000 rows was marked PARTIAL even when every requested row was delivered). Skipped records and unparseable event dates are now disclosed as PARTIAL reasons at any sample size, and a core-field format drift fails loudly even on small runs. Restored the .actor metadata files (actor, input, dataset, and output schemas), which were empty in the 0.1 delivery. Baseline messages now correctly say 90 days.
  • 0.1.0 (2026-11-01): Initial build. openFDA MAUDE device/event endpoint, limit/skip paging within the 25,000-result ceiling, 60-day default window and 90-day baseline probe sized to the MAUDE publication lag, FDA unverified-submissions disclaimer.