Epic Agent Factory Explained [What It Changes for Health Systems]

Epic Agent Factory is a no-code visual builder embedded directly inside the Epic EHR that lets health systems create, configure, and deploy custom AI agents for clinical, operational, and patient-facing workflows — without writing code or leaving the system their clinical staff already uses.

TL;DR

• Epic unveiled Agent Factory at HIMSS 2026 (March 2026), expanding its AI roadmap beyond the existing three named agents into user-configurable territory.

• The builder is embedded inside Epic — health systems do not need a separate platform or IT project to start building agents.

• According to Fierce Healthcare, 85% of Epic customers already actively use Epic AI as of the HIMSS 2026 announcement.

• Early real-world results: a 42% reduction in prior authorization submission time at Summit Health and a 69% early lung-cancer detection rate at The Christ Hospital, per HIT Consultant.

• Honest limits: Agent Factory is only available to Epic customers; non-Epic EHR users have no access to this tooling.

• As of June 2026, Agent Factory was announced as a preview capability at HIMSS 2026 — health systems should confirm GA availability and BAA coverage with their Epic account team.

What Happened and Why Now

Epic has operated three named AI agents for the past several years: Art for clinical decision support, Penny for revenue cycle automation, and Emmie for patient-facing interactions. These agents are effective but fixed — a health system can configure them but cannot build a new agent for a workflow that Epic's product team has not yet addressed.

The constraint that broke was the agent-building bottleneck. Health system IT departments receive hundreds of workflow automation requests annually and have capacity to address a small fraction. Epic Agent Factory moves agent creation from the IT project queue to the department level — a clinical informatics team or revenue cycle director can build an agent for their specific workflow without waiting for a developer.

According to Fierce Healthcare's HIMSS 2026 coverage, Epic expanded its AI roadmap at HIMSS 2026 specifically to include the Agent Factory capability, positioning it as the infrastructure for health systems to build and orchestrate agents across workflows that Epic's standard agent library does not cover.

According to Healthcare IT News, Epic highlighted Agent Factory as one of the headline AI advances at HIMSS 2026, describing the capability as enabling autonomous reasoning and action across clinical, operational, and patient-facing workflows from a single visual interface inside the EHR.

85% of Epic customers actively use Epic AI, according to Fierce Healthcare, meaning the installed base for Agent Factory adoption is already primed.

The Mechanism: How Agent Factory Works Inside Epic

The Agent Factory interface is embedded in Epic's standard administrative tooling — the same environment where Epic analysts configure workflows, build SmartForms, and manage decision support rules. The no-code visual builder uses a drag-and-drop interface to connect triggers (a specific order type, a patient event, a revenue cycle status change) to actions (a notification, a task creation, a documentation pull, an external API call) with configurable conditional logic.

The key architectural difference from external agent platforms: Agent Factory agents have native, credentialed access to the full Epic data model from the moment they are created. An external agent platform requires an integration team to build and maintain a FHIR or HL7 connector to get data in and out of Epic. An Agent Factory agent already has that access — the authentication, the data model mapping, and the compliance scope are inherited from Epic's existing HIPAA infrastructure.

According to Healthcare IT News, the prebuilt agent library gives health systems a starting point for common workflows, while the local policy and knowledge-base configuration layer allows customization for health-system-specific protocols and payer rules.

The three existing named agents — Art, Penny, and Emmie — continue to operate as before. Agent Factory is additive: it fills the workflow gaps that the named agents do not cover, using the same underlying AI infrastructure but exposing the configuration surface to health system administrators rather than only Epic's product team.

Real-World Performance: What Early Results Show

The HIMSS 2026 announcement came with two sets of production results from live Epic AI deployments:

Summit Health — Prior Authorization: According to Fierce Healthcare, Summit Health achieved a 42% reduction in prior authorization submission time using Epic AI capabilities. Prior authorization is the highest-administrative-burden workflow in most outpatient and specialty practices — a 42% time reduction at a large health system represents substantial recovered staff capacity.

The Christ Hospital — Early Lung Cancer Detection: According to Fierce Healthcare, The Christ Hospital achieved a 69% early lung-cancer detection rate using Epic AI. This is a clinical outcome metric, not an administrative efficiency metric — it demonstrates that Epic's AI infrastructure is operating at the clinical decision support layer with measurable patient outcome impact.

According to HIT Consultant, a 42% cut in prior auth submission time at Summit Health — with 92% of AI-generated responses accepted without human edits — represents the administrative efficiency floor that Agent Factory aims to extend to custom workflows. A 69% early lung-cancer detection rate at The Christ Hospital (versus a 46% national average) demonstrates that Epic AI operates at the clinical outcome layer, not just administrative efficiency.

Documented Performance: Epic AI Results Across Health Systems

The following table compiles real-world results from the HIMSS 2026 announcement and related coverage. All figures are sourced from published reports.

Sources: HIT Consultant; Fierce Healthcare.

The Three-Agent Framework and Agent Factory's Role

Sources: HIT Consultant; Healthcare IT News.

The expansion from three fixed agents to an open factory model is a structural shift in how health systems can use Epic AI. The named agents cover the highest-volume universal workflows. Agent Factory covers everything else — the department-specific, payer-specific, and protocol-specific workflows that vary by health system.

What Agent Factory Enables: Use Cases by Domain

Clinical Operations

An inpatient charge nurse can build an agent that monitors bed.status changes, triggers a housekeeping notification on discharge, and updates the bed management board — without an IT ticket. A pharmacy informatics team can build an agent that flags high-risk medication combinations for a specific patient population based on locally configured criteria.

Revenue Cycle

A revenue cycle director can build an agent that monitors the denial rate for a specific payer and procedure code, triggers a documentation audit workflow when denials exceed a threshold, and sends a weekly report to the revenue integrity team. This is the Anomaly Detection use case applied to revenue cycle — catching systematic billing problems at the department level rather than in the quarterly report.

Patient-Facing Workflows

An outreach team can build an agent that identifies patients who are overdue for a preventive screening, sends a templated outreach message through the patient portal, and flags non-responders for a phone-based follow-up task — using Epic's patient communication infrastructure natively, without a third-party campaign tool.

Timeline: Epic AI Roadmap Milestones

Sources: Fierce Healthcare; Healthcare IT News.

What This Changes for Smaller Health Systems and Independent Practices

The HIMSS 2026 announcement focused on large health system implementations (Summit Health and The Christ Hospital are large regional systems). The more consequential long-term implication may be for smaller Epic customers — independent multispecialty groups, community hospitals, and regional health systems — that cannot staff a dedicated AI team to build custom workflow tooling.

Agent Factory shifts the required skill from AI developer to workflow analyst. A clinical informatics analyst who knows Epic's data model and understands the clinical workflow can build a functioning agent. That skill set exists at virtually every Epic-using health system, regardless of size.

For practices with existing automation workflows outside of Epic — teams already routing scheduling and billing tasks through US Tech Automations — Agent Factory creates a bridge. Workflows that need to read or write EHR data can now have an Epic-native agent handle the EHR side, while external orchestration handles the downstream steps. That division of labor means less data moves outside the EHR, reducing HIPAA surface area.

For broader implications on how these capabilities affect daily practice operations, see the spoke article What Epic Agent Factory Means for Healthcare Practices.

Honest Limits

Epic-only: Agent Factory is an embedded Epic capability. Health systems on Cerner, Athena, eClinicalWorks, or MEDITECH have no access to this tooling. The benefits are real but limited to the Epic-installed base.

Preview status as of HIMSS 2026: The announcement at HIMSS 2026 described Agent Factory as a capability Epic was previewing and expanding. Health systems should confirm current GA availability and pricing with their Epic account team rather than assuming immediate deployment availability.

No-code has limits: Complex multi-step agents involving custom ML models, external API calls to systems outside Epic's connector library, or intricate conditional logic will require Epic analyst or developer involvement beyond what the visual builder handles.

BAA scope: Epic's infrastructure is HIPAA-compliant and covered entities using Epic have an existing BAA with Epic. Whether specific Agent Factory deployments — particularly those involving external API calls to third-party systems — require additional BAA review depends on the data flows in the specific agent. Confirm with your compliance team before routing PHI to external endpoints through an Agent Factory agent.

Signal vs Speculation

Demonstrated facts (sourced):

• Epic unveiled Agent Factory at HIMSS 2026 (March 2026) as a no-code visual builder inside Epic for custom AI agent creation. Source: Fierce Healthcare; Healthcare IT News.

• 85% of Epic customers actively use Epic AI. Source: Fierce Healthcare.

• Summit Health achieved a 42% reduction in prior authorization submission time using Epic AI. Source: Fierce Healthcare.

• The Christ Hospital achieved a 69% early lung-cancer detection rate using Epic AI. Source: Fierce Healthcare.

• Agent Factory supports a prebuilt agent library and local policy and knowledge-base configuration. Source: Healthcare IT News.

Our read (analyst forecast, 12–36 months): With 85% of Epic customers already using Epic AI, Agent Factory has an unusually large ready-to-adopt installed base.
The most significant implication of Agent Factory is not that large health systems will build more agents — they already have teams doing that. The implication is that mid-size and smaller Epic customers will for the first time be able to build custom workflow agents without a dedicated AI engineering team. Our read: health systems that deploy Agent Factory for revenue cycle use cases (prior auth, denial management, coding audit) will see the fastest measurable ROI because those workflows have direct financial impact. Clinical workflow agents — medication safety checks, care gap identification — carry higher complexity and regulatory scrutiny and will take longer to reach production.

The 36-month speculation: if Epic extends Agent Factory to support external model access (similar to how Google's Gemini Enterprise Agent Platform supports 200+ models), the capability gap between Epic-native AI and standalone agent platforms will narrow significantly. That would position Epic-using health systems with Agent Factory access as the default winner in the healthcare AI deployment race — not because their model is better, but because the compliance and EHR-integration infrastructure is already in place. That is a plausible but not certain direction based on the HIMSS 2026 roadmap signals.

Key Takeaways

• Epic Agent Factory, unveiled at HIMSS 2026 (March 2026), is a no-code visual builder inside Epic for creating custom AI agents without code or external platforms.

• The capability is additive to the existing Art/Penny/Emmie agent framework — filling the workflow gaps that named agents do not cover.

• 85% of Epic customers already use Epic AI, giving Agent Factory a large ready-to-adopt installed base.

• Early production results: 42% prior auth time reduction at Summit Health, 69% early lung-cancer detection at The Christ Hospital.

• The shift from IT-built to analyst-built agents is the structural change that matters most for mid-size health systems.

• Honest limits: Epic-only, preview status at HIMSS 2026, complex agents need developer support, external API calls require BAA review.

• Health systems with external automation workflows can use Agent Factory for the EHR-side steps and existing orchestration for downstream actions.

Frequently Asked Questions

What is Epic Agent Factory?

Epic Agent Factory is a no-code visual builder embedded inside the Epic EHR that allows health systems to create, configure, and deploy custom AI agents for clinical, operational, and patient-facing workflows — without writing code or leaving Epic's administrative environment.

How does Agent Factory differ from Epic's existing AI agents (Art, Penny, Emmie)?

Art, Penny, and Emmie are Epic-configured agents covering specific defined domains. Agent Factory is health-system-configured — it gives Epic administrators and clinical informatics teams the tooling to build agents for workflows that the named agents do not cover. The two capabilities complement each other rather than replacing one another.

Do you need to be an Epic customer to use Agent Factory?

Yes. Agent Factory is embedded inside the Epic EHR and is only available to organizations running Epic. Health systems on Cerner, Athena, eClinicalWorks, MEDITECH, or other EHR platforms do not have access to Agent Factory.

What were the real-world results cited at HIMSS 2026?

According to Fierce Healthcare, Summit Health achieved a 42% reduction in prior authorization submission time, and The Christ Hospital achieved a 69% early lung-cancer detection rate using Epic AI capabilities.

Is Agent Factory HIPAA-compliant?

Epic's infrastructure is HIPAA-compliant and covered entities have an existing BAA with Epic. Specific Agent Factory deployments that make external API calls or process data outside Epic's managed environment may require additional BAA review. Confirm with your compliance team and Epic account manager before routing PHI to external systems through an Agent Factory agent.

What does "no-code" mean in practice for Agent Factory?

The Agent Factory visual builder uses a drag-and-drop interface to connect Epic triggers to actions. A clinical informatics analyst with Epic configuration experience and an understanding of the workflow logic can build a functional agent. Agents requiring custom ML models, complex external integrations, or logic outside the visual builder's capabilities will require Epic analyst or developer support.

Can Agent Factory agents call external APIs (e.g., payer portals)?

According to Healthcare IT News, Agent Factory supports custom agents with configurable knowledge-base and policy settings. External API connectivity depends on Epic's current connector library and the specific agent's deployment configuration. Confirm external API capability with your Epic account team.

Next Step

Health systems and practices that want to map Epic Agent Factory's capabilities against their current administrative and clinical workflow automation should start with a workflow audit — identifying the highest-volume manual steps that fall outside the Art/Penny/Emmie coverage. US Tech Automations teams already orchestrating scheduling and billing workflows at healthcare organizations can integrate with Epic-native agents at the data handoff layer, keeping PHI inside Epic while extending automation downstream. For the practice-level operational playbook — prior auth, billing, and patient outreach — see What Epic Agent Factory Means for Healthcare Practices. For the workflow detail on connecting EHR agent events to downstream billing and scheduling actions, the home health authorization re-verification guide walks through the integration pattern step by step. See the agentic workflow orchestration layer for how the broader integration works in practice.