Use Case

Start With Manifests, Checksums, and Quality Gates

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

Use the product as a reference implementation for ingestion, normalization, evidence, object storage, and catalog publication.

Published Catalog

Version-bound CSV access

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

Explore the implementation

Secure checkout · Exact-snapshot delivery

Problems You're Probably Running Into

Large replacement files

Long-running jobs

Weak retry semantics

Catalog and artifact drift

How Data Teams Teams Use the Data

Pipeline architecture

Release automation

Catalog modeling

Object-storage evidence

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 Operations Healthcare Software Provider Networks View All