In our last article, we talked about how fraud and abuse concerns often start with patterns in the data—unusual DRG mixes, sudden shifts in coding behavior, or departments with higher case mix that documentation doesn't quite justify.
Patterns are powerful, but they only matter if they're visible at the chart level.
Today, let's walk through how those patterns show up in individual cases, and what coders and auditors can do when they see them.
Case Example 1: The "Always Complex" Heart Failure Stay
You're auditing a series of inpatient heart failure cases from the same service line. You notice that almost all of them land in a higher‑weighted DRG because of a CC/MCC—often acute respiratory failure.
On paper, this looks like a pattern of legitimately complex heart failure patients. But when you open the charts, you see something different:
- The provider mentions "acute respiratory failure" once in the assessment, with no supporting objective data.
- Nursing notes describe shortness of breath, but there's no discussion of mechanical ventilatory support or significant gas exchange abnormalities.
- The discharge summary lists acute respiratory failure as a diagnosis, but doesn't describe how it was treated or resolved.
Individually, each chart might have passed as "technically coded." Taken together, they show a pattern of high‑impact secondary diagnoses without consistently strong documentation.
Coder/auditor action:
- Flag the series for focused documentation review and education.
- Work with CDI on documentation concerns and what isn't supported.
- Adjust query templates and internal guidance so they reinforce clear criteria rather than just naming conditions that raise DRG weight.
This turns a pattern‑level red flag into a chart‑level improvement opportunity—before an external reviewer does the same analysis.
Case Example 2: The "Post‑Policy" Sepsis Spike
Your facility adopts new sepsis guidelines and launches an education push. Three months later, sepsis diagnoses surge across multiple service lines.
When you pull a sample of charts, you find:
- Some cases with classic sepsis: infection, organ dysfunction, clear systemic response.
- Some borderline cases where the term "sepsis" appears, but clinical indicators are limited or inconsistent.
- A handful of charts where sepsis seems to have been added late in the stay with minimal explanation.
At the aggregate level, this is a sudden shift after a policy change. At the chart level, it's a mix of strong and weak cases that could easily be interpreted as "aggressive coding" if not carefully reviewed.
Coder/auditor action:
- Separate charts into clearly supported sepsis, borderline sepsis, and non‑sepsis profiles.
- Collaborate with clinical and documentation leadership to align sepsis criteria, documentation expectations, and coding rules.
- Refine queries so they seek clarification on suspected sepsis without nudging providers toward the diagnosis in borderline cases.
The goal is to preserve legitimate sepsis recognition while reducing noise—so your sepsis pattern looks more like clinical reality and less like a coding swing.
Case Example 3: Orthopedic Short Stays with High Complexity
Your data shows a particular orthopedic group with consistently higher case mix for short inpatient stays than their peers.
In the charts:
- Many cases have multiple secondary diagnoses coded, including chronic conditions and vague "complication" language.
- Documentation mentions complex medical histories but doesn't clearly describe how those conditions impacted the hospital stay.
- Length of stay and treatment plans look similar to lower‑complexity peers.
From a pattern perspective, this looks like "high severity short stays." From a chart perspective, it looks like heavy coding of comorbidities without linking them to the inpatient course.
Coder/auditor action:
- Review how coders are interpreting chronic conditions and complications in this group's charts—are they linking them to current care or just listing them?
- Provide targeted education on the difference between "documented history" and "clinically relevant comorbidity for this stay."
- Encourage providers to document explicitly when a chronic condition materially changes risk, monitoring, or treatment during the stay.
This helps your DRG assignments reflect true clinical complexity, not just long problem lists.
Turning Case Examples into Team Learning
These case‑level patterns aren't just "gotchas" for audits—they're teaching tools.
A few ways to build them into your team's practice:
- Case rounds: Choose one pattern (e.g., sepsis, respiratory failure, short‑stay complexity) and walk through 3–5 charts as a group, highlighting what makes each case strong or vulnerable.
- Checklists: Create simple, pattern‑specific checklists for coders and auditors: "For sepsis charts, do we see X, Y, Z clinical elements?" "For acute respiratory failure, do we see objective evidence and treatment?"
- Feedback loops: When internal or external audits flag cases, trace them back to pattern‑level questions: "Is this a one‑off, or part of a trend?" "What education or guideline update would prevent similar cases?"
The more you connect the dots between data patterns and chart‑level realities, the more you move your team from reactive fixes to proactive risk management.
From Red Flags to Roadmaps
Patterns and case examples aren't just ways to find problems. They're ways to design better processes.
When coders and auditors:
- Notice outlier trends,
- Drill down to representative charts, and
- Work with clinical and documentation leaders to address root causes,
they're no longer just defending codes. They're helping shape a more accurate, defensible story of patient care.
In upcoming pieces, we'll dig into specific topics coders ask about most often—like "What does a defensible CC/MCC look like?" and "How do we distinguish true acuity from documentation noise?" Each one will build on the same foundation: seeing our work the way a neutral reviewer would, and using that view to strengthen both reimbursement and integrity.
Miss the first article in this series?
Share this article