Skip to content
FonteumPublic-records evidence
Screen 25 NPIs free →Buy $129 certificate →
Trust · Data freshness

Content changes, source by source.

This dashboard covers the 6 sources registered in its cadence table. It shows the last proved content change, the upstream release date when recorded, the expected publication cadence, and a derived status band. A workflow run or flat row count cannot advance the change date.

recent changeaging changeold changechange-age legend; publisher release dates remain separate

0 of 6 sources have a recent content change · 2 evidence errors

monthly
NPPES (NPI registry)
methodology —
Last content change
—
—
latest ledger observation —
Upstream release date
—
not recorded
No content baseline
quarterly
CMS PECOS PPEF
methodology —
Last content change
—
—
latest ledger observation 2026-07-15
Upstream release date
—
not recorded
Evidence error
quarterly
CMS Care Compare
methodology —
Last content change
—
—
latest ledger observation 2026-07-13
Upstream release date
—
not recorded
Evidence error
quarterly
HRSA HPSA
methodology —
Last content change
—
—
latest ledger observation —
Upstream release date
—
not recorded
No content baseline
annual
BLS OEWS
methodology —
Last content change
—
—
latest ledger observation —
Upstream release date
—
not recorded
No content baseline
annual
BEA Regional
methodology —
Last content change
—
—
latest ledger observation —
Upstream release date
—
not recorded
No content baseline
How to use this page
  • Age bands compare the last row-count or content-hash change with the configured cadence. Workflow checks are tracked separately and cannot make an unchanged source look current.
  • For full source identity, licensing, and ToS posture see /sources. For the ranking + ingestion methodology see /methodology.
  • Each row is also emitted as schema:DataFeed JSON-LD so clients can read the stored content-change and upstream-release fields separately.

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