Track every FDA field alert report (FAR) and FDA-issued supply notification. 3,419 events indexed, joined to plant and product, refreshed weekly.
The catalog indexes 3,419 FDA field alerts and supply notifications. Field alert reports are the upstream signal of recall and shortage: a manufacturer files a FAR within 72 hours of identifying a quality issue that may affect distributed product. Roughly 60% of field alerts resolve without a formal recall; the remainder escalate to Class II or Class III recall. The feed surfaces FARs, manufacturing-problem notifications, and increased-demand supply events in a single stream.
Upload products, NDC codes, or supplier plants. PharmaDB resolves to the field-alert taxonomy.
Every new field alert, manufacturing-problem notification, and supply event is matched against the resolved list weekly.
Citation-anchored dossier with the alert reason, the projected escalation path, and the historical resolution arc for the same plant or product.
Field alerts publish before formal recalls. The buyer gets the upstream view of quality issues that may escalate to Class II or III.
FDA drug-shortage feed entries surface in the same stream. Manufacturing-problem and increased-demand signals matter to procurement planning, not just to QA.
Median time from a field alert to a formal recall is roughly twenty-five days across the historical archive. The lead-time chip flags imminent recall risk.
Plants and products with two or more field alerts in trailing 12 months get a repeat-FAR chip. The pattern is more predictive of systemic CGMP risk than any single alert.
A real chat thread in PharmaDB. Type a question, the AI agent runs the tools, the answer lands as a saveable note.
pharmagraph_query Twelve plants with a field-alert pattern in the catalog · alert reason and downstream recall co-occurrence shown.
The field alert feed is the upstream recall and shortage signal. PharmaDB joins FARs to the plant catalog, overlays the drug-shortage list, and projects escalation lead-time from the historical arc. The view is compliance_events filtered to event_type = 'field_alert'. Refresh cadence is weekly.
A field alert report (FAR) is a notification a drug manufacturer must file with the FDA within three working days of identifying a quality issue that may affect distributed product. It is the upstream signal: most recalls begin with a field alert. The FAR is non-public at filing; PharmaDB indexes the resulting FDA publications and downstream enforcement events.
Roughly 40% across the historical archive. The remainder resolve through CAPA and product-quality investigation without distribution-level removal. The escalation rate varies by product class: sterile injectable field alerts escalate at a higher rate than oral solid alerts.
Median is roughly twenty-five days across the catalog. The chip flags imminent recall risk where the lead-time signal is short. Useful for supply planning when a downstream product is dependent on the cited plant.
MHRA medicines recalls, EMA quality defect notifications, Health Canada signals, and TGA quality alerts are all tracked. The cross-regulator field-alert view surfaces in a combined feed at the buyer's choice.
Field alerts publish on the FDA enforcement feed weekly, with a typical seven-day lag from filing. PharmaDB pulls each refresh and surfaces new events within days. The catalog row carries the filing date and the publication date.
Yes. The FDA drug-shortage list and the EMA shortage feed are joined to the field-alert stream. Manufacturing-problem and increased-demand notifications surface alongside the QA-driven FARs because both matter to procurement planning.
Bring the molecule, the lane, or the supplier you're sourcing this week. The AI agent runs it on PharmaDB in 30 minutes. You keep the brief.