HIM Practice Questions and Project Planning Review

Project Planning and Process Management Tools

  • PERT Chart (Program Evaluation and Review Technique)

    • Definition: A network diagram where each activity is represented as a node, with arrows indicating the necessary sequence of tasks.

    • Function: Used for planning a project by mapping every activity, the specific order in which they must occur, and the projected duration for each, including the determination of the critical path.

    • Distinction: Unlike a Gantt chart, it emphasizes the structure of dependencies and the network of activities.

  • Gantt Chart

    • Purpose: Provides a visual timeline of tasks against a calendar using horizontal bars to show start and end dates.

    • Limitation: While it shows when tasks occur, it does not typically map out complex task dependencies as a network in the same way a PERT chart does.

  • Flowchart

    • Purpose: Used to map the step-by-step sequence and decision points of a repeatable process from start to finish.

    • Application: Ideal for ensuring team members understand a process (e.g., how a coding process runs or how a claim moves through billing).

    • Components: Uses arrows and symbols to show branches, decisions, and outcomes.

  • Benchmark

    • Definition: A single reference point or target used for comparison against industry standards or peer institutions.

    • Establishment Rule: When establishing departmental benchmarks, a director must first determine if the data source is from a comparable institution (similar size, patient mix, and setting) before implementation.

  • Fishbone Diagram (Ishikawa/Cause-and-Effect)

    • Purpose: A root cause analysis tool used to identify and organize contributing causes to a problem.

    • Structure: Organizes causes into major branches such as People, Process, Policy, Technology, and Environment, all pointing toward a central problem (the "spine").

    • Application: Used for open-ended brainstorming to understand why a problem like poor documentation compliance is occurring.

  • Force-Field Analysis

    • Purpose: A tool used to weigh the forces pushing for a change against the forces resisting it to decide how to implement something new.

Data Visualization and Monitoring

  • Dashboards

    • Definition: A real-time data monitoring tool that pulls multiple key metrics (e.g., productivity, denials, turnaround time) onto a single screen.

    • Key Feature: Provides "at a glance" information using gauges and small charts, allowing for immediate decision-making without viewing separate reports.

  • Line Graph

    • Function: Best for displaying trends over a continuous period of time (e.g., years or months).

    • Application: Used to track a single continuous measure, such as the number of deaths due to breast cancer from 2012 through 2022, to make trend directions (rising or falling) obvious.

  • Pareto Chart

    • Function: Ranks problems or causes by frequency to identify the most significant factors.

    • 80/20 Rule: Based on the principle that a few causes often account for most of the trouble.

  • Histogram

    • Function: Shows the distribution of values across specific ranges (e.g., patient age groups).

    • Limitation: It does not track changes over time, distinguishing it from line graphs.

  • Scatter Diagram

    • Function: Tests for correlation or relationship between two variables (e.g., hours worked versus error rate).

  • Pie Chart

    • Function: Shows how various parts make up a whole (e.g., percentage of denials by reason).

    • Constraint: It cannot show sequencing, scheduling, or trends over time.

Outpatient Status Indicators and APCs

  • Status Indicators (OPPS)

    • On an outpatient hospital bill, every CPT/HCPCS code is assigned a status indicator (a single letter) that dictates the Medicare payment logic.

    • V (Clinic or ER Visit): Always paid at 100%100\%.

    • S (Significant Procedure): Stands on its own; always paid at 100%100\%.

    • X (Ancillary Service): Includes tests like X-rays or labs; always paid at 100%100\%.

    • T (Significant Procedure - Subject to Discounting):

      • If only one T-status code appears on a claim, it is paid at 100%100\%.

      • If multiple T-status codes appear on the same claim, the highest-paid code is paid at 100%100\%, and subsequent T-status codes are discounted (typically paid at 50%50\%\text{ of the allowed rate}).

  • Example Case Study (Status Indicator T):

    • Claim contains: 99285-25 (V), 25500 (T), 72050 (X), 72128 (S), 70450 (S).

    • Result: Code 25500 is paid at 100%100\% because it is the only T-status indicator in that specific encounter.

  • Ambulatory Payment Classifications (APCs)

    • APCs group CPT/HCPCS codes that are clinically and resource-similar.

    • A single claim can have multiple procedures but fewer unique APCs if different codes map to the same APC.

    • Example Calculation: A claim with five codes where two codes map to APC 0283 results in only 4 unique APCs (e.g., APC 0612, 0044, 0261, 0283).

HIM Statistics and Quality Calculations

  • Fixed Percentage Random Sample Audit

    • Formula: Work Output×Sample Percentage\text{Work Output} \times \text{Sample Percentage}

    • Example for a 5%5\% audit on four coders:

      • Coder A: 500×0.05=25500 \times 0.05 = 25

      • Coder B: 480×0.05=24480 \times 0.05 = 24

      • Coder C: 300×0.05=15300 \times 0.05 = 15

      • Coder D: 360×0.05=18360 \times 0.05 = 18

      • Total Records Required: 25+24+15+18=8225 + 24 + 15 + 18 = 82

  • Average Daily Census

    • Formula: Total Inpatient Service DaysNumber of Days in the Period\frac{\text{Total Inpatient Service Days}}{\text{Number of Days in the Period}}

    • Example: Community Hospital had 3,000 inpatient service days for September (30 days).

    • 3,00030=100 patients per day\frac{3,000}{30} = 100 \text{ patients per day}

  • Full-Time Equivalent (FTE) Staffing Calculation

    • Formula: Total Annual Work Hours RequiredHours Worked by One FTE per Year\frac{\text{Total Annual Work Hours Required}}{\text{Hours Worked by One FTE per Year}}

    • Step 1: Calculate total work hours needed. Example: 12,500 records at 30 minutes (0.5 hours0.5\text{ hours}) per record = 6,250 hours6,250\text{ hours}.

    • Step 2: Divide by annual FTE hours (2,080). 6,2502,0803.0\frac{6,250}{2,080} \approx 3.0.

    • Requirement: 3 employees.

  • Completion/Timeliness Rate

    • Formula: Compliant RecordsTotal Records Sampled×100\frac{\text{Compliant Records}}{\text{Total Records Sampled}} \times 100

    • Example: 150 sampled records, 13 out of compliance.

    • 15013=137 compliant records150 - 13 = 137\text{ compliant records}

    • 137150×100=91.3%\frac{137}{150} \times 100 = 91.3\%

  • Case-Mix Index (CMI)

    • Definition: The average relative weight per discharge.

    • Formula: Sum of Relative DRG WeightsTotal Number of Discharges\frac{\text{Sum of Relative DRG Weights}}{\text{Total Number of Discharges}}

    • Example: Sum of weights = 15,192; discharges = 10,471.

    • 15,19210,471=1.45\frac{15,192}{10,471} = 1.45

    • Note: A CMI > 1.0 suggests the hospital treats cases more resource-intensive than a typical case.

Productivity and Performance Improvement

  • Telecommuting Impact on Staffing

    • Scenario: 5 FTEs handle 100 discharges/day (20 per FTE20 \text{ per FTE}). Volume increases to 144/day. Telecommuting increases productivity by 20%20\%.

    • New Productivity: 20×1.20=24 discharges per FTE20 \times 1.20 = 24 \text{ discharges per FTE}.

    • Total FTEs Needed: 14424=6 FTEs\frac{144}{24} = 6 \text{ FTEs}.

    • Additional Hires Needed: 65=1 additional FTE6 - 5 = 1 \text{ additional FTE}.

  • Productivity vs. Quality

    • Analysis of scanning staff data reveals that high production rates (e.g., 1,700 images/hour) can correlate with high error rates (7%7\%).

    • Recommendation: Quality expectations should be incorporated directly into productivity standards so that speed does not compromise accuracy.

  • Performance Improvement Recommendations

    • If a delinquency rate fluctuates above a established benchmark (e.g., 35%35\%), the correct action is to analyze the data further to determine why the benchmark is not being met, specifically investigating recent upward trends rather than ignoring or loosening the target.

Clinical Coding Case Study

  • CPT Selection for Hernia Repair

    • Scenario: Laparoscopic incisional herniorrhaphy for a recurrent reducible hernia, including mesh insertion.

    • Code Selection Factors:

      • Approach: Laparoscopic (excludes codes for open procedures like 49560, 49565, and 49568).

      • Type: Recurrent (excludes initial repair codes).

      • Condition: Reducible.

    • Correct Code: 49656 (Laparoscopy, surgical, repair, recurrent incisional hernia, reducible).

    • Note: Code 49656 includes mesh insertion; therefore, code 49568 (intended for open repairs) should not be reported separately.