Certified Health Data Analyst (CHDA) Practice Review

Healthcare Analytics Taxonomy and Applications

  • Descriptive Analytics:

    • Definition: Descriptive analytics summarizes, aggregates, and describes historical data to answer the core operational question: What happened?

    • Reporting of Historical Performance: A monthly management report summarizing coder productivity, overall denial rate, and Case Mix Index (CMI\text{CMI}) for the prior month is an example of descriptive analytics because it consolidates completed operational events.

    • Specialty Dashboards: Displaying the previous quarter's claim denial rates stratified by clinical specialty constitutes descriptive reporting by visualizing past revenue cycle outcomes.

    • Inpatient Metrics: Calculating and publishing an average length of stay (LOS\text{LOS}) of 4.8 days4.8\,\text{days} for the preceding month summarizes past inpatient utilization.

  • Diagnostic Analytics:

    • Definition: Diagnostic analytics evaluates historical data patterns, relationships, and anomalies to identify root causes and address the question: Why did it happen?

    • Workflow Change Investigation: Investigating root causes when claim denial rates spike following an electronic health record (EHR\text{EHR}) workflow update represents diagnostic analysis.

    • Length of Stay Anomaly Isolation: Analyzing inpatient data to determine that an observed increase in average LOS\text{LOS} was concentrated specifically among patients awaiting placement in skilled nursing facilities (SNFs\text{SNFs}) exemplifies diagnostic analysis by isolating the driver of the variance.

  • Predictive Analytics:

    • Definition: Predictive analytics utilizes statistical modeling, machine learning algorithms, and historical data patterns to estimate future outcomes, answering: What is likely to happen?

    • Readmission Modeling: A statistical model that assesses clinical variables to estimate which inpatients are likely to experience an unplanned hospital readmission within 30 days30\,\text{days} of discharge.

    • Emergency Department Demand Forecasting: Building a time-series or regression model to forecast the total patient volume arriving at an emergency department (ED\text{ED}) during the subsequent month.

    • Denial Propensity Scoring: Identifying clinical, demographic, and billing characteristics strongly associated with past payer rejections to predict which newly submitted claims will encounter denials.

    • Separation of Extraction and Modeling: Extracting candidate predictor fields (such as patient age, principal diagnosis, count of prior hospital admissions, and historical length of stay) from an underlying relational database via Structured Query Language (SQL\text{SQL}) represents the preliminary data preparation step; generating risk scores from these features requires a distinct analytic modeling step.

  • Prescriptive Analytics:

    • Definition: Prescriptive analytics applies optimization formulas, simulation methods, and decision rules to determine the optimal course of action, answering: What action should be taken?

    • Clinical Intervention Assignment: An automated clinical decision support system that evaluates a high-risk patient's profile and prescribes the specific post-discharge care management protocol to be initiated.

    • Staffing Optimization: An automated scheduling system that translates predicted emergency department patient arrival volumes into the optimal number of nurses to schedule across specific operational shifts.

    • Constrained Risk Mitigation: Coupling a predictive readmission model with a mathematical optimization algorithm to select the specific intervention bundle that minimizes readmission probability at the lowest total implementation cost.

SQL Syntax, Relational Algebra, and Query Logic

  • Fundamental Clauses and Execution Roles:

    • SELECT: Identifies the specific data attributes, mathematical calculations, aggregate expressions, or database columns to return in the query output.

    • FROM: Specifies the source table, view, or joined entities from which records are retrieved.

    • WHERE: Defines the row-level filtering criteria that each record must evaluate to true in order to be included in the result set.

    • * (Wildcard): Instructs the database engine to return every column present in the specified table schema (e.g., SELECT * FROM Patients;).

  • Comparison and Logical Operators:

    • Logical AND: Requires every connected logical condition to evaluate to true for a row to be returned. If an analyst queries WHERE systolic_bp > 194 AND weight > 94, a patient exhibiting a systolic blood pressure of 200200 and a weight of 9090 is excluded because the second criterion (90>9490 > 94) evaluates to false.

    • Logical OR: Returns a row if at least one of the connected conditions evaluates to true. For the filter WHERE age > 80 OR systolic_bp > 180, a patient aged 7575 with a systolic blood pressure of 190190 is included because the blood pressure condition is satisfied (190>180190 > 180).

    • Strict Inequalities vs. Inclusive Bounds:

    • The operator > defines a strict upper boundary that excludes the threshold value itself (e.g., WHERE los > 5 selects stays of 6 days6\,\text{days} or more, omitting stays of exactly 5 days5\,\text{days}).

    • The operator >= establishes an inclusive lower boundary that retains the exact threshold value (e.g., WHERE los >= 5 includes stays equal to 5 days5\,\text{days} alongside higher values).

    • Explicit inclusion intervals require two bounded operators joined by logical AND (e.g., selecting patients from age 1818 through 6464 inclusive is expressed as WHERE age >= 18 AND age <= 64).

    • Multiple simultaneous criteria requiring threshold adherence must combine explicit conditions (e.g., isolating poorly controlled, obese diabetic patients requires WHERE a1c > 9.0 AND bmi >= 30).

  • Aggregate Functions:

    • AVG(): Computes the arithmetic mean of an assigned numeric column across all qualifying rows (e.g., SELECT AVG(los) FROM Encounters;).

    • COUNT(*): Calculates the total integer count of rows returned by the query, irrespective of null values in individual columns (e.g., SELECT COUNT(*) FROM Encounters;).

  • Relational Joins:

    • INNER JOIN: Evaluates two related tables and returns only records that have matching keys in both entities. Unmatched records in either table are discarded.

    • LEFT JOIN (Left Outer Join): Preserves every single record from the left table regardless of whether a matching record exists in the right table. For non-matching left records, right-table attributes are populated with NULL.

    • RIGHT JOIN (Right Outer Join): Preserves every record from the right table, retaining records even when no corresponding record exists in the left table, with left-table attributes populated with NULL.

    • FULL OUTER JOIN: Returns all records from both tables, combining matched rows and preserving left-only and right-only records with NULL fill for non-matching sides.

  • Unmatched Record Detection Pattern:

    • To identify parent records that lack corresponding child records (such as identifying registered patients who have never completed a clinical encounter), implement a LEFT JOIN from the parent to child table, followed by a filter verifying that the primary key of the child table evaluates to NULL:

    • SELECT p.patient_id FROM Patients p LEFT JOIN Encounters e ON p.patient_id = e.patient_id WHERE e.patient_id IS NULL;

  • Healthcare Query Implementations:

    • Filtering Categorical Billing Status: Extracting denied claims requires filtering the categorical status string: SELECT * FROM Claims WHERE claim_status = 'Denied';.

    • Targeted Column Extraction: Retrieving specific denial metadata: SELECT claim_id, denial_reason FROM Claims WHERE claim_status = 'Denied';.

    • Multi-Attribute Threshold Filtering: Isolating Medicare encounters exceeding an acute length of stay: SELECT patient_id FROM Encounters WHERE payer = 'Medicare' AND los > 5;.

    • Downstream Risk Score Consumption: Selecting high-risk patients identified by a predictive algorithm where the threshold is 0.800.80 or above: SELECT patient_id FROM RiskScores WHERE risk_score >= 0.80;.

Descriptive Statistics, Inferential Methods, and Data Visualization

  • Measures of Central Tendency and Dispersion:

    • Range: The arithmetic difference between the maximum and minimum observed values in a dataset:     Range=xmax⁡−xmin⁡\text{Range} = x_{\max} - x_{\min}

    • For the values 12,18,22,31,4712, 18, 22, 31, 47:       Range=47−12=35\text{Range} = 47 - 12 = 35

    • Mean: The arithmetic average of a dataset containing nn observations:     xˉ=1n∑i=1nxi\bar{x} = \frac{1}{n} \sum_{i=1}^{n} x_i

    • For the values 6,8,10,12,146, 8, 10, 12, 14:       xˉ=6+8+10+12+145=505=10\bar{x} = \frac{6 + 8 + 10 + 12 + 14}{5} = \frac{50}{5} = 10

    • Median: The middle value in an ordered dataset. For an even number of observations (nn is even), calculate the arithmetic mean of the two central numbers:     Median=x(n/2)+x(n/2+1)2\text{Median} = \frac{x_{(n/2)} + x_{(n/2 + 1)}}{2}

    • For the sorted set 4,7,9,12,15,204, 7, 9, 12, 15, 20 (n=6n = 6), average the 3rd and 4th observations:       Median=9+122=10.5\text{Median} = \frac{9 + 12}{2} = 10.5

    • Outlier Resistance:

    • The median is resistant to extreme outliers, whereas the mean, range, and standard deviation are sensitive to extreme skewness.

    • In a sample of inpatient stays displaying lengths of stay of 2,3,3,4,5,6, and 28 days2, 3, 3, 4, 5, 6,\,\text{and } 28\,\text{days}, the single extreme value of 28 days28\,\text{days} dramatically inflates the mean and range, making the median the preferred, least affected measure of central tendency.

  • Data Visualization Selection Principles:

    • Line Graph: The optimal visualization for displaying trends, rates, and patterns across sequentially ordered, continuous time intervals (e.g., tracking monthly coding denial rates from January through December).

    • Bar Chart: The standard chart type used to compare discrete numeric values or summary statistics across distinct categories, cohorts, or facilities (e.g., comparing average length of stay across four separate hospital facilities).

    • Histogram: Designed to display the underlying frequency distribution of a single continuous numeric variable by segmenting data into adjacent, non-overlapping intervals or bins (e.g., plotting the frequency distribution of patient ages grouped into 10-year10\text{-year} age bands).

    • Scatterplot: The primary visualization used to explore the bivariate relationship, distribution, and potential correlation between two paired continuous numeric variables (e.g., evaluating whether patient length of stay is associated with total hospital charges).

  • Correlation vs. Causation:

    • A scatterplot whose data points trend upward from left to right as the horizontal variable increases demonstrates a positive correlation (e.g., older age is associated with an increased length of stay).

    • Observational statistical correlation indicates co-movement between variables but does not prove a causal relationship.

  • Statistical Process Control (SPC\text{SPC}):

    • Control charts track process performance over time relative to three lines: a center line (representing the process mean) bounded by an Upper Control Limit (UCL\text{UCL}) and a Lower Control Limit (LCL\text{LCL}).

    • Inherent random variation within the control limits reflects common-cause variation.

    • Any data point plotted outside the established control boundaries (such as a monthly value exceeding the UCL\text{UCL}) serves as an operational signal of special-cause variation that warrants diagnostic investigation.

  • Inferential Statistical Hypothesis Testing:

    • Two-Sample Independent tt-Test: Parametric test appropriate for comparing the difference between the arithmetic means of two independent groups (e.g., assessing whether mean LOS\text{LOS} differs significantly between two distinct hospitals).

    • One-Way Analysis of Variance (ANOVA\text{ANOVA}): Statistical technique used to determine whether statistically significant differences exist among the means of three or more independent groups (e.g., evaluating mean LOS\text{LOS} across four separate hospital facilities).

    • Chi-Square (χ2\chi^2) Test of Independence: Non-parametric test utilized to determine whether a significant association exists between two categorical, nominal, or ordinal variables (e.g., evaluating whether primary payer category is associated with discharge disposition).

Work Relative Value Units (wRVU) and Physician Productivity Analysis

  • Productivity Frameworks: Volume vs. Clinical Intensity:

    • Encounter Volume (Visit Count): A raw quantitative count measuring clinical access, patient throughput, and total capacity (∑Visits\sum \text{Visits}).

    • Work Relative Value Units (wRVUs\text{wRVUs}): A standardized, objective measure quantifying the relative time, technical skill, physical effort, and mental stress expended by a physician to perform a given service or procedure.

    • Case Mix Index (CMI\text{CMI}) and Discharged Not Final Billed (DNFB\text{DNFB}): CMI\text{CMI} reflects the relative severity and resource intensity of an inpatient population, while DNFB\text{DNFB} tracks revenue cycle billing lag. Neither metric directly measures individual physician work productivity.

    • Work Output Primacy: When assessing true clinical productivity defined as total physician work delivered, total wRVUs\text{wRVUs} represent a more comprehensive metric than gross encounter volume because wRVUs\text{wRVUs} adjust for service complexity.

  • Mathematical Calculation of Total wRVUs:

    • Total physician work generated across diverse Current Procedural Terminology (CPT\text{CPT}) codes is calculated by taking the sum of the product of visit volume and the assigned wRVU\text{wRVU} weight for each specific code:     Total wRVUs=∑i=1k(Visitsi×wRVUi)\text{Total wRVUs} = \sum_{i=1}^{k} \left( \text{Visits}_i \times \text{wRVU}_i \right)

    • Sample Procedure-Level Calculation:

    • A clinician records the following procedural volume:

      • 12 visits12\,\text{visits} at code 9920599205 (3.50 wRVU3.50\,\text{wRVU} each)

      • 25 visits25\,\text{visits} at code 9920499204 (2.60 wRVU2.60\,\text{wRVU} each)

      • 40 visits40\,\text{visits} at code 9921499214 (1.92 wRVU1.92\,\text{wRVU} each)

      • 15 visits15\,\text{visits} at code 9921599215 (2.80 wRVU2.80\,\text{wRVU} each)

    • Calculate total work output by summing the individual code contributions:       Total wRVUs=(12×3.50)+(25×2.60)+(40×1.92)+(15×2.80)\text{Total wRVUs} = (12 \times 3.50) + (25 \times 2.60) + (40 \times 1.92) + (15 \times 2.80)       Total wRVUs=42.00+65.00+76.80+42.00=225.80\text{Total wRVUs} = 42.00 + 65.00 + 76.80 + 42.00 = 225.80

  • Comparative Physician Productivity Analysis:

    • Established Procedural Weights:

    • CPT 9920299202: 0.93 wRVU0.93\,\text{wRVU}

    • CPT 9920399203: 1.60 wRVU1.60\,\text{wRVU}

    • CPT 9920499204: 2.60 wRVU2.60\,\text{wRVU}

    • CPT 9920599205: 3.50 wRVU3.50\,\text{wRVU}

    • CPT 9921299212: 0.70 wRVU0.70\,\text{wRVU}

    • CPT 9921399213: 1.30 wRVU1.30\,\text{wRVU}

    • CPT 9921499214: 1.92 wRVU1.92\,\text{wRVU}

    • CPT 9921599215: 2.80 wRVU2.80\,\text{wRVU}

    • Physician Encounter Distributions:

    • Dr A: Visits across the eight codes: 10,20,10,5,20,80,60,1010, 20, 10, 5, 20, 80, 60, 10

    • Dr B: Visits across the eight codes: 5,15,25,10,10,60,80,205, 15, 25, 10, 10, 60, 80, 20

    • Dr C: Visits across the eight codes: 20,30,10,2,30,100,40,520, 30, 10, 2, 30, 100, 40, 5

    • Total Encounter Volume Comparison:

    • Dr A: 10+20+10+5+20+80+60+10=215 visits10 + 20 + 10 + 5 + 20 + 80 + 60 + 10 = 215\,\text{visits}

    • Dr B: 5+15+25+10+10+60+80+20=225 visits5 + 15 + 25 + 10 + 10 + 60 + 80 + 20 = 225\,\text{visits}

    • Dr C: 20+30+10+2+30+100+40+5=237 visits20 + 30 + 10 + 2 + 30 + 100 + 40 + 5 = 237\,\text{visits}

    • Result: Dr C achieved the highest encounter volume (237 visits237\,\text{visits}).

    • Total wRVU Output Comparison:

    • Dr A:       (10×0.93)+(20×1.60)+(10×2.60)+(5×3.50)+(20×0.70)+(80×1.30)+(60×1.92)+(10×2.80)(10 \times 0.93) + (20 \times 1.60) + (10 \times 2.60) + (5 \times 3.50) + (20 \times 0.70) + (80 \times 1.30) + (60 \times 1.92) + (10 \times 2.80)       =9.30+32.00+26.00+17.50+14.00+104.00+115.20+28.00=346.00 wRVUs= 9.30 + 32.00 + 26.00 + 17.50 + 14.00 + 104.00 + 115.20 + 28.00 = 346.00\,\text{wRVUs}

    • Dr B:       (5×0.93)+(15×1.60)+(25×2.60)+(10×3.50)+(10×0.70)+(60×1.30)+(80×1.92)+(20×2.80)(5 \times 0.93) + (15 \times 1.60) + (25 \times 2.60) + (10 \times 3.50) + (10 \times 0.70) + (60 \times 1.30) + (80 \times 1.92) + (20 \times 2.80)       =4.65+24.00+65.00+35.00+7.00+78.00+153.60+56.00=423.25 wRVUs= 4.65 + 24.00 + 65.00 + 35.00 + 7.00 + 78.00 + 153.60 + 56.00 = 423.25\,\text{wRVUs}

    • Dr C:       (20×0.93)+(30×1.60)+(10×2.60)+(2×3.50)+(30×0.70)+(100×1.30)+(40×1.92)+(5×2.80)(20 \times 0.93) + (30 \times 1.60) + (10 \times 2.60) + (2 \times 3.50) + (30 \times 0.70) + (100 \times 1.30) + (40 \times 1.92) + (5 \times 2.80)       =18.60+48.00+26.00+7.00+21.00+130.00+76.80+14.00=341.40 wRVUs= 18.60 + 48.00 + 26.00 + 7.00 + 21.00 + 130.00 + 76.80 + 14.00 = 341.40\,\text{wRVUs}

    • Result: Dr B demonstrated the highest overall productivity when measured by total work (423.25 wRVUs423.25\,\text{wRVUs}).

    • Average Work Intensity per Visit:     Average wRVU per Visit=Total wRVUsTotal Encounters\text{Average wRVU per Visit} = \frac{\text{Total wRVUs}}{\text{Total Encounters}}

    • Dr A:       346.00215≈1.61 wRVUs per visit\frac{346.00}{215} \approx 1.61\,\text{wRVUs per visit}

    • Dr B:       423.25225≈1.88 wRVUs per visit\frac{423.25}{225} \approx 1.88\,\text{wRVUs per visit}

    • Dr C:       341.40237≈1.44 wRVUs per visit\frac{341.40}{237} \approx 1.44\,\text{wRVUs per visit}

    • Result: Dr B produced the highest average work intensity per clinical encounter (1.88 wRVUs per visit1.88\,\text{wRVUs per visit}).

  • Evaluation and Management (E&M\text{E\&M}) Distribution Dynamics:

    • A high proportion of Level-5 visits indicates greater case mix intensity within encounters, but total productivity requires multiplying intensity by total volume.

    • A practitioner managing lower overall patient volume can outperform higher-volume peers in total work output if their clinical service mix involves higher code intensities (e.g., Dr Y completing 210 visits210\,\text{visits} and producing 360 total wRVUs360\,\text{total wRVUs} generated more physician work than Dr X completing 250 visits250\,\text{visits} and generating 330 total wRVUs330\,\text{total wRVUs}).