Study guide
20.1 Documentation Impact on Mortality Index (SOI/ROM)
Certified Clinical Documentation Specialist CCDS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways and the 2,000-Hour Year 1.3 Allowed Resources and Test-Day Rules 1.4 Recertification, Fees, and How This Guide Maps the Eight Domains
2 IPPS Foundations
2.1 How IPPS Works and How CMS Updates It 2.2 MS-DRG Assignment, Relative Weights, and Grouping 2.3 Provider and Clinical Staff Documentation Duties under IPPS
3 Severity, CMI, Medical Necessity, and Oversight
3.1 CC versus MCC Recognition and CC Exclusion Lists 3.2 Case Mix Index and Why CDI Tracks It 3.3 Two-Midnight Rule, Medical Necessity of Setting, and Principal Diagnosis 3.4 MAC, RAC, CERT, OIG, and Denial-Vulnerable Practices
4 Nervous and Respiratory System CDI
4.1 Nervous System Conditions for CDI 4.2 Acute and Chronic Respiratory Failure, ABGs, and Ventilation Support 4.3 Pneumonia, COPD, PE, Pleural Effusion, and Respiratory Infections
5 Circulatory, Digestive, Hepatobiliary, Musculoskeletal, and Skin CDI
5.1 Circulatory Disorders 5.2 Digestive and Hepatobiliary Disorders 5.3 Musculoskeletal and Skin
6 Endocrine, Nutrition, Kidney, and Hematologic CDI
6.1 Diabetes, Dehydration, and Obesity 6.2 Malnutrition Criteria, Severity, and Audit Risk 6.3 AKI, CKD Staging, UTI, and Urinary Stones 6.4 Anemia, Coagulation, Sickle Cell, Lymphoma, and Leukemia
7 Infectious Disease, Other MDCs, and Clinical Indicator Tools
7.1 Sepsis, Severe Sepsis, Postoperative and Other Infections 7.2 Mental, Substance Use, Injuries/Toxicology, and HIV-Related Conditions 7.3 Medications, Diagnostic Tests, and Abbreviations as Clinical Indicators
8 Health Record Elements and Query Triggers
8.1 Which Record Elements Support Diagnosis and Procedure Codes 8.2 Attending versus Radiologist, Pathologist, and Other Providers 8.3 When a Physician Query Is Warranted 8.4 When Queries Are Not Appropriate
9 Query Timing, Verbal Queries, Formats, and Clinical Indicators
9.1 Concurrent, Retrospective, Pre-Bill, and Prospective Timing 9.2 Verbal Queries and Required Documentation 9.3 Open-Ended, Multiple-Choice, and Yes/No 9.4 Clinical Indicators and How to Source Them
10 Compliant Query Practice and Clinical Validation
10.1 Compliant versus Leading and Other Noncompliant Queries 10.2 ACDIS/AHIMA 2026 Guidelines for Achieving a Compliant Query Practice 10.3 Clinical Validation and Diagnoses without Clinical Support
11 CDI Program Metrics
11.1 Productivity, Query Volume, and Provider Response Rates 11.2 CMI, CC/MCC Capture, and High-Frequency DRGs 11.3 SOI/ROM as CDI Program Performance Metrics
12 Physician Metrics, PEPPER, Forecasting, and Public Data
12.1 Measuring Physician Documentation Performance 12.2 PEPPER, Forecasting, Hospital Financial Data, and Public Reporting
13 CDI Roles, Coder Collaboration, and Physician Education
13.1 Roles and Responsibilities of the CDI Specialist 13.2 Coder Roles Working with a CDI Department 13.3 Physician Education Tools, Forms, and Presentations
14 Provider Communication and DRG Reconciliation
14.1 Non-Confrontational Communication and When Verbal Beats Written 14.2 Working DRG versus Final DRG Reconciliation
15 Official Guidelines, Principal Diagnosis, and Secondary Diagnosis
15.1 Official Guidelines, Cooperating Parties, Updates, and AHA Coding Clinic 15.2 Principal Diagnosis Selection 15.3 Secondary Diagnosis Reporting Criteria
16 Sequencing, Coding Conventions, and POA Indicators
16.1 Sequencing When Two Diagnoses Equally Meet PD; Working DRG with Multiple Diagnoses 16.2 Integral Signs/Symptoms, the With Convention, and Uncertain Diagnoses 16.3 Present-on-Admission Indicator Assignment and Payment Impact
17 Hospital-Acquired Conditions, Disposition, and ICD-10-PCS Essentials
17.1 CMS Hospital-Acquired Condition Payment Provision 17.2 Discharge Disposition, Transfer Payment, Principal Procedure, and ICD-10-PCS Essentials
18 Ethics, Privacy, and Leading Queries as Compliance Failures
18.1 ACDIS Code of Ethics and CDI Goals beyond Reimbursement 18.2 HIPAA, Minimum Necessary, and Record Confidentiality 18.3 Leading Queries as a Compliance Failure
19 DRG Creep, OIG Oversight, PEPPER, and the False Claims Act
19.1 DRG Compliance, DRG Creep, and the OIG Work Plan 19.2 PEPPER Compliance Risks and the False Claims Act
20 Mortality Index, Observed-to-Expected Ratios, and Quality Data Sources
20.1 Documentation Impact on Mortality Index (SOI/ROM) 20.2 Mortality Reviews and Observed-to-Expected Ratios 20.3 Abstracted versus Claims-Based Quality Data
21 CMS Quality Programs, PSIs, and Infection versus Complication Codes
21.1 HVBP, HAC Reduction Program, HRRP, 30-Day Mortality, and Hospital IQR 21.2 PSI 90 Components and PSIs beyond the Composite 21.3 Healthcare-Associated Infections versus Complication Codes
20.1 Documentation Impact on Mortality Index (SOI/ROM)
Key Takeaways Explain This Topic AI
APR-DRG severity of illness (SOI) and risk of mortality (ROM) are independent 1–4 subclasses (minor, moderate, major, extreme), not MS-DRG CC/MCC payment tiers
A mortality index commonly compares observed deaths with expected deaths; coded diagnoses feed the expected side when the hospital uses APR-DRG ROM or a similar claims-risk model
Valid, reportable secondary diagnoses can raise expected risk through the grouper; CDI specialists do not type a 1–4 subclass onto the claim
Under-documentation of true severity leaves expected deaths too low, so the same observed deaths make outcomes look worse
Compliant queries may not use quality-outcome or reimbursement language to chase a ROM subclass; unsupported diagnoses that inflate expected risk are an integrity failure
Last updated: September 2026
20.1 Documentation Impact on Mortality Index (SOI/ROM)
Quick Answer: All Patient Refined Diagnosis Related Groups (APR-DRGs) assign severity of illness (SOI) and risk of mortality (ROM) as independent subclasses 1–4 (minor, moderate, major, extreme). Valid secondary diagnoses that meet reporting criteria raise the expected risk the model assigns. Under-documentation leaves expected risk too low, so the same observed deaths make the mortality index look worse.
Domain VIII asks a different question than Domain IV. Chapter 11 treated SOI and ROM as program metrics —averages, subclass 3–4 shares, and mix caveats. This section treats them as the risk story behind a mortality index: how the coded record tells a severity engine whether a death was statistically surprising. Medicare Severity Diagnosis Related Groups (MS-DRGs) still drive most Inpatient Prospective Payment System (IPPS) payment. APR-DRG grouping often runs in parallel for quality profiling, some Medicaid or commercial contracts, and vendor mortality dashboards. Confusing the two engines is a classic exam miss: a CC or MCC can move payment and still leave ROM too low for the death the clinicians actually managed.
Independent 1–4 subclasses, not a single “severity” digit
APR-DRG assignment (3M methodology, used widely in inpatient quality work) produces three descriptors for each stay: a base APR-DRG , an SOI subclass , and an ROM subclass .
SOI is the extent of physiologic decompensation or organ-system loss of function. ROM is the likelihood of dying. They are related clinical ideas and they are not the same number . Each subclass is 1 minor, 2 moderate, 3 major, or 4 extreme . A stay can be SOI 4 and ROM 2 , or SOI 2 and ROM 4 . A dashboard that reports “severity” as one digit has already hidden the mortality problem.
- Subclass Label SOI idea ROM idea
- 1 Minor Limited decompensation Limited likelihood of dying
- 2 Moderate Intermediate physiologic loss Intermediate death risk
- 3 Major Significant organ-system loss of function Significant mortality risk
- 4 Extreme Overwhelming decompensation Extreme likelihood of dying
CDI specialists do not key “ROM 4” onto the claim or the abstract. The grouper infers subclasses from principal diagnosis , secondary diagnoses and their combinations , age , sex , and certain procedures . Unspecified, unlinked, or missing secondaries produce subclasses that understate how sick the patient was. Manufactured secondaries produce subclasses that will not survive audit or clinical validation.
MS-DRG families commonly split with major complication or comorbidity (MCC) / with complication or comorbidity (CC) / without CC or MCC . That is a two- or three-tier payment engine plus a CC exclusion list that can neutralize a CC or MCC. It is not an independent four-level SOI/ROM pair. Do not treat “we captured an MCC” as proof that expected mortality is correct.
How SOI/ROM become a mortality index
Hospitals and vendors convert risk-adjusted mortality into a ratio. The form used throughout CDI teaching is:
Mortality index ≈ observed deaths ÷ expected deaths
Some tools label that ratio the mortality index; some invert it; a few report observed-minus-expected counts. Read the local definition. The interpretation CCDS items expect for the usual observed-to-expected (O/E) form is directional: when expected deaths are understated , the ratio rises even if the death count does not change.
Observed deaths are actual deaths in the cohort the model defines . In-hospital expiration is common for APR-DRG ROM profiling. Centers for Medicare & Medicaid Services (CMS) public mortality measures often use a 30-day window and a different claims model (Chapter 21). Those are not interchangeable numbers.
Expected deaths are the sum of predicted death probabilities for the stays in that cohort. When APR-DRG ROM (or another coded-risk engine such as a vendor model that consumes ICD-10-CM) is the risk adjuster, documentation that becomes coded diagnoses is a major input to expected value.
The numerator is largely a fact of who died. The denominator is a function of how completely the record described how sick they were. That split is the documentation impact Domain VIII tests.
Documentation state Typical coded risk Expected deaths Same 10 observed deaths How the index looks
Complete, valid secondaries ROM closer to true risk Higher (example 12.5) 10 / 12.5 = 0.80 Fewer deaths than expected
Missing shock, acute organ failure, metastatic disease, severe malnutrition, or linked acute respiratory failure ROM too low Lower (example 7.5) 10 / 7.5 = 1.33 More deaths than expected
Unsupported secondaries added to inflate ROM ROM too high; audit risk Artificially high Ratio may look better until recoded Integrity failure, not a quality win
The 7.5 and 12.5 figures are teaching arithmetic only . CMS and vendors do not publish a single national “correct” expected-death table for you to memorize, and you should not invent relative weights. Memorize the direction : under-capture of valid risk inflates the index; accurate capture raises expected and can move the index toward or below 1.0 without changing who died.
Valid secondaries raise expected risk—when they are reportable
A secondary diagnosis affects APR-DRG SOI/ROM only if it is coded . It should be coded only if it meets Uniform Hospital Discharge Data Set (UHDDS) reporting logic used with the ICD-10-CM Official Guidelines for Coding and Reporting : clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care and/or monitoring—or if the guidelines otherwise require reporting. Dumping the entire problem list into the discharge summary does not automatically raise expected risk. Vague labels (“history of cancer,” “renal insufficiency,” “altered mental status”) often fail to carry the ROM weight of metastatic solid tumor , acute kidney injury with a specified stage, or metabolic encephalopathy when those are the conditions actually evaluated and treated.
Conditions that frequently move ROM when they are clinically present and documented include shock, acute respiratory failure, acute organ dysfunction linked to the underlying disease, anoxic brain injury, metastatic malignancy, and severe protein-calorie malnutrition. Conditions that more often move SOI include extensive multi-system decompensation that consumes resources even when immediate death risk is not the dominant story. Because the subclasses are independent, documenting only the resource-intensive complications can lift SOI while ROM still understates lethality. Mortality indices that use ROM-weighted expected deaths follow death risk, not “how busy the floor was.”
Age and procedures still feed the grouper. A review that ignores a young adult with the same shock physiology, or that ignores an operating-room procedure the logic uses, will misread the score. CDI leverage remains reportable diagnoses that are true , not a target subclass.
Under-documentation makes outcomes look worse
Picture two clinically identical deaths from septic shock with acute hypoxemic respiratory failure and acute kidney injury. Hospital A’s record supports those diagnoses as reportable secondaries (or as principal diagnosis when UHDDS “after study” logic points there). Hospital B’s record says “sepsis,” “shortness of breath,” and “elevated creatinine” without linking organ dysfunction or naming acute respiratory failure. Hospital B’s expected mortality is lower. Both hospitals count one observed death . Hospital B’s ratio looks worse.
A high mortality index can mean true excess mortality, a sicker mix the model cannot see, coding error, or a mixture. CDI’s ethical job is to reveal true risk, not to manufacture it. The August 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice still require a nonleading query with sourced clinical indicators and no reimbursement or quality-outcome language . Do not write “please document acute respiratory failure to improve our mortality index.” Place the indicators (arterial blood gas, ventilator support, documented hypoxemia, vasopressors, treatment) and let the provider name the diagnosis. Provider judgment stays independent. If the chart cannot support shock, do not chase ROM 4.
Worked documentation path
An 82-year-old is admitted from home with pneumonia and dies on hospital day 4. The attending wrote “pneumonia, DNR, family meeting.” The record also contains norepinephrine for a mean arterial pressure of 55 mm Hg after fluids, invasive mechanical ventilation, lactate 6.2 mmol/L, creatinine rising from 0.9 to 2.4 mg/dL, and bilateral infiltrates on imaging. Without clarification, coding may report pneumonia plus “hypotension” or unspecified kidney disease. APR-DRG ROM may sit at 2. The death looks unexpected relative to coded risk.
If the provider documents septic shock , acute hypoxemic respiratory failure , and acute kidney injury with clinical support, ROM can rise (often toward 3 or 4 depending on the rest of the cluster—do not memorize a guaranteed subclass). Expected mortality for that stay increases. Observed death is still one. The cohort index moves because the denominator moved.
Present on admission (POA) does not rewrite APR-DRG SOI/ROM the way it rewrites some Patient Safety Indicator and hospital-acquired condition logic, but POA still belongs in the completeness conversation: a high-lethality condition that started after admission is a different quality story than the same condition present at the inpatient order. Do not collapse those stories. Do not invent an unpublished CMS cut score for “acceptable” ROM among decedents.
Traps that invert the mortality-index story
Treating SOI and ROM as the same subclass, or as CC versus MCC.
Believing a higher MS-DRG relative weight automatically repairs the mortality index.
Putting mortality-index or reimbursement language in the query.
Adding unsupported diagnoses to “help quality.”
Assuming every problem-list secondary raises ROM.
Confusing in-hospital APR-DRG expected deaths with CMS 30-day mortality models.
Trying to change observed deaths by recoding discharge status from expired to something else—that is not CDI work; it is a compliance failure.