The Revenue Cycle is Broken (Because It Was Designed That Way)

The average ambulatory practice loses a significant portion of collectible revenue to administrative friction—not to fraud, undercoding, or difficult payers, but to the ordinary drag of a system that makes getting paid harder than it needs to be.

The scale of that drag is measurable: by the end of 2023, 15 percent of initial claims were denied for payment, up from 9 percent in 2016, according to McKinsey. Prior authorizations alone cost care delivery organizations an average of $6 to $11 per claim, at a rate of roughly 45 per physician per week. Think about what happens after a single patient encounter: a provider documents the visit, a coder interprets that documentation and assigns billing codes, a biller submits the claim, and a payer adjudicates it—often across multiple disconnected systems, with manual handoffs at every step. Any one of those transitions is a place where errors enter, information gets lost, and revenue quietly slips away before anyone notices.

The frustrations most practices feel in revenue cycle management aren’t the result of bad luck or poor execution. They’re the predictable output of a system that was never designed to make reimbursement straightforward in the first place.

What is revenue leakage in healthcare?

Revenue leakage in healthcare refers to the gap between what a practice earns through care delivery and what it actually collects. It’s not typically the result of outright fraud or dramatic billing failures. It accumulates in smaller, harder-to-see places:

• Claims denied on first submission due to coding errors or missing documentation
• Authorization delays that push encounters past the timely filing windows
• Charge capture gaps when clinical documentation doesn’t cleanly translate to billable codes
• Write-offs are accepted as “normal” because chasing them costs more than recovering them
• Manual re-entry between systems introduces errors at every transition

Revenue leakage is often invisible precisely because it’s distributed. No single event looks catastrophic. But across thousands of encounters a year, the sum is significant—and in most practices, it’s treated as an acceptable cost of doing business rather than a solvable problem.

That normalization is the real issue.

Why is the revenue cycle so complicated?

The healthcare revenue cycle is complicated because it was built by multiple systems—clinical, financial, regulatory, and administrative—that were never designed to work together. Each layer added requirements without removing the ones underneath.

Payer rules introduced complexity. Regulatory requirements added documentation burdens. EHR adoption digitized existing workflows without redesigning them. The result is a process where a single patient encounter can touch a dozen systems, require manual handoffs between clinical and billing staff, and still fail to produce a clean claim on the first attempt.

The administrative overhead isn’t incidental to the revenue cycle. In many ways, the revenue cycle system is so dependent on human intervention to bridge gaps, that the people managing it have become load-bearing walls.

There’s also a structural misalignment of incentives. Payers benefit from claim complexity. Clearinghouses charge per transaction. Legacy EHR vendors charge for integrations that should have been native from the start. The practice bears the cost of it all.

What looks like an operational inefficiency is actually a design outcome.

What are the hidden costs of a legacy EHR?

This is the question most practices aren’t asking, and the one that matters most when evaluating the total cost of ownership.

The license fee is the number that gets negotiated. But the real cost of a poorly designed EHR shows up in:

• Provider time. The average physician spends five hours per day interacting with their EHR: documentation, re-entry, workarounds, and the slow accumulation of tasks that were never clinical work. At that rate, a 10-provider practice loses more than 14,000 hours a year before a single patient is seen.*
• Revenue cycle performance. A system that doesn’t connect clinical documentation to coding and billing natively creates friction at every step. Clean claim rates suffer. Days in A/R extend. First-pass denial rates rise. The revenue that should follow care delivery gets delayed, reduced, or lost entirely.
• Staff burden. Prior authorizations, eligibility verification, and scheduling follow-ups that fall to clinical and front-desk staff aren’t just inefficient; they’re a leading driver of burnout and turnover. Replacing a single medical assistant costs an average of $14,200—roughly 40% of an annual salary, once recruiting, onboarding, and training are factored in. These costs rarely appear in the same spreadsheet as the EHR budget.
• Growth capacity. A practice operating at administrative capacity can’t take on more patients without adding staff. A platform with broken workflows caps growth—not because the practice isn’t capable, but because the infrastructure won’t scale.

When you add it up, the true cost of a poorly designed EHR isn’t the license fee. It’s the revenue you never collected, the hours you can’t get back, and the growth you couldn’t pursue.

Why was the system built this way?

It’s tempting to frame revenue cycle dysfunction as a technology problem waiting for a technology solution. But the architecture goes deeper than software.

The U.S. healthcare payment system was built on complexity. Fee-for-service reimbursement requires granular documentation of every service delivered. Payer contracts vary by plan, region, and specialty. Regulatory requirements layer on top of clinical requirements, which in turn layer on top of billing requirements.

EHRs were adopted into this environment without fundamentally changing it. They digitized the paper; they didn’t redesign the workflow. So the same handoffs that existed between paper charts and billing departments now exist between clinical modules and revenue cycle tools. They’re just faster, and they generate more data that has to be managed.

This is why patching a legacy EHR rarely solves revenue cycle problems at their root. Adding a bolt-on AI coding tool to a system that wasn’t built for end-to-end data flow doesn’t eliminate re-entry. It creates a new integration to maintain and a new place for data to break.

The practices that are starting to move past this aren’t finding better bolt-ons. They’re asking whether their infrastructure was built from the ground up to connect clinical work to reimbursement without the gap.

What getting paid accurately actually requires

Getting paid accurately and on time for the care you deliver requires a system that treats clinical documentation and revenue cycle management as parts of the same workflow, not as separate functions that have to be bridged.

That means:

• Clinical data captured during the encounter flows directly into coding and billing, with no manual reconciliation
• AI-assisted coding that improves accuracy at the first pass, not after denials have already accumulated
• Automated eligibility and prior authorization that removes the human bottleneck before it becomes a cash flow problem
• Revenue cycle KPIs that are visible, trackable, and tied to specific workflow decisions—not black-boxed in a separate system

None of this is theoretical. Practices operating on platforms designed with this architecture, where the workflow runs continuously from pre-encounter to payment posting, are seeing measurable improvements in clean claim rates, days in A/R, and provider time returned to clinical work.

The revenue cycle doesn’t have to be this complicated. It was designed to be. The question is whether your platform is working with that design or against it.

*Results based on a 10-provider practice with 15 staff members, $4.6M in annual revenue, and 46-48K encounters/year.