Author: Clearsense
Application portfolio modernization is not an IT inventory exercise. It is an enterprise margin decision about what the organization should run, and it gets made before anything is retired.
IDC frames the discipline as application portfolio modernization and rationalization (APM), a continuous cycle that inventories the estate, assesses each application across business, financial, operational, and technical dimensions, and then rationalizes toward consolidation, modernization, or retirement. The assessment comes first. Everything downstream is an output of it, including an executive-approved roadmap that sequences rationalization, archiving, and decommissioning.
The decision is getting more expensive to defer. Gartner forecasts worldwide software spending of $1.47 trillion in 2026, up 15.5% in a single year, while technology budgets are strained by inflation, hardware costs, AI funding, and shifting priorities. IDC found 23% of organizations shifting budgets toward GenAI, at the risk of overlooking the portfolio work underneath. Portfolios keep growing while the money to run them is rationed.
A complete inventory is only a list. It will not tell a health system which applications do the same job, what that overlap costs, or which system should become the standard.
Duplication is also more expensive than it looks. Every application carries a license line in the budget, but the support hours, interfaces, and data reconciliation it generates are rarely charged back to it. That spread-out spend is the cost you cannot see, and it strengthens the case for consolidating to one enterprise standard for each function.
License is the number in the budget line. It is rarely the largest.
Finance already tracks the license. Renewal dates, escalators, and tiering are on paper. Three larger costs are not. Support is internal FTE time and vendor hours spread across dozens of low-use systems, rarely allocated back to the application that generates them. Integration cost scales with the number of endpoints rather than their value, because every duplicate system is an interface to build, monitor, and fix. Operations absorb the rest. Analysts reconcile the same patient, provider, or charge across systems that hold different versions of it. That work sits in operations’ budget, so an IT budget review never sees it.
The concentration is not even. Gartner finds that roughly 20% of applications drive 80% of an organization's cost, complexity, and risk (Gartner, G00797456). Four out of five applications are not where the money is. Ranked on license alone, a portfolio points at the wrong twenty percent.
This is also why a credible engagement does not open with a savings number. Benchmark percentages borrowed from other organizations do not survive a finance review. The baseline gets built from the health system's own contracts, support data, and interface inventory in the first four weeks, and the model has to be one the finance organization owns and can re-run on its own assumptions.
Three things you must know
What applications are you running? The authoritative list rarely exists in one place. Contracts, asset inventories, and site knowledge each hold part of it, and shadow systems sit outside all of them.
What does each application truly cost? License is the visible number. Support hours, interface maintenance, infrastructure, and the cost of reconciling duplicate data are where the spend hides.
Which ones should remain? Some redundancy is genuine waste. Some is a specialty clinic whose billing rules only one system handles. Getting that distinction wrong is how rationalization programs stall.
Answering those three takes contract analysis, cost normalization, and clinical validation together, which is why it rarely gets done from inside the IT organization alone. Answer them, and you will know where to standardize, where to invest, and what you can permanently remove from the P&L.
A disposition for every application
Every application is scored against six criteria: future-state fit, footprint and migration lift, contract economics, integration burden, clinical and operational necessity, and data and retention obligation. The scoring must be visible and auditable, so the reasoning behind each recommendation is on the record, and dissenting views are documented.
The scores produce a disposition using Gartner's TIME framework.
Tolerate keeps a system as is, with no new investment and a set date to revisit.
Invest names the enterprise standard that other sites move onto.
Migrate moves an application onto that standard or consolidates it into a single contract.
Eliminate switches the system off and exits the contract.
Elimination is one path of four, and it is not the objective. The portfolio contracts through standardization and consolidation as much as through outright removal. When a duplicate migrates onto the enterprise standard, the contract ends, but the capability does not. It moves to the system the enterprise decided to keep.
Applications are retired. Data is not. A data disposition is required in all four cases. A tolerated system keeps accumulating records. An invested standard inherits history from every site that migrates onto it. A migrated one leaves history behind. An eliminated one leaves records behind as unmanaged retention risk. Every disposition needs a strategy to migrate the data forward, archive it as discrete records, or purge it, set by record type and state law rather than by the application's end date.
Governance keeps the portfolio from refilling
Choosing one system for each function is where the portfolio starts to change. Keeping it that way is the harder part. Acquisitions, new implementations, and shifting priorities add applications faster than health systems retire them, and finishing an assessment does not turn that mechanism off.
That is why governance matters as much as the roadmap. Every new request gets tested against the choices the enterprise already made. A second scheduling system or a new departmental billing tool needs a documented reason to run alongside the system the organization decided to keep. Without that check, the portfolio drifts back toward the sprawl it started with.
The bottom line
The goal of this work is a standard operating platform. Each function runs on one designated system, and every other application is tolerated for a stated reason, migrated onto the standard or retired. That is the decision TIME is built to make. It sorts the portfolio by what deserves investment and what should converge, not by what costs the most.
Cost still matters. The spend you cannot see is real, and surfacing it makes the case for the standard harder to argue with. The larger return is a portfolio that runs on fewer systems, shares data across sites, and absorbs new demands without adding another application each time.
APM is an executive decision about what the enterprise should run. It belongs with IT, clinical, and finance leadership together, and it gets revisited on a schedule rather than treated as a one-time exercise. The health systems pulling ahead are not the ones with the longest project list. They are the ones that decided what the portfolio should look like, wrote it down, and put governance behind it.
Sources
Gartner, “Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion,” press release, July 27, 2026. Serge Findling, IDC, “Strategize, modernize, and lead: Transform your business with application portfolio modernization,” CIO, August 27, 2024. Survey figure from IDC Future Enterprise Resiliency and Spending Survey, Wave 1, January 2024.
Gartner, application cost and complexity concentration, G00797456.
Gartner TIME Framework. gartner.com/document-reader/document/5450064?ref=pubsite
