Back to search

revenue per visit

rev_per_vst
finance·Updated Jun 13, 2026

Definition

ISO-11179 Definition

A financial productivity metric measuring the average net revenue generated per patient visit or encounter across a defined service line, provider, or facility, used to evaluate revenue generation efficiency and compare performance across providers and time periods. Revenue per visit is calculated by dividing total net patient service revenue by total visit volume for the measurement period and service category. Variation in revenue per visit across providers may reflect differences in patient complexity, coding completeness, service mix, or payer mix rather than true productivity differences, requiring risk adjustment for fair comparison.

Revenue per visit trends are analyzed in context with visit volume trends to understand total revenue dynamics — declining revenue per visit combined with stable volume indicates coding, payer mix, or contract issues while declining visit volume with stable revenue per visit indicates access or referral pattern changes. Healthcare data teams use rev_per_vst in provider performance dashboards, service line profitability analysis, and revenue forecasting models that project total revenue from planned visit volume changes.

Standard Abbreviation

rev_per_vst

Category

finance

Production DDL — FACT_CLAIM_TRANSACTION

FACT_CLAIM_TRANSACTION.sql
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