Back to search

provider identifier

prvdr_id
provider·Updated Jun 23, 2026

Definition

ISO-11179 Definition

The provider identifier (prvdr_id) is a unique reference number assigned to a healthcare provider within a specific health plan's or organization's internal system, used to identify the provider in claims, credentialing, contracting, and network data. Unlike the NPI, which is a universal 10-digit identifier assigned by CMS that is the same across all payers, the internal prvdr_id is specific to one organization's systems and may differ from the NPI format. In many health plan data models, prvdr_id is a surrogate key in the provider dimension table that links to the NPI, TIN (Tax Identification Number), UPIN (legacy), and payer-specific provider numbers.

Provider records may have multiple identifiers: the individual physician's NPI (Type 1), the group practice NPI (Type 2), the group's TIN, and the payer's internal contract identifier. The provider identifier is the key that connects a claim to the provider dimension, enabling provider-level analytics such as utilization reporting, quality measurement, network adequacy assessment, and contract performance monitoring. Fragmented provider identity — the same provider appearing under multiple different prvdr_id values due to inconsistent data entry, system migrations, or mergers — is one of the most pervasive data quality problems in healthcare analytics.

A provider who is attributed different IDs in the claims system, credentialing system, and care management platform cannot be reliably attributed for quality measure reporting or value-based care program performance. Healthcare data engineers build provider master data management (MDM) systems that reconcile multiple provider identifiers into a single golden record linked by the NPI as the universal anchor. The provider dimension table typically includes prvdr_id (internal surrogate), npi (VARCHAR(10), primary external identifier), npi_type_cd (1=individual, 2=organization), billing_tin (VARCHAR(9)), taxonomy_cd (NUCC specialty code), network_status_cd (IN/OUT of network), and contract_id.

Critical data quality rules include Luhn check-digit validation on every NPI value, validation that individual provider NPIs (Type 1) are not used as billing NPIs where an organization NPI (Type 2) is required, and quarterly reconciliation against the CMS NPPES dissemination file to detect deactivated NPIs, changed addresses, and updated specialty taxonomy codes. Provider data degrades rapidly — CMS estimates 15-20% of NPPES records change annually — requiring scheduled refresh jobs to maintain directory accuracy.

Standard Abbreviation

prvdr_id

Category

provider

Production DDL — DIM_PROVIDER

DIM_PROVIDER.sql
CREATE OR REPLACE TABLE DIM_PROVIDER (
    prvdr_key           INTEGER        NOT NULL  -- surrogate key,
    prvdr_npi           VARCHAR(10)              -- NPI number,
    prvdr_tin           VARCHAR(10)              -- tax ID number,
    prvdr_first_nm      VARCHAR(100)             -- first name,
    prvdr_last_nm       VARCHAR(100)             -- last name,
    prvdr_org_nm        VARCHAR(255)             -- organization name,
    prvdr_typ_cd        VARCHAR(20)              -- provider type code,
    prvdr_spclty_cd     VARCHAR(10)              -- specialty code,
    prvdr_tax           VARCHAR(10)              -- taxonomy code,
    prvdr_state_cd      CHAR(2)                  -- state code,
    prvdr_zip_cd        VARCHAR(10)              -- zip code,
    prvdr_ntwk_sts      VARCHAR(10)              -- network status,
    prvdr_accpt_pt_ind  CHAR(1)                  -- accepting patients,
    prvdr_excl_ind      CHAR(1)                  -- exclusion indicator,
    load_dt             TIMESTAMP_NTZ  NOT NULL  -- load timestamp
);

Standard Snowflake DDL for the canonical provider table. Convert to BigQuery or Databricks →

Why This Term Matters

Provider data management is one of the most operationally complex data domains in healthcare because providers move, merge, and update their credentials continuously. A data engineer who understands provider terminology can build NPI validation, credentialing, and network adequacy pipelines that keep provider directories accurate and prevent claim rejections. Stale or incorrect provider data is a leading cause of prior authorization delays and CMS compliance findings.

Looking for more healthcare terms?

Browse our complete library of 100,000+ standardized healthcare data terms

Browse All Terms