How Do I Reduce IT Complexity in My Healthcare Organization?

Too many systems, too little integration. Here’s a practical framework for reducing IT complexity in healthcare — without disrupting care delivery.

Manpreet

10/26/20267 min read

If you’ve asked this question, you’re not alone and the fact that you’re asking it matters.

IT complexity in healthcare doesn’t usually start with a bad decision. It starts with a series of reasonable ones-: a new EHR to meet regulatory requirements, a telehealth platform added during a crisis, a scheduling tool requested by one department, a billing solution that came with an acquisition. Each made sense at the time. Together, they created something that nobody planned and everyone now has to live with.

The result is a technology environment that costs too much, integrates too little and makes every process harder than it should be for IT staff, clinical teams and the leadership trying to make sense of it all.

There’s no single switch to flip. But there is a practical path forward.

Why Healthcare IT Gets So Complex

Understanding how complexity accumulates makes it easier to address it systematically. The average mid size healthcare organization manages hundreds of separate applications. Larger integrated delivery networks often manage more than 1,000 and some exceed 2,000 after years of mergers and acquisitions. Most healthcare organizations manage anywhere from 400 to 1,000 applications and large integrated delivery networks can easily exceed that, sometimes reaching 2,000 applications after years of mergers and acquisitions.

The problem compounds over time. Every application adds a licensing cost, a maintenance burden, a security exposure and at least one integration point that has to be maintained. And every integration point that breaks causes a disruption somewhere in care delivery or operations.

The drivers behind this sprawl are consistent across organizations -:

  • Systems added to solve immediate problems without a long term plan

  • Point solutions purchased department by department, outside central IT governance

  • Legacy systems kept running because migrating off them feels too risky

  • Acquisitions that bring in entirely separate technology environments

  • Compliance requirements that triggered new tool purchases without retiring old ones

According to the annual symplr Compass Report, the share of departments purchasing software outside formal governance has climbed steadily from 74% in 2022 to 81% in 2024 and now 86% in 2025 a trend that fragments data, increases risk and makes it harder for IT leadership to maintain any coherent picture of what the organization is actually running.

What IT Complexity Actually Costs You

The financial case for addressing IT complexity is strong, but the full cost is often underestimated because it shows up in several different places at once.

Direct technology costs-: Licensing fees, maintenance contracts and vendor support for applications that are partially used, duplicative, or no longer aligned with organizational needs.

Integration costs-: Custom built interfaces between systems are fragile, expensive to maintain and a frequent source of downtime. Every redundant application typically requires at least one integration.

Security risk-: Every application is a potential entry point for a cyberattack. Redundant or rarely used systems are often the least maintained and the least patched, making them attractive targets for ransomware.

Clinician burden-: Clinicians now spend an average of 88 minutes a day on administrative tasks and fragmented workflows across multiple systems are a significant contributor. When staff have to navigate a dozen different tools to complete a single process, they either disengage from the tools entirely or spend time on workarounds that create new risk.

IT staff time-: High application counts mean more vendor relationships to manage, more assessments, more patching cycles and more helpdesk tickets all of which crowd out strategic work.

Rationalization efforts in healthcare have been associated with a 30% reduction in IT support tickets and 20–25% improvements in clinical workflow efficiency, along with enhanced data interoperability.

The Framework-: How to Actually Reduce IT Complexity

Reducing IT complexity isn’t a cleanup project. It’s a strategic program that requires executive sponsorship, clinical involvement and a structured approach. Here’s how to think about it.

Step 1-: Get a Complete Picture of What You’re Running

You can’t rationalize what you can’t see. The first step is building a complete, verified inventory of every application in your environment including tools purchased outside of IT governance. Most organizations discover more than they expected. Applications used by only a handful of people. Duplicate tools doing essentially the same thing in different departments. Systems that were never formally decommissioned after a prior consolidation effort.

This inventory should capture, for each application what it does, who uses it, how often, what it costs in licensing and support, what it integrates with and whether it’s under active vendor support.

Step 2-: Evaluate Each Application Against Clear Criteria

Once you have a complete inventory, the next question is which of these should we keep, consolidate, or retire?

A practical evaluation framework typically considers-:

  • Business value-: Does this application directly support clinical care, operations, or a compliance requirement?

  • Utilization-: Is it actually being used and by how many people?

  • Total cost of ownership-: What does it cost to license, maintain, integrate and support?

  • Redundancy-: Does another system in the portfolio perform the same or similar functions?

  • Security posture-: Is the vendor actively maintaining and patching the system?

  • Integration complexity-: How many custom integrations depend on this application?

This is where clinical and operational leaders have to be involved. IT can’t make these calls alone and shouldn’t try. Every application has a stakeholder who will advocate for keeping it. Every application has a champion. Every department has a reason why their system is different. The evaluation process has to be structured enough to weigh these perspectives without being captured by them.

Step 3-: Prioritize Consolidation Where It Hurts Most

Application rationalization programs fail when they try to do everything at once. The more sustainable approach is to identify the highest impact consolidation opportunities and sequence them carefully. Look first at areas where fragmentation is visibly hurting the business workflows that require staff to log into multiple systems, integration points that break frequently, departments running two or three tools that perform overlapping functions.

Platform consolidation enables organizations to standardize workflows, improve interoperability and reduce administrative burden. More than 75% of healthcare leaders say a consolidated healthcare operations platform would help address inefficiency and administrative complexity.

Consolidating toward platforms rather than continuing to add point solutions is increasingly the direction that well run health systems are moving. A platform approach reduces the number of integrations required, standardizes the user experience for clinical and administrative staff and makes it easier to demonstrate ROI from technology investments.

Step 4-: Decommission with Discipline

Retiring a legacy system is harder than it sounds. There are data retention requirements, compliance considerations, users who depend on the system for processes that may not be fully documented and integrations that have to be cleanly severed. Application decommissioning needs its own project management discipline a clear data migration or archival plan, communication to affected users well in advance, validation that the replacement system covers all critical functions and a defined cutoff date with a path for handling edge cases.

Skipping this step or doing it informally is how organizations end up maintaining “decommissioned” systems for years because some process still depends on them.

Step 5-: Build Governance to Prevent Recurrence

Reducing complexity is valuable. Preventing it from coming back is what makes the effort sustainable. The most common failure mode is a consolidation program that succeeds in the short term, then watches application sprawl return over the following two or three years as departments resume purchasing tools independently. This is especially common in healthcare, where clinical units and service lines have significant autonomy.

An effective governance structure establishes a clear process for technology evaluation and approval before new tools are purchased. It doesn’t have to be bureaucratic, but it does have to exist. Key elements include a defined application review process, criteria for evaluating new requests against existing portfolio capabilities, visibility into shadow IT purchases and a standing group with both IT and clinical leadership representation.

The Role of Strategic Leadership in Simplifying Healthcare IT

Reducing IT complexity is ultimately a leadership challenge, not a technical one. The technical work is real, but what determines success or failure is whether the organization has the strategic clarity, the executive alignment and the sustained attention to see it through.

This is one of the most common gaps in community health organizations and mid market health systems. The IT team may understand what needs to happen, but without C-suite sponsorship and a coherent strategy, the program stalls when it hits its first difficult decision which it always does.

Technology alone does not solve inefficiency. Aligning systems with how care is delivered does.

This is the work Paul McRae and the TransformativeHLTH team do through fractional CTO services for healthcare organizations-: helping leadership teams develop the strategy, governance and prioritization frameworks needed to simplify their technology environments and align IT with the operational and clinical goals of the organization. For organizations that don’t have dedicated senior technology leadership but are ready to make meaningful progress, this kind of embedded advisory partnership can accelerate the entire program.

If you’re working through an IT complexity challenge and want to talk through where to start, schedule a strategy conversation with Paul.

Common Pitfalls to Avoid

A few patterns consistently derail IT simplification efforts in healthcare

Starting without executive sponsorship. Application rationalization requires decisions that create short term friction departments losing familiar tools, vendors losing contracts. Without visible leadership support, those decisions get reversed.

Treating it as a one time project. IT complexity will return if governance doesn’t change. Build the structural safeguards from the beginning.

Underestimating the change management piece. Staff who lose tools they rely on need clear communication about what’s replacing them and why, along with training that doesn’t feel like an afterthought. This is especially true in clinical settings where workflow disruption has direct patient care implications.

Consolidating without involving clinical users. Systems selected without clinical input frequently get bypassed in practice. Clinicians will find workarounds, which creates new shadow IT and new complexity.

Focusing only on cost. Cost reduction is a legitimate goal, but the most successful programs also frame consolidation in terms of workforce experience, security posture and care quality. Those arguments sustain momentum when cost alone isn’t enough.

Where to Start

If you’re not sure where to begin, start with a question Where is IT complexity most visibly hurting your organization right now?

Pick one workflow or department where fragmented technology is creating real problems for staff, for patients, or for operations. Map what’s actually happening. Count the systems involved. Understand the integrations. Estimate the real cost. That scoped exercise will reveal more than any high level assessment and it will give you a concrete, defensible case for a broader program.

The organizations that successfully reduce IT complexity don’t wait until everything is aligned perfectly. They identify where the pain is highest, build a plan grounded in that reality and move.

Innovation

Empowering health systems through strategic digital transformation solutions.

Support

© 2026. All rights reserved.

TransformativeHLTH  logo
TransformativeHLTH  logo