Use Case

Operational Provider Lists With the Definition Attached

1,582,477 reviewed rows in the current published product

Build provider reference workflows from explicit state, taxonomy, entity-type, and field contracts instead of undocumented extracts.

Published Catalog

Version-bound CSV access

Review 1,582,477 source-dated rows across the published catalog, with product definitions and immutable release evidence.

Review the current provider catalog

Secure checkout · Exact-snapshot delivery

Problems You're Probably Running Into

Ambiguous provider inclusion rules

Manual reconciliation across source files

No reproducible release evidence

Unclear fixture versus production state

How Healthcare Operations Teams Use the Data

Provider reference lists

Operational reconciliation

State and taxonomy segmentation

Release audit support

Fields in the Provider Data

Published products use documented public NPPES fields and retain their source release context:

NPI — the ten-digit National Provider Identifier
Provider Name — individual or organization name from NPPES
Primary Taxonomy — the documented specialty-selection result
Practice Location — source-reported city, state, and postal code
Release Evidence — source date, manifest, and artifact checksum

Frequently Asked Questions

Is the current public catalog an official NPPES release?

Yes. The first reviewed NPPES-derived catalog product is published with aggregate coverage and release evidence. Provider rows are not publicly browsable; secure Stripe checkout provides controlled access to the purchased snapshot.

What evidence accompanies a release?

The release contract includes source identifiers, checksums, schema and transform versions, row counts, quality results, artifact paths, and publication timestamps.

Other Use Cases

Healthcare Software Provider Networks Research Teams View All