What Commure Means for Healthcare Practices

If you run the operations of a healthcare practice, the question that matters is not whether Commure raised money — it is which of your daily tasks change, what they cost after the change, and who on your team does what next. This piece answers exactly that.

The context, briefly: Commure is an AI platform whose agents automate revenue cycle, documentation, coding, and prior authorization, and on May 19, 2026 it raised capital at a $7 billion valuation. That hub piece explains what it is. This one is about your operation specifically.

Who should care

This is for the practice administrator, billing manager, or physician-owner at an independent or mid-size practice (roughly 3–50 providers) who is currently running prior auth, coding, and denial management with a mix of human staff and a legacy EHR or RCM tool. The pain it touches is capacity: too much low-judgment paperwork, not enough hands, and rising denial rework.

Red flags: This is probably not for you if (1) you are a solo provider with low claim volume where a staff member already handles everything in a few hours a week, (2) your EHR is a closed system with no integration path and a vendor that blocks third-party automation, or (3) your leadership is unwilling to retrain staff from "do the task" to "review the exceptions" — without that shift, automation relocates work instead of removing it.

What changes, task by task

The honest way to think about this is per-workflow, because the savings are uneven. Prior authorization is the highest-volume, most-rules-driven task, so it changes the most. Clinical documentation changes meaningfully but still needs clinician sign-off. Coding sits in between.

The volume that automation attacks is documented. According to the AMA's prior-authorization survey, practices complete an average of 39 prior authorizations per physician per week, with physicians and staff spending 13 hours weekly on them, per the AMA's reporting. For a five-physician practice, that is roughly 195 authorizations and 65 staff-hours every single week — before a single denial is appealed.

What it costs — and what it saves

The cost case rests on the gap between manual and automated transaction handling. According to the CAQH Index, U.S. healthcare avoided $258 billion in administrative costs in 2024 through automation, with a remaining $21 billion opportunity in transactions still done by hand, per CAQH's reporting. At the practice level, that macro number translates into staff-hours reclaimed per week.

According to that same CAQH Index, more than 25% of provider organizations now use AI tools in administrative workflows — meaning your competitors for staff and margin are already moving. And per Commure's funding announcement, its agents complete 85%+ of revenue cycle work without human intervention across 500+ organizations — the number to test against your own books, not to take on faith.

Worked example

Take a five-physician primary-care practice. Using the AMA's figure of 39 prior authorizations and 13 staff-hours per physician per week, that practice handles roughly 195 authorizations and 65 staff-hours weekly. If agents handle the routine share and a human only reviews exceptions, then applying the Commure-stated 85% no-human completion rate as illustrative arithmetic leaves about 29 authorizations and roughly 10 hours per week needing human judgment — a reduction of about 55 staff-hours weekly that the practice can redeploy or not backfill. In an integration, the trigger is a real event: when the EHR fires a notification.eligibility_check (or an equivalent inbound authorization request), the agent picks it up, assembles the packet, and only routes the exceptions to a queue. The 85% figure is a vendor claim to validate against your own reworked-claim count, not a promise — but even at half that rate the staff-hour math reshapes a billing department.

Staffing decisions this forces

The hard part is not the software; it is the org chart. When 85% of a task completes itself, the question is what the people who used to do it now do. The good news is that demand for those people is not disappearing — the profession is short-staffed to begin with.

According to the AMA, 40% of physicians have staff working exclusively on prior authorizations, and 89% say the work drives burnout, per the AMA's survey. Automation does not fire those people in a healthy practice — it moves them from data entry to exception review, denial strategy, and patient-facing work that actually needs a human.

The firms that operationalize this first treat it as a workflow redesign, not a layoff. Practices routing intake and payer documents through US Tech Automations workflows reassign the freed hours to the contested denials and complex appeals where humans recover the most revenue — the exact 15% the agents hand back.

To make the staffing math concrete, it helps to scale the per-physician burden up to a whole practice and look at where the hours actually go. The table below applies the AMA's per-physician figures across practice sizes — the weekly volume and hours are arithmetic from those sourced figures, and they show why even a partial automation rate moves a real number of full-time-equivalent hours.

Those annual hours are the prize and the risk in one column. A 10-physician practice spending roughly 6,500 staff-hours a year on prior auth alone (AMA-derived) has a large pool to reclaim — but only if it redesigns the role rather than simply layering a tool on top. The practices that capture it are the ones that decide, in advance, what the freed staff will do next: work denials, manage appeals, or take on the patient-facing tasks that improve collections.

Signal vs Speculation

Sourced facts above this line. Our analysis below.

Our read on the facts: the burden is documented and the savings are documented. The AMA's 13 hours per physician per week and CAQH's $258 billion avoided are not in dispute. What is not yet proven for your practice is whether the headline 85% completion rate from Commure survives contact with your specific payer mix and EHR.

Our forecast (next few years, unverified): we expect the practices that win are the ones that instrument first — measuring their current authorizations, denial rates, and rework hours before automating, so they can prove the savings rather than assume them. We expect smaller practices to reach this capability through their existing workflow and RCM vendors rather than by buying an enterprise platform directly. And we expect a two-tier outcome: practices that redesign roles around exception-handling will keep their best staff and recover more denied revenue, while practices that simply bolt on a tool and change nothing will see the work reappear as a different bottleneck. The technology is real; the operational discipline is the variable.

A practical adoption path

Start by measuring. Count your weekly authorizations, your denial rate, and the hours your staff spends — those are your baseline. Then standardize the intake step so a document arrives in a consistent, machine-readable shape. Then automate the highest-volume, most-rules-driven task first (almost always prior auth), with a human reviewing the exception queue.

A realistic rollout is staged, not a flip of a switch. The phases below are an illustrative sequencing — not vendor commitments — that reflects how document-heavy automations typically land in a practice: a short instrumentation phase, a single-workflow pilot, then expansion. The point of the numbers is to set expectations so leadership does not abandon the effort in week two.

The discipline that table encodes — measure, standardize, pilot one thing, then expand — is the difference between a practice that reclaims hours and one that quietly reverts to manual work after a frustrating launch. Treat the first automated workflow as a proof, not a finish line.

This is the sequence the firms that operationalize this first follow. Teams building these steps inside US Tech Automations workflows keep the intake and routing layer stable, so that when a better engine ships, it is a swap rather than a rebuild. For the specific sub-workflows, see our guides on routing referral requests to specialists, verifying insurance eligibility before appointments, and handling authorization re-verification for home-health agencies, plus the eight steps to referral tracking between specialists.

Key Takeaways

• The task that changes most is prior authorization — the AMA puts it at 39 requests and 13 hours per physician per week.

• The savings are real at scale: per CAQH, $258 billion in admin cost was avoided in 2024.

• Commure's stated 85% no-human completion rate (funding announcement) is a benchmark to verify against your own rework count, not a guarantee.

• The hard part is staffing: move people from data entry to exception review and denial strategy, not out the door.

• Measure your baseline first, standardize intake, then automate the highest-volume task — as of June 2026 this sequencing separates real savings from relocated work.

Frequently Asked Questions

What does Commure change for a healthcare practice day-to-day?

It changes who does the high-volume paperwork. Agents handle the routine share of prior authorization, coding, and documentation, while staff move to exceptions and appeals. According to the AMA, prior auth alone consumes 13 hours per physician per week today.

How much staff time can a practice actually save?

It depends on volume and payer mix, but the math is large. Using the AMA's 13 hours per physician per week, a five-physician practice spends about 65 staff-hours weekly on prior auth before appeals — much of which is the routine, automatable share.

Will Commure or similar tools cause layoffs?

In a well-run practice, no — the profession is short-staffed and the freed hours move to higher-value work. According to the AMA, 40% of physicians already have staff working exclusively on prior auth; automation redeploys those people to exception review.

Is this technology proven or still experimental?

It is deployed at scale. According to Commure's announcement, the platform runs across 500+ organizations with agents completing 85%+ of revenue cycle work — though every practice should verify those rates against its own data.

How do small practices access this if enterprise platforms favor big buyers?

Most reach it through their existing workflow and RCM vendors. Per the CAQH Index, 25%+ of provider organizations already use AI tools, and smaller practices typically adopt the same agent capabilities through integrated platforms rather than direct enterprise contracts.

Ready to map your own workflows? See how customer-service and front-office AI agents can take the routine intake and authorization load off your staff, or explore the customer-service agent capabilities in detail.