Provenance

Why Every Data Release Needs an Immutable Manifest

How manifests connect source files, transforms, row counts, checksums, and downloadable artifacts.

NPI Data Hub1 min read
Why Every Data Release Needs an Immutable Manifest

A manifest is the compact record that makes a data release inspectable. It connects the source artifact to the generated product files and the exact pipeline version that produced them.

What the manifest records

A useful manifest includes source identifiers, checksums, row counts, schema version, transform version, quality results, artifact paths, and timestamps.

Why object storage is a good fit

Immutable release files and manifests belong in versioned object storage. Postgres keeps the searchable control plane and the active catalog pointer; object storage keeps large artifacts and evidence economically.

Share

Need a documented NPI provider list?

Review 120+ source-dated U.S. provider rows across the published catalog. Each CSV includes a documented definition, immutable release evidence, and clear limitations.