6.2 MCC/CC Identification and Reimbursement Risk
Key Takeaways
- MCCs and CCs are severity designations used by the MS-DRG system, not independent permission to code a diagnosis.
- A secondary diagnosis must first meet reporting criteria before its MCC or CC effect matters.
- High-impact diagnoses such as acute respiratory failure, sepsis, encephalopathy, malnutrition, and acute kidney injury require strong documentation and clinical consistency review.
- Audit defensibility depends on provider documentation, clinical indicators, POA status, and clear evidence of resource use or clinical significance.
MCC and CC Logic Begins With Reportability
A major complication or comorbidity, or MCC, and a complication or comorbidity, or CC, are MS-DRG severity concepts. They help distinguish cases with greater expected resource use from less complex cases in the same DRG family. However, an MCC or CC label does not make a diagnosis codable. The coder must first determine whether the condition is a reportable secondary diagnosis under official guidelines and facility policy. Only then does its severity designation matter for grouping.
Reportable secondary diagnoses generally require more than a mention. The record should show clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, increased nursing care or monitoring, or another documented impact on care. A chronic condition may be reportable if it affects management during the stay, such as chronic kidney disease influencing medication dosing or fluid decisions. A past condition that no longer exists is usually history, not a current MCC or CC.
The reimbursement risk is two-sided. Missing a valid MCC or CC may understate patient severity, distort quality data, and reduce legitimate payment. Capturing an unsupported MCC or CC may create overpayment, false claim exposure, payer denial, and coder ethics risk. CCS-level judgment is not simply finding every severe-sounding word. It is deciding whether the coded condition is current, provider-documented, clinically supported, reportable, correctly sequenced, and assigned the proper POA indicator.
High-Risk MCC/CC Review Table
| Diagnosis area | Why it is high risk | Defensible coder action |
|---|---|---|
| Sepsis | Can shift DRG and quality measures; documentation may conflict with criteria | Verify provider diagnosis, infection source, treatment, organ dysfunction, and timing |
| Acute respiratory failure | Often depends on severity, oxygen support, and provider statement | Review blood gases, oxygen needs, work of breathing, and treatment intensity |
| Encephalopathy | Must distinguish toxic, metabolic, unspecified, delirium, dementia, and baseline status | Look for mental status change, cause, treatment, and provider linkage |
| Malnutrition | Severity affects DRG and is frequently audited | Validate dietitian findings, provider agreement, treatment plan, and present-on-admission status |
| Acute kidney injury | May be documented from lab movement alone or true clinical diagnosis | Confirm provider diagnosis, baseline renal function, treatment, and clinical significance |
A coder should not use clinical criteria to overrule a provider diagnosis, but coders are expected to validate that documentation supports code assignment and to query when the record is unclear, conflicting, or missing needed specificity. For example, if a provider documents acute respiratory failure but the record only shows routine oxygen after anesthesia with no persistent distress, the coder should not silently delete or automatically code the condition without analysis. If facility policy indicates clinical validation review, the coder may need to escalate or query with non-leading clinical indicators.
MCC/CC Decision Checklist
- Is the condition documented by a provider authorized to establish diagnoses for coding?
- Is it current for this encounter rather than historical, ruled out, or copied forward without support?
- Does it meet secondary diagnosis reporting criteria?
- Is the code specific enough to capture acuity, type, cause, stage, or complication status?
- Does POA status match the admission timeline and provider documentation?
- Are there clinical indicators supporting the diagnosis, or is a compliant query needed?
- Does the final DRG make clinical sense when compared with the record?
Consider a patient admitted for acute on chronic systolic heart failure. The progress notes mention chronic kidney disease stage 3, diabetes with insulin use, and acute kidney injury. The creatinine rose from a baseline documented in prior records, nephrology evaluated the patient, diuretics were adjusted, and renal function was monitored daily. In this case, AKI may be reportable if provider-documented and clinically managed. If the only mention is a lab comment from a non-provider or an encoder suggestion based on creatinine, coding AKI as an MCC or CC would be risky without provider documentation.
Another common scenario involves malnutrition. A dietitian may document severe protein-calorie malnutrition and recommend supplements, but coding rules require provider documentation or provider agreement for a reportable diagnosis. A compliant query can present dietitian assessment findings, weight loss, intake history, muscle or fat loss findings, albumin only if clinically relevant and not used alone, and treatment recommendations. The query should ask the provider to clarify the diagnosis supported by the record. It should not say that severe malnutrition is needed for an MCC.
Documentation conflicts are also testable. If the discharge summary states postoperative anemia due to acute blood loss, but the progress notes only say expected drop in hemoglobin, the coder must resolve the conflict. If the diagnosis would change reimbursement or quality reporting, unsupported capture is especially vulnerable. The correct exam answer usually involves reviewing the full record and querying for clarification when the record contains conflicting provider statements.
MCC/CC analysis also intersects with exclusion logic. Some secondary diagnoses do not count as an MCC or CC in certain DRG families because they are closely related to the principal diagnosis. A grouper handles those rules, but coders need to recognize why a documented condition may not change the DRG. If a condition is reportable, code it even when it does not affect payment. If it is not reportable, do not code it just because the grouper would pay more.
For CCS preparation, practice explaining each MCC or CC in one sentence: the provider documented it, the record shows it was clinically significant, the code is specific, the POA status is supported, and the final DRG impact was reviewed. That sentence is an audit defense. If you cannot say it honestly, the case needs more review.
Which statement is most accurate about MCC and CC diagnoses?
A dietitian documents severe malnutrition, recommends supplements, and the provider does not address nutrition status. What is the best next step if the facility permits querying?
Why should coders review clinical consistency for high-impact MCC or CC diagnoses?