Skip to content
FonteumThe Graph
DataResearchCare CompareThe DifferAttestAPI
See the proof
  • Data
  • Research
  • Care Compare
  • The Differ
  • Attest
  • API
See the proof

← All sources · Life sciences

FDA Enforcement

FDA Enforcement Reports (Drug + Device Recalls)

U.S. Food & Drug Administration (openFDA) · Tier-1 · research-only (never on individual profiles)

Research-only
Source:FDA Enforcement·Snapshot May 2026Open official source ↗

The openFDA enforcement feeds publish drug and device recall enforcement reports — the recalling firm, recall classification (Class I–III), reason for recall, distribution pattern, and status. Fonteum folds the drug and device enforcement partitions into one source keyed by recall number and product kind.

What Fonteum uses it for

How this source shows up on Fonteum.

Aggregate research context on drug and device recalls, keyed to the recalling firm. The firm name is normalized so an Open Payments manufacturer organization can be cross-referenced in a separate, gated follow-up; that entity-graph link is deferred and ambiguous matches are held, not written.

What this source does NOT mean

A recall enforcement report is an FDA action about a product and the firm that distributed it — it is not a statement about any healthcare provider, not a quality measurement, and not a Fonteum assessment. A named firm is not an asserted identity match to any provider profile.

What this dataset answers

Research and data questions this source supports.

  • 01Pull every drug and device recall enforcement report for a manufacturer in one query, keyed to the recalling firm name.
  • 02Build a recall-monitoring feed that flags new Class I recalls weekly as openFDA republishes the enforcement partitions.
  • 03Cross-reference a manufacturer's recall history against its Open Payments footprint for a supply-chain risk review.
  • 04Power a research surface on recall classification and reason-for-recall trends across drug and device categories.

Dataset size: 56,777 recall records (2026-06-14 snapshot)

Fields used

Per-field display contract.

Every field below has a `display_allowed` flag in the §94 provenance schema. Write-locked fields are captured to provenance for audit but never rendered on profile pages.

Research-only — never on profiles

6 fields
recall_numberRecall number
product_kindProduct kind (drug / device)
classificationRecall classification (Class I–III)
recalling_firmRecalling firm (by name)
reason_for_recallReason for recall
statusRecall status
Limitations

What we can’t infer from this source.

  • Tier-1 — aggregate research context only; never rendered on individual provider profiles.
  • Firm-keyed by name (normalized); there is no NPI in the source, and the entity-graph cross-link to Open Payments manufacturers is deferred — ambiguous matches are held, not written.
  • openFDA omits empty fields; some legacy recalls carry sparse dates or classifications.
  • A recall record reflects the FDA enforcement action as published; Fonteum does not adjudicate the underlying facts.
Source metadata

Authority, license, refresh cadence.

Authority

U.S. Food & Drug Administration (openFDA)

Tier

Tier-1 · research-only (never on individual profiles)

Refresh cadence

Weekly — openFDA republishes the enforcement partitions; Fonteum re-pulls on snapshot publication.

License

openFDA — CC0 public domain (U.S.-government works). Free to use; no API key required for bulk downloads. License ↗

Official URL

https://api.fda.gov/drug/enforcement.json

Attribution requirement

Source: U.S. Food & Drug Administration (openFDA) — Enforcement Reports · Snapshot {YYYY-MM-DD}

ToS & usage notes

What the source allows.

openFDA data is CC0 public domain. No API key is required for bulk downloads; attribution to openFDA / the U.S. Food & Drug Administration is the courtesy ask. Fonteum pulls the enforcement partitions and attests each snapshot.

Sample provenance

What a single field looks like in the graph.

A worked example. Every field surfaced from this source carries this shape of provenance line — source · last checked · display rule · confidence (when applicable).

Field

Recall enforcement report (research-only)

Sample value

Recall Z-0000-2025 · Class II · Reason: labeling mix-up · Ongoing

Provenance line

Source: openFDA Enforcement · Snapshot 2026-06-14 · Methodology fda-enforcement/v1 · Display rule: firm-keyed research context — never an asserted provider-identity match

How to access

Official API, bulk download, and Fonteum endpoints.

Official API / download

https://api.fda.gov/drug/enforcement.json ↗

Fonteum surface

https://fonteum.com/api/v1/fda/manufacturer/{id} →

Frequently asked

Common questions about FDA Enforcement.

What is the openFDA enforcement (recall) dataset?
The openFDA enforcement feeds publish drug and device recall enforcement reports — the recalling firm, recall classification (Class I, II, or III), reason for recall, distribution pattern, and status. Fonteum folds the drug and device enforcement partitions into one source keyed by recall number and product kind.
Where does this data come from and is it free?
It comes from the openFDA enforcement API (api.fda.gov). openFDA data is CC0 public domain (U.S.-government works) — free to use and redistribute with attribution, and no API key is required for bulk downloads.
Is a recall linked to a healthcare provider?
No. Enforcement reports are keyed to the recalling firm (a manufacturer or distributor), not to any healthcare provider. The firm name is normalized so an Open Payments manufacturer organization can be cross-referenced in a separate, gated follow-up; that entity-graph link is deferred and ambiguous matches are held, not written.
What do the recall classifications mean?
FDA assigns Class I (reasonable probability of serious harm or death), Class II (temporary or reversible harm), or Class III (unlikely to cause harm) to each recall. The classification reflects FDA's assessment of the product hazard, not a Fonteum judgment.
How often does the data refresh?
openFDA republishes the enforcement partitions on a roughly weekly cadence. Fonteum re-pulls on snapshot publication and attests the snapshot. As of the 2026-06-14 snapshot, Fonteum holds 56,777 enforcement records.
Related

Where this source already shows up.

Related sources in the graph

  • /sources/fda-drugs-at-fda →
  • /sources/fda-drug-ndc →
  • /sources/fda-establishment-registrations →
See also
  • /sources → The full source library — every dataset Fonteum cites.
  • /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
  • /methodology → Network-wide sourcing, refresh cadence, and corrections policy.
  • /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.

The substrate, by the numbers

9.2Mgraph entitiesProviders, organizations, owners, and facilities
15.7Mlinked identifiersNPIs, CCNs, LEIs and more, resolved to entities
5Mgraph edgesSource-attested relationships between entities
44federal source familiesDistinct CMS, OIG, HRSA, FDA and peer datasets
35dataset pagesCitable, downloadable /data catalog pages
56reproducible studiesEach shipping the SQL behind its figures

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Every figure traces to its federal source.

14-tuple provenance

Every rendered fact ties to a source URL, dataset ID, snapshot date, row key, and SHA-256 — the full chain-of-custody record.

Reproducible SQL

Each study ships the exact query behind its figures, run against the cited federal snapshot. Re-run it yourself.

Daily reconciliation

Published counts are reconciled against the upstream federal datasets on a daily cadence, with drift logged.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Two doors

Use the free API and open data

Query providers, facilities, sanctions, and quality scores — each field carrying its federal source. Self-serve, no call to start.

Explore the API →Browse the data catalog →

Talk to us

Managed pilots, enterprise terms, and audit-ready, signed attestation packages for compliance, risk, and research teams.

Talk to us →
Fonteum
Products
The DifferAttestAPIFHIR API
Data
Care CompareResearchData catalogSources
Company
Why FonteumAboutPressEditorial policyCorrections
Legal
Privacy policyTerms of serviceMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

The U.S. healthcare graph AI can cite — every fact carries its source.

Request access→