ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog
Healthcare AI Pays Off in Admin, and Payers Know It Too

Healthcare AI Pays Off in Admin, and Payers Know It Too

Jaione AmigotNovember 9, 2026
Premium

Healthcare AI's countable return is administrative: prior authorization, claims, coding and scheduling. Payers automate the same work from the other side of the claim, so the provider with the best evidence trail wins, and that trail belongs inside the hospital's own perimeter.

The Short Answer

Healthcare AI's most measurable return sits in administrative work, meaning prior authorization, claims, coding and scheduling, and payers are automating the same work from the other side of the claim. ibl.ai is the agentic AI platform where you own all the code and the data, so a health system runs its revenue-cycle agents inside its own perimeter, on any model, with every action logged for the appeal.

The argument is not that diagnostic AI fails. It is that administrative outcomes are countable within a quarter (hours spent, denials written off, appeals won), and that the counterparty already runs software against them.

Where does healthcare AI show its most measurable return?

Healthcare AI shows its most measurable return in administrative and documentation work, because those outcomes are counted in hours and dollars rather than in multi-year clinical endpoints.

The burden is large and well measured. The AMA's 2025 prior authorization physician survey puts prior authorization at 13 hours of physician and staff time a week, and 94% of physicians say it contributes to burnout.

The evidence that AI reduces that burden is real but young. A December 2025 systematic review and meta-analysis in BMC Medical Informatics and Decision Making pooled 23 studies of AI documentation tools.

It found a moderate reduction in clinician workload and burnout (standardized mean difference βˆ’0.71) and in documentation time (βˆ’0.72).

The authors also rate the studies' methodological quality as generally low, with no randomized controlled trials. That caveat belongs in every budget memo.

How much of US healthcare spending is administrative?

Administrative work accounts for roughly a quarter of US healthcare spending on the most-cited estimate, which is why automating it on either side of a claim moves real money.

Sahni, Carrus and Cutler, writing in JAMA in 2021, estimated administrative spending at about $950 billion in 2019, against national health spending of about $3.8 trillion: close to 25%.

The same authors estimated that about $265 billion a year could be saved through administrative simplification.

A Health Affairs policy brief puts the published range at 15–30%, depending on what counts as administrative, so the 25–30% figure that circulates on social media sits at its high end.

Are health insurers using AI and algorithms to deny claims?

Health insurers use algorithms and predictive models in claims and prior-authorization review, and the public record documents bulk, fast denials, though in every documented case a human clinician still signs the denial or the insurer says one does.

Cigna. In 2023 ProPublica reported that Cigna doctors denied over 300,000 payment requests in two months using its PxDx review system, spending an average of 1.2 seconds on each case. Cigna disputes the characterization.

UnitedHealthcare. The October 2024 Senate Permanent Subcommittee on Investigations report found UnitedHealthcare's post-acute denial rate rose from 8.7% in 2019 to 22.7% in 2022, while its overall rate barely moved, from 7.3% to 7.6%.

The subcommittee tied that rise to the period when the company was launching initiatives to automate prior authorization. UnitedHealthcare said the report mischaracterizes its clinical practices.

The nH Predict lawsuit. In February 2025 a federal court in Minnesota let the breach-of-contract claims proceed in Estate of Lokken v. UnitedHealth Group, which alleges the insurer used the nH Predict model in place of physicians.

Plaintiffs allege that over 90% of those denials are reversed on appeal. Those are allegations, not findings, and UnitedHealthcare says nH Predict is not used to make coverage determinations.

So "AI denial engines auto-reject claims" overstates the documented record. What is documented is narrower and still serious: software that sorts and flags at a speed no human appeal process matches.

What does Medicare Advantage denial data say about appealing?

Medicare Advantage denial data says appeals usually win but are rarely filed, which is the asymmetry an administrative AI agent on the provider side exists to close.

KFF's analysis of 2024 Medicare Advantage data, published January 2026, counts the funnel:

Medicare Advantage prior authorization, 2024 Figure
Determinations made 52.8 million
Denied in full or in part 4.1 million (7.7%)
Share of denials appealed 11.5%
Appeals partially or fully overturned 80.7%

Read the last two rows together. Roughly nine in ten denials go unchallenged, and four in five of the challenged ones are reversed. The gap is not clinical merit; it is the cost of assembling the evidence by hand.

That is the provider-side opportunity our earlier post on why healthcare AI should start in the billing office sized across all payers, where roughly 65% of denied claims are never appealed.

What are regulators doing about AI in prior authorization?

Regulators are setting rules of engagement for AI in prior authorization rather than banning it: faster deadlines, stated denial reasons, and a licensed clinician on every medical-necessity call.

CMS-0057-F. The CMS Interoperability and Prior Authorization final rule requires impacted payers to decide within 72 hours for expedited and seven calendar days for standard requests, and to give a specific reason for each denial, from 1 January 2026.

Payers had to post their first prior authorization metrics by 31 March 2026, and must run a Prior Authorization API from 1 January 2027.

California SB 1120. The Physicians Make Decisions Act, effective 1 January 2025, requires a licensed physician or qualified health care professional to make medical-necessity determinations; an AI tool may not supplant that decision.

CMS WISeR. Medicare itself now runs AI on prior authorization. The WISeR model uses AI and machine learning to review selected services in traditional Medicare across six states from 2026 to 2031, and CMS states that "all recommendations for non-payment are determined by appropriately licensed clinicians."

Who wins when providers and payers both run AI on a claim?

When providers and payers both run AI on a claim, the side with the better evidence trail wins, because every contested denial ends as a document someone has to read.

Illustration of a provider-side billing robot holding medical bills facing a payer-side robot holding Denied and Rejected stamps, titled The Code War: AI vs AI in Healthcare

Step in the claim Payer side (documented) Provider side (what an agent does)
Review speed 1.2 seconds per denied case (Cigna, per ProPublica) Pre-submission check of codes and documentation against the payer's criteria
Deadline 72 hours expedited, 7 days standard (CMS-0057-F) Status monitoring and follow-up against those clocks
Denial A specific reason, required from 2026 The reason parsed and matched to evidence in the chart
Appeal Only 11.5% of MA denials appealed (KFF, 2024) A drafted appeal with assembled evidence, reviewed by staff, filed in hours

The specific-reason requirement matters most. A stated denial reason is a structured input, and an agent that reads it, pulls the matching notes and drafts the response turns an appeal from a staffing decision into a routine one.

The patient appears in neither side's objective function unless someone puts them there. The measure worth adding is time to care, which our post on prior-auth automation optimizing a queue, not the patient works through across 13 weekly hours of burden.

What should a health system's administrative AI look like?

A health system's administrative AI should run where the chart already lives, log every action it takes, and cost in proportion to claim volume rather than headcount.

Inside the perimeter. Appeals need protected health information. An agent that ships the chart to a vendor API starts a business associate review that can outlast the pilot; one that runs in the hospital's data center or VPC does not.

An audit trail per action. CMS-0057-F and SB 1120 both turn on who decided what and why. Every document retrieved and every letter drafted should be attributable, reviewable and exportable.

Model choice. Coding, letter drafting and document classification suit different models, and the best model in 2026 will not be the best in 2028. Lock-in to one vendor's model is a cost the revenue cycle pays later.

A cost shape that tracks claims. Per-seat pricing at $30–60 per user per month bills every coder and biller whether or not an agent worked that day. The per-letter token math for prior authorization shows the usage-based alternative at three scales.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing β€” so you can deploy anywhere, from your own cloud to a fully air-gapped network. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY β€” a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on. Our AI transformation team builds the first revenue-cycle agents alongside your staff on Agentic OS.

Related: Healthcare AI Should Start in the Billing Office, Not the Exam Room β€” the all-payer denial and appeal economics; Duplex Voice Agents Reach the Payer Phone Call β€” what voice agents change about the phone leg of prior authorization.

Sources: administrative spending from Sahni, Carrus and Cutler, JAMA 2021; documentation evidence from Zhao et al., BMC Medical Informatics and Decision Making, December 2025; burden figures from the 2025 AMA Prior Authorization Physician Survey; denial funnel from KFF, January 2026; payer practices from ProPublica, the Senate PSI report and the Lokken order; rules from CMS-0057-F, SB 1120 and WISeR.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing β€” so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform β€” the stack itself is yours.

  • Model-agnostic

    Run any LLM β€” Claude, GPT, Gemini, Llama, Command, or your own fine-tune β€” and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY β€” a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

Related Articles

Healthcare AI Should Start in the Billing Office, Not the Exam Room

Roughly 65% of denied healthcare claims are never appealed, while 54% of the ones that are get overturned. That gap is the highest-ROI AI deployment in healthcare, and it sits in the revenue cycle rather than at the point of care β€” but only if the PHI architecture survives a security review.

ibl.aiAugust 27, 2026

Prior Auth Is Not a Question. Why Clinical AI Needs Pipelines.

Prior authorization, medical coding, and care coordination are multi-step processes with approval gates and failure branches β€” not single questions. Chat cannot express them, which is why hospital AI pilots that demo well stall at production, and why the unit of deployment has to be a governed pipeline.

ibl.aiAugust 28, 2026

PE Firms Put AI Agents in Healthcare. The Data Comes First

Private equity sponsors are putting AI agents into healthcare revenue cycle companies, from R1 under TowerBrook and CD&R to New Mountain's Smarter Technologies. The most specific sponsor-published result we found, Partners Group's 120 bps margin uplift at an insurance brokerage, was built on a clean proprietary dataset, and KPMG lists fragmented, unstructured data among the main bottlenecks. The data is the prerequisite, and who owns it decides what is left at exit.

ibl.ai EngineeringOctober 9, 2026

Duplex Voice Agents Reach the Payer Phone Call. The $31 Billion Figure Is From 2009.

Decagon launched Voice 3 and its Chord speech model on 1 October 2026, bringing duplex voice agents that talk while they work. AI voice agents have called payers since 2019, so the news is the removal of hold time, not the arrival of the capability. Meanwhile the $31 billion prior authorization figure everyone quotes is a 2009 estimate covering every physician-plan interaction. The deployment question is control and evidence, not feasibility.

ibl.ai EngineeringOctober 3, 2026

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work β€” so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope Β· fixed timeline

A time-boxed proof of value on your real data β€” not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time Β· not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data Β· run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Custom quote

perpetual license Β· you own the stack

We transfer the full source code. You own and self-host the entire platform β€” outright.

Best for: Organizations and enterprises that benefit from perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable Β· zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM β€” Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY