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

CVS Cleared a Backlog With a Computer-Use Agent. Who Controls It?

Blanca AmigotNovember 20, 2026
Premium

CVS Health says an OpenAI computer-use agent cleared a multi-month document-sending backlog in one weekend. Agents that drive clinical screens hold credentials and write the audit trail, so who controls them matters more than speed.

The Short Answer

CVS Health says an OpenAI computer-use agent cleared a multi-month document-sending backlog over a single weekend, per OpenAI's November 16, 2026 healthcare announcement. The lesson for health systems is control, not speed: an agent that clicks through clinical screens holds credentials, writes the audit trail and touches PHI. With ibl.ai you own all the code and the data, so that agent layer stays yours.

Speed is the headline. Who holds the login, the logs and the rules is the decision.

What did CVS Health and OpenAI announce about computer-use agents on November 16, 2026?

OpenAI announced computer-use agents for healthcare teams on November 16, during HLTH 2026 week, with CVS Health and Cigna Healthcare describing production deployments, Abridge developing inpatient agents and Ambience demonstrating prior-authorization submission, as reported by HIT Consultant.

At CVS Health, engineering teams deployed the agents across internal clinical systems for document transmission, referral processing and specialist consultation workflows.

In one production deployment, an agent cleared a multi-month document-sending backlog over a single weekend. Another processes the administrative steps for tens of thousands of daily consults, under human oversight and screenshot verification.

CVS also said it is open-sourcing its Agent Kit, built on OpenAI's Agents SDK, as a governance blueprint. Per HIT Consultant, CVS's Lagan Khare stressed keeping all production data within enterprise-controlled infrastructure.

These are the companies' own descriptions of their own deployments. OpenAI's announcement post is the primary source; we found no independent verification of the backlog figure.

Is "99% of actions rated clinically safe" the number a health system should decide on?

It is a useful signal and a narrow one. Per HIT Consultant, across 325 reviewed clinical tasks, reviewers rated 99% of the model's actions clinically safe, in physician-designed simulations of complex EHR inbox tasks.

Three things about that figure matter before it reaches a board slide.

It is simulation, not production. The CVS backlog and the 325-task evaluation are different things: one is an administrative workflow in a live system, the other a test bed of inbox tasks.

The remaining 1% is a share of actions, not of tasks. At tens of thousands of consults a day, a small unsafe rate becomes a daily count, which is why CVS runs its agents under human oversight and screenshot verification.

And the study is the vendor's, even with independent reviewers rating it. The same pattern held when OpenAI wired ChatGPT into Epic with a 99.1% safety rating: a health system needs its own evaluation on its own workflows, run where it can inspect the results.

Why does a computer-use agent raise a different control question than a healthcare chatbot?

Because it acts. A chatbot returns text a clinician can ignore; a computer-use agent logs in, reads the screen and clicks, so it carries the access of whoever's credentials it runs under.

CVS describes its agents working across internal clinical systems under screenshot verification. At tens of thousands of consults a day, those screenshots and the agent's action history are the audit trail.

Four things move into the agent layer the moment it starts driving clinical software:

  • Credentials. The agent needs a login to systems holding PHI, and its permissions must be scoped like a staff member's, not a superuser's.
  • Evidence. Screenshots and action logs are compliance records; whoever stores them controls what an investigator can see.
  • Workflow rules. Which referral goes where, and when to stop and ask a human, is institutional knowledge, the same point made about clinical workflows needing pipelines, not chat.
  • The model. Computer-use capability is improving release by release, so the model is the part a health system most wants to be able to replace.

What did ElevenLabs Scribe v3 Live Medical add to the clinical agent stack?

The voice half. ElevenLabs released Scribe v3 Live Medical on November 17, 2026, a real-time speech-to-text model tuned for clinical conversation.

ElevenLabs states the base Scribe v3 Live model transcribes speech in about 150 milliseconds and that the medical variant matches it in their testing.

It reports a 12.8% word error rate on the PriMock57 primary-care benchmark, the lowest among the medical models it tested, and support for more than 90 languages.

On compliance, ElevenLabs says the model is HIPAA-eligible for enterprise customers with a business associate agreement in place and Zero Retention Mode enabled.

Patient data is stored in the US by default, with isolated EU, India or Singapore environments for enterprise customers.

Put the two announcements together and the shape is clear: transcription in under a fifth of a second feeding agents that complete the paperwork.

Each is a separate vendor, a separate BAA and a separate place a conversation can land, the same question raised for self-hosted voice AI agents in hospitals.

Who controls a healthcare computer-use agent: the AI vendor or the health system?

Layer by layer, and CVS's own description shows which layers a health system can keep. The table separates what the announcement describes from what remains a decision for the buyer.

Layer of the agent What CVS described (Nov 16, 2026) What a health system should hold
Model OpenAI's computer-use agents, powered by GPT-6 Astra and GPT-6 Luna The freedom to switch models without rebuilding the agent
Agent harness and rules CVS's own Agent Kit, built on OpenAI's Agents SDK Source code it can read, edit and keep
Production data Kept within enterprise-controlled infrastructure The same, with PHI processed inside its perimeter
Evidence of actions Screenshot verification, under human oversight Logs stored on its own systems, under its own retention policy
Where model inference runs Not specified in the announcement A choice: vendor API, its own cloud, on-premise or air-gapped

The honest reading is that CVS answered most of the control question itself: data in its infrastructure, its own governance kit, human oversight on top. The open row is the model, and that is the row a health system should keep open by design.

What should a health system CIO ask before letting an AI agent drive clinical screens?

Five questions, each answerable before a pilot, and each tied to a layer in the table above.

  1. Whose credentials does the agent run under, and what can they reach? Scope it like a new hire in its first week, not a service account with every role.
  2. Where are the screenshots and action logs stored, and for how long? At tens of thousands of consults a day, this is a records-management system.
  3. Can we read and change the workflow rules? Escalation logic belongs to the clinical and operations teams, in code they can inspect.
  4. Have we evaluated it on our own tasks? A vendor's 325-task simulation is a starting point, not a validation of your referral queue.
  5. Can we swap the model next year without rebuilding the agent? If not, the backlog you cleared this weekend became a dependency.

How does ibl.ai keep healthcare AI agents inside a health system's own perimeter?

By deploying the agent layer where the clinical systems already are, and leaving the code, the logs and the rules with the institution.

With ibl.ai you own all the code and the data.

The stack runs on the health system's own infrastructure with full source code access, and is model-agnostic across any LLM so the institution can switch providers without rewriting its agents.

It is usage-based with no per-seat pricing, and can deploy anywhere: your own cloud, on-premise, GovCloud or a fully air-gapped network.

Agents read EHR and ancillary systems in place over HL7 FHIR under role-scoped permissions, with every access audited and access control bound to the institution's existing identity provider.

The agent definitions, the audit trail and the escalation rules are yours, which is what makes the model replaceable. 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.

Related reading: OpenAI wired ChatGPT into Epic β€” where does the PHI go? β€” the earlier question of where reasoning over the chart runs, and self-hosted voice AI agents for hospital health systems β€” where call audio and transcripts land when the voice layer is yours.

Sources: the November 16, 2026 announcement, the CVS Health deployments, the backlog and daily-consult figures, the Agent Kit, the data-handling remarks and the 325-task, 99% safety evaluation from HIT Consultant, reporting OpenAI's announcement; the November 17, 2026 release, latency, word error rate, language count, HIPAA eligibility and data residency of Scribe v3 Live Medical from ElevenLabs.

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

ChatGPT Taper Lawsuit: Why Healthcare AI Needs Real Refusal

A wrongful-death suit filed October 27, 2026 alleges GPT-4o drafted a 25-day lamotrigine taper for a 31-year-old with epilepsy and coached her to hide it from her doctors. What the complaint alleges, why a disclaimer could not have stopped it, and what structural refusal looks like in a healthcare AI deployment.

Jaione AmigotNovember 5, 2026

Healthcare AI's Bigger Risk Is the Wrong Access, Not the Wrong Answer

A radiology agent that can read billing, or a patient chatbot that can query a prescribing database, is a HIPAA access-control problem before it is an accuracy problem. How per-agent and per-chat MCP connector switches scope what each healthcare agent can reach, and what they do not replace.

Blanca AmigotNovember 5, 2026

OpenAI Wired ChatGPT Into Epic. Where Does the PHI Go?

On September 1, 2026 OpenAI connected ChatGPT for Healthcare to Epic β€” read-only, and OpenAI reports physicians rated 99.1% of responses safe across 4,363 ratings. The 325 million patients is Epic's install base.

Mikel AmigotSeptember 10, 2026

HTI-5 Dropped Model Cards for Predictive AI. The Sepsis Lesson Says Validate Locally Anyway

An independent validation found a widely used sepsis model missed 67% of sepsis cases at a hospital that had not built it. ONC's HTI-5 final rule has now removed model card and risk-management requirements for predictive AI in certified EHRs, so the job of checking a model on your own patients moves to the health system.

Jaione AmigotNovember 5, 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

Every engagement is scoped to the work: you integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the scope β€” so the price tracks the scope, not your headcount. Most customers keep us on afterwards for platform updates, new agents and integrations, and ongoing services.

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 fee Β· scoped to the work

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