Study guide
11.3 SOI/ROM as CDI Program Performance Metrics
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
11.3 SOI/ROM as CDI Program Performance Metrics
Key Takeaways Explain This Topic AI
APR-DRG severity of illness (SOI) and risk of mortality (ROM) are each four subclasses: 1 minor, 2 moderate, 3 major, 4 extreme
SOI and ROM are scored independently; a stay can be high SOI with lower ROM, or the reverse
Coded secondary diagnoses—together with principal diagnosis, age, and certain procedures—feed the grouper; CDI specialists do not type a 1–4 into the claim
MS-DRG payment commonly uses CC/MCC presence to choose among two or three family tiers; that is not a four-level independent SOI/ROM score
Average SOI/ROM and the share of subclass 3–4 cases can be program metrics, but they are mix-sensitive and must not become query quotas
Last updated: September 2026
11.3 SOI/ROM as CDI Program Performance Metrics
Quick Answer: Under All Patient Refined Diagnosis Related Groups (APR-DRGs) , severity of illness (SOI) and risk of mortality (ROM) are four-level subclasses ( 1 minor, 2 moderate, 3 major, 4 extreme ) scored independently . Secondary diagnoses—with principal diagnosis, age, and certain procedures—feed those scores. That is a different severity engine from MS-DRG CC/MCC payment tiers. Programs may track SOI/ROM distributions as performance metrics; they must not treat a higher subclass as a query quota.
IPPS payment for most Medicare acute inpatient stays uses MS-DRGs. Many hospitals still run APR-DRG grouping in parallel for quality profiling, some Medicaid or commercial contracts, and internal severity dashboards. CCDS Domain IV expects you to use SOI and ROM as program metrics without confusing them with CC/MCC. (Chapter 20 returns to SOI/ROM in mortality-index work; this section stays on how the scores are built and how a CDI program should read them.)
Four levels, two independent subclasses
APR-DRG assignment gives each stay three descriptors: a base APR-DRG , an SOI subclass , and an ROM subclass .
SOI denotes the extent of physiologic decompensation or organ-system loss of function. ROM denotes the likelihood of dying. They are related clinical ideas and they are not the same number .
- Subclass Label SOI idea ROM idea
- 1 Minor Limited decompensation Limited likelihood of dying
- 2 Moderate Intermediate Intermediate
- 3 Major Significant organ-system loss of function Significant mortality risk
- 4 Extreme Overwhelming physiologic decompensation Extreme likelihood of dying
The four SOI subclasses and four ROM subclasses are numbered 1 through 4. A stay can be SOI 4 and ROM 2 , or SOI 2 and ROM 4 . A program that reports “severity” as a single digit has already collapsed the model.
APR-DRG logic uses principal diagnosis, secondary diagnoses and their combinations , age, sex, and certain procedures. CDI specialists do not key a 1–4 into the grouper. The grouper infers subclasses from coded data. Unspecified, unlinked, or missing secondary diagnoses produce subclasses that understate how sick the patient was. Manufactured secondary diagnoses produce subclasses that will not survive audit.
Independence is the exam trap. A patient can consume large hospital resources (high SOI) without a high short-term likelihood of dying (lower ROM)—for example, a severe but usually survivable acute illness with intensive monitoring. Another patient can carry high mortality risk (high ROM) without the same burst of acute organ-failure resource use (lower or moderate SOI). If a stem says SOI and ROM “always move together,” that statement is false.
How secondary diagnosis documentation feeds the scores
Uniform Hospital Discharge Data Set (UHDDS) secondary diagnoses are conditions that received clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care or monitoring. When those conditions are specified and linked where linkage matters, they become coded secondary diagnoses. The APR-DRG methodology then asks not only “is a CC present?” but how those diagnoses interact for that base APR-DRG.
That is why “add any secondary diagnosis” is not a severity strategy. A symptom that is integral to the principal diagnosis may add no SOI. Two moderate conditions together may raise SOI more than either alone. Age can modify ROM. A procedure can change the base APR-DRG before subclasses are applied.
CDI’s program-metric job is to make the coded severity match the clinical severity that was already present , by clarifying type and acuity (systolic versus unspecified heart failure; acute versus unspecified kidney injury), linkage when the classification requires it (organ dysfunction due to sepsis), conditions that were treated but named only in ancillary notes until a provider documents them, and clinical validation when a high-severity label has no support.
Moving a population’s average SOI from 2.1 to 2.4 can be appropriate capture or it can be label inflation. As with CMI, pair the metric with validation and with mix . A month heavy with elective low-risk surgery will suppress average SOI even if medical CDI is excellent. A software or grouper-version change can move averages without any chart changing. Domain IV analysis names those confounders instead of declaring a CDI victory or collapse.
Contrast with MS-DRG CC/MCC tiers
Feature MS-DRG (typical IPPS payment) APR-DRG SOI/ROM
Usual role on a Medicare acute IPPS claim Payment grouping Severity and mortality-risk profiling (and some non-MS-DRG payment systems)
Typical severity split inside a family With MCC / with CC / without CC/MCC (some families have fewer splits) Four SOI levels and four ROM levels
What one secondary diagnosis can do An eligible MCC (not excluded) often moves the case to the MCC-paying MS-DRG; a CC may move it to the CC-paying MS-DRG Contributes to a 1–4 scale that considers combinations, not a single CC flag
“How sick” versus “how likely to die” No separate ROM score for IPPS payment SOI and ROM scored independently
Who assigns the severity label Grouper from codes using CMS CC/MCC lists and exclusions Grouper from codes using APR-DRG severity logic
Common CDI dashboard CMI and CC/MCC capture Mean SOI, mean ROM, share of SOI-3/4 or ROM-3/4 cases
A case can have no MCC for MS-DRG purposes and still reach a high APR-DRG SOI if multiple interacting diagnoses meet that methodology. The reverse also happens: a single MCC can lift MS-DRG payment while APR-DRG ROM stays moderate. Domain IV items that treat “we captured an MCC, therefore ROM is 4” are testing that confusion.
Do not report APR-DRG subclass changes as IPPS dollar impact unless the hospital is actually paid on APR-DRG for that stay. Mixing the engines is how a program double-counts value. CC and MCC are not the names of APR-DRG subclasses; they are CMS severity categories inside MS-DRG logic.
Using SOI/ROM as performance metrics
Programs commonly track mean SOI and mean ROM for the hospital, a service, or a high-frequency APR-DRG; the percent of discharges at SOI 3 or 4 and, separately, ROM 3 or 4; mortality by SOI/ROM cell (deaths in extreme ROM should not shock anyone; deaths in ROM 1 should prompt review); and change after a documentation initiative compared with a control service.
These are lagging, mix-sensitive metrics, like CMI. They are useful when you hold the base APR-DRG or service line roughly constant and you have a clinical-validation backstop. They are harmful when leadership sets “average SOI must be 3.0” as a specialist goal. That goal recreates the query-quota problem from section 11.1: specialists hunt for extreme labels instead of for accurate labels. Putting “please document extreme mortality risk to improve our ROM metric” on a query also fails the 2026 ban on quality-outcome language on the query.
Scenario: high SOI, lower ROM. A 62-year-old is admitted with severe acute pancreatitis, large fluid resuscitation, and a week of intensive monitoring, then goes home. Resource use is high, so SOI can be high, while inpatient death risk for that trajectory may be lower, so ROM need not match. If the record only says “abdominal pain, unspecified,” both subclasses understate the stay. If CDI queries for pancreatitis acuity and treated complications that indicators already support, SOI/ROM can rise because the chart now matches the care . If CDI queries “please document extreme mortality risk” to move a dashboard, the query is leading and the metric is corrupted.
Scenario: ROM moved, capture did not. A monthly report shows average ROM up 0.2 while MS-DRG CC/MCC capture is flat. Honest explanations include APR-DRG-sensitive diagnoses that are not MCCs being specified, age mix changing, a high-ROM service growing, or a grouper version changing. A dishonest explanation is “ROM is the same thing as MCC capture.” Analyze the engines separately.
Track SOI/ROM to see whether coded secondary diagnoses reflect physiologic severity and mortality risk. Do not use them as a fourth query quota, and do not substitute them for MS-DRG CMI when the question is IPPS payment.