Skip to content
1,322,867 nurse-staffing records · CMS PBJ
fonteum
DataAPIRisk SignalsResearchCompareSnapshotsRequest access →
Side-by-Side Comparison

NPPES (CMS NPI Registry) vs CMS PECOS: Side-by-Side Comparison

NPPES and CMS PECOS are both CMS-operated federal systems for healthcare provider identity, but they serve distinct regulatory purposes. NPPES issues and maintains National Provider Identifiers — the 10-digit identifiers used on all HIPAA-covered claims. PECOS is the Medicare enrollment system — it tracks which providers are actively enrolled to bill Medicare fee-for-service.

Dimension by dimension

NPPES (CMS NPI Registry) vs CMS PECOS, across 8 dimensions

DimensionNPPES (CMS NPI Registry)CMS PECOS
Data typeFederal provider identity — 10-digit NPI, taxonomy code, practice addressMedicare fee-for-service enrollment — active billing authorization by specialty and state
Coverage8 million+ active NPI records (individuals + organizations)~900,000 active Medicare FFS enrollment records
Refresh cadenceWeekly publish by CMS; Fonteum re-checks per practice on a 6-month cycleMonthly CMS publish; Fonteum ingests the monthly file
License / CostU.S. government public-domain works (17 U.S.C. § 105) — free to use and redistribute with attributionU.S. government public-domain works — free to use and redistribute with attribution
API accessPublic REST API at npiregistry.cms.hhs.gov/api — no key required for basic lookupsCSV bulk download via data.cms.gov; no dedicated REST API
Source provenanceEvery field carries source + snapshot date + limitation; raw federal record is the direct upstreamSource row → snapshot → SHA-256 digest chain; per-field date on every rendered value
Primary use caseCanonical provider identity backbone — NPI lookup, taxonomy matching, cross-source joinsMedicare enrollment status checks, billing-authority signal on provider profiles
PricingFree (federal public domain)Free (federal public domain)

Cells marked "—" indicate values not publicly documented by the respective platform. No data has been estimated or fabricated.

Honest fit

Which platform fits your team

When to use NPPES (CMS NPI Registry)

Use NPPES as the identity backbone — any application that needs to look up a provider by NPI, resolve taxonomy, or join across multiple federal datasets starts with NPPES. Every CMS cross-source join flows through the NPI key.

NPPES (CMS NPI Registry) source detail →

When to use CMS PECOS

Use PECOS when the specific question is Medicare enrollment status — whether a provider is actively enrolled and authorized to bill Medicare FFS, and in which specialty and state. PECOS answers the billing-authorization question; NPPES answers the identity question.

CMS PECOS source detail →

FAQ

Common questions

Do all providers in NPPES appear in PECOS?
No. NPPES covers all healthcare providers who have enumerated an NPI — over 8 million records — including many who do not bill Medicare. PECOS covers only providers enrolled in Medicare fee-for-service, a smaller subset (~900,000 active enrollments). A provider can have an NPI (in NPPES) but not bill Medicare (absent from PECOS).
Which comes first — NPI or Medicare enrollment?
NPI enumeration (NPPES) comes first. Providers must obtain an NPI before applying for Medicare enrollment in PECOS. NPI is the primary identifier; PECOS records cross-reference NPI as the provider identity link.
Can I use NPPES data to determine if a provider is licensed?
NPPES records are administrative, not licensure records. An active NPI does not confirm current state licensure or board certification. For licensure, state medical board records are the authoritative source; for Medicare billing authorization specifically, PECOS is the relevant check.
How does Fonteum use both NPPES and PECOS?
Fonteum ingests NPPES for provider identity (NPI, taxonomy, address) and cross-resolves it against PECOS for Medicare enrollment status. A PECOS-enrolled provider gets a 'Medicare fee-for-service active' indicator on their profile, alongside the CMS provider type and enrollment state — each field with source attribution, last-checked date, and applicable limitation.

Last updated 2026-05-31. See all comparisons at /compare →

READY TO SHIP

Add federal-data citations to your agent in 60 seconds.

Drop our MCP server into Claude Desktop or call the API with pk_dx_sample. No signup. No credit card. Live demo key.

Add Fonteum to your agent →Request pilot access

Compliance posture

Methodology · Corrections log · Editorial policy

fonteum

Product

  • Data
  • API
  • Methodology
  • Sources
  • Freshness
  • Citations

For buyers

  • AI agents
  • RAG developers
  • Compliance
  • Researchers
  • Developers

Reference

  • Compare
  • llms.txt
  • Agent card
  • Audit pack
  • Quality scorecard
  • Pilot intake
  • Research

Sourced from federal agencies. Fonteum, Inc., Delaware C-corp. © 2026.

Request access→