Continuously refreshed provider data vs annual snapshots
A paywalled annual snapshot freezes provider records at one point each year. Fonteum re-ingests each federal source on its native cadence, stamps every field with a last-checked date, and keeps the records free to read — NPPES weekly, OIG LEIE monthly, CMS Care Compare quarterly, across as of June 2026.
Published June 17, 2026 · Last reviewed June 2026 · Capability comparison — public facts only
From a yearly edition to a continuously refreshed, dated record
| Capability | Paywalled annual snapshots | Fonteum |
|---|---|---|
| Refresh cadence | One edition per contract year. | Each source on its native cadence — NPPES weekly, LEIE monthly, Care Compare quarterly. |
| Access model | Behind a paid annual license. | Free to read — the same public-domain federal records, no paywall. |
| Freshness visibility | A single edition date for the whole dataset. | A last-checked date on each individual field. |
| Point-in-time history | Each annual edition replaces the prior one. | Bitemporal as-of history retained — query the record as it stood on a past date. |
| Stale-data risk | An edition ages across the full year between releases. | Drift monitoring and a last-checked stamp surface staleness same-day. |
| Tamper-evidence | No public provenance or integrity chain. | SHA-256 digest and an Ed25519 attestation chain per snapshot. |
| Identity resolution | Varies by product; not always NPI-keyed. | NPI-resolved across active providers. |
| Reproducibility | Methodology is often proprietary and not re-derivable. | Every figure reproducible from the open federal file it came from. |
| Delivery | Annual export or a portal seat. | FHIR R4 API, MCP server, bulk export, and free research CSV/JSON. |
A point-in-time annual snapshot is accurate the week it ships and drifts until the next release. Descriptions reflect the annual-snapshot model — a licensed yearly edition — not any single vendor.
What a once-a-year edition cannot show
An annual edition ages all year
A point-in-time snapshot is accurate the week it ships and drifts every week after. Providers move, enroll, get excluded, and change ownership continuously. A once-a-year edition cannot reflect a mid-year OIG exclusion or a new enrollment until the next release.
Freshness you can see, field by field
Fonteum re-ingests each of its on the source cadence and stamps every field with a last-checked date. Instead of one edition date for the whole dataset, each fact shows when it was last reconciled — and drift monitoring flags a source that falls behind.
Open and reproducible, not licensed and opaque
Annual snapshots are licensed assets with proprietary methodology. Fonteum publishes public-domain federal records openly, and every figure is reproducible against the original file — so the data is free to read and independently checkable, not a sealed annual export.
Compare other data capabilities
Provider data vs raw public files →
NPI-resolved, provenance-tracked records vs parsing bulk CSVs yourself.
Exclusion screening vs single-list checks →
Multi-source, NPI-resolved exclusion screening vs checking one list.
Healthcare provider data platforms compared →
How sourcing model and provenance separate the category.
Common questions
- What is wrong with an annual data snapshot?
- Nothing, if the data never changes — but provider data changes constantly. An annual snapshot is accurate the week it ships and drifts all year. A mid-year OIG exclusion, a new Medicare enrollment, or an ownership change will not appear until the next yearly edition, which can be eleven months away.
- How current is Fonteum's data?
- Fonteum re-ingests each federal source on its native cadence — NPPES weekly, OIG LEIE monthly, CMS Care Compare and PBJ quarterly — across . Each field carries the date it was last reconciled, and drift monitoring flags any source that falls behind its expected schedule.
- Can I still get a point-in-time view if the data is always refreshing?
- Yes. Continuous refresh and point-in-time history are not in tension. Fonteum keeps dated snapshots, so you can query a record as it stood on a past date as well as today. A licensed annual edition gives you only the point in time it was cut, with the prior edition overwritten.
- Is the data free, and how is freshness proven?
- The data is free to read — the underlying records are public-domain federal works. Freshness is shown rather than asserted: a visible last-checked date on each field, a SHA-256 digest and attestation chain per snapshot, and a public status surface reporting the last successful refresh for each source.
- Why do paywalled snapshots cost money if the data is federal?
- Much provider data originates in public-domain federal files, but a vendor adds packaging, enrichment, and a yearly license on top. Fonteum keeps the federal records open and charges only for what costs money to provide — scoped exports, API throughput, and integration support — not for access to the federal data itself.
- What is the risk of confidently stale data?
- The real failure mode is data that is stale but labeled current. An annual edition with one date hides how old any single field is. Fonteum dates each field, monitors for drift, and exposes per-source refresh status, so staleness is visible and flagged rather than silently carried inside a yearly snapshot.
Read federal data that is current — and free.
Check per-source freshness at /freshness, browse free research at /research, or request access.
- /freshness → Per-source refresh cadence and last-successful-refresh status.
- /sources → Every source family with tier, cadence, and limitations.
- /data-provenance → How each field carries its source and date.
- /research → Free, reproducible studies on the federal record.