# ⚕️ FDA MAUDE Medical Device Event Triage (`snuggly_beanie_970/fda-maude-device-event-triage`) Actor

⚕️ Search and prioritize FDA MAUDE adverse-event reports by death, injury, malfunction, device, UDI, manufacturer and patient outcome. ✅ Privacy-conscious normalized output with narratives, product problems and official FDA data.

- **URL**: https://apify.com/snuggly\_beanie\_970/fda-maude-device-event-triage.md
- **Developed by:** [Ilia](https://apify.com/snuggly_beanie_970) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 prioritized device events

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## 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

## ⚕️ FDA MAUDE Medical Device Event Triage

Search FDA medical-device adverse event reports and turn deeply nested MAUDE/openFDA records into a privacy-conscious, analysis-ready dataset. Each report gets normalized devices and UDI fields, event and product problems, patient outcomes, public narratives, and a transparent deterministic priority score.

### What is different

This is not a raw openFDA dump and it does not invent a clinical conclusion. Priority is rules-based: death reports rank above injuries, injuries above malfunctions, with documented adverse-event and serious patient-outcome flags adding weight. The original fields remain available so every score is auditable.

Reporter names, phone numbers, email addresses, street addresses, age, sex, race, ethnicity, and other patient demographics are intentionally not exported.

### Input and scheduling

Filter by received-date range, manufacturer, device brand/generic name, event types, and product-problem phrases. Leave dates empty to receive the newest records available from openFDA. `maxItems` is a hard cost cap. Add an optional free openFDA API key for higher rate limits.

### 📤 Output

Results include report identifiers, dates, event type, risk score and priority, manufacturer, normalized devices (brand, generic name, model, lot, product code, UDI, class and specialty), deduplicated problems/outcomes/actions, optional public narratives, and source provenance.

### 🔎 Data interpretation

MAUDE reports can be incomplete, duplicated, unverified, or updated later. A report does not prove that a device caused an event, and reporting volume is not an incidence rate. Do not use this dataset for diagnosis or individual medical decisions; verify critical findings with FDA source data and qualified professionals.

### 📥 Complete input reference

| Field | Type | Default | Purpose |
|---|---|---:|---|
| `dateFrom` | string | — | Optional YYYY-MM-DD; provide together with dateTo. |
| `dateTo` | string | — | Optional YYYY-MM-DD; provide together with dateFrom. |
| `manufacturer` | string | `""` | Optional exact-phrase manufacturer filter. |
| `deviceQuery` | string | `""` | Search brand and generic device names. |
| `eventTypes` | array | `[]` | Filter outcomes such as Death, Injury, or Malfunction. |
| `productProblems` | array | `[]` | Filter FDA product-problem phrases. |
| `maxItems` | integer | `100` | Hard cap on paid dataset records. |
| `includeNarratives` | boolean | `true` | Include FDA event and manufacturer narratives; reporter contact fields are never exported. |
| `apiKey` | string | — | Optional free key for higher API limits; omitted from output and logs. |

### 📤 Complete output reference

The default dataset is exportable as JSON, CSV, Excel, XML or RSS. Fields remain stable for scheduled runs and API integrations.

| Field | Type |
|---|---|
| `reportNumber` | string / null |
| `mdrReportKey` | string / null |
| `dateReceived` | string / null |
| `dateOfEvent` | string / null |
| `eventType` | string / null |
| `riskScore` | integer |
| `priority` | string |
| `adverseEventFlag` | boolean |
| `productProblemFlag` | boolean |
| `productProblems` | array |
| `manufacturer` | string / null |
| `devices` | array |
| `patientOutcomes` | array |
| `patientProblems` | array |
| `remedialActions` | array |
| `narratives` | array |
| `source` | string |
| `sourceApiUrl` | string |

### 🔌 API & integrations

Run this Actor from the Apify Console, API, CLI, MCP, Make, Zapier or n8n. Replace the Actor identifier and token in this template:

```bash
curl -X POST "https://api.apify.com/v2/acts/fda-maude-device-event-triage/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Results are stored in the run's default dataset and can be forwarded with Apify webhooks or scheduled Tasks.

### 🔎 Search keywords

FDA MAUDE Medical Device Event Triage, fda, maude, medical, device, event, triage, Apify Actor, scraper API, structured data, scheduled monitor, automation.

### 💰 Pricing

Billing is tied to successfully delivered result events. Empty, filtered, duplicate or failed records are not charged as results. Open the **Pricing** tab for the current per-event rate before starting a run, and use Apify's maximum-charge control to enforce a hard budget.

# Actor input Schema

## `dateFrom` (type: `string`):

Optional YYYY-MM-DD; provide together with dateTo.

## `dateTo` (type: `string`):

Optional YYYY-MM-DD; provide together with dateFrom.

## `manufacturer` (type: `string`):

Optional exact-phrase manufacturer filter.

## `deviceQuery` (type: `string`):

Search brand and generic device names.

## `eventTypes` (type: `array`):

Filter outcomes such as Death, Injury, or Malfunction.

## `productProblems` (type: `array`):

Filter FDA product-problem phrases.

## `maxItems` (type: `integer`):

Hard cap on paid dataset records.

## `includeNarratives` (type: `boolean`):

Include FDA event and manufacturer narratives; reporter contact fields are never exported.

## `apiKey` (type: `string`):

Optional free key for higher API limits; omitted from output and logs.

## Actor input object example

```json
{
  "manufacturer": "",
  "deviceQuery": "",
  "eventTypes": [],
  "productProblems": [],
  "maxItems": 100,
  "includeNarratives": true
}
```

# Actor output Schema

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

Default dataset with one normalized MAUDE report per item.

# 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("snuggly_beanie_970/fda-maude-device-event-triage").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("snuggly_beanie_970/fda-maude-device-event-triage").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 snuggly_beanie_970/fda-maude-device-event-triage --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snuggly_beanie_970/fda-maude-device-event-triage"
        }
    }
}

```

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/UxrTrDUVSSF32cv4A/builds/Kqcz4EFTgkqE1TdyU/openapi.json