Beyond the AI Hype: What Healthcare Leaders Should Be Asking at HLTH 2026
Healthcare AI is entering a new phase. The question is no longer what technology can do. It is whether organizations can turn that potential into measurable operational and financial performance.
As healthcare executives prepare to gather in Las Vegas for HLTH 2026, artificial intelligence will undoubtedly dominate conversations across the conference floor. From predictive analytics and clinical decision support to administrative automation and patient engagement, the industry has no shortage of promising innovations.
But for CFOs, CIOs, revenue cycle executives, and health system leaders, the conversation needs to move beyond impressive demonstrations and ambitious promises.
Healthcare organizations are operating under persistent financial pressure, growing administrative complexity, workforce constraints, and increasingly demanding reimbursement processes. In this environment, adopting AI simply to keep pace with innovation is not a strategy. Technology investments must solve identifiable problems, integrate into existing operations, and produce outcomes that leadership can measure.
An October 2026 article published by the American College of Healthcare Executives (ACHE), For Health System Leaders, AI's Real Test Is Revenue Cycle Performance, makes a similar argument: The true value of AI emerges when it improves the decisions and workflows that influence reimbursement, operational efficiency, and the patient financial experience.
The article reflects a vendor perspective, but raises an important question for healthcare executives evaluating AI solutions: Is the technology generating more information, or is it helping the organization achieve better results?
As HLTH 2026 approaches, here are five questions every healthcare leader should be asking before making their next AI investment.
1. Does Your AI Actually Execute Workflows, or Does It Just Identify Problems?
Healthcare organizations have invested heavily in technologies that collect, organize, analyze, and display information. Dashboards can identify outstanding claims, predictive models can flag potential denials, and reporting platforms can highlight revenue cycle bottlenecks.
These capabilities provide visibility, but visibility alone does not resolve the underlying problem.
Consider a system that identifies a claim likely to be denied. The prediction may be accurate, but if someone must manually investigate the issue, locate missing documentation, contact the payer, and correct the claim, the organization has improved its awareness without necessarily reducing the workload.
This distinction is becoming increasingly important as healthcare organizations evaluate the difference between AI-powered insights and AI-driven execution.
Effective revenue cycle automation should help move work forward. Depending on the workflow, that could mean validating insurance eligibility, identifying missing information, supporting authorization processes, reconciling payments, or routing an exception to the appropriate employee with the necessary context.
The objective is not to eliminate every human interaction. It is to reduce unnecessary manual steps while allowing employees to focus on decisions that genuinely require their expertise.
When evaluating an AI solution, executives should ask vendors to demonstrate what happens after the technology identifies a problem. Does it initiate an appropriate next step? Can it validate the outcome? Does it provide visibility into completed actions?
The most valuable AI does more than tell an organization where work is getting stuck. It helps move that work toward completion.
2. Can It Work With Existing Technology Without a Major System Overhaul?
One of the most significant challenges in healthcare technology adoption is the complexity of existing infrastructure.
Health systems often rely on multiple electronic health records, practice management systems, payer portals, clearinghouses, document management tools, and financial platforms. Even when individual systems function effectively, information may not move seamlessly between them.
Introducing another disconnected application can create additional work rather than eliminate it.
The October 2026 ACHE article emphasizes that AI capabilities should extend the electronic health record rather than operate around it. The underlying principle is that intelligence should support existing workflows, preserve the system of record, and deliver actionable information where employees already work.
For healthcare executives, this shifts the evaluation beyond a simple question of technical compatibility.
A vendor may demonstrate that its technology connects to an EHR, but connectivity does not automatically translate into operational integration. Leaders also need to understand how information is exchanged, where actions are recorded, and whether employees must navigate additional platforms to complete their responsibilities.
A more meaningful evaluation considers the entire workflow. How does information enter the AI solution? What happens after an action is completed? How are updates reflected in existing systems? What new responsibilities, if any, does implementation create for internal teams?
At Jorie AI, our approach centers on a system-agnostic orchestration layer designed to operate across existing healthcare technologies, including EMRs, payer portals, APIs, documents, and operational platforms.
Rather than requiring organizations to replace their core infrastructure, Jorie AI's virtual AI employees are designed to coordinate and execute revenue cycle workflows within the environments organizations already use.
The broader lesson is straightforward: Successful AI implementation should simplify an organization's technology environment, not add another layer of fragmentation.
3. How Does It Handle Exceptions, Validation, and Human Oversight?
Healthcare revenue cycle operations rarely follow a perfectly predictable path.
Insurance information may be incomplete. Payer responses may conflict with previous records. Authorization requirements can change. Claims may contain unusual circumstances that require interpretation rather than a standardized response.
These exceptions are precisely where the limitations of simplistic automation become apparent.
In an August 2026 article updated in September, the Healthcare Financial Management Association (HFMA) explored this challenge in Integrating Human-Enabled AI Emerges as Key Consideration for Revenue Cycle.
The roundtable featured perspectives from healthcare organizations including Yale New Haven Health, Hackensack Meridian Health, Geisinger, and LifeBridge Health. Participants discussed the importance of combining automation with domain expertise, governance, quality assurance, and clearly defined responsibilities.
One example highlighted a particularly important distinction: An eligibility technology could confirm that a patient had insurance coverage while failing to surface other circumstances that might still result in a denial.
In other words, a task can be technically completed without the underlying operational risk being resolved.
For healthcare leaders, this raises questions about how AI systems determine whether a workflow is truly complete.
What happens when required information is missing? How does the system respond when payer information is inconsistent? When does an exception require human review, and what supporting information is provided to the employee responsible for resolving it?
Reliable automation requires more than speed. It requires validation, transparency, appropriate escalation, and a clear understanding of where human expertise remains essential.
At Jorie AI, we view automation, validation, visibility, and continuous optimization as connected components of an effective revenue cycle strategy.
The goal is not automation without oversight. It is to create a more dependable operating model in which routine work progresses efficiently and complex exceptions receive the attention they deserve.
4. What Measurable Financial and Operational Results Can We Expect?
Healthcare executives are increasingly expected to demonstrate the business value of technology investments.
For revenue cycle management, that means looking beyond the number of tasks automated or the volume of information processed.
A solution may complete thousands of transactions, but the more important question is whether those activities translate into stronger organizational performance.
Relevant measures may include denial rates, days in accounts receivable, net collections, payment accuracy, cost to collect, staff productivity, and revenue captured per patient encounter.
These metrics help executives connect technology performance to broader financial objectives.
For example, Jorie AI's work with an orthopedic practice demonstrates how revenue cycle automation can contribute to measurable improvement over time. Across a three-year engagement, the practice achieved more than $7.2 million in combined revenue realization and cost-to-collect savings, including approximately $5.97 million in revenue realization and $1.23 million in savings.
During the engagement, the practice's cancellation rate decreased from 2.33% to 0.66%, while days in accounts receivable declined from approximately 42 to 34–35 days.
These results illustrate the importance of evaluating multiple operational and financial indicators together. A successful revenue cycle strategy is not simply about processing claims faster. It is about reducing preventable revenue loss, improving workflow reliability, and strengthening financial performance.
Of course, results vary based on organizational circumstances, baseline performance, implementation scope, and operational conditions.
That is why executives should ask AI vendors to explain not only their reported outcomes but also how those outcomes were measured, over what period, and under what conditions.
The strongest business case for healthcare AI is not a list of capabilities. It is a measurable connection between technology execution and organizational results.
5. Can the Solution Scale Beyond a Pilot Into Everyday Operations?
A successful AI pilot is an encouraging starting point, but it is not proof that the technology can support an entire healthcare organization.
Pilots often operate within narrowly defined environments, with limited workflows, carefully selected data, and additional implementation attention. Scaling introduces new challenges involving workflow variation, departmental coordination, payer complexity, exception management, governance, and change management.
For a health system, the question is not simply whether AI can automate one repetitive task. It is whether the organization can extend automation across interconnected processes without creating new operational bottlenecks.
Consider how patient access, eligibility verification, prior authorization, coding, claims submission, denial management, and payment reconciliation influence one another. An error or delay in one stage can create downstream work across multiple departments.
Automating these activities independently may generate local efficiencies while leaving the broader process fragmented.
An orchestration-based approach considers how work moves between systems, employees, and departments. It establishes a framework for coordinating activities, validating outcomes, routing exceptions, and improving performance as operational needs evolve.
This is also where workforce strategy becomes important.
AI should not be viewed solely as a replacement for manual activity. When implemented thoughtfully, it can function as a workforce multiplier, allowing experienced revenue cycle professionals to devote more attention to complex cases, process improvement, payer relationships, and other high-value responsibilities.
Healthcare leaders evaluating scalability should ask how a vendor supports implementation, monitors performance, manages exceptions, and adapts workflows over time.
A pilot demonstrates possibility. Sustainable enterprise adoption requires operational discipline.

Moving Beyond the AI Conversation at HLTH 2026
HLTH 2026 will bring together healthcare leaders, technology innovators, and industry experts to explore what comes next for healthcare.
The opportunity is significant, but so is the responsibility to distinguish meaningful innovation from technology that simply adds complexity.
For organizations considering AI investments, the most productive conversations will not necessarily be about the most advanced model or the most impressive demonstration.
They will be about practical execution.
Can the technology operate within existing systems? Can it handle real-world exceptions? Can it support employees rather than overwhelm them? Can it deliver measurable financial improvement? And can those results be sustained as the organization grows?
These are the questions that will help determine which AI investments create lasting value.
At Jorie AI, we believe the future of revenue cycle management depends on connecting automation with validation, visibility, and continuous optimization. Our virtual AI employees are designed to help healthcare organizations move beyond isolated tasks toward coordinated, end-to-end revenue cycle execution.
Because the real promise of healthcare AI is not simply doing more with technology. It is building healthcare operations that work better.
Heading to HLTH 2026? Let's Talk About AI That Delivers.
The future of healthcare AI is about execution, not just innovation.
Join Jorie AI at Booth #2813 in Las Vegas, November 16–18, to discover how virtual AI employees can help your organization automate revenue cycle workflows, reduce administrative burdens, and improve financial performance.
Our executive team will be available for personalized conversations about your organization's revenue cycle challenges, automation opportunities, and goals for 2027.
Meeting times are filling up. Reserve your one-on-one conversation with Jorie AI today.
Keep reading
Explore more insights from our team
Stay ahead
Receive the latest thinking on healthcare revenue cycle management delivered to your inbox


.png)
.png)
.png)

.png)
.png)
.png)
.png)


.png)
.png)



























.png)








.jpeg)
.png)
.png)
.png)
.png)
%2520(10).png)
%2520(14).png)
.png)

.png)
.png)

.png)
.jpeg)

.jpeg)
.png)
.png)
.png)
.png)



.png)
.jpeg)



.png)


.png)



.png)

.png)
.png)






%201.webp)


