Methodology

NPI Provider Data Sources & Release Controls

NPI Data Hub is designed around explicit source evidence, product contracts, quality gates, immutable artifacts, and manual publication. This page states what the current product does and does not claim.

Public status published · data as of 2026-08-09

Source Acquisition

Discover required official source roles, archive immutable evidence, and verify source metadata before transformation.

Normalization

Validate NPI shape, separate entity types, normalize selected fields, and apply an explicit taxonomy and geography contract.

Quality & Review

Freeze counts, field coverage, checksums, quality results, sample rows, and artifact keys for operator review.

Versioned Publication

Promote an approved immutable release by changing an atomic pointer; preserve the prior release for rollback.

Source Foundation

The source model distinguishes official artifacts from derived products and keeps the represented source release attached to every downstream artifact.

CMS NPPES public data disseminationCMS NPI RegistryNUCC Healthcare Provider TaxonomyNPPES weekly incremental filesNPPES monthly replacement filesVersioned release manifests

Representative M2 Product Contract

The representative product is scoped to one Type 1, primary-taxonomy, one-state dentist product. The contract avoids calling an NPI active practice or licensure.

NPI and entity type
Provider name and credentials
Primary taxonomy code and label
Source-reported practice geography
Represented source date
Release ID, manifest, and checksums

Interpretation Boundaries

An NPI identifies a provider or organization; it does not prove current practice, licensure, credentialing, availability, purchase intent, or willingness to be contacted.

NPPES values are source-reported and can be incomplete, historical, duplicated across locations, or absent. Published products must disclose row grain, taxonomy selection, geography rules, and field coverage.

Current M2 Status

The official release passed NUCC permission and attribution validation, sensitive-address policy review, immutable source/build identity checks, the 60 GiB scratch preflight, 14 blocking quality checks, and authenticated operator publication. Secure Stripe checkout and entitlement-backed delivery provide access to the exact reviewed snapshot.

Frequently Asked Questions

Where does NPI Data Hub get provider data?

The source foundation begins with official CMS NPPES dissemination files and the NUCC Healthcare Provider Taxonomy reference, subject to its permission and attribution requirements.

Is the current public catalog official provider data?

Yes. The current reviewed product is derived from the official NPPES release with source data as of 2026-08-09. The public site exposes aggregate catalog evidence rather than provider rows.

What evidence accompanies a release?

Source identities and checksums, schema and transform versions, row counts, field coverage, quality results, artifact paths, and publication events are recorded with each release.

Can the pipeline publish automatically?

No. The worker can prepare and submit a frozen candidate, but only an authorized operator can publish or roll back.