Every hospital is fighting the same fire right now: denials, rework, coding, labor cost. Good. But there's a second fire in the building, and almost nobody is pointing a hose at it. Operational efficiency and structural revenue loss are two different problems, and you can't automate your way out of the second one.

We keep looking for someone to blame for rising healthcare costs, and we keep hoping AI will rescue us. After most of a career in the revenue cycle, I think both instincts are getting in the way of the work that actually moves the number. Here is why.

Will AI replace revenue cycle jobs; AI revenue cycle staffing 2030; RCM workforce modernization; healthcare AI layoffs revenue cycle; deskilling revenue cycle; new RCM roles AI

Automation doesn't shrink your revenue cycle team; it changes what they have to be good at. Here is why AI is creating more work, not less, and what hospital CFOs should do about it before 2030.

Three flavors of AI laziness are quietly stalling hospital revenue cycles right now: the pilot that never ends, the checkbox deployment, and the assumption that your vendor handles it. This week proved the runway is shorter than most leaders think. Here is the honest 2030 forecast and the one thing worth doing before your next leadership meeting.

Pennsylvania just sued an AI chatbot for impersonating a licensed physician. UnitedHealthcare faces a class action over an algorithm plaintiffs say has a 90% error rate and was used to override physician judgment without human review. Both cases are being treated as consumer tech and payer problems. They are not. Every legal theory being established in these lawsuits applies directly to how hospitals use AI in prior authorization, denial routing, and charity care screening right now. Here is what CFOs and RCM leaders need to do before the next lawsuit names a provider.

Waystar posted 22% revenue growth in Q1 and said out loud what most vendors only say in board decks: they are building toward automating a meaningful portion of the $100 billion in annual RCM labor pool. That is excellent marketing. It is also a market thesis about your headcount, your vendor contracts, and what the revenue cycle looks like in 2028 — and most CFOs and PE firms are not asking the right questions about what it means yet.

Rush University Medical Center is 18 months into its agentic AI journey. What they learned should be required reading for every CFO and revenue cycle director in the country. The problem with agentic AI isn't that it breaks. It's that it drifts, slowly, quietly, in directions nobody notices until the damage is already in your A/R. Here's what that means for your revenue cycle and what to do about it.

I stopped writing RCM 2030 for three weeks when the reconciliation bill passed. Not because I was stuck, but because I had to rethink what I'd written about 2027 and beyond. The Senate just passed a budget resolution with reconciliation instructions due May 15 and hundreds of billions in unspecified cuts to find. This week's news tells me the trajectory I described is exactly right. Here's what the book predicted and what's actually happening.

Hospitals are facing pressure from multiple directions at once. Medicaid funding is tightening. Amazon continues expanding its healthcare footprint. And behind the scenes, many health systems are quietly abandoning AI pilots that never delivered real results.

These forces might look unrelated, but they all converge in one place: the revenue cycle. As margins tighten and expectations rise, finance leaders are being pushed to separate real operational transformation from technology hype. The next few years will determine which organizations turn AI and automation into real financial resilience and which ones get left managing the wreckage of failed experiments.

Three health systems cut RCM and IT jobs this week. Some of those decisions will age well. Others won't. April Wilson breaks down what organizations get wrong when they outsource without keeping internal oversight — and what the ones getting it right are doing differently.

Artificial intelligence is beginning to reshape the healthcare workforce itself. From AI scribes training new physicians to shifting workforce roles and the end of healthcare’s AI experimentation phase, revenue cycle leaders should start preparing their teams for a fundamentally different operational environment.

UnitedHealth just deployed 22,000 engineers on AI. Payer recoupments are growing at twice the rate of claims. A new federal fraud enforcement division just launched. Here's what this week's news means for your revenue cycle.

Artificial intelligence is moving quickly into healthcare operations. Ambient documentation tools are listening during visits, AI systems are influencing claim workflows, and predictive models are shaping payer decisions.

Now policymakers are starting to respond.

From state legislation targeting AI-driven claim denials to policy recommendations from major EHR vendors, a new phase of healthcare AI is emerging. Governance.

For revenue cycle leaders, this is more than a regulatory debate. AI is increasingly embedded in the workflows that determine how claims are documented, coded, and reimbursed. That means policy decisions about automation could directly affect hospital margins and operational strategy.

As of March 31, 2026, payers have to show their work for the first time in history. Prior authorization denial rates, turnaround times, and appeals outcomes are now public. Revenue cycle leaders who know how to use that data have a real advantage in their next payer contract negotiation. Here is what to do with it.

Artificial intelligence in healthcare is moving beyond pilots and experiments. A new generation of systems known as agentic AI can observe workflows, make decisions, and act across operational processes.

Recent developments from AWS, CVS, Microsoft, and Optum suggest that this shift is already underway. These technologies are beginning to influence scheduling, documentation, and claims infrastructure, which means the financial life of a healthcare claim may soon be shaped by automation long before it reaches the billing office.

For revenue cycle leaders, the real strategic question is no longer whether AI will influence operations. The question is how quickly automation will move upstream and reshape the workflows that determine whether claims are paid or denied.

75% of health systems now use at least one AI solution. More than half of those that can quantify the return report 2x ROI or better. So why are so many organizations still unable to tell you what their AI is actually doing for them? The measurement gap is real — and in a margin environment this tight, it's one your revenue cycle can't afford.

Artificial intelligence is no longer a side project in healthcare. It is moving directly into the electronic health record, becoming part of the operational infrastructure hospitals rely on every day. That shift will reshape documentation, coding, clean claim rates, and denial prevention. Revenue cycle leaders who understand what is happening inside the EHR will have a strategic advantage. Those who ignore it may spend the next decade chasing problems that could have been prevented upstream.

Five separate headlines this week. One underlying problem. Payers, big tech, and the federal government are all moving on a timeline that wasn't set by waiting for providers to catch up. Here's what the BCBS coding study, Amazon's Health AI expansion, and the January 2027 prior auth deadline have in common, and what revenue cycle leaders need to do before the gap gets any wider.

A federal lawsuit against OhioHealth alleges the system blocked lower-cost health plans from expanding in its market. The case raises uncomfortable but important questions about how hospitals protect commercial reimbursement and how market dominance shapes employer plan options.

While the legal outcome remains uncertain, the broader signal is clear: provider-side market power is under scrutiny. If enforcement efforts increase, dominant regional systems may face pressure on premium commercial contracting strategies that have historically supported cross-subsidization.

In this analysis, I explore what the OhioHealth case reveals about structural margin tension, affordability, and how revenue cycle leaders should be thinking about contracting assumptions as we move toward 2030.