4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels

4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels

An MS-DRG describes a classified discharge. A diagnosis code's CC or MCC label describes one possible role of that code as a secondary diagnosis. Understanding the difference lets a CDI practitioner explain a working group, investigate an unexpected result, and avoid promising a payment change from a diagnosis label alone.

For the examples here, use the final Version 44 MS-DRG definitions applicable to discharges October 1, 2026–March 31, 2027. A different discharge period requires its applicable release. Proposed-rule tables and old severity lists do not substitute for that release.

Classification and payment are related decisions

Under 42 CFR 412.60, a discharge is assigned to one DRG using the applicable information abstracted from its inpatient bill. Inputs include principal and secondary diagnoses, procedures, age, sex, and discharge status, as appropriate. The regulation also provides for relative weights that reflect comparative hospital resource costs and for at least annual classification and weight updates.

The relative weight is not the hospital's payment in dollars. CMS's IPPS overview explains that the base rate has labor and nonlabor shares. The labor share is wage-adjusted; the nonlabor share has an applicable cost-of-living adjustment in Alaska and Hawaii. The adjusted base is multiplied by the DRG weight. DSH, IME, and qualifying outlier payments are additional considerations.

For an operating-base illustration without an applicable nonlabor cost-of-living adjustment:

$\text{DRG-adjusted operating base}=[(\text{Labor share}\times\text{Wage index})+\text{Nonlabor share}]\times\text{Relative weight}$

This expression describes a component of payment. A financial estimate must apply the hospital's and discharge's actual payment rules and adjustments. Calling every IPPS payment fixed regardless of the case's costs or circumstances would overlook, for example, CMS's outlier provisions.

Read the grouper's conditions, rather than inventing a universal shortcut

The v44 Definitions Manual supplies logic tables and code collections. Read the required cells together. A useful review order is:

1. Confirm the inputs and release. Resolve the principal diagnosis, reportable secondary diagnoses, complete procedures, and other applicable inputs before treating a result as final.
2. Check applicable special routes. Pre-MDC logic can assign cases before the usual diagnosis-based MDC route. Its actual predicates matter; a description such as prolonged ventilation does not by itself establish a pre-MDC DRG.
3. Follow the applicable MDC and procedure logic. Procedures have versioned OR attributes, and some non-OR procedures also affect grouping. The physical location where a procedure occurred does not establish its grouper attribute. A surgical hierarchy orders surgical classes; it is not a request to choose the largest weight or move a favored code to the first line.
4. Evaluate the specific group's severity and other conditions. The route may use CC/MCC status, discharge status, specified diagnoses, procedure combinations, or other listed attributes. Not every group has the same three severity branches.

For example, v44's pre-MDC 003/004 logic distinguishes ECMO and qualifying tracheostomy circumstances, including ventilation greater than 96 hours, major OR procedure status, and specified principal-diagnosis relationships. The presence of a ventilation code alone does not determine 003 or 004. A bedside procedure can matter to grouping, and an OR procedure unrelated to principal diagnosis requires the applicable unrelated-OR review. These are classification questions answered by the complete logic and claim, rather than by how dramatic the procedure sounds.

Recognize the actual severity pattern

Appendix A identifies current group titles. These examples illustrate different structures; they do not establish assignment from a clinical label alone.

The 064–066 intracranial hemorrhage/cerebral infarction family has three current titles: with MCC, with CC or tPA in 24 hours, and without CC/MCC. Cervical spinal fusion likewise has 471 with MCC, 472 with CC, and 473 without CC/MCC. Memorizing an outdated two-tier description would produce a wrong interpretation even before any diagnosis exclusion is checked.

Work through baseline status and all applicable exclusions

The manual defines secondary diagnoses as MCC, CC, or NonCC after evaluation of hospital resource use. Those are classification assignments, not diagnoses a reviewer may infer from a laboratory result, a universal length-of-stay threshold, or an informal label such as severe organ failure. Verify the actual complete code and release. First establish the diagnosis and its reportability under the coding guidelines; the desired severity tier does not establish either.

Appendix C supplies three distinct checks:

An exact Part 1 lookup

Suppose a reconciliation screen displays J81.0, acute pulmonary edema, as a potential MCC, with principal code I50.21, acute systolic heart failure. Start by checking whether the edema is separately reportable under the coding rules. A severity lookup cannot authorize adding an otherwise unreportable condition.

For the exclusion lookup itself, v44 Part 1 lists J81.0 as an MCC linked to PDX collection 0999. That collection explicitly includes I50.21. Consequently, J81.0 cannot supply MCC severity against that principal code through Part 1. The conclusion comes from the actual linked collection. A reviewer should not construct an exclusion by deciding that two conditions seem clinically related.

This is a severity exclusion, not an instruction to erase a correctly reportable diagnosis. Conversely, absence from this particular collection does not establish final MCC impact: the remaining applicable checks and the group's actual logic still matter.

Other exclusions can change the result

Part 2 includes R57.0, cardiogenic shock. Its baseline MCC designation does not function as an MCC when the patient is not discharged alive under that provision. Part 3 separately addresses secondary-diagnosis suppression in selected groups, such as the listed respiratory-infection and inflammation groups. Neither check is replaced by looking only at the Part 1 principal-diagnosis collection.

Selected-HAC/POA rules are another applicable consideration. As in the prior POA lesson, continued reportability and final grouping are distinct questions. A suppressed diagnosis does not automatically establish a particular lower DRG or dollar loss; other qualifying diagnoses and procedures remain part of the claim.

Understand the limited ceiling within an unchanged family

Assume a complete claim has been correctly classified into the 291–293 family, one secondary MCC qualifies after all applicable checks, and no other routing conditions change. The claim is at the family's with-MCC tier. Adding another qualifying MCC does not create a fourth severity tier or add a second DRG weight. Similarly, more CCs do not create a tier above with CC when no MCC qualifies and the route remains unchanged.

Those assumptions are essential. A newly established diagnosis can affect another part of the classification logic, and payment has rules beyond the severity split. It is inaccurate to promise that every additional MCC always adds zero dollars to every case.

Complete documentation still serves clinical communication and correct reporting. A remaining qualifying diagnosis may preserve a severity tier if a different diagnosis is removed, but that must be verified by regrouping the corrected claim. It does not guarantee that an appeal succeeds or that no recoupment occurs. Likewise, a reportable secondary condition does not necessarily enter every quality or risk model, raise expected mortality, or generate a Medicare Advantage payment. Apply the specific model's rules when evaluating those separate uses.

Distinguish APR-DRG severity from MS-DRG tiers

The current Solventum APR-DRG overview describes an inpatient classification for all patient populations, including newborns, pediatrics, and obstetrics. Its severity logic considers the number, nature, and interaction of comorbidities within the base APR-DRG. Payers choose configurations, update schedules, prices, and payment policies; the classification alone does not establish reimbursement.

Solventum's methodology eGuide describes a base APR-DRG, a severity of illness (SOI) subclass, and a separate risk of mortality (ROM) subclass. Each subclass can be minor, moderate, major, or extreme. SOI and ROM describe different dimensions, so their levels need not match. An SOI level is not a dollar amount, a ROM level is not a percentage probability, and the levels are not a simple count of diagnoses. Use the applicable methodology and payer policy to interpret an actual result rather than converting an MS-DRG MCC label directly into an APR-DRG level.