Skip to content
FonteumThe Graph

The capability layer

APIREST + bulk accessMCP serverCallable by AI agentsFHIR R4 APIBulk exportAttestation & audit packReconciliationSource-vs-source diffsEntity graphSnapshotsPoint-in-time, bitemporal

By use case

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskDevelopers & AI teams

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

Platform

APIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots

Solutions

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams

Data

Coverage & sourcesFreshnessMethodologyCare CompareBrowse all datasets →
Research

Developers

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

GUIDE · PROVIDER CREDENTIALING DATA

The credentialing file, sourced and dated.

Every federal record a credentialing or enrollment file leans on — the NPI, Medicare enrollment, specialty taxonomy, and exclusion status — pulled from one API, each field carrying its source and snapshot date. This guide maps the data behind the file and the pages that put it to work.

Request accessThe credentialing use case →

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 those fields resolved to one provider and dated to their source, so a credentialing record can be confirmed against the primary source and re-checked as of any past date — not taken on faith.

Build the file

The use-case pages and tools that assemble a credentialing or enrollment record from federal data.

Use case

Credentialing & provider-data enrichment

Enrich a roster with identity, enrollment, taxonomy, and exclusion status from one API.

Open →
Use case

Payer credentialing

The health-plan path: credential and re-credential against dated federal records.

Open →
Tool

Look up an NPI

Pull a provider's source-traced identity and taxonomy by name or number.

Open →
Tool

Look up a MIPS score

Read a clinician's CMS quality score as a credentialing signal.

Open →

The underlying datasets

Dataset

CMS PECOS Medicare enrollment

Who is approved to bill Medicare and in what role, keyed to the NPI and dated to source.

Open →
Dataset

The NPPES provider registry

Identity, taxonomy, and practice address for every Type 1 and Type 2 provider.

Open →
Dataset

OIG LEIE — exclusion status

The exclusion check that belongs in every credentialing file.

Open →
How-to

Run the exclusion screen

Screen a provider against the OIG LEIE, SAM.gov, and state Medicaid lists in one pass.

Open →

Research on enrollment & licensure

Studies on the moving parts of a credentialing file — enrollment, revalidation, and license status.

Research

Who can bill Medicare, by specialty

What PECOS enrollment shows about the active billing population.

Open →
Research

How accurate are provider directories?

Why directory data drifts — and what that means for a credentialing file.

Open →
Research

The Medicare revalidation backlog

Where enrollment revalidation is overdue and what it signals.

Open →
Research

Active nurse license share by state

How much of the licensed workforce is currently active, by state.

Open →
Research

The Medicare deactivation spike

A dated look at NPI deactivations relevant to re-credentialing.

Open →

Key terms

Glossary

Provider enrollment, defined

Getting a provider approved to bill a federal program.

Open →
Glossary

PECOS, defined

Medicare's provider enrollment system.

Open →
Glossary

Provider taxonomy codes

The NUCC code set behind a provider's stated specialty.

Open →
Glossary

PTAN, defined

The Provider Transaction Access Number tied to Medicare enrollment.

Open →
Glossary

MIPS, defined

The Merit-based Incentive Payment System quality score.

Open →

Pull it from the platform

Platform

The capability layer

REST, MCP, FHIR R4, and snapshots over the provider graph.

Open →
Developers

The provider API

Resolve a provider and return enrollment, taxonomy, and exclusion status in one call.

Open →
Method

How every field is sourced

The provenance contract behind each credentialing field.

Open →

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 family is pulled on its published cadence and every field carries the snapshot date of the file it came from. A credentialing record shows how fresh each fact is and can be replayed as of a past date — so a re-credentialing review can be reconstructed exactly as it stood.

Go deeper

The other pillar guides

  • GuideHealthcare provider data
  • GuideExclusion & sanctions screening
  • GuideHealthcare data for AI / RAG
START HERE

Build a credentialing file you can re-derive.

Request access to pull identity, enrollment, taxonomy, and exclusion status for any provider — each field signed back to its federal source.

Add Fonteum to your agent →Request pilot access

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Every figure traces to its federal source.

14-tuple provenance

Every rendered fact ties to a source URL, dataset ID, snapshot date, row key, and SHA-256 — the full chain-of-custody record.

Reproducible SQL

Each study ships the exact query behind its figures, run against the cited federal snapshot. Re-run it yourself.

Daily reconciliation

Published counts are reconciled against the upstream federal datasets on a daily cadence, with drift logged.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Two doors

Use the free API and open data

Query providers, facilities, sanctions, and quality scores — each field carrying its federal source. Self-serve, no call to start.

Explore the API →Browse the data catalog →

Talk to us

Managed pilots, enterprise terms, and audit-ready, signed attestation packages for compliance, risk, and research teams.

Talk to us →
Fonteum
Platform
Platform overviewAPIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareSanctionsOwnershipStaffingDeficienciesSpecial Focus Facilities
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsCitationsWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustQualitySecurityPrivacy policyTerms of serviceMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

The U.S. healthcare graph AI can cite — every fact carries its source.

Request access→

The substrate, by the numbers

44federal source familiesDistinct CMS, OIG, HRSA, FDA and peer datasets
35dataset pagesCitable, downloadable /data catalog pages
67reproducible studiesEach shipping the SQL behind its figures