# Medical Device Adverse Event Tracker — FDA MAUDE Reports (`m_ctim/medical-device-adverse-event-tracker`) Actor

Search FDA MAUDE adverse event reports for medical devices by device name and event type (malfunction, injury, death). Raw incident reports, not official recalls, for device safety monitoring.

- **URL**: https://apify.com/m\_ctim/medical-device-adverse-event-tracker.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Medical Device Adverse Event Tracker — FDA MAUDE Reports

Search FDA MAUDE (Manufacturer and User Facility Device Experience)
adverse event reports by device name and event type. These are raw
incident reports — malfunctions, injuries, deaths associated with a
device — not official recalls, and often the earliest public signal of
a device problem.

Built for hospital risk management, device safety teams, and
researchers who want to know what's being reported before it becomes an
official recall.

### Input

```json
{
  "deviceName": "insulin pump",
  "eventType": "all",
  "daysBack": 30,
  "maxResults": 25
}
```

| Field | Type | Description |
|---|---|---|
| `deviceName` | string (optional) | Free-text search across the device's generic name. |
| `eventType` | string | `"all"`, `"Malfunction"`, `"Injury"`, or `"Death"`. Default `"all"`. |
| `daysBack` | number | How many days back from today to search, by date received by FDA. Default `30`, max `365`. |
| `maxResults` | number | Max reports to return, most recently received first. Default `25`, max `100`. |

### Output

One record per report:

```json
{
  "reportNumber": "2124215-2026-35065",
  "eventType": "Injury",
  "dateReceived": "2026-07-01",
  "dateOfEvent": "2026-06-19",
  "deviceGenericName": "PACEMAKER",
  "deviceBrandName": null,
  "manufacturer": "MEDTRONIC",
  "productProblemFlag": true,
  "reporterOccupation": "PHYSICIAN"
}
```

A search with no matching reports returns no items but is still billed
once for the search.

### How it works

Direct calls to the official [openFDA Device Adverse Event
API](https://open.fda.gov/apis/device/event/) (`api.fda.gov`) — no
proxy, no key, no scraping.

**Note:** these are unverified reports submitted by manufacturers,
health professionals, and consumers — FDA publishes them as filed,
without confirming a device caused the reported outcome. Treat volume
and pattern as a signal worth investigating, not proof of a defect.

### Pricing note

Billed per **search**, not per report returned — one charge whether the
search returns 0 reports or 100.

### Related products

- [Product Recall Alert](https://github.com/timmKal01/product-recall-alert) — official FDA drug, food, and device recalls, the confirmed-issue counterpart to this actor's raw incident reports
- [Vehicle Complaint Tracker](https://github.com/timmKal01/vehicle-complaint-tracker) — the same raw-complaints-before-recall pattern for vehicles instead of medical devices

# Actor input Schema

## `deviceName` (type: `string`):

Free-text search across the device's generic name (e.g. "insulin pump", "pacemaker", "hip implant"). Leave blank to skip device-name filtering.

## `eventType` (type: `string`):

Malfunction = device didn't work as intended. Injury = a patient/user was harmed. Death = a death was associated with the device.

## `daysBack` (type: `integer`):

How many days back from today to search, by date the report was received by FDA.

## `maxResults` (type: `integer`):

Maximum number of reports to return, most recently received first.

## Actor input object example

```json
{
  "eventType": "all",
  "daysBack": 30,
  "maxResults": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/medical-device-adverse-event-tracker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("m_ctim/medical-device-adverse-event-tracker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call m_ctim/medical-device-adverse-event-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/medical-device-adverse-event-tracker"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/uqdjsAxIwU6VUgFZt/builds/6ryaYwSyVlfjXwPh9/openapi.json