For some health systems, moving to Epic is becoming as much an application-consolidation project as an EHR project.
Recent Becker’s reporting shows health systems using Epic implementations and optimization efforts to retire dozens or even hundreds of legacy and third-party applications, with some tying the reductions to millions of dollars in expected savings.
The trend was underscored by Valhalla, N.Y.-based Westchester Medical Center Health Network, where an Epic implementation is expected to eliminate 88 separate software applications.
Here are six health systems where Epic is playing a broader role in shrinking the technology stack:
1. Westchester Medical Center Health Network (Valhalla, N.Y.)
WMCHealth expects its ongoing Epic implementation to displace 88 applications accumulated across the health system over years of growth.
The health system currently operates multiple EHR platforms across its facilities. CIO Leo Bodden told Becker’s that once the Epic implementation is complete and the applications are retired, the health system expects its Epic costs to be significantly lower than its current technology costs.
WMCHealth is scheduled to go live with Epic Dec. 4, 2027.
2. Inspira Health (Mullica Hill, N.J.)
Inspira Health launched Epic across all of its facilities July 27, deploying more than 50 digital tools from Epic’s AI suite and cognitive computing models on the first day.
The health system’s Epic investment is also expected to significantly reduce its reliance on third-party applications.
Warren E. Moore, president and COO of Inspira Health, told Becker’s last year that the health system’s $120 million investment in Epic over 10 years would allow it to turn off about 100 third-party applications and lower annual technology costs.
Inspira has also said the Epic implementation could save tens of thousands of staff hours annually. The system is using Epic tools for documentation, translation, predictive analytics and other clinical workflows.
3. Trinity Health (Minot, N.D.)
Minot, N.D.-based Trinity Health expects application consolidation to account for a significant portion of the financial return from its Epic implementation.
The health system plans to reduce its portfolio from more than 400 applications to fewer than 200. CIO John McDaniel told Becker’s the consolidation alone is expected to generate $5 million to $6 million in annual savings.
Trinity projects nearly $1 billion in savings, revenue recovery or revenue generation over 10 years from processes affected by the Epic implementation.
4. UPMC (Pittsburgh)
UPMC’s transition to a single Epic platform extends beyond the nine EHRs the health system has accumulated through years of mergers and acquisitions.
As of a February 2026 update, about 40% of the organization had transitioned to the unified platform. The rollout also included more than 15 specialty systems and roughly 200 additional applications that were still being replaced.
UPMC has described the project as a systemwide clinical and operational transformation rather than simply an EHR replacement.
5. Cone Health (Greensboro, N.C.)
Cone Health is taking a similar approach without replacing Epic itself.
The health system is investing at least $40 million to rebuild its existing Epic environment after years of customization and reliance on third-party applications. Chief Medical Information Officer Mike Kramer, MD, told Becker’s that several bolt-on applications are no longer necessary because Epic now provides the same capabilities.
Cone Health estimates a $5 million to $10 million opportunity from replacing third-party applications with Epic modules.
The health system is pairing that effort with broader application rationalization and process optimization.
6. Providence (Renton, Wash.)
Providence is also looking to Epic as a way to reduce reliance on standalone technology.
The health system has been expanding its use of Epic’s native AI capabilities while working to reduce application complexity and consolidate functionality within the EHR when possible.
Adar Palis, senior vice president and chief of clinical applications and technology at Providence, told Becker’s that keeping more capabilities inside the medical record can reduce the infrastructure, interfaces and troubleshooting required when separate third-party applications are involved.
Providence’s strategy reflects a broader shift from simply adding new tools to examining whether existing functionality can instead be consolidated within Epic.
