19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay

AHIMA Certified Documentation Integrity Practitioner CDIP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Authoritative Coding Resources & Conventions

1.1 Official Coding Resources: Scope, Authority & Research 1.2 General Coding Conventions, Punctuation & Instructional Notes 1.3 Chapter-Specific and Setting-Specific Coding Guidelines

2 Chapter 2: Principal & Secondary Diagnosis Determination

2.1 UHDDS Definitions & Principal Diagnosis Selection 2.2 Two or More Diagnoses Equally Meeting Criteria 2.3 Secondary Diagnosis Reporting Standards & POA Status

3 Chapter 3: Procedure Coding & Sequencing Standards

3.1 ICD-10-PCS Root Operations & Inpatient Procedure Coding 3.2 Principal Procedure Selection & Surgical Sequencing 3.3 Applying Official References to Ambiguous Records

4 Chapter 4: Inpatient Prospective Payment & DRG Grouping

4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels 4.2 Working vs. Final DRG Assignment & Optimization vs. Maximization 4.3 CDI-Coding Reconciliation & Annual Regulatory Updates

5 Chapter 5: Enterprise CDI Promotion & Program Value

5.1 Articulating CDI Value to C-Suite & Hospital Leadership 5.2 Organizational Models, Inpatient/Outpatient Scope & Staffing 5.3 Cross-Functional Collaboration: HIM, Quality & Case Management

6 Chapter 6: Cross-Functional Alignment & Improvement Projects

6.1 Partnering with Nursing, Pharmacy & Allied Health Professionals 6.2 Documentation Improvement Project Identification & Scoping 6.3 Executing, Piloting & Measuring CDI Project Outcomes

7 Chapter 7: Physician Champion Engagement & Clinical Advocacy

7.1 Selection, Role & Credibility of the CDI Physician Champion 7.2 Peer-to-Peer Engagement, Coaching & Overcoming Resistance 7.3 Developing Standard CDI Operational Policies & Procedures

8 Chapter 8: Compliant Policy Architecture & Query Governance

8.1 AHIMA/ACDIS Practice Brief Standards in Policy Construction 8.2 Medical Record Integration of Provider Query Responses 8.3 Policies for Electronic, Paper, and Verbal Query Communications

9 Chapter 9: Query Escalation & Professional Communication

9.1 Chain of Command & Protocols for Unanswered Queries 9.2 Conflict Resolution & Professional Feedback Mechanisms 9.3 Assessing Stakeholder Learning Needs & Specialty Curricula

10 Chapter 10: Educational Delivery & Broader Healthcare Impacts

10.1 Delivery Methods: Microlearning, Case Studies & Grand Rounds 10.2 Documentation Impacts on Clinical Research & Epidemiology 10.3 Documentation Impacts on Case Management, LOS & Reimbursement

11 Chapter 11: Clinical Record Synthesis & Encounter Trajectory

11.1 Synthesizing Provider Notes, Consults & Progress Trajectory 11.2 Interpreting Diagnostic Imaging, Pathology & Labs 11.3 Resolving Conflicting, Ambiguous & Copy-Forward Entries

12 Chapter 12: Advanced Clinical Concepts & Review Prioritization

12.1 Pharmacotherapy, Clinical Trajectories & Disease Correlations 12.2 Inpatient Review Prioritization: High-Risk & High-Volume 12.3 Payer Prioritization, Length of Stay & Re-Review Cadence

13 Chapter 13: Clinical Indicator Mapping & Gap Recognition

13.1 Systematic Identification of Documentation Gaps 13.2 Sepsis Definitions, SEP-1, and Coding 13.3 AKI Criteria, Tubular Injury, and CKD Staging

14 Chapter 14: Diagnostic Precision in High-Impact Conditions

14.1 Respiratory Failure: Acuity, Evidence, and Sequencing 14.2 Heart Failure Phenotype, Acuity, and Hypertensive Combinations 14.3 Encephalopathy, Delirium, and Acute Cognitive Change

15 Chapter 15: Clinical Validation & Complication Discrepancies

15.1 Malnutrition Assessment, Severity, and Provider Documentation 15.2 Principles of a Compliant, Nonleading Query 15.3 Open-Ended, Multiple-Choice, and Yes/No Queries

16 Chapter 16: Query Mechanics & Direct Provider Collaboration

16.1 Electronic Query Systems, Templates, and Technology Oversight 16.2 Collaborating With the Appropriate Query Recipient 16.3 Capturing and Clarifying Query Responses

17 Chapter 17: Quality Indicators & Post-Discharge Clarification

17.1 Present on Admission Clarification and Selected HAC Rules 17.2 Clarifying Acuity, Cause, Site and Severity 17.3 Post-Discharge Query Opportunities and Limits 17.4 Managing Post-Discharge Query Workflows

18 Chapter 18: CDI Operational Dashboards & Quality Auditing

18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use 18.2 Internal CDI Quality Audits and Reviewer Calibration 18.3 Query Trends: Understanding the Process and Provider Experience

19 Chapter 19: Benchmarking, Productivity & Data-Driven Workflow

19.1 Provider Documentation Benchmarking 19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay 19.3 Evaluating CDI Professional Performance 19.4 Using Data to Design CDI Workflow and Staffing

20 Chapter 20: Ethical CDI Standards & Regulatory Frameworks

20.1 Applying AHIMA Ethics to CDI Decisions 20.2 Responding to Financial Pressure and Upcoding Risks 20.3 Maintaining Competence and Professional Integrity

21 Chapter 21: Regulatory Compliance & Enforcement Landscapes

21.1 False Claims, Overpayments and Referral Laws 21.2 Regulatory Agencies, Review Contractors and Appeals 21.3 EHR Templates, Copied Text and Record Integrity

22 Chapter 22: Technology Risks & Second-Level Review Protocols

22.1 CAC, NLP and AI: Context, Oversight and Performance 22.2 Selecting Cases for Second-Level Review 22.3 Conducting and Closing a Second-Level Review

23 Chapter 23: Clinical Validation Queries & Risk Mitigation

23.1 Clinical Validation and Coding Clarification 23.2 Clinical Validation Queries and Denial Evidence 23.3 Detecting Leading, Biased and Unsupported Queries

24 Chapter 24: Noncompliant Query Remediation & Query Lifecycle Management

24.1 Query Remediation and Corrective Action 24.2 Query Timeframes, Aging and Measurement 24.3 Query Records, Retention and Evidence Preservation

19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay

Key Takeaways Explain This Topic AI

CMI is the discharge-weighted average of the specified relative weights; identify population, exclusions, grouper and corrections before comparing periods or payers.

MS-DRG 795 is Normal Newborn. HFMA MAP FM-5 excludes normal newborns, so an all-payer comparison must state its inclusion rules rather than assume a fixed Medicare gap.

APR-DRG SOI and ROM are separate classifications, while O/E depends on the defined cohort and risk model. Their distributions do not establish documentation failure, an automatic CC/MCC crosswalk or a payment penalty.

Use corrected Table 5 and actual grouping/exclusions for LOS comparisons; GMLOS is distinct from an arithmetic mean and has specified transfer/payment roles.

Current PEPPER identifies Index Analytics as contractor and quarterly STACH reporting; high outliers are at or above the 80th percentile, with low boundaries at or below the 20th only for coding-focused targets. Outliers do not prove payment errors.

Last updated: October 2026

External Benchmarking: CMI, Severity, Mortality and Length of Stay

An external comparison is useful only when its population and measurement rules fit the question. A different case mix, grouper version, data source or observation window can change a result without any change in documentation quality. Use the comparison to identify a question for investigation, then examine the records and applicable methodology.

Choose the correct source and release

Source What it supplies What to verify

CMS MedPAR Medicare Part A inpatient hospital and skilled nursing facility stay information Release, population, time period, available variables and limits for the proposed comparison

CMS annual IPPS files Published MS-DRG weights, LOS values and related payment-system data Fiscal year, corrections and whether the file uses historical or current grouping

PEPPER Facility-specific Medicare target-area statistics compared with other facilities The target's exact numerator, denominator, exclusions, comparison groups and reporting period

A comparative clinical or hospital database Measures defined by that particular resource Participation, data completeness, population, risk model and version; do not assume every product uses APR-DRGs or claims alone

The CMS MedPAR description identifies it as a stay dataset. It is not itself the annual Table 5 of current DRG weights. The FY2027 IPPS final-rule page separately lists Table 5, correction notices and other files. For example, its published CMI file describes historical FY2025 claims grouped with v42; it should not silently be treated as a v44 re-grouping of the same cases.

Calculate and interpret case mix index

For a defined population using one specified set of MS-DRG weights:

CMI = ∑ g n g w g ∑ g n g \text{CMI}=\frac{\sum_g n_gw_g}{\sum_g n_g} CMI = ∑ g ​ n g ​ ∑ g ​ n g ​ w g ​ ​

Here n g n_g n g ​ is the number of included discharges in group g g g , and w g w_g w g ​ is that group's weight. The denominator counts discharges, not inpatient days. The weight describes relative resource use under the classification; CMI is not a direct measurement of every patient's physiologic severity or the hospital's quality of care.

Hypothetical training weights—not actual CMS DRG values:

• Training group Discharges Weight Weight points
• A 50 1.40 70
• B 100 0.90 90
• C 50 0.60 30
• D 100 1.70 170
• Total 300 360

CMI is 360 / 300 = 1.20 360/300=1.20 360/300 = 1.20 . Do not attach those training weights to named current DRGs. For actual analyses, identify the annual weights and corrections used.

Medicare and all-payer comparisons also need explicit inclusion rules. An all-payer MS-DRG CMI may apply MS-DRG weights to included discharges regardless of how each payer actually pays. It should not mix MS-DRG and APR-DRG relative weights into one unexplained average. Under HFMA MAP FM-5 , normal newborns and specified Medicare-exempt units are excluded. A custom report including them measures a different population.

There is no universal 0.30–0.50-point gap between Medicare and all-payer CMI. Obstetric and neonatal services can change a population's mix, but v44 MS-DRG 795 is Normal Newborn, not normal vaginal delivery . Check the actual definition and inclusion rules instead of attributing every difference to nursery days.

Decompose changes before attributing them to CDI

A new high-resource surgical service, referral change, fewer low-weight discharges, different payer mix, coding correction or updated weights can change CMI. Compare service-line composition and within-group results using compatible definitions. A before-and-after rise alone does not isolate a causal CDI effect.

Case-level validated documentation and coding changes can demonstrate specific contributions. Preserve the original and final grouping assumptions and distinguish newly available clinical information from a correction. Do not label all within-service variation “true CDI yield” or assume that a rise is always desirable.

Keep APR-DRG severity and mortality distinct

Solventum's APR-DRG description distinguishes the base APR-DRG from separate severity-of-illness and risk-of-mortality subclasses. The four subclass labels are minor, moderate, major and extreme. SOI and ROM are different dimensions; neither is the same thing as an MS-DRG CC/MCC designation.

The complete case and the applicable APR-DRG version determine its classification. A condition does not universally increase a subclass, and the same subclass does not mean one fixed individual probability of death in every context. Compare distributions only after checking the population, version and method. An academic hospital with a particular proportion in minor/moderate categories is not thereby proven to have “massive under-capture.” There is no universal community-versus-academic percentage table that establishes that conclusion.

Read an observed-to-expected mortality ratio

For an explicitly defined cohort and outcome:

O/E = Observed deaths Expected deaths \text{O/E}=\frac{\text{Observed deaths}}{\text{Expected deaths}} O/E = Expected deaths Observed deaths ​

In a model that assigns each included patient a predicted death probability, expected deaths are the sum across all included patients , including survivors. The outcome may be inpatient mortality or another defined interval; use the actual measure specification. Claims, clinical records, demographic information or other sources may contribute, depending on the model.

Hypothetical example: Ten observed deaths divided by eight expected deaths gives 10 / 8 = 1.25 10/8=1.25 10/8 = 1.25 . If the same ten observed deaths are compared with ten expected deaths, the ratio is 1.00. That demonstrates the denominator's mathematical effect. It does not establish that adding a particular diagnosis would cause that change in a real model.

Missing valid risk information can affect a model when it uses that information in the relevant time window. But not every additional diagnosis, CC or MCC is an eligible predictor, and not every model uses claims alone. Verify the risk factors, timing, exclusions and version. The CMS risk-adjustment overview and procedures explain those model-specific choices.

A ratio below 1 means fewer observed deaths than expected under that model; a ratio above 1 means more. Interpretation also needs sample size, uncertainty, data quality and model adequacy. It does not automatically prove superior or negligent care, establish a public star rating or trigger a payment penalty. The applicable quality program determines its own measures and consequences. Keep quality-score improvement out of patient-specific queries.

Interpret LOS benchmarks without changing diagnoses to fit them

CMS Table 5 publishes geometric and arithmetic mean LOS separately. A geometric summary differs from an arithmetic average. A hospital's actual arithmetic average divided by published GMLOS is a chosen comparison, not a universal efficiency standard requiring a result at or below 1.00.

For illustration, the FY2027 corrected Table 5 gives these values:

• MS-DRG Description Capped relative weight GMLOS
• 291 Heart Failure and Shock with MCC 1.2685 3.8 days
• 292 Heart Failure and Shock with CC 0.8616 2.9 days
• 293 Heart Failure and Shock without CC/MCC 0.5462 2.1 days

These are version-pinned reference values, not instructions to assign a higher tier. A four-day stay divided by 2.1 is approximately 1.90 ; divided by 3.8 it is approximately 1.05 . Neither calculation determines the patient's diagnosis or proves efficient or inefficient care.

In a case appropriately classified in this family, unspecified AKI N17.9 is a CC, not automatically an MCC placing the case in 291. Principal-diagnosis exclusions and the full case also matter; do not assume pulmonary edema automatically adds an effective MCC to heart failure. Check the actual v44 definitions and exclusions .

Payment rules are another question. IPPS cost outliers depend on applicable cost/payment thresholds, not merely exceeding GMLOS. GMLOS also appears in specified transfer-payment rules and certain transfer outlier calculations; saying it never matters to outliers would also be wrong. See CMS outlier guidance and the Claims Processing Manual, Chapter 3, Section 20.1.2.4 . Use the particular payment rule rather than treating a dashboard ratio as a claim calculation.

Use PEPPER as an audit signal

As of October 2026, the official PEPPER FAQ identifies Index Analytics LLC, with its partners, as the CMS contractor. STACH reports are quarterly; other facility types have their own schedules. Review the report's target definitions rather than treating PEPPER as a universal physician scorecard or a single hospital-wide CC/MCC capture measure.

Distinguish a target-area rate from its percentile rank . In a hypothetical coding-focused target, 18 target discharges among 60 eligible discharges gives 30%. Its national percentile tells where that rate falls among comparison facilities; it is not necessarily the 30th percentile.

PEPPER flags high outliers at or above the 80th percentile . The low boundary is at or below the 20th percentile for coding-focused target areas . These are inclusive boundaries, not simply “above 80” and “below 20.” Low-outlier logic does not apply indiscriminately to every target.

An outlier is not proof of a payment error, leading queries, underdocumentation or a required recoupment. Confirm the target's current definition, population and comparison group; review representative claims and records to understand the pattern. Preserve valid coding, correct demonstrated errors and monitor the result. Neither a percentile nor a desired CMI authorizes adding unsupported diagnoses or suppressing supported ones.