Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

FONTEUM · USE CASE · PAYER CREDENTIALING

LEIE exclusions

Provider credentialing data, auditable to the federal source.

Loaded CMS NPPES, OIG LEIE, and CMS PECOS records in one graph, with source metadata where the response supplies it.

Request access →
Federal source stack

Three federal sources. One provenance graph.

  • active providers

    CMS NPPES

    NPI identity backbone

    6.8M+Source: CMS NPPES · As of 2026-06-10
    active providers (8.9M total records) — provider taxonomy code, practice address, entity type, enumeration date. Distributed as a weekly full-replacement file. The authoritative federal identifier for individual practitioners and organizations.

    Source documentation →

  • LEIE rows

    OIG LEIE

    Federal exclusion flag

    OIG HHS List of Excluded Individuals and Entities —

    68,055Source: OIG LEIE · As of 2026-05-08
    loaded rows from the May 8, 2026 source release when checked July 12. Exclusion fields and source metadata vary by record.

    Source documentation →

  • Active enrollment status

    CMS PECOS

    Medicare enrollment status

    CMS PECOS Physician and Practitioner Enrollment File — Medicare enrollment indicator, provider type, and reassignment data. A PECOS row joins to NPPES only when it publishes the same NPI; an NPI without a matching PECOS row does not establish Medicare enrollment.

    Source documentation →

Why source provenance matters for credentialing

Auditable to the federal source — not a vendor's derived list

CMS expects primary-source screening

The CMS Interoperability and Patient Access Final Rule (CMS-9115-F) and the Provider Directory Accuracy requirements expect health plans to maintain directory data sourced from NPPES and PECOS. Fonteum makes loaded federal records accessible across

6.8M+Source: CMS NPPES · As of 2026-06-10
active providers with source metadata where available. Fonteum's NPPES table had a newest system date of June 10, 2026 when checked July 12; that is not a source-release date or a claim that the table is current.

OIG exclusion screening, monthly cadence

CMS requires Medicare Advantage organizations and Medicaid plans to screen providers against the OIG LEIE monthly. OIG publishes monthly, but Fonteum's loaded

68,055-rowSource: OIG LEIE · As of 2026-05-08
release was dated May 8, 2026 when checked July 12. Results expose available source and observation fields; no provenance fact currently links deterministically to a signature. Confirm consequential status against the current OIG file.

FHIR R4 for automated workflow integration

Fonteum's FHIR R4 surface exposes Practitioner, PractitionerRole, Organization, Location, and HealthcareService resources. The CapabilityStatement lists advertised resources and search parameters; it does not establish universal source metadata or current coverage.

How it works

From federal portal to auditable credentialing record

Step 1 / Ingest

Ingest

Publisher cadence and loaded dates are separate. In the July 12 production audit, NPPES had a June 10, 2026 newest system date, PECOS had a June 18 source date, and the

68,055-row OIG LEIESource: OIG LEIE · As of 2026-05-08
table had a May 8 source date.

Step 2 / Provenance

Provenance

Responses expose source, observation-date, and limitation fields where those values are populated. They are nullable and vary by dataset; they do not establish universal signature linkage or a completed primary-source check.

Step 3 / Deliver

Deliver

Screening data is available at /research and /sanctions, through the FHIR R4 surface, and via HL7 bulk $export. Scoped pilot exports start at $2,500/mo; source metadata varies by record.

FAQ

Common questions

What provider data does Fonteum provide for payer credentialing?
Fonteum exposes loaded NPPES, OIG LEIE, and PECOS records within a graph of the documented federal-source catalog. In the July 12 production audit, NPPES had a newest system date of June 10, PECOS a newest source-release date of June 18, and OIG LEIE a newest source-release date of May 8. Source, date, and limitation fields vary by response; Fonteum is a screening data layer, not a credentialing decision.
How often is the OIG LEIE exclusion data refreshed?
OIG publishes the LEIE monthly. Fonteum's loaded release was dated May 8, 2026 when checked July 12, so it may trail the official file. Source and observation fields vary by response. Confirm consequential status against the current OIG list.
Does Fonteum's data meet CMS requirements for provider directory accuracy?
Fonteum exposes loaded NPPES, PECOS, and selected Care Compare data, but it does not certify directory accuracy or establish regulatory compliance. In the July 12 audit, NPPES had a June 10 newest system date, PECOS a June 18 newest source date, and checked Care Compare modules a May 7 newest source date. Fields and provenance metadata vary by response.
Can I access Fonteum provider data via API for automated credentialing workflows?
Fonteum exposes Practitioner, PractitionerRole, Organization, Location, and HealthcareService resources through its FHIR R4 surface, plus an NDJSON bulk-export workflow. Source and observation metadata varies by resource and field; the CapabilityStatement does not establish universal provenance or current coverage.
How does field-level provenance change a credentialing audit?
Fonteum can expose source, observation-date, and limitation fields alongside loaded NPPES, OIG, and PECOS values where those fields are present. Coverage varies by endpoint and record, and no provenance fact currently links deterministically to a signature. Consequential credentialing and exclusion decisions still require confirmation against current primary sources.
Is Fonteum's credentialing data free, and what does the pilot tier add?
Public NPPES, OIG LEIE, and PECOS records are available through Fonteum's public surfaces and documented APIs. The scoped pilot tier, starting at $2,500/mo, adds network-scoped exports and integration support. Source and observation metadata is included where the selected response supplies it; it is not universal.
Request access →

Request a credentialing data pilot.

This page covers the payer-specific angle. For the full dual-buyer walkthrough — the developer API and the compliance workflow side by side — see the credentialing & provider-data enrichment use case. Scope a custom NPPES + OIG LEIE + PECOS export for your provider network. Free public data at /research and /sanctions. Pilot tier from $2,500/mo.

Request access →or read the FHIR R4 docs →

FONTEUM · PILOT

Run a 90-day pilot. Public data only. No PHI.

Request access→ Read the methodology
See also
  • /solutions/credentialing → The canonical credentialing & provider-data enrichment use case — dual-buyer, with the developer API and the compliance workflow side by side.
  • /sanctions → OIG LEIE exclusion surface — loaded rows.
  • /docs/fhir → FHIR R4 US Core 6.1.0 endpoint reference and CapabilityStatement.
  • /data-provenance → Field-level provenance pipeline for NPPES, LEIE, and PECOS.
  • /compare/verisys-alternative → How Fonteum compares to Verisys for exclusion monitoring.

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
35sources liveCrosswalk-resolved sources with a snapshot in 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

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

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations 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 →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

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

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→