UPMC brought its second Epic electronic health record wave live on October 3, 2026, including Pittsburgh-area facilities. Becker’s reporting on October 6 puts the scope at 15 hospitals and hundreds of ambulatory sites. To follow projects relevant to your services, you can try PipeSignals for free.
A changeover within an established program
This is an implementation milestone, not a newly awarded contract. Becker’s obtained a statement from UPMC’s chief information officer describing the Pittsburgh and most southwestern Pennsylvania transition. The broader consolidation was announced in 2023; this article does not treat that older decision as fresh news.
Josh Ewers’ October 9 TribLive report, carried by the Mon Valley Independent, dates the second wave to the preceding Saturday and places the first wave in September 2025. It also identifies Washington, Greene and Trinity as future phases. The October milestone therefore should not be read as completion across every UPMC facility.
The patient portal has changed too
UPMC’s current MyUPMC guidance describes the updated portal as available. Messages from before October 3 remain readable but cannot receive further replies; a new conversation is needed. The portal displays the most recent five years of records, with older records available through a request process. This is a change in access and presentation, not evidence that older records were deleted.
Stabilization is still part of the work
The TribLive report documents patient complaints and quotes UPMC’s CIO acknowledging longer waits in some cases and a stabilization period. UPMC characterizes the known issues as specific to workflows, departments, devices or operational areas rather than systemwide. Neither that statement nor the go-live itself establishes that every problem has been resolved.
What service providers can qualify
Our analysis: this milestone is relevant to healthcare technology consultancies working on implementation support, user documentation and workflow testing. The useful question is which post-launch work, if any, remains open to external suppliers. Existing support arrangements may already cover it.
A credible discussion would distinguish portal guidance from clinical workflow support, identify the accountable team and establish whether any additional service is actually required. Public reporting does not disclose an open procurement, an available budget or an invitation to replace the existing implementation partners.
You can configure a watchlist around deployments in your market and try PipeSignals for free. Confirm the remaining scope before treating a live rollout as a commercial opportunity.
