Skip to content
FonteumThe Graph

ARCHIVE

Snapshot Archive

Content-addressed snapshots of federal healthcare datasets. Stored digests and chain metadata are shown where present; an archive row is not automatically signature-linked, and its contents are not individually signed.

Latest archive capture: 2026-05-28 · Dataset: cms-nppes · Method: 2026.05.28. Capture time is not content-change freshness; freshness is unknown without change evidence.

Append-only chain

3Snapshots archivedContent-addressed records in the public archive.
1,497Links in chainSigned links from genesis to head.
ActiveProduction source registryRegistry status is not completeness, load status, or freshness.

CHAIN MANIFEST

/api/v1/chain

Head link 1496.
f950647f7eb1…

GENESIS

Link 0

Signed 2026-06-16.
0000000000000000000000000000000000000000000000000000000000000000

Browse the archive

Filter by dataset or capture window. Every row links to the full provenance record and a downloadable, content-addressed archive whose SHA-256 digest can be checked against the chain. For dataset-level capture observations at a chosen date, see the point-in-time as-of view.

Archived snapshots with per-row SHA-256 provenance
CapturedDatasetRecordsSizeSHA-256 digestMethodSnapshot
2026-05-28cms-nppes1.03 GB8b5267e250fd…2026.05.28Open
2026-02-01cms-nppes1.03 GB8b5267e250fd…2026.05.28Open
2026-01-01cms-nppes1.03 GB2625999a2b1b…2026.05.28Open
  1. The documented federal-source catalog sits within the active production registry; registry status is not completeness, load status, or freshness. Each snapshot records its upstream source and capture date when supplied.
  2. Chain manifest — head pointer, total links, and published signing key.
  3. Published Ed25519 signing key (JSON).
  4. Chain semantics and offline re-derivation steps.

What’s on file, by the numbers

Platform snapshot · 2026-07-22

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
79fresh 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 →