FDA Safety Signal Monitor

Normalize the public openFDA device-recall records implemented by this Actor into source-linked safety-review data for internal decision support. Safety, quality, compliance, legal-research, and product-risk teams. Create a review queue from normalized public FDA recall data and retain the official record link beside each result.

What it does

This Actor normalizes the supported evidence into a default Apify dataset and keeps the original source reference with each buyer-visible result. Its buyer-value event is recall-alert; it uses Apify pay-per-event pricing, so inspect the current Pricing tab and begin with a small validation run.

Supported sources and boundary

• openFDA device recall API
• buyer-supplied public or authorized source URLs

Only the sources and buyer inputs listed above are supported. The Actor does not bypass login, CAPTCHA, paywalls, robots restrictions, private APIs, or any other access control. It is an independent tool and is not affiliated with the named source platforms or authorities.

Inputs

• watchlistTerms — Optional product, recalling-firm, or product-code terms.
• maxItems — Maximum normalized records to write for the run.
• startUrls — Optional public or authorized URLs; overview and dashboard pages are not treated as structured feeds.

Existing saved-task fields remain accepted for backward compatibility. Use Apify's maximum run-charge limit for any live validation run.

Buyer-ready output

• recordId
• productName
• recallingFirm
• recallStatus
• reasonForRecall
• action
• sourceUrl
• confidence
• retrievedAt

Every output preserves source provenance where the input or public source provides it. Unsupported sources return an explicit boundary error instead of an invented record.

First run

{
    "sourceMode": "sample",
    "watchlistTerms": [
        "infusion pump"
    ],
    "maxItems": 1
}

The bundled first-run example is a labelled deterministic demonstration, not proof of current live coverage:

{
    "evidenceType": "deterministic_demo",
    "productName": "Illustrative openFDA device recall record",
    "signalType": "medical_device_recall",
    "sourceUrl": "https://api.fda.gov/device/recall.json"
}

API, dataset, schedules, and webhooks

Use the Apify API or default dataset for programmatic retrieval. Save an input as an Apify task to schedule recurring runs. If the current input schema exposes webhookUrl, it can notify a buyer-controlled endpoint after a completed run; otherwise use Apify webhooks for the task or run.

Common use cases

• Build a source-linked internal review queue.
• Compare repeated signals across a buyer watchlist.
• Export normalized JSON or CSV for an approved downstream workflow.

Limitations and responsible use

The current built-in adapter is limited to the implemented openFDA device-recall endpoint. It is an independent data tool, not medical, regulatory, treatment, efficacy, diagnosis, or prescribing advice.

Support

Include the Actor run ID, the input field names (not secrets), an example source URL when authorized, and the observed output field when contacting Zentra support. Check the current Pricing and API tabs before production-scale runs.