One BMI, Three Questions, One Connected Workflow

Key Takeaway

The takeaway isn’t just that each team has a role. It’s that information needs to move between them.

  Coding: Can we report it?

  CDI: Does the documentation support the clinical picture?

  Denials: Can we defend it if challenged?

Those are different questions, but they’re all tied to the same patient record.

A new, more specific code can expose a documentation gap that was always there but never had to be named. A documentation gap can create denial risk. And denial trends can point right back to opportunities in CDI and coding, if anyone is looking for them.

For leaders, the bigger question is: are those insights making their way back upstream?

What that looks like in practice

The two new BMI codes effective October 1 didn't change any of the underlying rules. They just made an existing gap easier to see. BMI codes still require an associated, reportable diagnosis, and that diagnosis, and must be backed by clinical evidence that withstands payer scrutiny. Ultimately, denials are rarely about the BMI code itself. They're about whether the underlying diagnosis was fully documented, clinically supported, and defensible in the medical record.

Three teams, three parts of the same question. When they operate as connected functions instead of separate steps, a few things start to happen:

• A coding change, like a new code or a guideline update, prompts a documentation and workflow review, not just a coder in-service.
• CDI patterns, like a recurring gap between a BMI value and a diagnosis, shape coding education before it becomes a habit.
• Denial findings, like a specific set of diagnoses driving clinical validation denials, inform both teams before the next claim goes out the door, not after the appeal is due.

The question worth asking in your own organization

It’s rarely whether Coding, CDI and Denials are each doing their job. Most of the time, they are. The more useful question is whether what one team learns is reaching the other two, or whether each is solving its part of the same problem in isolation, on its own timeline, without the others knowing there was a problem at all.

That’s the opportunity in a connected middle revenue cycle: not just getting each step right, but making sure each step informs the next.

If that connection isn't happening consistently in your organization, that's worth a conversation. Talk to us (link) about how UASI helps mid revenue cycle teams work as one connected function instead of three separate ones. 

About the Author

Autumn Reiter, MBA, BSN, RN, CCDS, CCDS-O, CDIP, CCS

Chief Strategy and Solutions Officer at UASI

A registered nurse with 20 years of experience and a BSN from Virginia Commonwealth University, Autumn began her career as a CDI specialist and has spent more than a decade building and leading CDI programs at scale. At CorroHealth, she advanced from Director of Clinical Documentation Improvement to Vice President of CDI Services and Tech Enablement and, most recently, Senior Vice President of Payment Integrity and Provider Risk Strategies. Now Chief Strategy and Solutions Officer at UASI, she pairs frontline CDI insight with the business perspective of an MBA from Western Governors University, helping healthcare organizations strengthen documentation accuracy, protect revenue integrity, and connect clinical care to financial performance.