Epic's seven bets beyond the EHR, sorted by when hospitals can actually use them
Epic is expanding past its EHR into ERP, IT staffing, AI, drug pricing and payer technology. Delivery runs from tools live today to a full EpicOps rollout that may not arrive until 2029. The payer platform has the clearest proof point: St. Luke's and UnitedHealthcare automated status updates on 88% of the claims they exchanged.
This story was produced through MarketScale. See how Healthcare teams put it to work with Executive Thought Leadership.
Key takeaways
Epic's payer platform is the expansion bet with a measured result: 88% of claim status updates automated between St. Luke's and UnitedHealthcare, plus a 25% drop in status calls.
EpicOps, Epic's ERP suite, may not be fully available until 2029, so a health system whose ERP commitments end sooner can test individual modules alongside its current system without a full switch.
Before buying any third-party app that has to work inside Epic, ask the vendor to demonstrate the exact write operation it needs in your own environment, because FHIR support alone does not guarantee write access.
Free workspace
Turn your Healthcare expertise into content.
Record interviews, organize footage, and write with AI on a free trial of the MarketScale platform for qualifying companies. No demo required, no credit card.
An ERP suite. A long-term IT staffing service. A drug-price comparison tool. A platform for doing business with insurers. Epic built its company selling health systems one product, and its 2026 announcements now reach into markets where it's the newcomer, according to a Nov. 10 tally by Becker's Hospital Review reporter Giles Bruce, who counted seven ambitions beyond the EHR.
The seven don't arrive together. Some are running in hospitals today. Others carry 2027 dates. The largest, the EpicOps ERP suite, may not be fully available until 2029. Most CIOs Becker's interviewed said they were withholding judgment on the expansion. That makes sense when the products ship years apart. For a CIO or revenue cycle leader deciding what to pilot, renew or wait on, the useful way to read Epic's list is by delivery date.
The EHR base behind the new bets
The EHR is still the foundation, and KLAS Research figures cited by Becker's show how wide it is.
Epic's U.S. acute care footprint, per KLAS
KLAS Research, via Becker's Hospital Review
In 2025 Epic added fewer than half as many hospitals as it did in 2024, and its share of beds runs well ahead of its share of hospitals. Together those figures suggest Epic's biggest growth opportunity is now inside systems that already run it: selling them ERP, staffing and payer connectivity alongside the chart. That reading is ours, and it fits the shape of the list. Almost every new product works best for an organization that already has an Epic chart in place.
For a health system already on Epic, expect these products to come up in conversations with the vendor that used to be about clinical modules. The real question for a buyer is which of these products exist in a form it can test before the next budget cycle closes.
Pieces hospitals can test this year
Clinical AI is the most mature. Epic launched AI Charting in February 2026. It drafts notes from patient encounters and suggests orders, which a physician then reviews. Agents that help with clinical protocols are in development, with no release date announced.
On the IT side, Epic introduced Analyst Build Assistant at its August conference to help hospital analysts finish selected configuration tasks faster. It's also exploring agents that would make routine system changes and troubleshoot problems, though those remain developmental. Then there's Rangers, a service that places Epic-hired and Epic-trained professionals inside hospital IT departments for long engagements. That's a different model from Epic's existing Boost program, which covers temporary assignments, and it puts Epic in competition with established healthcare IT consulting firms.
Those two products together raise a workforce question that hospital IT leaders, as Becker's reporting notes, are already asking. If junior analysts lean on automated configuration and senior capacity can be rented from the vendor, how does a hospital grow its own experienced Epic builders? For IT departments that depend on promoting analysts from within, it's worth answering before signing up for either.
Of the seven bets, the payer platform is the one with a measured result attached: St. Luke's and UnitedHealthcare automated status updates on 88% of the claims they exchanged. The platform handles coverage discovery, prior authorization, claim status checks and documentation exchange between providers and insurers. UnitedHealthcare also reported a 25% drop in claim status phone calls from St. Luke's University Health Network after go-live.
Those are company-reported figures from one provider-payer pair, so other systems may not see the same results. A different payer mix or a less standardized claims workflow could produce smaller gains. Still, an automation rate and a drop in call volume are the two numbers a revenue cycle director can check against their own baseline. That makes this the easiest of the seven to put in a business case.
The 2027 to 2029 queue
The rest of the list runs on announced or estimated dates:
- Connectors: developer-built Connectors expected in Epic Showroom starting March 2027.
- Prescription Marketplace: expected summer 2027, built with Amazon Pharmacy, Mark Cuban Cost Plus Drugs and other pharmacy companies, showing cash prices next to insurance-based costs before a prescription is sent.
- EpicOps: full rollout may not be available until 2029, according to Henry Ford Health executives.
- Clinical protocol agents: in development, no release timeline announced.
EpicOps is the one that matters most to operations and supply chain leaders. Epic detailed the suite at its Aug. 17-20 Users Group Meeting. It's an ERP built for healthcare that ties workforce scheduling, supply chain, credentialing and finance to clinical data. The pitch is that resource decisions follow patient care: flagging a supply substitution before a procedure starts, or matching staffing to clinical demand. General-purpose ERP systems weren't designed to see the procedure schedule. Epic is betting that integration is worth a migration.
Health systems are already taking different routes. Becker's reported that Henry Ford Health wants to adopt EpicOps eventually. Ohio State University Wexner Medical Center is testing selected modules without replacing its existing ERP. For a system whose current ERP commitments run out before EpicOps is complete, the Wexner approach shows a middle path: test the clinically connected modules now and decide on the core financials once the full suite exists.
The strongest case for going all in is simplicity. Some leaders argue that fewer platforms mean fewer interfaces, less duplicate administration and fewer vendors to manage. The case against is concentration, since putting more services under one supplier can limit contracting flexibility and access to competing tools. Research from Epic's own installed base adds a twist. A 2022 study in Computer Supported Cooperative Work, which followed preparations for Epic in Central Norway, found that configuring a large generic system tended to become standardization, favoring regional goals over local needs. That study covered a public health system preparing for an EHR, not an ERP, but the lesson carries over: the broader the platform, the earlier local workflow requirements need to be written into the configuration plan.
Connectors and the write-back question
Connectors is the least flashy item on the list and possibly the most important for integration teams. In its Oct. 21 announcement, Epic described a framework that lets its applications pull information from external software and complete selected tasks inside it. The framework is meant to support Epic's AI assistants: Emmie for patients, Art for clinicians and Penny for operational work. Epic's examples include retrieving ambulance arrival information or letting a patient's assistant submit a meal request through a hospital's dietary app.
That's a write problem as much as a read problem. ISHIR project manager Abdul Rasul, writing in a technical guide on ambient AI integration, points out that FHIR support does not automatically mean full read-and-write access. Epic's public specifications include FHIR R4 operations to create, read and search clinical documents. Even so, a given customer's environment may not expose the same functions or permissions. Connectors run in the opposite direction, with Epic's assistants acting in other systems, but the same rule holds: having an interface listed doesn't guarantee a hospital can use it.
Before relying on a Connector or a FHIR integration, ask for a live test of the exact operation the workflow needs, whether that's read, create or update, in your own Epic environment. A demo in someone else's build doesn't settle it.
The next signal comes in March 2027, when developer-built Connectors are due in Epic Showroom. How many third-party vendors publish them, and which actions those Connectors can actually complete, will show how open Epic's growing platform is in practice.
Sources
Your experts belong here
Every story in MarketScale Healthcare starts with a company putting its clinicians, service-line leaders, and field engineers on the record. Buyers are already reading this topic. The only question is whose experts they find.
Service-line buyers vet vendors quietly, and your clinicians become the proof they find while doing it.
About the author
The MarketScale Newsroom reports on the companies, technologies, and trends shaping 16 B2B industries. It turns primary sources and expert commentary into clear, useful coverage for the people doing the work.