Hospital CFOs: You May Be Throttling Your Own Margin
- Tracy Bostrom
- 4 days ago
- 2 min read
For healthcare finance leaders wrestling with margin compression despite clean RCM dashboards.
I spend a lot of time with hospital CFOs and health system finance leaders who are doing everything "right."
Revenue cycle management dashboards look clean. Denials are under control. Days in AR are reasonable. Vendors are hitting their KPIs.
And yet, hospital margin compression persists.
The instinct is always the same: look harder at Revenue Cycle. Push vendors. Tighten follow-up. Add oversight.
But here's what I've learned over decades inside hospital operations:
Most margin problems aren't revenue leakage. They're revenue throttling.
And the throttle isn't being applied by payers or RCM vendors. It's being applied upstream, by your own systems, before Revenue Cycle ever sees the encounter.
The Invisible Throttle on Hospital Revenue
Revenue Cycle can only collect what the organization gives it permission to bill. That permission is set long before a claim touches a clearinghouse.
It's set by:
Registration habits normalized under volume pressure
Clinical documentation patterns that understate intensity
Facility guidelines that haven't been updated in years
None of these show up as revenue leakage. None trigger denials. All of them quietly compress what you're allowed to capture.
By the time your revenue cycle management team sees the encounter, the story is already written, and it's often incomplete.
Why This Revenue Integrity Issue Stays Hidden
The most dangerous problems aren't the ones throwing alarms. They're the ones that look stable enough to stop asking questions.
Your RCM team is optimizing within the lane they've been given. The issue is that the lane is too narrow, and it's self-imposed.
Example: Many hospitals rely on standardized acuity guidelines baked into their EHR. The data looks consistent. The rules are compliant. The dashboards stay green.
What's easy to miss? Medicare explicitly allows—and expects—hospitals to tailor those frameworks to reflect the resources actually used at your facility. When that customization never happens in your revenue integrity workflow, you're running compliant… and throttled.
Throughput looks fine. Capacity is constrained. Hospital margins erode.
What Happens When You Remove the Throttle
My work at Cigal focuses on that upstream gap, where operational decisions shape the data before it ever reaches Revenue Cycle.
I don't audit charts after the fact. I don't re-code visits. I don't second-guess clinical judgment.
I look at where care delivery, clinical documentation, and billing rules have drifted out of alignment. I find patterns that have become invisible simply because they're familiar.
When those patterns are corrected in this revenue integrity framework:
Revenue Cycle performance doesn't work harder—
it stops operating behind a constraint it didn't create and can't see
Claims don't become riskier—they become more accurate through better clinical documentation improvement
Margin doesn't spike from aggressive tactics—it stabilizes when the system is allowed to tell the full story
The Question Worth Asking
If your RCM dashboards look fine but hospital margin compression persists, you're probably not missing something downstream.
You're likely throttling something upstream.
The problem isn't who's collecting the revenue. It's how much of the story you're allowing to be told before collection ever begins.
That's where I work.




Comments