> ## Content Index
> Fetch the complete content index at: https://www.healthdatacon.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Epic plans incoming and outgoing AI-agent connections for 2027
- URL: https://www.healthdatacon.io/articles/epic-incoming-outgoing-mcp-agents-2027-hlth/
- Published: 2026-11-18T18:40:00.000Z
- Updated: 2026-11-18T19:28:49.000Z
- Description: An exchange with developers and policy veterans put the focus on which tasks outside software will be able to perform, who controls access and who pays as traffic rises.
- Author: HDM Staff
- Tags: Interoperability, Americas, HLTH

Epic plans to let outside AI agents connect into its software on the same timetable as agents built in Epic reaching out to other applications, a company executive said Wednesday. The planned two-way support for Model Context Protocol, or MCP, would give developers another route to build tools that work with the electronic health record.

Antonia Papajani, Epic’s third-party relations lead, said the company had already outlined outgoing MCP connections for next year. In a live discussion of EHR access, she added that “we’re also going to build incoming MCP at the same time.” She did not give a release month for incoming connections or specify which clinical and administrative functions they would expose.

The comments came during [Examining EHRs](https://hlth.com/events/usa/agenda/2026/stat-at-hlth-examining-ehrs?ref=healthdatacon.io), a STAT-hosted session at HLTH USA 2026 in Las Vegas. STAT reporter Brittany Trang moderated the discussion with Papajani, Epic executive vice president of research and development Seth Howard, HTD Health interoperability practice lead Brendan Keeler and former U.S. chief technology officer Aneesh Chopra, a strategic advisor to Andor Health. Matthew Herper, STAT’s editorial director of events, introduced the program and later joined the questioning.

## A new connection still needs useful functions behind it

Epic’s [developer conference recap](https://www.oec.epic.com/?ref=healthdatacon.io) already describes tools coming in 2027 that will let customer-built agents connect to external products and content through standards such as MCP servers. It also describes a way for developers to distribute preconfigured connectors through Epic Showroom starting in March 2027\. Papajani’s comments Wednesday added the company’s intention to support traffic in the other direction on the same timeline.

The [protocol’s documentation](https://modelcontextprotocol.io/docs/getting-started/intro?ref=healthdatacon.io) describes MCP as a standard for connecting AI applications to external data sources and tools. In a health system, the practical value depends on the information and actions the connected system makes available. A common way to send a request can help developers reuse work across applications, while the available functions determine whether an agent can finish the job.

Keeler pressed that distinction during the discussion. “MCP is just an API,” he said, arguing that it would inherit limits in the capabilities an EHR makes accessible. He said software operating a user interface can sometimes reach more of a workflow than an application programming interface, giving developers a reason to use that approach when a needed function is missing.

Howard said direct connections can make the work faster and less expensive to run than software navigating screens on a virtual machine. He described robotic process automation as useful in some circumstances and argued that a more direct route between systems is generally preferable when one exists. For buyers, that leaves a concrete question about any proposed integration, including whether it can carry out the required task through supported interfaces.

## Who gets to choose the application?

Trang asked Epic’s executives to respond to complaints in STAT’s reporting that outside developers and hospital customers had struggled to get the access or assistance they needed. Howard said Epic supplies the technology while patients and health systems decide which applications connect to their information. “We can’t be the gatekeepers of every application,” he said.

Papajani described [open.epic](https://open.epic.com/?ref=healthdatacon.io) as available without company approval and said its Connection Hub directory is optional for developers with a live connection. She said Epic wants to support both health systems and outside developers as they build connections, and said it is difficult to address anonymous complaints without details. Her answer returned to “who gets to decide what is best,” which she said should be the patient or health system.

Keeler acknowledged changes Epic had made to its developer support program, while saying some developers remain concerned about intellectual property language in the agreement. Howard responded that the company’s goal is to provide support without obtaining a developer’s intellectual property, while preserving Epic’s ability to build competing products. The exchange identified a business issue that a new technical protocol alone would leave for the parties to resolve.

Keeler said “competition is the name of the game,” including for Epic and other certified EHR vendors. He argued for technical parity between a vendor’s own modules and outside products, allowing health systems to choose among them. Howard said Epic measures success by whether its customers can serve patients and operate more efficiently, with interoperability part of that work.

## Growing use brings an infrastructure bill

Chopra described complaints he had received from health system chief information officers about sharp growth in requests from patient-facing applications. He said one application had repeatedly requested the same broad set of patient data, creating much more traffic than an approach based on notifications could have required. He did not name the health system or offer an independently audited cost comparison.

Howard agreed that increased use creates real infrastructure costs and said Epic had announced changes intended to help manage them, including FHIR notifications. “It’s something we have to solve together,” he said. Epic’s developer recap also describes bulk data processing on reporting servers starting with its November 2026 release, intended to reduce competition with operational work.

For a hospital, a connection that is free to an app developer can still consume computing resources and staff time. More frequent queries, larger exports and agents carrying out multiple steps can change that workload. Chopra’s argument was to settle shared approaches to this growth early, including “getting ahead of it on standards,” before new connections become another source of disputes between developers and health systems.

## Availability and adoption can diverge

The discussion repeatedly returned to the distance between publishing an interface and using it in day-to-day operations. Chopra said standards can exist before a health system has the staff, demand or operational plan to adopt them. He described an attempted payer-provider data exchange that stalled because the health system’s technology leadership did not know how to operate the available tools.

“Regulation doesn’t necessarily mean it’s embraced or adopted or used,” Chopra said. He disclosed his advisory relationship with Andor Health and described its relationship with Epic as supportive. He also argued that hospitals, developers and policymakers need to accelerate standards for work such as scheduling, where participants disagreed over the extent of consensus and the role of proprietary specifications.

The federal [information-blocking framework](https://healthit.gov/information-blocking/?ref=healthdatacon.io) applies to practices likely to interfere with access, exchange or use of electronic health information, subject to the law and its exceptions. The panel’s disagreement about particular integrations offered no regulatory ruling on a specific case. It showed how questions about technical access, support contracts and operational capacity can become intertwined.

Epic’s incoming MCP plan gives developers another forthcoming capability to evaluate. The test will be in the functions it exposes, the conditions under which outside products can use them and the work needed to operate those connections across hospitals. Those details will determine how much of the agent-driven workflow a health system can actually put into service.