Mid-sized health systems need a different RCM model

Mid-sized health systems carry enterprise-level revenue cycle complexity without enterprise-level redundancy. Multiple facilities, specialties, payer contracts, and technology systems create the same need for specialized expertise found in larger organizations, while smaller teams leave less capacity to absorb a backlog, employee departure, or change in payer behavior.

This imbalance makes the mid-sized health system revenue cycle financially distinct. Complexity extends across the organization, while expertise and available capacity often remain concentrated among a limited number of people. Protecting cash therefore requires a revenue cycle management model built around earlier capacity signals, shared decision logic, and scalable execution before a local disruption affects billing or payment.

Mid-sized complexity requires a tailored operating model. | The Mid-Sized Operating Gap

Mid-sized systems occupy a distinct position between smaller providers and large enterprises. They may support hospitals, physician groups, and outpatient locations across different payer environments without maintaining dedicated specialist coverage for every facility or revenue cycle function. Their operating model needs enough flexibility to preserve local knowledge while promoting consistent performance across the organization.

A team may have sufficient capacity for routine eligibility, authorization, coding, or billing work while relying on one or two experienced employees to resolve complex exceptions. Staffing can therefore appear adequate even when coverage for payer-specific edits or specialty workflows remains limited.

This difference changes how leaders need to evaluate capacity. Headcount shows how many people work within a function. Coverage depth shows whether the system can maintain the decisions required to keep reimbursement moving. Understanding this distinction helps protect cash conversion and forecasting accuracy.

Margin pressure makes this issue more consequential. The American Hospital Association reported that labor represented 56% of hospital costs in 2024, while Medicare and Medicaid underpayments totaled $130 billion in 2023. Limited room to absorb disruption makes unresolved workflow problems financially significant.

Concentrated expertise can increase reimbursement exposure. | Concentrated Expertise Creates Exposure

Experienced employees often connect complex payer rules with local clinical and administrative workflows. One specialist may understand how an insurer applies authorization requirements to a particular service line. Another may know why documentation from one location repeatedly produces coding holds.

When this knowledge remains informal, coverage plans may replace processing capacity without replacing the judgment required for exceptions. Unresolved work can accumulate in authorization, documentation, coding, or billing queues. The financial effect appears when claims leave the workflow later or require added correction.

Exposure can extend across several parts of a mid-sized organization when the same specialist supports multiple facilities or specialties. Leaders can assess the dependency by asking:

• Which decisions require specialized payer or clinical knowledge?
• How much reimbursement depends on timely resolution?
• How many employees can complete the work independently?
• When will unresolved work begin to affect payment?

These questions reveal dependencies that volume measures can miss. They also help leaders decide where cross-training, workflow documentation, or added specialist capacity will provide the greatest financial value.

Local disruptions consume capacity across lean teams. | Local Disruptions Spread Quickly

‍Many mid-sized systems organize work by facility, specialty, or function to retain local expertise and clarify ownership. This structure can also make it difficult to see how an issue originating in one area consumes capacity elsewhere.

An eligibility error at one clinic may later become a claim edit, denial, and aged balance handled by different teams. Weaknesses in patient access management can create downstream corrections, while limited medical coding capacity can slow claims from a high-value specialty. Employees may eventually resolve each account, although repeated intervention increases the cost to collect.

This effect carries greater risk when resolving one backlog requires redirecting employees from another function. A contained issue can become a sequence of delayed handoffs through access, coding, billing, and A/R follow-up.

A connected operating model returns downstream findings to the workflow where the defect originated. Denial patterns can inform scheduling and registration changes, while payer variance can guide contract oversight and follow-up priorities. This feedback helps reduce revenue leakage without asking lean teams to correct the same problem repeatedly.

Capacity needs to be measured in financial terms. | Capacity Needs Financial Measures

A/R days and cash collections reflect work completed across prior weeks. Mid-sized systems benefit from earlier measures because they may have fewer available employees to redirect after a backlog begins affecting several functions.

Queue size alone provides an incomplete view. Two queues with the same account count may carry different financial exposure based on age, expected reimbursement, payer requirements, and the expertise needed for resolution.

Useful measures include:

• ‍Queue age: Time work remains unresolved within each function.
• ‍Specialist-dependent volume: Accounts requiring intervention from a limited group.
• ‍First-pass exception rate: Work leaving the standard workflow for manual review.
• ‍Coverage depth: Employees qualified to complete high-risk work independently.
• ‍Cash at risk: Expected reimbursement attached to delayed accounts.

Segmentation by payer, facility, specialty, and process stage prevents enterprise averages from hiding local deterioration. One facility may accumulate coding holds while another experiences authorization delays, even when systemwide A/R remains stable.

Revenue resilience depends on distributing capability. | Resilience Requires Distributed Capability

Many mid-sized systems cannot maintain a separate specialist team for every revenue cycle risk. Building revenue resilience depends on identifying which capabilities require internal coverage and where the organization needs flexible access to additional expertise.

Cross-training provides value when employees can make the decisions involved, rather than process routine transactions alone. Effective coverage combines documented workflows with payer-specific decision logic and clearly defined escalation paths.

Leaders also need to distinguish temporary pressure from structural weakness. A short-term rise in A/R inventory may require added execution after an implementation or unexpected departure. Recurring backlogs may indicate upstream defects, unclear ownership, or insufficient specialist coverage.

Technology can strengthen this model when deployed inside a governed workflow. Revenue cycle technology working within existing systems can identify accelerating queues and recurring exceptions. McKinsey’s 2026 healthcare analysis identifies prior authorization, claims management, and medical records among the areas where healthcare organizations are applying AI.

Mid-sized systems can gain value when technology expands capacity without adding another disconnected queue or weakening practitioner oversight. A repeatable operating model can also scale revenue cycle capacity as the organization adds facilities, practices, or service lines.

How Vee Healthtek supports mid-sized health systems. | Vee Healthtek's Approach

Mid-sized health systems need a revenue cycle model designed for their balance of operational breadth and specialist depth. Financial exposure can grow when critical knowledge remains concentrated or when resolving one problem redirects capacity from another priority.

Vee Healthtek identifies where limited coverage, aging queues, and concentrated expertise create disproportionate reimbursement risk for mid-sized health systems. Practitioner-led analysis traces these pressures across facilities and functions to determine whether the underlying issue involves a temporary capacity gap, a recurring workflow defect, or specialist knowledge held by too few people. This distinction helps leaders address the source without shifting employees from another revenue-critical priority.

Scalable execution adds specialized depth where and when the organization needs it, while preserving leadership oversight across existing systems and governance structures. Open Accountability connects each intervention to measurable outcomes, including queue reduction, fewer repeated account touches, improved cash timing, and more predictable reimbursement. Mid-sized multi-facility health systems gain a flexible way to manage disruption and growth without creating a separate internal team for every payer, specialty, or revenue cycle exception.

‍

Key takeaways

• Mid-sized systems manage broad revenue cycle complexity with fewer layers of specialist coverage.
• Staffing totals can conceal dependence on experienced employees who resolve high-risk exceptions.
• Local problems can spread when teams redirect limited capacity from another priority.
• Capacity measures provide greater decision value when connected to expected reimbursement.
• Distributed expertise and defined intervention triggers strengthen revenue resilience.

‍