Table of Contents
When a hospital merger closes, one veteran CIO reaches for the exact same playbook every time, while another insists no two acquisitions ever call for the same one, illustrating just how differently health systems can approach CIO IT decisions hospital merger integration once the deal is signed.
The Growth Context Behind These CIO IT Decisions Hospital Merger Strategies
Health systems keep getting bigger. Mergers, acquisitions and affiliations have become one of the primary paths to scale, and each deal hands a CIO two organizations, two technology stacks and a clock that starts the moment the ink is dry. Becker’s tracked 29 large health systems pursuing mergers, acquisitions or strategic partnerships in 2026, describing a pickup in hospital consolidation after several quieter years following the pandemic.
The Two Deals Anchoring This Comparison
MultiCare is working through a planned merger with Corvallis, Ore.-based Samaritan Health Services that would create an 18-hospital system with more than 33,000 employees, while UNC Health is in the midst of the Onslow Memorial Hospital affiliation, a deal structured in phases that gives UNC Health a 30% membership interest in Onslow this year, rising to 49% in a second phase and full membership by 2029.
MultiCare’s Case-by-Case Approach to CIO IT Decisions Hospital Merger Integration
Scott Waters, interim CIO of Tacoma, Wash.-based MultiCare Health System, treats every acquisition as its own case study. The deal structure, the cultural fit between the two organizations and how much technical detail MultiCare could gather during due diligence all shape what happens first. “If you have done one acquisition, you have done one acquisition,” he told Becker’s. “They are all slightly different in most ways, but the amount of information you are able to get during the due diligence period is widely variable.”
Starting With People, Not Platforms
That variability is why Waters said he starts with people rather than platforms. “I generally start with determining how users are going to communicate and move between the two separate environments and for how long,” he said. “Typically, we need to have a bridge strategy for a period that allows for business-to-business connectivity for things like email, calendar, intranets and policy access.”
How MultiCare Handles EHR Integration Within This CIO IT Decisions Hospital Merger Framework
MultiCare almost always runs parallel EHR systems for a period, Waters said, with the length tied to geographic overlap between the two patient populations, opportunity prioritization and cultural alignment. The more a market overlaps, the more urgency there is to get both organizations onto one system, since overlapping markets mean shared patients navigating two records.
A Timeline That Has Evolved Over Time
Depending on the size of the organization being acquired, Waters said full integration generally takes 18 months to three years, and even that range has shifted over time. “This has evolved, but the pendulum swings back and forth a bit as bridging technology has evolved to make being on separate environments easier for our users,” he said.
UNC Health’s Standardized Approach to CIO IT Decisions Hospital Merger Integration
UNC Health’s Brent Lamm described a nearly opposite philosophy, one enterprise standard applied almost the same way every time. UNC Health recently completed its 11th go-live, absorbing Jacksonville, N.C.-based Onslow Memorial Hospital, bringing the health system to 20 hospitals across 11 go-lives. For Onslow, Lamm said the commitment to implement UNC Health’s enterprise systems within a set time frame was written into the acquisition agreement itself, which simplified the first decision considerably.
Transitioning IT Teammates First
Like Waters, Lamm said the first move is about people, not systems. “One of the very first things we do is we transition the entity’s IT teammates to UNC Health Information Services teammates,” he said. “We’ve created a recipe that we believe works really well for us, and we don’t deviate from it.”
UNC Health’s Non-Negotiable Epic Standard Within This CIO IT Decisions Hospital Merger Approach
Where Waters described running parallel EHR systems for years in some cases, UNC Health does not keep an acquired hospital on its legacy EHR long term under any circumstance. Every acquisition moves to UNC Health’s Epic build. “It is a requirement that we move them to our Epic at UNC implementation for our electronic health record system, so we don’t take over other hospital or practice entities and keep for the long term any other EHR,” Lamm said.
A Three-Phase Budgeting Structure
That standardization also extends to budgeting. Lamm said UNC Health builds a three-phase budget for every acquisition, starting with a full inventory of the incoming hospital’s hardware, software and contracts during due diligence, then splitting the work into three phases: one before the Epic go-live, one at the same time as go-live and one covering anything that must remain afterward.
The Speed Payoff From UNC Health’s Standardized CIO IT Decisions Hospital Merger Model
The payoff, Lamm said, has been speed. UNC Health has completed full IT migrations in as little as eight months and as long as 18, depending on the acquired hospital’s starting condition. “One of our entities had a situation where they were in desperate need of an IT transition, and we actually did that in eight months, end to end, full IT migration from their legacy IT service provider to UNC Health,” he said.
Why Consistency, Not Customization, Is Lamm’s Advice
Asked what advice he’d offer other CIOs navigating growth, Lamm pointed back to consistency, even when it isn’t the popular answer. “We don’t try to do custom arrangements for IT systems for one entity versus another,” he said. “Overall, we’ve been very careful to stay very standardized, and I believe that’s paid off well for us.”
What This Contrast in CIO IT Decisions Hospital Merger Philosophy Means Going Forward
Between the two health systems, the throughline is the same even where the philosophy isn’t. Neither CIO waits for the technology conversation to start with the technology; both start with the workforce that has to run it. Given the accelerating pace of hospital consolidation, with 29 large systems already pursuing mergers or affiliations in 2026, other CIOs navigating similar growth may find value in weighing MultiCare’s flexible, deal-by-deal approach against UNC Health’s speed-focused standardization, depending on their own organization’s culture and risk tolerance.
What to Watch Going Forward
As more health systems pursue mergers and acquisitions through the remainder of 2026, industry observers will likely watch whether MultiCare’s variable timeline approach or UNC Health’s standardized, Epic-first model proves more durable as consolidation activity continues accelerating. Given Lamm’s reported eight-to-18-month migration range and Waters’ 18-month-to-three-year integration window, the choice between these two philosophies may increasingly come down to how much speed a health system prioritizes against how much flexibility it needs to accommodate varying deal structures and cultural fit across future acquisitions.
For more healthcare industry updates, insights and news, visit DistilINFO. Click here to subscribe to stay informed.
