NPPES (NPI Registry) vs PECOS: Side-by-Side Comparison
NPPES assigns and publishes NPIs; PECOS tracks Medicare fee-for-service enrollment. Both are CMS-operated systems with distinct purposes: an NPI from NPPES establishes provider identity for HIPAA transactions, while a PECOS enrollment establishes authorization to bill Medicare.
NPPES (NPI Registry) vs PECOS, across 8 dimensions
| Dimension | NPPES (NPI Registry) | PECOS |
|---|---|---|
| Data type | Federal provider identity — 10-digit NPI, taxonomy code, practice address | Medicare fee-for-service enrollment — active billing authorization by specialty and state |
| Coverage | 8 million+ active NPI records (individuals + organizations) | ~900,000 active Medicare FFS enrollment records |
| Refresh cadence | CMS publishes weekly; Fonteum's newest serving-table system date was 2026-06-10 when checked 2026-07-12 | CMS publishes periodically; Fonteum's newest loaded source-release date was 2026-06-18 when checked 2026-07-12 |
| License / Cost | U.S. government public-domain works (17 U.S.C. § 105) — free to use and redistribute with attribution | U.S. government public-domain works — free to use and redistribute with attribution |
| API access | Public REST API at npiregistry.cms.hhs.gov/api — no key required for basic lookups | CSV bulk download via data.cms.gov; no dedicated REST API |
| Source provenance | Responses identify available source, date, and limitation fields; coverage varies and facts are not individually signed | Available source and observation metadata varies by response; no provenance fact currently links deterministically to a signature |
| Primary use case | NPI lookup, submitted taxonomy fields, and joins where another source supplies NPI | Medicare enrollment status checks, billing-authority signal on provider profiles |
| Pricing | Free (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.
Which platform fits your team
When to use NPPES (NPI Registry)
Use NPPES to look up an assigned NPI and its submitted taxonomy fields. Join another federal dataset by NPI only when that dataset supplies the identifier; facility sources may instead use CCN and other sources use their own keys.
When to use 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.
Common questions
- Do all providers in NPPES appear in PECOS?
- No. NPPES contains records for providers and organizations that have enumerated an NPI, including many that do not bill Medicare. PECOS covers Medicare fee-for-service enrollments. An NPI can exist in NPPES without a matching active PECOS enrollment.
- 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. Returned profile fields expose source, date, and limitation metadata where the response supplies them; fields may be unavailable.
Last updated 2026-05-31. See all comparisons at /compare →
Add federal-data citations to your agent in 60 seconds.
Connect the hosted MCP server to your agent, or call the API with an issued bearer credential. See the developer docs for the current public contract.