Skip to content
FonteumThe Graph
Screen 25 NPIs free →Buy $129 certificate →

SOLUTIONS · BY USE CASE AND BUYER

Start with the job to be done.

One source-provenanced US healthcare provider graph, applied to the work you need done — exclusion screening, credentialing, audit evidence, provider data for AI, and M&A diligence. Supported results expose their available source and observation metadata, with gaps left explicit. Each use-case page carries both a developer and a compliance view, so the whole buying committee evaluates one page.

Request accessStart with exclusion screening →

By use case

Five use cases, one provenance graph

Compliance · sharpest pain

Exclusion & sanctions screening

Screen a workforce and vendor roster against OIG LEIE plus the loaded federal and state exclusion lists. Completed checks expose the source and observation fields available for that response.

Open Exclusion & sanctions screening→
Provider data

Credentialing & provider-data enrichment

Enrich a provider roster with NPI-keyed public records — licensure signals, enrollment, sanctions — with source and snapshot metadata where the participating record supplies it.

Open Credentialing & provider-data enrichment→
Audit

Audit evidence & defensible programs

Retain a timestamped screening artifact with the available source fields. A separate signature, when present, covers its identified attestation object rather than each returned fact.

Open Audit evidence & defensible programs→
AI / developers

Provider data for AI & RAG

A chunk-ready, citation-stable corpus and a paginated chunks endpoint — drop federal provider data into a retrieval pipeline with provenance intact.

Open Provider data for AI & RAG→
Diligence

M&A & network diligence

Resolve ownership and chain affiliation across PECOS and CMS records to map who controls a provider network before a deal closes.

Open M&A & network diligence→

By buyer

Two buyer doors into the same data

Builders & data licensing →Healthtech data API →All audience pages →

Solutions FAQ

Common questions

Which use case should I start with?
Exclusion and sanctions screening is the sharpest pain and the quickest to prove — OIG says monthly LEIE screening best minimizes potential liability, and a single NPI check returns the available dated source record. The credentialing and audit-evidence pages draw on the same data and provenance, so they reinforce each other.
Do the use-case pages serve both developers and compliance buyers?
Yes. Each use-case page carries a dual-buyer view: developers see a copy-paste request and a sample JSON response; compliance teams see the workflow and the audit-evidence artifact. One URL, because the buying committee evaluates together and the champion forwards a single page.
What data backs every use case?
The healthcare use cases draw from named participating sources such as NPPES, PECOS, Care Compare, and OIG LEIE. The wider active production registry does not mean every source participates in every use case or that every source is loaded, complete, or fresh. Supported responses expose only the source, observation date, and methodology fields available for their records.
Is any patient data involved?
No. These use cases run against public federal and state records using each source's identifiers — such as NPI where present, CCN for facilities, or a source-specific record key. An NPI is not forced onto sources that do not publish it. There is no PHI in the pipeline.
Why not just download the raw federal files myself?
You can. Fonteum adds cross-list matching and records the check time plus available source-snapshot fields. If an export references a separate attestation, that reference applies only to the identified object; it is not an individual-fact signature.

Go deeper

Where to go next

PICK A USE CASE

Run a roster scan on public data only. No PHI.

Supported use cases return the source and observation fields available for their result. Request access for a pilot, or start with the screening API.

What’s on file, by the numbers

Platform snapshot · 2026-07-22

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