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

Trust · Methodology changelog

Every methodology bump, on the public record.

Each row in this changelog is one methodology version bump for one source — the date it landed, the version it moved from, the version it moved to, and a plain-language summary. The log is built directly from the Fonteum snapshot store; entries are auto-generated on publication and refined post-hoc with hand-edited prose.

1 entries · 1 sources tracked

Subscribe via RSS · Atom.

uk-sanctions

uk-sanctions

uk-sanctions/v1 → uk-sanctions/v2

uk-sanctions methodology version uk-sanctions/v1 → uk-sanctions/v2 on 2026-07-11. The operator will replace this auto-generated summary with hand-edited prose describing what changed between versions.

machine_diff
{
  "to": "uk-sanctions/v2",
  "from": "uk-sanctions/v1",
  "kind": "version-bump",
  "snapshot_id_new": 1526,
  "snapshot_id_old": 1527
}
How to use this page
  • Each entry is an immutable, citeable record of a methodology change — journalists and researchers can pin a citation to a specific version bump on a specific date.
  • For the full Fonteum methodology — sourcing, refresh cadence, claim ceiling, corrections policy — see /methodology. For per-source identity, licensing, and ToS posture see /sources.
  • Entries are also emitted as schema.org BlogPosting items (one per row) plus a DataFeed wrapper for the changelog overall, so AI agents and search engines can read the evolution without scraping the rendered HTML.

What’s on file, by the numbers

Platform snapshot · 2026-08-24

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
70fresh 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