Production source registry
Registry status does not establish loaded, complete, or fresh coverage.
Providers in scope
Broad NPPES-derived provider universe for aggregate reporting context.
NPPES + PECOS rows
Current serving-table rows counted separately; not retained-history depth.
Answer first
Answer-first capsule for public-records reporting.
A newsroom should not have to bury the finding under caveats. Fonteum gives reporters the top-line answer first, then the trail: source family, snapshot date, methodology version, field limitation, and the public route where the editor can inspect the backing record.
Answer: [FIGURE] across [POPULATION]. Source trail: [SOURCE FAMILY] · [SNAPSHOT DATE]. Method: [METHODOLOGY VERSION]. Limitation: [KNOWN SOURCE LIMITATION]. Re-check: fonteum.com/verify/[SNAPSHOT].
Re-check line · source trail
Give the editor a sentence they can re-run.
The re-check line is the newsroom edge: the available source, date, method, and limitation behind a figure. A reporter can publish the number, an editor can re-check it, and a reader can see the limitation without needing a vendor statement.
Start with the reporting surface at /research, inspect the source catalog at /sources, and use /verify for a separately attested artifact when one exists.
SOURCE
Available source-family and upstream-URL fields identify the named record; fields can be null.
DATE
Use the source or observation date actually present; publisher cadence is not a loaded date.
LIMIT
Known source limitations are visible before publication.
CHECK
Where a separate attestation exists, inspect it independently; provenance facts do not currently link deterministically to signatures.
Time-machine edge
Re-check retained versions where they exist.
Public datasets change, but retained row history is source-specific. On July 12, production held closed versions for UK sanctions (9,442), procurement awards (38), provenance claims (20), OFAC SDN (10), and UN sanctions (1); EU sanctions had none. Sources without banked versions cannot be reconstructed to arbitrary dates.
Lead with the answer
Start from the aggregate figure, then open the trail behind it: source family, snapshot date, method, limitation, and export context.
Show the re-check line
Every cited figure should carry the sentence an editor can rerun later: source, date, methodology version, and the public page where the trail lives.
Keep the receipts chained
Where snapshot, attestation, and correction linkage exists, retain the identified object and date. Linkage and retained history are not universal.
Stay aggregate and factual
Fonteum is for public-records reporting, not eligibility decisions, not consumer-reporting, and not provider endorsement.
NEWSROOM EVIDENCE
Publish the figure, then show the dated public trail behind it.
Aggregate · factual · FCRA-safe
Public records for reporting, not provider judgment.
Fonteum helps a newsroom cite public administrative records. It does not certify a provider, rank providers for readers, or turn public files into a consumer-reporting product. Use the aggregate signal, cite the source, and show the limitation.
For exclusion and sanctions context, route readers to the public screening workflow at /screening.
Provider universe
providers in the broad public-records frame.
Use that scale for context, then narrow the story to the source family that supports the claim. The trail matters more than the headline number: source, date, limitation, and methodology.
Browse the source catalog →Next step
Bring the source trail before the story locks.
Start with the public research library, then use /verify for signed artifacts when a chart, claim, or aggregate figure needs a durable trail.