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 · HEALTHCARE PROVIDER DATA

Every healthcare provider, traced to its federal source.

A 9M+-provider record assembled from 44 federal source families — NPPES, CMS PECOS, Care Compare, and more — resolved into one entity graph where every field carries the source row it came from. This guide is the map to that data and the pages built on it.

Request accessSee the NPPES dataset →

The short answer

What counts as healthcare provider data, and where does it come from?

Healthcare provider data is the public record of who a clinician or facility is: their NPI, specialty taxonomy, practice address, Medicare enrollment, and quality and enforcement history. Almost all of it is published by the federal government — the national NPPES registry, CMS PECOS, Care Compare, Open Payments — and scattered across dozens of files that disagree on the same provider.

Fonteum resolves those files into one entity graph and signs each field back to its source, so a provider record reads as a single answer you can re-derive on demand.

Datasets & sources

The federal source families that make up a provider record. Each page leads with a liftable stat, a visible-HTML table, and a downloadable extract.

Dataset

The NPPES provider registry

The national NPI registry — every Type 1 and Type 2 provider, their taxonomy, and practice address, with field-level provenance.

Open →
Dataset

CMS PECOS Medicare enrollment

Medicare enrollment and ordering/referring status, keyed to the NPI and dated to its source file.

Open →
Catalog

Browse every federal dataset

The full data catalog — each source page is a standalone, citable surface with its own stat and table.

Open →
Coverage

Source families & cadence

Every source Fonteum ingests, with refresh cadence, jurisdiction coverage, and a displayability note.

Open →
Identity

The provider entity graph

How providers, organizations, and facilities are resolved across NPI, CCN, and PECOS-ID into one entity.

Open →
Facilities

CMS Care Compare facility data

Quality, staffing, and ownership signals for nursing homes, hospices, dialysis, and ASCs — keyed by CCN.

Open →

Look one up

Tool

Look up an NPI by name or number

Search the NPI registry and read the source-traced record for any provider.

Open →
Profiles

Per-provider profiles

A per-NPI profile that resolves a provider across every federal source, each field carrying its provenance.

Open →

Research on the provider record

Original, reproducible studies built on the same provider graph — the donor pages that earn citations.

Research

What's actually inside NPPES

A field-by-field read of the national provider registry and what each column really tells you.

Open →
Research

How accurate are provider directories?

An analysis of stale and conflicting directory data across federal sources.

Open →
Research

Who can bill Medicare, by specialty

What PECOS enrollment reveals about the active Medicare provider population.

Open →
Research

The Medicare deactivation spike

A dated look at NPI deactivations and what drives them.

Open →
Research

All original studies

The research bureau — every study with its method, dataset, and CSV/JSON downloads.

Open →

Key terms

Glossary

What is an NPI number?

The 10-digit National Provider Identifier — what it is and how CMS assigns it.

Open →
Glossary

NPPES, defined

The registry CMS runs behind every NPI.

Open →
Glossary

PECOS, defined

Medicare's provider enrollment system.

Open →
Glossary

Provider taxonomy codes

The NUCC code set that classifies a provider's specialty.

Open →
Glossary

CCN — the facility identifier

The CMS Certification Number that keys facility-level data.

Open →

Put it to work

Use case

Credentialing & provider-data enrichment

Enrich a roster with licensure, enrollment, and taxonomy from one API.

Open →
Platform

The capability layer

REST, MCP, FHIR R4, bulk export, and point-in-time snapshots over the same graph.

Open →
Method

How every field is sourced

The provenance contract and methodology behind each rendered value.

Open →

Common questions

Answers in one line each

Is healthcare provider data free to use?
The federal records — NPPES, PECOS, Care Compare, Open Payments — are public works and free to download and cite. Fonteum keeps reads of that public data free so AI engines can cite it; authentication raises rate limits and unlocks bulk export and signed attestation.
What is the difference between NPPES and PECOS?
NPPES is the registry that issues and holds the NPI for every provider; PECOS is Medicare's enrollment system that records who is approved to bill Medicare and in what role. A provider can have an NPI in NPPES without being actively enrolled in PECOS, so a complete record needs both.
How does Fonteum keep provider data current?
Each source family is pulled on its own published cadence, the raw bytes are hashed and retained, and the change is folded into the entity graph. Every record carries the snapshot date of the file it came from, so you can see how fresh each field is and read it as of a past date.
How do you resolve one provider across many federal files?
Records are linked deterministically on shared identifiers — NPI, CCN, PECOS-ID, and chain identifiers — into one entity, and each linked assertion keeps the source row and snapshot it came from. The entity graph is how a provider reads as a single answer instead of a dozen conflicting rows.

Go deeper

The other pillar guides

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

Pull one provider, resolved across every federal source.

Look up an NPI free, or request access to call the API and get a signed, source-traced provider record.

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