The CapEx Trap: Why OpEx Is the More Disciplined Model for Hospital IT 

At a recent healthcare industry dinner, a CIO put the challenge plainly: “I can get all the capital I want. It’s the operating dollars that get scrutinized.” The wording was striking, but the sentiment was familiar. I have heard variations of it for years and experienced it firsthand as a health system CTO evaluating a move to the cloud.

Capital budgets are neither limitless nor lightly governed; they are simply scrutinized through a different lens. Operating expenses affect current-year performance more directly and, therefore, attract a distinct level of attention. As health systems move more infrastructure and services to the cloud, this CapEx-to-OpEx tension will surface. Navigating it requires more than a sound technology case. It requires a financial narrative that clarifies the tradeoffs, aligns stakeholders, and builds confidence in the path forward.

Same Technology Investment, Different Spending Rules 

The difference between CapEx and OpEx is more than accounting. It represents the shift from a legacy model built on rigid, long-range forecasts to an agile approach that aligns spending directly with current demand and delivered value. That distinction shapes how an investment is financed, governed, and perceived.

A capital project, whether a new data center, a server refresh, or a five-year infrastructure buildout, is typically evaluated within a multiyear capital plan and may be financed through bonds, variable-rate debt, or commercial paper. It is assessed against debt capacity, bond covenants, and balance-sheet priorities, then depreciated over several years. Healthcare capital issuance reached roughly $50 billion in 2025, up 34% from the prior year, while variable-rate debt nearly doubled.¹ Because the cost is spread over time, the investment does not affect the current year’s operating margin in the same way as a recurring subscription or service expense.

Operating spending follows a different path. A cloud services bill is recognized as incurred, making it immediately visible on the income statement and in the operating margin watched by boards, bondholders, and rating agencies. A 2026 survey of 100 hospital and health system CFOs found that 72% reported margins of 2% or lower, with declining reimbursement, reduced government funding, and rising labor costs among the leading pressures.² In that environment, recurring expenses understandably receive intense scrutiny—even when they replace large capital purchases and provide greater flexibility, utilization, and long-term value. 

The CIO’s observation is therefore less about the size of each budget than about how the two categories are treated. CapEx can appear easier because its cost is financed, depreciated, and absorbed through a familiar governance model. OpEx is more visible, but that visibility can create better discipline: spending tracks consumption, scales with demand, and is tested continuously against delivered value. As organizations shift more technology into the operating budget, leaders should ask a harder question: are they favoring capital because it is truly the more efficient use of scarce dollars, or because it fits the planning and approval model they already know?

What the CapEx Model Actually Costs 

While the price tag of a data center refresh is obvious, the true burden of the CapEx model extends far beyond the initial purchase.

The most immediate penalty is a loss of innovation. A five-year depreciation schedule assumes today’s technology will still meet the organization’s needs years from now. Yet AI, analytics, and data platforms are evolving faster than even the most thoughtful planning cycle. This long commitment creates a natural inertia: once hardware is placed on the books, organizations are financially incentivized to keep using it, even when better, faster options emerge. By locking into fixed infrastructure, health systems risk falling behind before the server is even fully depreciated. 

This rigidity also forces an impossible financial forecasting model. Because hardware operates on a strict timeline, IT leaders must predict future capacity and capabilities years in advance. This creates a lose-lose scenario: plan too narrowly, and the organization faces unbudgeted emergency upgrades; plan too broadly, and precious capital is trapped in underused assets. 

Ultimately, this trapped capital represents a massive opportunity cost. As Vizient’s analysis of health system capital planning observed, “the challenge has shifted from capital availability to capital selectivity.” ¹ Debt capacity is finite. Every dollar committed to commodity servers and storage is a dollar unavailable for patient towers, clinical equipment, or other investments that differentiate the health system.

Why the OpEx Model Is the More Disciplined One 

The OpEx model replaces a fixed, five-year technology bet with continuous accountability and adaptability. Public cloud provides the flexibility to adapt without locking tomorrow’s needs into today’s assumptions. Cloud resources can scale with demand, but the greater advantage is continuous access to new AI, analytics, and data capabilities as your workload requirements evolve. Instead of defending yesterday’s investment, leaders can keep spending aligned with current needs and demonstrated value. 

The financial impact is measurable, often translating to millions in avoided upfront costs. By transitioning its Epic deployment to a shared cloud model, UCI Health successfully bypassed approximately $36 million in preliminary hardware and infrastructure expenses.³ SCL Health’s move to lower-cost devices and cloud-based tools avoided several million dollars in capital spending while reducing labor overhead.³ In both cases, the shift eliminated a large upfront commitment and created room to adjust technology spending as organizational needs changed. 

The accounting treatment still matters. Under FASB ASC 350-40, eligible cloud implementation costs may be capitalized, while ongoing subscription and service fees are expensed as incurred.⁴ That visibility gives CFOs a legitimate reason for scrutiny, but it also creates a recurring opportunity to test cost against utilization, capability, and outcomes. Engaging finance early turns scrutiny into a governance advantage and helps create an operating model that can evolve with the technology.

The Real Barrier Is Not the Technology

A 2026 industry survey found that 56% of CIOs struggle to explain the CapEx-versus-OpEx tradeoff when competing for budget.² That is the real gap. For organizations seeking elastic capacity, modern security, and access to rapidly evolving AI and analytics capabilities, cloud is undeniably the right technology decision. The harder task is bringing the CFO and the board into that decision as partners rather than asking them to approve it after the fact. 

That requires speaking the language of finance: preserving debt capacity for strategic investment rather than commodity infrastructure; ensuring operating spend adjusts with demonstrated value rather than locking in a five-year forecast; and providing a candid view of how the shift will affect margins in the near term. The strongest case for cloud does not minimize those implications. It makes them transparent and manageable. 

Where EHC Consulting Comes In

This is the work EHC Consulting does alongside CIOs: building a financial narrative that makes an Epic-to-Azure move clear to a CFO and a board, not merely defensible to an IT steering committee. We quantify avoided capital, model how operating costs change with utilization, and bring finance into the migration design early enough to shape the plan and avoid a surprise line item in next year’s budget.

The CapEx model is not more comfortable because it is more responsible. It is more comfortable because it is familiar, and because it was built for an era when technology changed more slowly. Health systems that move beyond it will do more than modernize infrastructure. They will preserve capital and gain the agility to act as new clinical, data, and AI opportunities emerge. 

If your organization is evaluating what this shift means for its capital plan, operating model, and board conversation, EHC Consulting would welcome the opportunity to help. 

Schedule a consultation to start a conversation with us about next steps. 

Sources:  

1. Vizient, “A capital playbook for health systems“, March 3, 2026.
2. LeanTaaS, State of Hospital Financial Health 2026, LeanTaaS survey of 100 hospital/health system CFOs, April 21, 2026.
3.  Healthcare IT News, “Solving cloud computing’s CapEx vs. OpEx conundrum once and for all“, November 28, 2017.
4. FASB ASC 350-40 (cloud computing arrangements, internal-use software accounting), updated September 2025.