Ask a healthcare organisation how much their EHR implementation cost, and you will typically get the software licensing figure. Ask them how much it actually cost — including infrastructure, training, lost productivity, custom integration work, data migration, post-go-live support, and the remediation of issues that were not anticipated — and the number is significantly larger. The gap between the purchase price of a healthcare IT system and the total cost of owning and operating it is one of the most persistent and damaging financial miscalculations in healthcare management. This article describes what organisations consistently miss, and how to build a more accurate picture before committing.
Why Healthcare IT Projects Run Over Budget
Healthcare IT projects are, by nature, complex. They involve multiple vendors, large numbers of clinical and administrative stakeholders, intricate integration requirements, and implementation timelines that stretch across months or years. Complexity creates cost, and cost that is not anticipated at the outset becomes overrun at the end.
But the overruns are not random. They cluster around a set of costs that are structurally underestimated in almost every healthcare IT budget. These are not obscure costs that only an expert would know to look for. They are predictable, well-documented costs that get excluded because they are difficult to estimate early, because they are owned by a different budget holder, or because including them would make the business case harder to approve.
The Hidden Costs
Training and Education
Training is the most consistently underestimated cost in healthcare IT projects. Organisations budget for the vendor's standard training package and consider the problem solved. They do not account for:
- The cost of clinical staff time away from patient care to attend training
- The development of role-specific training programmes beyond what the vendor provides
- The cost of superuser training (extended training for designated champions in each department)
- The ongoing training costs as new staff are hired and staff change roles
- Re-training when the system is upgraded significantly
For a 200-bed hospital implementing a new EHR, the internal cost of staff time for training alone — just the hours spent by clinical staff in training rooms rather than delivering care — can exceed the cost of the vendor's training services.
Change Management
Change management is frequently excluded from IT project budgets entirely, or allocated a token amount. The costs include: a dedicated change management resource or consultant, communication materials development, clinical champion time (which needs to be backfilled if champions are released from clinical duties), and post-go-live adoption support activities. For large implementations, change management typically represents 10–15% of project cost when done properly.
Integration Work
Healthcare IT environments are complex integration landscapes. An EHR connects to laboratory systems, radiology systems, pharmacy systems, patient administration systems, billing platforms, and increasingly to external networks for referring facilities and health information exchanges. Each integration requires design, development, testing, and ongoing maintenance.
Integration costs are frequently underestimated because vendors quote their standard interface package without understanding the specific integration requirements of a given environment, and because integration issues are often discovered during testing rather than during scoping. A rule of thumb for complex healthcare implementations: integration work should be budgeted at 15–25% of the total software licensing cost, sometimes more.
Infrastructure Upgrades
New systems often require infrastructure investments that were not anticipated at the time of the software purchase decision. A cloud-hosted system may require a WAN upgrade to provide adequate bandwidth to clinical areas. A new clinical workstation application may require replacement of end-of-life hardware. A high-availability clinical system may require storage and compute upgrades on-premise. These costs are real and often significant, but they belong to the infrastructure budget rather than the project budget — and as a result, they are often not counted in the project's total cost.
Data Migration
Migrating data from legacy systems to a new system is expensive, technically complex, and frequently underscoped. Data migration costs include: data quality assessment and cleansing (legacy data is rarely clean), development of extract-transform-load (ETL) processes, testing and validation of migrated data, and clinical review of migrated records. For systems holding years of patient data, migration can consume hundreds of project hours and significant consultant fees. Organisations that decide to freeze legacy data rather than migrate it still incur costs for maintaining legacy system access.
Post-Go-Live Support and Optimisation
The first six months after a system goes live are not the end of the project — they are the beginning of the optimisation phase. System configuration issues become apparent only when real clinical workflows interact with the system in real conditions. Clinical staff request configuration changes. Reports need to be built or adjusted. Interfaces need tuning. These activities require ongoing project resource or vendor professional services, and they are rarely budgeted adequately.
The transition from project to business-as-usual also creates internal costs. IT staff need time to develop operational competence in supporting the new system. Helpdesk call volumes are elevated for three to six months post-go-live.
Vendor Lock-In Costs
Once a healthcare organisation has committed to a major clinical system, the cost of switching becomes very high. This is not hidden at the time of purchase, but its long-term implications are consistently underweighted. Vendor lock-in means that subsequent contract renewals are negotiated from a position of weakness. Price increases are difficult to resist because the cost of switching — data migration, retraining, workflow disruption — is so large. Over a ten-year contract lifetime, the cumulative cost of price escalation resulting from vendor lock-in can significantly exceed the original licensing cost.
Total Cost of Ownership vs Purchase Price
Total cost of ownership (TCO) analysis accounts for all costs associated with a system over its operational life. For a healthcare IT system, a five-year TCO model should include:
- Year 0: implementation costs (licensing, professional services, training, integration, infrastructure, data migration)
- Years 1–5: recurring costs (licensing/subscription fees, maintenance and support, helpdesk burden, ongoing training, infrastructure, optimisation and enhancement)
TCO analysis frequently shows that the Year 0 implementation cost represents only 30–50% of the five-year total. The ongoing operational costs are substantial and must be funded from recurring operational budgets. Many organisations approve capital investment for a system without adequately planning the recurring operational budget, creating financial pressure in subsequent years.
Building Realistic Budgets
A realistic healthcare IT project budget should be built from first principles, with input from the vendor, from comparable organisations that have implemented the same system, and from internal stakeholders who understand the clinical and operational context.
Key practices:
- Include all cost categories from the outset, even if estimates are rough. A rough estimate is better than a zero.
- Apply a contingency of 15–25% for complex implementations. This is not pessimism — it is recognition that integration issues, data quality problems, and scope changes are normal in healthcare IT projects, not exceptional.
- Separate capital and operational costs in budget presentations, but ensure operational costs are approved by the budget holder who will own them before the project is sanctioned.
- Track actual costs against budget throughout the project, not just at the end. Cost overruns that are identified early can be managed. Overruns that are disclosed at project close cannot.
The Opportunity Cost of Failed Projects
The cost of a failed healthcare IT project is not just the money spent. It is the opportunity cost: the systems not implemented, the clinical improvements not achieved, and the staff confidence in IT that takes years to rebuild. Organisations that have experienced a high-profile IT project failure typically see reduced staff engagement in subsequent projects, which makes the next implementation harder and more expensive.
Realistic budgeting, rigorous project governance, and honest reporting of project status are not just financial disciplines — they are clinical quality and organisational culture disciplines.
FZ Consulting LLP helps healthcare organisations build realistic IT business cases and govern technology investment effectively. Contact us to discuss a project budget review or investment case.