provider credentialing
prvdr_credntlDefinition
ISO-11179 Definition
The formal process through which a health plan or healthcare organization verifies and assesses the qualifications, training, licensure, experience, and professional standing of a healthcare provider prior to granting network participation or clinical privileges. Credentialing involves primary source verification of medical school graduation, residency and fellowship training, board certification, state licensure, DEA registration, malpractice history, hospital privileges, and sanctions history. NCQA, URAC, and The Joint Commission establish credentialing standards that health plans must meet for accreditation.
The credentialing process typically takes 60 to 90 days and must be completed before providers can treat members as in-network. Healthcare data teams build credentialing workflow systems that track application status, document collection, verification completion, committee approval dates, and expiration dates for credentials requiring periodic renewal.
Standard Abbreviation
prvdr_credntl
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