Use Case
Build Provider Discovery on a Stable Contract
1,582,477 reviewed rows in the current published product
Prototype directory, search, and data-quality experiences using documented provider fields and release semantics.
Published Catalog
Version-bound CSV access
Review 1,582,477 source-dated rows across the published catalog, with product definitions and immutable release evidence.
Inspect the data contractSecure checkout · Exact-snapshot delivery
Problems You're Probably Running Into
How Healthcare Software Teams Use the Data
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.
Related Guides
Other Use Cases
Published Catalog
Version-bound CSV access
Review 1,582,477 source-dated rows across the published catalog, with product definitions and immutable release evidence.
Inspect the data contractSecure checkout · Exact-snapshot delivery