NPPES remains the authoritative source for MIPS, cost attribution, and ACO enrollment today and shouldn't be replaced. The new CMS National Provider Directory (NPD) is a FHIR-based API layer that adds what NPPES can't explicit provider-organization affiliations, near real-time updates, and digital endpoints. For Healthmonix and Prism, the play is to keep NPPES operational while ingesting NPD alongside it, unlocking a "Provider Network Intelligence" layer.
Side-by-side comparison
The core problem NPD is solving
Why NPPES alone isn't enough
CMS itself has at least five systems managing provider information. NPPES is the de facto standard but has been branched and corrected over 5,000 times across the industry — every payer, health system, and vendor maintains their own silo of fixes. The cost of not having a single source of truth is estimated at $2.76B per year. NPD is CMS's attempt to fix this at the infrastructure level.
What NPD adds that NPPES cannot
Explicit provider-to-organization affiliations, FHIR digital endpoints for EHR-to-EHR data exchange, and a queryable API that answers real-time questions — not just "who is this provider" but "who do they work with, where do they practice, and how do systems connect to them." These are the building blocks for dynamic network accountability.
What this means for Healthmonix and Prism
Today — no operational change required
Continue using NPPES for all current pipelines: MIPS eligibility, TIN/NPI attribution, cost measures, provider lookup. NPD is not authoritative for any of these today. Do not replace NPPES.
Near term — start ingesting alongside NPPES
Begin parsing NPD NDJSON alongside NPPES. Map NPI ↔ organization relationships from NPD affiliation data. Validate differences vs current attribution assumptions — especially for ACO and multi-site clients.
Strategic — Provider Network Intelligence in Prism
NPD enables a "Provider Network Intelligence" layer: real affiliations (not inferred), stronger MSSP/ACO alignment, ASM episode ownership clarity, TEAM bundle coordination. First mover advantage before competitors recognize this shift.
Positioning statement
"While others rely on static NPI data, Healthmonix is building on CMS's next-generation provider network infrastructure — so our attribution logic reflects how care is actually organized, not how it was billed."
Data format: what you're working with
Bottom line
NPPES remains the operational source of truth for every CMS program today — MIPS eligibility, cost attribution, TIN/NPI relationships, ACO enrollment. Do not change current pipelines.
NPD is infrastructure, not a dataset. It is CMS signaling where provider accountability is heading: from static identifiers toward dynamic, affiliation-aware networks. The practices and platforms that understand this shift early will have a structural advantage as TEAM, ASM, and next-gen ACO models evolve.
For Prism the opportunity is specific: NPD affiliation data is the missing layer between "who submitted this claim" and "who is actually responsible for this patient's care across the network." That gap is exactly where attribution logic breaks down in episode-based cost models — and NPD starts to close it.
NPD is infrastructure, not a dataset. It is CMS signaling where provider accountability is heading: from static identifiers toward dynamic, affiliation-aware networks. The practices and platforms that understand this shift early will have a structural advantage as TEAM, ASM, and next-gen ACO models evolve.
For Prism the opportunity is specific: NPD affiliation data is the missing layer between "who submitted this claim" and "who is actually responsible for this patient's care across the network." That gap is exactly where attribution logic breaks down in episode-based cost models — and NPD starts to close it.
Healthmonix internal analysis · directory.cms.gov · github.com/CMS-Enterprise/npd · May 2026
