Skip to content
FonteumThe Graph

GUIDE · PROVIDER CREDENTIALING DATA

The credentialing file, sourced and dated.

Supported federal records a credentialing or enrollment file leans on — the NPI, Medicare enrollment, specialty taxonomy, and exclusion status — pulled from one API, with available source and snapshot metadata displayed alongside supported fields. This guide maps the data behind the file and the pages that put it to work.

The short answer

What data goes into provider credentialing?

Credentialing confirms that a provider is who they say they are and is eligible to practice and bill: identity and specialty from NPPES, Medicare eligibility from PECOS, and a clean exclusion screen. The hard part is that each fact lives in a different federal file with a different refresh cadence.

Fonteum returns supported fields with the available source and observation metadata. Historical reconstruction is possible only when the named source has a retained version after tracking began; provider-wide replay is not universal.

Common questions

Answers in one line each

What data does provider credentialing rely on?
At minimum: identity and specialty from NPPES, Medicare eligibility from PECOS, license status, and a clean exclusion screen against the OIG LEIE and SAM.gov. Each lives in a separate federal file, so the work is resolving them to one provider and keeping each dated to its source.
Does Fonteum replace primary-source confirmation?
No. Fonteum returns federal records traced to the exact source file and snapshot date, so a credentialing team can confirm a fact against its primary source rather than a stale copy. It is the dated, source-chained record beneath the file — not a substitute for the credentialing decision itself.
Why does exclusion screening belong in credentialing?
Credentialing confirms eligibility to practice and bill, and an excluded provider is barred from both. Screening against the OIG LEIE, SAM.gov, and state Medicaid lists at credentialing and re-credentialing — and monthly in between — keeps an excluded party from slipping into the network. See the exclusion-screening guide for the full workflow.
How current is the enrollment data?
Each source has its own published cadence, while production responses show the available observation date. Provider-wide historical replay is not universal; a re-credentialing review can use a past version only when that source and subject have a retained captured row.
START HERE

Build a credentialing file you can re-derive.

Request access to query supported identity, enrollment, taxonomy, and exclusion records with the source and observation metadata available for each response.

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