Skip to content
FonteumPublic-records evidence

Time machine → As-of

Inspect a dataset-level observation from a captured date.

Pick one of the sources named below and a date. Fonteum will select the stored dataset-level observation whose selection window contains that date and show its row count and attested hash plus any witness and chain metadata. These observations do not replay an individual record and do not prove that the upstream source changed on the observation date.

How the as-of read works

  1. The picker is limited to the named entries in this tool. A scheduled observation records dataset-level metadata such as a row count; it is not a banked copy of every source row.
  2. Your as-of date selects the stored observation whose selection window [attested observation, next attested observation) contains your date. The window is a lookup rule, not evidence that the upstream dataset stayed unchanged.
  3. Only observations with a complete attestation row enter public coverage. The page exposes the stored hash plus any witness and chain metadata; an integrity-read error makes the lookup unavailable instead of returning partial evidence.

Dataset-level attestation metadata does not sign individual fact rows, and it does not establish what an individual record showed. Row-history replay is available only on named source-specific surfaces that actually retain superseded rows.

What’s on file, by the numbers

Platform snapshot · 2026-07-26

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 →

Request access