upcoding
upcod_indDefinition
ISO-11179 Definition
A fraudulent billing practice in which a healthcare provider intentionally assigns a higher-paying diagnosis or procedure code than is supported by the clinical documentation, resulting in overpayment from insurance payers or government programs. Common upcoding schemes include billing for a higher complexity evaluation and management level than the documentation supports, assigning diagnosis codes that qualify for higher risk adjustment payments without adequate clinical documentation, and billing for a more complex surgical procedure than was actually performed. Upcoding is a major focus of OIG work plans, CMS RADV audits, and Medicare and Medicaid integrity contractor reviews.
Healthcare data teams build upcoding detection analytics that identify statistical outliers in code distribution compared to peer providers, flag cases where documented complexity metrics do not support billed code levels, and produce risk-stratified audit work lists for clinical documentation integrity review programs.
Standard Abbreviation
upcod_ind
Category
Production DDL — FACT_CLAIM_TRANSACTION
CREATE OR REPLACE TABLE FACT_CLAIM_TRANSACTION (
clm_txn_key INTEGER NOT NULL -- surrogate key,
clm_id VARCHAR(50) NOT NULL -- claim identifier,
mbr_key INTEGER NOT NULL -- FK to DIM_MEMBER,
prvdr_key INTEGER NOT NULL -- FK to DIM_PROVIDER,
clm_typ_cd VARCHAR(10) -- claim type code,
tot_chrg_amt DECIMAL(18,2) -- total charged amount,
tot_alwd_amt DECIMAL(18,2) -- total allowed amount,
tot_pd_amt DECIMAL(18,2) -- total paid amount,
cntrct_adj_amt DECIMAL(18,2) -- contractual adjustment,
denial_ind CHAR(1) -- denial indicator,
denial_rsn_cd VARCHAR(10) -- denial reason code,
prior_auth_nbr VARCHAR(30) -- authorization number,
clm_lag_days SMALLINT -- claim lag days,
days_ar SMALLINT -- days in AR,
load_dt TIMESTAMP_NTZ NOT NULL -- load timestamp
);
Standard Snowflake DDL for the canonical finance table. Convert to BigQuery or Databricks →
Why This Term Matters
Healthcare data terminology is foundational for any data engineer working in this industry. Precise understanding of standard terms enables accurate schema design, reduces downstream data quality issues, and ensures pipelines meet the regulatory and interoperability requirements imposed by HIPAA, HL7 FHIR, and CMS reporting frameworks. Without this foundation, even technically well-built pipelines produce data that fails validation when it reaches payers or regulators.
Related Content
Looking for more healthcare terms?
Browse our complete library of 100,000+ standardized healthcare data terms
Browse All Terms