Every health system board is currently facing some combination of scarcity. Capital is down, labor costs are high, and margins have hovered between 2-4% over the last year. Add to that the pressures to build AI as quickly as possible. It makes sense that every request that comes before the finance committee undergoes sharp scrutiny about where funding will come from and what the return on investment will be. So when interoperability is viewed as a line item or compliance cost, it can read as a drain on the system. 

That framing is understandable, but it is costing health systems. 

Infrastructure Sprawl is Hiding Interoperability ROI 

Walk through the technology stack of almost any hospital or health system today and you will find the same pattern. A platform for referrals, a separate tool for care coordination, another for patient outreach, and a fax gateway that nobody wants but nobody has fully replaced. Point solutions layered on top of point solutions, each one purchased to solve a specific problem at a specific moment, few of them talking to each other. 

The industry has a name for this now: infrastructure sprawl. IT budgets keep growing while the problems they were meant to solve, like dropped referrals, missing records, and delayed care, persist. None of this is evidence that interoperability doesn’t pay off. It is evidence that the return is scattered across a dozen disconnected systems, so no one can see it.  

Sprawl happened with the passage of the HITECH Act in 2009, which triggered a rapid and necessary migration to electronic health records. In just a seven-year span, healthcare went from roughly 90% paper-based to more than 80% digital. Without that mandate, we might not have connected EHRs at all, so it was a good step in the right direction. But the newness of the technology and the speed of the deadline meant that thousands of hospitals came online before vendors had a chance to build solutions that not only worked, but worked with each other. The result was nearly endless customized point solutions built to handle digitization, instead of a single standard every hospital could build on. 

The rush to AI is repeating the pattern. Health systems are building their own models and standing up their own agents, and every one of them is a data consumer, just as much as a clinician or an application is. Each needs its own path to the record, and each decision it makes is only as good as the infrastructure underneath it. Built one connection at a time, they become the next layer of sprawl. 

Now, vendor consolidation initiatives are increasingly showing up on strategic plans because the math has become impossible to ignore. Organizations that consolidate redundant point solutions onto shared infrastructure spend less, keep the capabilities those point solutions were bought to provide, and reduce the burden on IT teams, clinicians, and administrative staff who are managing too many disparate workflows. 

Infrastructure That Outlasts the Applications Built On It 

Those savings are not primarily about negotiating a better contract with fewer vendors, although that helps. They come from something more structural. Every point solution a health system buys to move information, a referral tool, a records request platform, a care coordination app, has to solve the problem of reliably reaching providers, EHRs, or organizations on the other end. Buy ten point solutions and you have paid, ten times, for ten different, incomplete answers to that same question. 

Connect once, and every one of those tools inherits the same reach. All of them get more valuable the moment they can plug into infrastructure that already reaches the providers, networks, and settings a patient actually uses, instead of rebuilding that reach over and over again. 

Communication is not an application, it’s the foundational infrastructure underneath the applications. Tools can get replaced as vendors change and priorities shift. Infrastructure gets built once and gets more valuable as more things connect to it. A board that funds another point solution is funding an application. A board that funds connectivity is funding a capability that every future application, every AI agent, and every future vendor decision, gets to use for free. 

Flip the Script 

A cost center is something you minimize. You negotiate it down, you audit it annually, you ask whether you can get by with less of it. That is the right instinct for a fax line or a document management license. It is the wrong instinct for the infrastructure that determines whether you can communicate with other providers, with payers, and with patients themselves. 

The ROI of interoperability shows up in other line items. Referrals that convert, avoided readmission penalties, and patient loyalties impact the bottom line in tangible ways, and they are only successful when communication happens.  

Communication, done well, determines whether EHRs, care management platforms, referral networks, and M&A integrations deliver the value they were bought for. That is a strategic asset, and strategic assets get evaluated differently than line items.  

The Bigger Picture 

We built Kno2 on the belief that every provider, hospital and PCP, but also the dentist, the home health agency, the behavioral health practice, the skilled nursing facility, deserves to be part of the same connected system, because patients move through all of them. But in addition to all of that, there is real monetary value in good communication. A health system’s ability to compete, retain patients, and operate efficiently increasingly depends on how well it moves information. 

Interoperability will keep showing up as a line item, because budgets need line items. But the organizations that will out-perform their peers over the next decade are the ones whose boards stopped asking what interoperability costs and started asking what connected infrastructure makes possible. At margins this thin, there is no more room to fund the same reach ten different ways. There is, however, plenty of room to fund it once, and let everything else the organization builds stand on top of it.