Source: Epic's Connectors announcement, October 21, 2026 · Epic Penny for revenue cycle and operations
The revenue cycle is full of software that knows something important but cannot easily finish the job. An eligibility platform knows the coverage; a payer portal knows the authorization status; a billing system knows the account; a denial platform knows the missing evidence. Revenue cycle staff spend hours moving between them. Epic's new Connectors initiative could change the architecture of that work: instead of asking operators to visit every application, let Epic's AI retrieve information and act in those applications from one workflow.
On October 21, 2026, Epic announced Connectors, a new way for app developers to link their software to Epic. Connectors are designed to do two things: bring data from external applications into Epic, and enable Epic to complete tasks inside those applications. The distinction matters. This is not just another inbound data feed or reporting integration. The strategic possibility is cross-application execution by an AI assistant.
Connectors will be compatible with Emmie, Epic's AI for patients; Art, its AI for clinicians; Penny, its AI for revenue cycle and operational teams; and custom AI agents built by health systems through Agent Factory. Developer-created Connectors are expected to become discoverable in Epic Showroom beginning March 2027. Epic says organizations will be able to inspect what a Connector can do, read, and change before enabling it.
That is the announced direction, not proof that every Epic customer can deploy every Connector today. Epic has introduced the capability for developers; the first public discovery milestone is still ahead, and the announcement does not specify general availability dates for individual partner integrations, pricing or implementation requirements.
Epic's stated starting point for health systems to find developer-created Connectors in Epic Showroom. The strategic shift begins with developer access now, but customer-facing availability and adoption will depend on which Connectors are built, approved and enabled.
Epic illustrates the concept with practical examples: an AI could fetch ambulance arrival information to help an emergency department prepare, or Emmie could request a meal from a hospital dietary application. Those examples explain the mechanics, but the financial implications become more substantial when the same capability is applied to Penny.
Penny already supports RCM and operational tasks such as drafting denial appeal letters, summarizing information for prior authorization and medical-necessity reviews, preparing coding suggestions and turning plain-language requests into reporting queries. Much of that work traditionally happens in or around Epic's own record and work queues.
Now consider the next step: if a Connector makes a third-party payer, RCM or patient access system available as an authorized tool, Penny could theoretically bridge the gap between analyzing a problem in Epic and taking the next permitted step outside Epic. Epic's October 21 announcement does not claim all of these workflows are live, but it establishes a technical and commercial direction that RCM leaders should pay attention to.
Several application developers appear in Epic's announcement, including Gozio Health for wayfinding and VPL for pharmacy logistics. For RCM, the standout is Availity, whose CEO, Russ Thomas, identifies coverage, prior authorization and claims management as potential areas of value in its collaboration with Epic.
Availity matters because it is already a major access point into payer workflows. Bringing parts of that network into Epic's AI experience could reduce the back-and-forth that makes payer interactions labor-intensive. An RCM analyst might ask Penny for the status of a pending authorization or for information needed to resolve a claim, instead of opening another portal and re-entering identifiers.
But the announcement describes a prospective collaboration and its potential. It does not publish a list of production-ready Availity Connector actions, participating payers, claim transaction types, response latency, denial categories or customer performance outcomes. Even where a partner provides access, workflow authorization and payer-specific restrictions will determine what a system can actually execute.
The EHR is moving from a system of record toward a system that can orchestrate work across other systems. For RCM, the most valuable capability may be closing the loop between the insight that a claim needs attention and the authorized action required to move it toward payment.
The scenarios below are illustrative opportunities, not a list of Connectors Epic says are available today. Each depends on the functionality, permissions and payer coverage developers ultimately deliver.
| RCM workflow | Potential Connector-enabled task | What remains to prove |
|---|---|---|
| Eligibility and insurance discovery | Retrieve coverage findings from an external service and populate a staff-facing work queue | Match accuracy, effective-date validation, write-back controls |
| Prior authorization | Check status, retrieve missing requirements, draft next steps and submit an approved update | Payer support, submission rights, clinical attestation boundaries |
| Denial appeals | Combine chart evidence with external denial data and route a prepared appeal through a permitted service | Medical necessity evidence, human approval, response confirmation |
| AR follow-up | Request claim status and document the verified payer response without switching systems | Status reliability, downstream task completion, duplicate follow-up prevention |
| Patient financial clearance | Retrieve payment, coverage or assistance details from a specialized partner at the point of need | Coverage accuracy, financial authorization, patient communication safeguards |
The value is not simply fewer browser tabs. The opportunity is to eliminate the handoff between recognizing an account problem and initiating its resolution. For example, an AI can already summarize a denied claim. The harder task is determining the relevant payer rule, securing the appropriate evidence, obtaining human approval where required, submitting to the correct destination and tracking the outcome back to cash.
The commercial implications cut both ways. For specialized RCM vendors, a Connector could be a useful distribution mechanism: an eligibility, prior authorization or claims platform may deliver its differentiated capability inside the workflow where a hospital operator already spends the day. Its customers may no longer need a separate interface for routine interactions.
That is an opportunity for vendors whose advantage is unique payer connectivity, validated policy intelligence, reliable automation or measurable financial outcomes. Connecting their service to Penny could make that intellectual property easier to use and increase the frequency with which it is called.
But it also creates exposure for vendors whose differentiator is primarily the screen through which staff operate. If Epic provides the front-end AI assistant, and a Connector exposes a vendor's functions as callable services, the value of another dashboard may decline. Vendors will have to defend themselves through superior data, coverage breadth, performance, reliability, contracting or specialized human expertise—not by owning every click.
For larger health systems, vendor selection may increasingly turn on whether a product can participate in a governed workflow as well as whether its standalone interface looks useful. The question becomes: Can the vendor provide an auditable, permissioned action with a clear outcome?
Epic says healthcare organizations can review the information a Connector reads and what it can change before enabling it. That is a particularly consequential distinction in revenue cycle management. Reading claim status is different from modifying insurance, submitting an appeal, issuing a patient refund or posting an adjustment.
A safe rollout should separate at least three levels of activity: read-only retrieval, draft or proposed actions, and authorized changes to systems of record. High-risk financial actions should have appropriate policy validation and human approval paths. Hospitals need to know whether actions can be reversed, which identities are recorded, how errors are reconciled and how third-party access is revoked.
The announcement does not provide complete specifications for Connector identity, audit formats, network standards, error handling or downstream permissions. It also does not establish whether Connectors use a particular protocol such as MCP; RCM buyers should not assume technical equivalence with every other agent-integration product until Epic releases implementation details.
The new announcement follows another meaningful infrastructure development: Rhapsody's Guardian is being positioned around authenticating agents, governing API access, setting restrictions and retaining an audit trail. Epic's Connectors announcement is centered instead on exposing outside applications to Epic AI and allowing actions in those systems, with healthcare organizations reviewing the access before enabling a Connector.
These are not necessarily direct substitutes. A Connector is a path for an Epic agent to use an outside capability. An enterprise security or API governance layer can potentially supervise access across many systems and AI vendors. The practical boundaries, overlaps and whether the systems can be used together will require vendor-specific validation.
What they signal together is significant: as hospitals move beyond AI copilots into agents that perform work, integration and authorization become central design decisions—not afterthoughts.
Connectors are not limited to Epic's three named assistants. Epic explicitly includes custom agents built in Agent Factory, its environment for health systems to create AI workflows. That gives hospitals a potential way to combine local process knowledge, Epic context and specialized external services rather than waiting for a standard Penny feature to cover every scenario.
Epic has previously described health-system teams building agents for operational needs inside Agent Factory. Extending this approach to Connectors may lower the technical cost of certain cross-application projects. But making a Connector available is not the same as validating an agent's clinical, compliance or financial safety. Each organization still needs clear ownership, quality testing, exception handling and ongoing performance monitoring.
Epic's stated March 2027 Showroom milestone is close enough that RCM leaders should start asking vendors about readiness, but far enough away that large deployment assumptions would be premature. An organization considering a new RCM application today should ask whether the vendor plans to build a Connector, what business actions it intends to expose and what dependencies or additional charges may apply.
That discussion should be grounded in observable scope. A claimed partnership is not a working Connector. A read-only status lookup is not a fully automated claim-resolution workflow. An AI-generated response is not proof of a successful payer transaction.
Epic Connectors may be one of the more strategically important healthcare AI announcements of the year, precisely because Epic is not introducing another isolated AI feature. It is opening a path for its existing AI assistants and customer-built agents to do work across software boundaries.
For revenue cycle teams, Penny is the central character. If developers expose meaningful payer and RCM actions—and if hospitals can govern them safely—the operator's workflow could shift from navigating a collection of portals to supervising a smaller set of agents that retrieve information and complete approved actions.
For vendors, this creates an opportunity to become a preferred capability inside Epic's ecosystem while raising a harder question about who owns the workflow, the customer relationship and the economics of automation. For hospitals, the unresolved questions are connector availability, rights, auditability and demonstrated return. Epic has announced the direction; March 2027 will be an important step in judging execution.
The next RCM platform battle may not be about who owns the best dashboard. It may be about who owns the workflow—and which underlying services the AI is trusted to call.
Independent analysis of healthcare AI, revenue cycle technology, payer operations and the companies reshaping how providers get paid.
Sources: Epic, “Introducing Connectors: A New Way for Apps to Communicate With Epic,” October 21, 2026; Epic Penny for Revenue Cycle and Operations; Epic Agent Factory Build-a-Thon, September 2026; Epic AI product overview. Announced availability, named partners and product capabilities are attributed to Epic. Illustrative RCM applications, buying criteria and competitive implications are RevCycleAI editorial analysis, not claims of live customer deployment.