provider supervising
prvdr_supv_npiDefinition
ISO-11179 Definition
The National Provider Identifier of the physician or qualified practitioner who oversees the services delivered by a supervised provider such as a resident physician, student, or non-physician practitioner operating under physician supervision requirements. Medicare incident-to billing rules require direct physician supervision for services billed under the supervising physician NPI in office settings. Teaching physician rules govern supervision requirements for resident services in academic medical centers.
Supervising provider identification is critical for claims compliance because incorrect use of supervising physician NPIs to bill for unsupervised services is a significant Medicare audit risk. Healthcare data teams use prvdr_supv_npi in claims editing to validate that incident-to and teaching physician supervision requirements are met, in compliance analytics to identify potentially improper supervising physician billing patterns, and in academic medical center billing workflows that require teaching physician attestation documentation.
Standard Abbreviation
prvdr_supv_npi
Category
Production DDL — DIM_PROVIDER
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.
Related Content
Related Definitions
Looking for more healthcare terms?
Browse our complete library of 100,000+ standardized healthcare data terms
Browse All Terms