About Us
Provider Data With the Definition Attached
NPI Data Hub turns public NPPES releases into scoped, versioned products without hiding source dates, transforms, quality evidence, or limitations.
Why We Built This
Raw public provider data is free to download and expensive to operationalize. Teams still have to acquire large releases, understand repeated fields, classify taxonomy codes, normalize addresses, define row grain, and explain what a record does and does not prove.
NPI Data Hub makes those decisions explicit. Each product is tied to a release contract, source evidence, transform version, quality report, checksums, and an immutable artifact set.
The current public catalog reports 1,578,155 reviewed rows from a manually published product with source data as of 2026-08-09. Provider-row browsing and commercial checkout remain intentionally deferred.
How the Data Foundation Works
The source plan begins with CMS NPPES monthly replacement files, weekly incremental and deactivation files, companion location and other-name files, and the NUCC taxonomy reference subject to its permission and attribution requirements.
The pipeline archives source evidence, normalizes selected fields, builds partitioned artifacts, produces quality reports and samples, freezes a candidate, and requires an authorized operator to promote or roll it back.
How We Work
Source Fidelity
Every product stays traceable to the official source artifacts and represented source date.
Publication Controls
Quality, permission, attribution, and policy gates are reviewed before official rows can become public.
Reproducible Delivery
Immutable artifacts, manifests, checksums, and atomic pointers keep releases recoverable.
Built for Data Users
Healthcare operations, software, network, research, compliance, and data teams get explicit contracts.
Honest Metrics
Counts are release-bound and fixture rows are clearly separated from official provider data.
Clear Support
Questions about methodology, release status, or product scope receive direct, documented answers.
Who Uses the Product Pattern
Healthcare operations teams, software builders, provider-network analysts, researchers, compliance reviewers, and data engineers can use the same state, taxonomy, release, and provenance semantics for different workflows.
Explore the Current Release Surface
Browse the state catalog or read the source and publication methodology.