Warehouse · Import Guide
Analyze a Versioned NPI Release in BigQuery
Load provider rows into a partitioned analytical table while preserving release metadata.
Official BigQuery import documentationBefore You Start
- A reviewed release artifact
- A BigQuery dataset
- A Cloud Storage staging location
Step-by-Step
- 1
Verify and stage
Validate the release checksum before uploading the artifact.
- 2
Define the schema
Declare NPI and taxonomy codes as STRING and dates explicitly.
- 3
Load the CSV
Use a named load job and retain its job ID with the release record.
- 4
Validate counts
Compare loaded rows and required-field coverage to the manifest.
- 5
Create release views
Expose a stable view that points at the approved release table.
Field Mapping Reference
| Our CSV Column | BigQuery Field | Note |
|---|---|---|
| npi | npi | Keep as text to preserve all ten digits |
| provider_name | provider_name | — |
| primary_taxonomy | primary_taxonomy | — |
| practice_state | practice_state | — |
| source_updated_at | source_updated_at | Parse as a date |
Tips for Better Results
Need the data contract first? Review the synthetic schema preview and published release methodology before importing a future delivered artifact.
Get the Agent ListFrequently Asked Questions
Should NPI be stored as a number?
No. Store NPI as a ten-character string so formatting and leading-zero behavior are explicit.
How do I verify the imported file?
Compare the file checksum and imported row count with the versioned release manifest before using the data.