Patterns That Raise Fraud & Abuse Red Flags

Fraud and abuse investigations rarely start with one claim. They start with patterns. Trends that say, “Something here doesn’t look like everyone else.” That’s why pattern awareness is one of the most powerful skills an inpatient coder or auditor can develop.

When coders and auditors hear “fraud and abuse,” it’s easy to picture a single egregious claim – a wildly inaccurate DRG or a clearly unsupported diagnosis. In reality, most serious investigations begin with something much less dramatic: patterns in the data that don’t look like everyone else.

Payers, regulators, and external auditors are trained to spot outliers long before they look at individual charts. They ask: Where does this facility, department, or provider deviate from typical coding and reimbursement behavior? Once they find those hotspots, that’s where the deeper review starts.

As coders and auditors, we can either be surprised by those patterns when someone else finds them—or learn to spot them ourselves and address the root causes before they become serious problems.

Pattern 1: High‑Weighted DRGs Showing Up Too Often

One of the clearest red flags is an unusually high rate of certain high‑weighted DRGs compared to peer hospitals or internal benchmarks.

If a facility seems to code into the highest‑paying DRGs more often than similar organizations, payers naturally wonder whether:

• Acuity is truly higher, or
• Coding and documentation practices are pushing cases into higher categories without sufficient support.

This doesn’t mean those DRGs are wrong. It does mean they’ll attract attention. For coders and auditors, the question becomes: Does the documentation for these cases consistently support the level of severity the DRG implies? If the documentation support is uneven, that pattern has already become a risk.

Pattern 2: Sudden Shifts After Policy or Financial Changes

Another pattern that raises suspicion is a noticeable shift in coding behavior following internal policy changes, new financial targets, or operational initiatives.

Examples include:

• A spike in certain DRGs immediately after a new “documentation improvement” campaign.
• A sharp increase in CC/MCC capture after the introduction of new query templates.
• A department that suddenly shows much higher case mix indices following a coding guideline change.

Again, these changes may reflect real improvements in documentation and accuracy. But from a fraud and abuse perspective, abrupt jumps can look like someone “turned a dial” rather than natural evolution. Coders and auditors who understand this will always ask not just what changed in the numbers, but why.

Pattern 3: High Case Mix Without Matching Documentation Quality

A third pattern to watch is departments or physician groups with consistently higher case mix and severity than peers—but without consistently stronger documentation.

If a particular service line shows:

• Higher average DRG weights,
• More frequent CC/MCC capture, or
• More complex principal diagnoses,

yet the documentation looks thin, inconsistent, or ambiguous, it creates a gap that external reviewers are almost guaranteed to explore. From their perspective, that department appears to be telling a more severe clinical story than the record can fully support.

When you combine high acuity, high payment, and weak documentation, you’ve created the perfect environment for denials, take‑backs, and deeper scrutiny.

How Experience with Trends and Root Causes Helps

In my own work leading inpatient coding and DRG audit divisions, I’ve spent years watching these patterns play out in real time: across facilities, within departments, and even at the level of individual provider groups.

What I’ve learned is that the most effective way to respond isn’t to blame coders or shut down initiatives, it’s to look for root causes:

• Are teams unclear on how guidelines apply to certain diagnoses?
• Are query templates unintentionally leading providers toward higher acuity language?
• Are productivity pressures affecting how much time coders spend reconciling documentation conflicts?
• Are providers and coders unclear on the documentation gaps that could mitigate these trends?

By pairing trend analysis with education, you can move a team from “we didn’t realize this looked risky” to “we understand why this pattern draws attention, and we know how to fix it.”

Questions Coders and Auditors Should Ask When They See Unusual Patterns

You don’t need a full analytics shop to start thinking like a pattern‑aware coder or auditor. Whenever you notice a trend that feels “off,” ask a few simple questions:

1. Is there a clear clinical or operational reason for this trend?
   For example: a new specialty module, a shift in patient population, or legitimate changes in acuity?
2. Does the documentation consistently support the higher acuity or complex DRGs we’re seeing?
   If support is uneven, that inconsistency becomes a risk point, even when some charts are rock‑solid.
3. Have we recently changed our query practices, coding guidelines, or documentation expectations?
   Sudden jumps after such changes aren’t automatically bad—but they need to be explained and, ideally, validated.
4. Would we feel confident walking an external reviewer through this pattern and our rationale?
   If your explanation is vague or heavily reliant on “that’s just how we do it,” it’s time to dig deeper.

These questions help shift coders and auditors from purely transactional work—code this chart, move to the next—to a more strategic role that anticipates how their work will look when someone steps back and reviews the big picture.

From Transactional Coding to Risk‑Aware Coding

Pattern awareness is one of the fastest ways coders and auditors can move from “transactional coding” to “risk‑aware coding.” When you start seeing DRGs, diagnoses, and procedures as part of a broader story—across time, departments, and provider groups—you’re no longer just assigning codes. You’re helping protect your organization from avoidable scrutiny.

In future articles, I’ll share specific chart‑level examples of how these patterns show up on the ground and how a few targeted changes in documentation, query practice, and audit focus can defuse red flags before they draw unwanted attention.

For now, consider this an invitation: the next time you look at your facility’s metrics or a batch of audit results, don’t just ask “What are the numbers?” Ask, “What story are these patterns telling—and would an external reviewer find that story believable?”