Skip to content
FonteumPublic-records evidence

← 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

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.

  • Pull every drug and device recall enforcement report for a manufacturer in one query, keyed to the recalling firm name.
  • Build a recall-monitoring feed that flags new Class I recalls weekly as openFDA republishes the enforcement partitions.
  • Cross-reference a manufacturer's recall history against its Open Payments footprint for a supply-chain risk review.
  • Power 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.

Fields listed below show their configured `display_allowed` flag from the §94 provenance schema. Fields marked write-locked are captured for audit and are not 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, publisher cadence.

Authority

U.S. Food & Drug Administration (openFDA)

Tier

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

Publisher / configured cadence

Declared or configured cadence: Weekly — openFDA republishes the enforcement partitions. Not evidence of the latest loaded source date.

License

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

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. Snapshot and attestation fields must be read from the specific artifact; no provenance fact currently links deterministically to a signature.

Sample provenance

What a single field looks like in the graph.

This worked example shows the provenance shape used when a surfaced field has populated source, last-checked, display-rule, and confidence metadata. Individual fields may omit unavailable values.

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.

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. Loaded dates must be read from the specific response; publisher cadence is not proof of a completed load. As of the 2026-06-14 snapshot, Fonteum holds 56,777 enforcement records.
Related

Related sources in the graph

See also
  • /sources → The generated source-catalog subset — documented datasets Fonteum cites.
  • /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
  • /methodology → Documented sourcing, publisher cadence, observed freshness, and corrections policy.
  • /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.

What’s on file, by the numbers

Platform snapshot · 2026-08-11

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

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

Read the full provenance and attestation methodology →

Request access