Product Safety Surveillance (multi-product, openFDA)

Retrieve and interpret post-market safety records across every FDA-regulated product class except drug-AE signal mining: medical devices, food / dietary supplements / cosmetics, veterinary drugs, and drug supply (shortages), plus cross-product enforcement/recall reports.

KEY PRINCIPLES

1. Decide the product class first. Device? Food/supplement/cosmetic? Vet drug? Drug shortage? Recall? The class picks the tool.
2. Build a valid Lucene query. openFDA uses field-scoped field:value terms; combine with a space-separated AND. Phrases and special characters need care (see Query Grammar).
3. Retrieve, then interpret. These are spontaneous/voluntary reports. Report the records and their fields; never assert causation or rates.
4. Cite every record with the tool name, the openFDA endpoint, the query used, and the total hit count from meta.results.total.
5. Stay in scope. If the request is drug-AE signal detection (PRR/ROR/IC), STOP and point to tooluniverse-pharmacovigilance / tooluniverse-adverse-event-detection.

When to Use vs When NOT to Use