Your Chief AI Officer · Friday, November 20, 2026 · Act today
Epic plans to let authorized outside AI agents pull EHR data
Announced2 sourcesFor patients and employees
Epic plans to allow authorized AI agents in third-party applications to retrieve data from its EHR by the first quarter of 2027, using Model Context Protocol (MCP), according to Becker's Hospital Review. STAT reported that Epic defended its competitive practices and promised AI access to records.
Epic plans to let authorized AI agents running in third-party applications retrieve data from its EHR by the first quarter of 2027, according to Becker's Hospital Review. The connections will use Model Context Protocol, or MCP, a standard designed to connect AI applications with external data sources and tools, and Epic said they will be built specifically for AI. Derek De Young, who leads Epic's Agent Factory development, announced the plans at HLTH, per a Nov. 18 company release. The same day, STAT reported that Epic defended its competitive practices while promising AI access to records.
The move extends a two-way design. In October Epic introduced Connectors, which let its own AI assistants retrieve information and perform tasks in outside applications, and organizations will be able to find developer-built Connectors in Epic Showroom starting in March 2027, Becker's reported. Epic said more than 3,700 applications already connect to its software, and executive vice president Seth Howard said developers can use more than 1,000 free technologies through Open.Epic, about one-third of them required by regulation. Third-party relations lead Antonia Papajani called MCP "a great example of a standard that's changing rapidly."
For health systems, this shifts the question from whether outside AI tools can reach the record to which ones should. That decision touches several desks at once. The Chief AI Officer and CIO own the roster of tools that will ask for access. The CISO owns the new pathway itself, since an agent pulling records is a new kind of requester to authenticate, scope and monitor. Compliance and privacy own the rules for what data leaves the EHR and why.
The evidence is thin by design. This is a plan, not a shipped product, and no independent evaluation exists. Epic has not named which third-party AI applications will use the MCP connections or which categories of EHR data authorized agents can reach, Becker's noted. The standard is also still moving, by Epic's own description.
The move: inventory the third-party AI tools in use or under contract that would request Epic data through MCP, and draft the authorization policy now that decides which agents get access, to what, and under whose sign-off. Having that policy ready before the 2027 window lets teams adopt useful tools faster, with the access controls patients and staff should expect already in place.
Do this week. Inventory the third-party AI tools that would request Epic data through MCP and draft the authorization policy that decides which agents get access.
Run this
The prompt to act on this item, for your own model.
Paste it into Claude, ChatGPT or Copilot and fill the bracketed slots with your own numbers. The output is a draft for your team to check, built only from the sources on this page. Never paste patient data. How these prompts are written.
You are an advisor to the Chief AI Officer and executive team of [your organization], a health system that runs Epic. Context: Becker's Hospital Review reports that Epic plans to let authorized AI agents in third-party applications retrieve data from its EHR by the first quarter of 2027, using Model Context Protocol (MCP), a standard for connecting AI applications to external data sources and tools. STAT Health Tech reported that Epic defended its competitive practices while promising AI access to records. Epic says more than 3,700 applications already connect to its software. Becker's noted that Epic has not named which third-party AI applications will use the MCP connections or which categories of EHR data authorized agents can reach. An Epic leader called MCP "a great example of a standard that's changing rapidly." No independent evaluation exists; this is a plan, not a shipped product. Task: Prepare us before the first quarter of 2027. First, build an inventory of the third-party AI tools in use or under contract that could request Epic data through MCP. Second, draft an authorization policy that decides which agents get access, to what data, and under whose sign-off. Output: A draft workflow with owners and checks, in three parts: (1) the tool inventory as a table with tool, vendor, purpose, data likely requested, and business owner; (2) the authorization steps, each with an owner (Chief AI Officer, CIO, CISO, Compliance and privacy) and a check before approval; (3) open questions for Epic and each vendor. Use these inputs: [the AI tools in use or under contract], [your current integration review process], [the name or role of the final access approver], [your data access tiers or categories]. Guardrails: Use only the facts above and the slots I fill. Cite Becker's Hospital Review and STAT Health Tech by name. Flag anything uncertain or that must be verified with Epic. Include no patient data. Mark this as a draft for the team to check. Nothing here is medical advice.
- The claim.
- Epic says the capability will connect authorized AI agents in third-party applications to its EHR data through MCP.
- The evidence.
- No independent evidence exists yet; the capability is planned for the first quarter of 2027.
By seat
For the Chief AI Officer. Decide which vendors in the AI portfolio should be first in line for MCP access and what governance review each must pass.
For the CIO and CTO. Ask Epic for the MCP authorization model and logging details so integration plans for 2027 can start now.
For the CISO and security. Define identity, scoping and audit requirements for any AI agent that retrieves EHR data before the first request arrives.
For the Compliance, privacy and legal. Map agent data access to existing business associate agreements and minimum necessary policies.
Disclosure at publication: Involves Epic, a platform Ecofy tracks by name.
Checked before publishing. 3 independent outlets. Also reported by Healthcare IT Today.
Sources
- Becker's Hospital Review, Epic to let outside AI agents pull EHR data
- STAT Health Tech, STAT+: Epic defends competitive practices; promises AI access to records
Drafted by Lumen from the sources above, scored by a second pass on six criteria, then checked by rule against those sources (every figure, two independent outlets or a primary source) and published only when it passes. A person can pull any item, and corrections are published here. Apolitical, always. Nothing here is medical advice. How Your Chief AI Officer is made.