AI only works if it changes the work
AI has become central to any RCM conversation because revenue cycle work is data-intensive, pattern-driven, and exception-heavy. The use cases are real. So are the implementation challenges and execution risk.
McKinsey found that AI and advanced technologies are moving up the priority list, with 51% of leaders citing them as focus areas in 2025, up from 33% in 2024. Everest Group found similar momentum, with 85% of surveyed senior healthcare executives and RCM leaders expecting AI, gen AI, or agentic AI to improve RCM efficiency, and 51% actively testing or considering RCM use cases.7
According to Adonis’ 2026 RCM research, the strongest interest is concentrated in the functions with the clearest financial pressure: 66% of respondents identified automated denial follow-up and resolution as a “very important” AI capability for their 2026 RCM strategy.5
These findings do not support an AI-first strategy. They support a performance-first strategy in which AI improves the timing, precision, and consistency of revenue cycle action.
The most valuable use cases are practical: detecting payer patterns, flagging documentation risk, prioritizing high-value work, identifying likely denial causes, accelerating appeal development, supporting coding accuracy, and reducing avoidable manual touches.
In a mature operating model, AI does not sit outside the workflow as a separate analytics layer. It informs the next action inside the work itself.
It’s an essential distinction. Many provider organizations have existing dashboards, reports, queues, and analytics tools. The gap is operational translation — the distance between insight and execution. A model that produces insight without changing action will not materially improve cash, yield, or cost to collect. An intelligence-led RCM model moves teams from knowing a problem exists to acting on it quickly, consistently, and with appropriate governance.
AI also needs clear operational boundaries. Revenue cycle leaders should understand where automation can make reliable decisions, where it should recommend action, and where human review is required. Clinical, coding, regulatory, payer, and patient-facing workflows carry different levels of risk. Governance should be specific enough to define escalation rules, audit requirements, quality controls, performance measures, and ownership.
The most credible AI strategies will be tied to near-term operating value, focusing on specific challenges within broader RCM processes, using ROI benchmarks, and demonstrating credible nine- to 12-month impact to sustain internal support.1
The case for modular, integrated adoption
Most health systems can’t rebuild their RCM infrastructure in one motion. They operate within existing EHR environments, payer processes, staffing models, vendor relationships, budget constraints, and competing priorities. The practical path is to start where financial pressure is most material while building toward a more connected operating model.
This is the case for modular, integrated adoption. Organizations may begin with a specific control point: access and authorization, documentation and coding, denial prevention, underpayment management, A/R recovery, or patient financial engagement. The value depends on whether each improvement strengthens the broader system.
Without integration, modular adoption can become another source of fragmentation. A new tool, workflow, or vendor may solve a local problem while making enterprise performance harder to govern.
McKinsey’s research supports this direction. Its analysis notes that market dynamics favor scaled platforms that integrate services and automation, and that organizations are prioritizing the same functions where revenue pressure is most acute: denials, A/R follow-up, coding, and eligibility and authorization. McKinsey also notes that half of surveyed leaders plan to pursue modular, integrated solutions that can be adopted over time and connected into a unified system.1
The starting point should reflect the organization’s revenue risk profile and operating capacity, but each step should contribute to a more connected performance model. One health system may begin with denials and underpayments, where the cash impact is visible. Another may focus on documentation and coding integrity to strengthen claim readiness before billing.
The principle is connection. Denial prevention should inform access, documentation, and coding workflows. A/R recovery should expose root causes that can be addressed upstream. Each capability should improve the next decision, the next workflow, and the next financial result.