In March 2026, Sutter Health and Allina Health announced a letter of intent to combine, creating a nonprofit system spanning 39 hospitals, more than 400 primary and specialty care sites, and more than five million patients across California, Minnesota, and Wisconsin. It's the kind of headline-making deal that signals where healthcare consolidation is headed.
What doesn't make the press release: the two organizations now face the task of reconciling two entirely different pictures of what they own, across every hospital, imaging center, ambulatory surgery center, and specialty clinic in both systems.
That's not a knock on either organization. It's the nature of how hospital capital data has always worked.
Consolidation is happening at every level, not just at the top
The Sutter/Allina announcement is the large-scale version of a story playing out constantly across the industry. In 2025, there were 46 announced hospital mergers or acquisitions (roughly one per week) and that was the lowest volume in 15 years. Analysts expect deal activity to climb in 2026.
And those numbers only capture the major transactions. Health systems are also continuously acquiring imaging centers, ambulatory surgery centers, urgent care locations, and physician practices. Some of these are high-profile deals. Many are not. All of them add assets, contracts, and equipment data to a growing footprint that was already difficult to see clearly.
Capital equipment represents roughly 20% of a hospital system's non-labor spend. When a health system grows through acquisition, that number grows with it, and the data complexity compounds at every step.
The data problem nobody puts in the due diligence deck
Before the ink dries on any transaction, both sides are already managing capital equipment data across incompatible systems. Each organization has its own CMMS. Its own ERP. Its own contract database, depreciation schedule, and departmental replacement request process. In many cases, equipment appears in one system but not another, or appears twice under different names.
For a newly acquired imaging center, that might mean MRI and CT records sitting in a standalone CMMS with no connection to the acquiring system's ERP or finance platform. For a surgery center acquisition, it might mean service contracts and equipment warranties that nobody at the parent organization can see or search.
This isn't a failure of either organization. It's the nature of how hospital capital data has always worked: fragmented by design, siloed by default.
Consolidation doesn't fix fragmentation. It compounds it.
What actually breaks during integration
In the months following a transaction, a few things happen consistently.
First, nobody can produce an accurate unified asset inventory. Clinical engineering teams on both sides have records, but reconciling them across two CMMS platforms (where the same manufacturer might be listed under three different names) is a manual, months-long effort.
Second, vendor contracts get duplicated. A newly combined system might discover it holds active service agreements with the same vendor across seven hospitals and three imaging centers, negotiated independently, at different price points. The opportunity to consolidate and renegotiate is there. The data to act on it usually isn't.
Third, capital planning stalls. The CFO needs a multi-year capital replacement forecast for the combined organization. Finance is waiting on clinical engineering. Clinical engineering is reconciling spreadsheets. The next budget cycle doesn't wait.
Here's the part that often gets missed: capital planning is not a one-time event. Every quarter, equipment ages. Service contracts expire. New facilities come online. Replacement requests accumulate. Without a unified data foundation, each of those moments requires another round of manual reconciliation across systems that were never designed to talk to each other.
What unified capital intelligence changes
The organizations that navigate merger integration cleanly share a common trait: they establish a single capital data layer early, one that spans all facilities, reconciles across their existing systems, and doesn't require either side to rip and replace their CMMS or ERP.
That's the architecture Capital Cycle Management (CCM®) is built on. Rather than forcing a system migration, CCM® ingests data from all existing platforms across the combined organization (CMMS, ERP, finance systems, service contracts, departmental spreadsheets), normalizes it, and surfaces a unified capital asset record for every piece of equipment across the combined fleet. Imaging centers. Surgery centers. Hospitals. Clinics. All of it, in one place.
The result is fleet visibility that actually reflects reality. Vendor spend that can be analyzed and consolidated across the full footprint. Replacement schedules grounded in asset-level data rather than category-level benchmarks.
Consolidation is supposed to create leverage. Without unified capital data, it rarely does.
The window is shorter than it looks
The first joint capital budget cycle comes fast. Most organizations have six to twelve months between transaction close and the moment leadership expects a coherent capital plan for the combined entity. That's the window to get the data right.
The systems that use that window well come out with a defensible replacement roadmap, a vendor consolidation opportunity map, and a capital planning process that scales as the organization continues to grow.
The ones that don't spend the next two years backfilling information they should have had from the start.
Capital Cycle Management (CCM®) gives health systems unified capital intelligence across their entire asset fleet, including during and after merger integration.