Title: Implementation Challenges - The Human Factor: How American Hospitals Navigate the People, Process, and Cultural Hurdles of Digital Transformation |
Short Executive Summary |
This chapter explores Implementation Challenges---the complex web of human, organizational, and cultural barriers that make deploying a Hospital Information System one of the most difficult undertakings in healthcare management. While technology itself is often the focus of excitement and investment, the true determinants of HIS success lie in the 'human factor': the resistance, misaligned incentives, inadequate training, and cultural inertia that can derail even the most sophisticated systems. Through detailed U.S. case studies---from a major academic medical center's decade-long, troubled EHR migration, to a community hospital's successful change management strategy that engaged clinicians early, and the federal government's ongoing struggles with the VA's EHR modernization---we examine the patterns of failure and success that have emerged from decades of HIS implementation experience. The chapter covers the core concepts: the organizational digital divide between high-resource and low-resource hospitals, the critical role of leadership and change management, the problem of physician resistance and how to address it, the hidden costs of training and workflow disruption, the importance of user-centered design and real-world testing, and the systemic lack of regulatory oversight that has allowed vendors to profit while providers struggle. It concludes that implementation challenges are not technical problems with technical solutions; they are human problems that require leadership, empathy, engagement, and a realistic understanding that digital transformation in healthcare is a long, iterative, and often messy journey. |
|
Implementation Challenges - The Human Factor |
A Detailed Popular-Science Exploration |
1. The Technology Isn't the Problem |
When a hospital decides to implement a new Hospital Information System, the natural focus is on the technology: the features, the functionality, the integration, the data migration. But experience across decades and thousands of implementations has shown that technology is rarely the main problem. The real challenges are human: resistance from clinicians, inadequate training, mismanaged expectations, cultural inertia, and the hidden costs of workflow disruption. |
In the United States, the implementation of health IT has been a story of mixed results. While federal subsidies under the HITECH Act drove rapid adoption, the evidence suggests that the promised benefits of efficiency, reduced costs, and improved outcomes have often been elusive. A 2025 report from Cornell University's ILR School, titled 'Financialization through Health IT,' provides systematic evidence of what has gone wrong in health IT implementation: federal rules did not require real testing of health IT capabilities prior to implementation, nor have they required evaluations to assess whether federal dollars are being used effectively. The authors argue that the federal government has not provided adequate safeguards, resulting in an unregulated multi-billion-dollar industry monetizing patient data without patients' or providers' knowledge . |
This chapter will take you inside the difficult reality of HIS implementation. We will explore the barriers that hospitals face, the role of leadership and change management, the persistent challenge of clinician resistance, and the lessons learned from both spectacular failures and quiet successes. |
|
2. The Organizational Digital Divide |
One of the most consistent findings in research on HIS implementation is that not all hospitals face the same challenges. The barriers to success are distributed unevenly, with lower-resourced hospitals facing a heavier burden. |
A 2023 nationally representative survey of 2,420 U.S. hospitals examined barriers to obtaining and using interoperable information. The results are striking : |
81% of hospitals experienced at least one minor barrier to exchange. |
62% experienced at least one major barrier. |
- The most common major barriers related to different vendors and exchange partners' capabilities. |
The Divide: The study found that higher-resourced hospitals and those often using network-based exchange tended to experience more minor barriers, whereas lower-resourced hospitals and those often using mail/fax or direct access to outside EHRs experienced more major barriers. This is a critical insight: the hospitals that are least resourced are the ones facing the most significant obstacles. |
The Consequences: In multivariate regression, hospitals indicating 'Patient matching' and 'Costs to exchange' as a major or minor barrier had the strongest independent negative association with the likelihood of reporting that providers at their hospital frequently use information from outside organizations . In other words, these barriers are not just annoyances; they actively prevent clinicians from using outside information to inform patient care. |
The Context: While many technical and policy efforts are underway to address these barriers, the study concludes that 'it will be important to monitor whether efforts are successful in ensuring information from outside organizations can be seamlessly exchanged and used to inform patient care' . |
|
3. The Human Cost of Flawed Systems |
The human consequences of poor implementation are substantial. The Cornell University report argues that health IT systems have 'frustrated medical professionals --- leading to burnout and high quit rates - while hospitals and physician practices have spent millions retrofitting or upgrading flawed systems' . |
Key Findings from the Report: |
- Federal rules did not require real testing of health IT capabilities prior to implementation, nor have they required evaluations to assess whether federal dollars are being used effectively. |
- Empirical evidence shows that EHRs have led to better billing and internal communications, but these studies do not calculate the hidden costs of installing, maintaining, and upgrading systems, as well as hiring, training, and retraining the healthcare workforce as systems continually change. |
- 'Behind the electronic health records, data analytics and financial management systems that health care organizations and providers depend on are private equity, venture capital, IT vendors and data-mining firms that own, operate or control health IT - and have made billions in the process' . |
The Regulatory Gap: The authors argue that 'federal rules have not provided adequate safeguards for patient information privacy and security, resulting in an unregulated multi-billion-dollar industry monetizing patient data without patients' or health care providers' knowledge' . The report warns that 'the unregulated integration of AI tools into these systems will make it even harder to protect patients' rights' . |
The Bottom Line: The history of health IT implementation and the lack of sufficient regulatory oversight should give us 'great pause for the current enthusiasm over the adoption of AI and machine learning in health information systems' . |
|
4. The VA EHR Modernization: A Case Study in Implementation Struggles |
The U.S. Department of Veterans Affairs has been attempting to modernize its EHR system for years. The effort has been plagued by challenges, providing a vivid illustration of the complexities of large-scale HIS implementation. |
The Lovell Federal Health Care Center Rollout: In March 2024, the VA and Oracle Health rolled out a new EHR system at the Captain James A. Lovell Federal Health Care Center in North Chicago, where the VA had to synchronize its system rollout with the Department of Defense's . |
The OIG Findings: The VA Office of Inspector General reviewed the interface testing for 24 EHR interfaces at Lovell. The findings are a cautionary tale : |
- While the correct tests were conducted, the OIG observed inadequate documentation. Sufficient documentation is needed to verify proper implementation, operation, and security requirements. |
- The required repository for recording problems identified in testing did not show testing had been done before the healthcare center went live with the Financial Management System interface, which bridges the EHR system and VA's payment and billing system. Testing was delayed by a cyberattack, and results were recorded in another system. |
- Some procedures did not clearly detail what to do when testing results and notations conflicted: the notation 'no run' (meaning no test steps were run) was used together with the notation 'passed' for four of 24 interfaces. |
- A lack of functionality was confirmed with two interfaces between VA and the DoD. For at least these two, documentation showed testers had not accounted for the joint nature of workflows at the Lovell facility . |
The Lessons: This case highlights the critical importance of thorough testing, clear documentation, and the need to account for complex, joint workflows in multi-organizational settings. |
|
5. What Makes Implementation SucceedA Framework from the Literature |
Despite the challenges, there is a robust body of research on the factors that contribute to successful HIS implementation. A synthesis of studies reveals several key success factors : |
| Factor | Key Insight | |
||| |
| Management Support | Management's active involvement and support is positively associated with EHR implementation and counterbalances physicians' medical dominance. | |
| Clinical Staff Participation | Participation of clinical staff in the implementation process increases support for and acceptance of the EHR implementation. | |
| Training and Support | Training end-users and providing real-time support is important for EHR implementation success. | |
| Comprehensive Strategy | A comprehensive implementation strategy, offering both clear guidance and room for emergent change, is needed for implementing an EHR system. | |
| Interdisciplinary Group | Establishing an interdisciplinary implementation group consisting of developers, IT, and end-users fosters success. | |
| Addressing Resistance | Resistance of clinical staff, in particular physicians, is a major barrier, but can be reduced by addressing their concerns. | |
| Champions | Identifying champions among clinical staff reduces resistance. | |
| Resources | Assigning a sufficient number of staff and other resources is important. | |
The Importance of Leadership: A 2025 study on healthcare service effectiveness reinforces these findings, showing that inspirational leadership style has both direct and significant indirect effects on healthcare service effectiveness, primarily mediated through structured change management and secondarily through new technology adoption . Change process implementation emerged as the most influential pathway, underscoring the 'critical role of structured change management in healthcare transformation' . The study concludes that these findings 'reinforce the strategic importance of leadership development, organizational change readiness, and technological adoption to improve healthcare outcomes' . |
|
6. Physician Resistance: The Elephant in the Room |
Physician resistance is one of the most frequently cited barriers to HIS implementation. It is not a sign of Luddism; it is a reflection of legitimate concerns about workflow disruption, loss of autonomy, and the impact on patient care. |
Why Physicians Resist: |
Workflow disruption: The EHR often forces physicians to work in ways that are not natural or efficient. |
Loss of autonomy: The system imposes structure and constraints on clinical decision-making. |
Time burden: Documentation takes time away from patient care. |
Lack of trust: Early EHRs were often poorly designed and unreliable. |
Status and autonomy: Physicians have historically had significant autonomy in how they practice. The EHR can feel like an intrusion. |
How to Address Resistance: |
Involve physicians early: Clinicians should be part of the selection and design process. |
Identify champions: Peer champions can be persuasive in a way that administrators cannot. |
Address concerns directly: Listen to physician concerns and address them. |
Provide training and support: Training is not a one-time event; it is an ongoing process. |
Show the benefits: Demonstrate how the system can improve care and reduce the documentation burden. |
|
7. The Training Gap |
One of the most common and avoidable implementation failures is inadequate training. The research is clear: training end-users and providing real-time support is critical for success . |
The Problem: Training is often viewed as a cost to be minimized rather than an investment. Staff are given a few hours of training and then expected to use the system competently. When they struggle, they become frustrated and resist. |
The Solution: Effective training is: |
Role-based: Training is tailored to the specific needs of each role. |
Hands-on: Staff practice in a simulated environment (the 'sandbox' described in Chapter 25). |
Ongoing: Training is continuous, not a one-time event. |
Supported: There is real-time support available during go-live and beyond. |
|
8. The Hidden Costs of Implementation |
The visible costs of HIS implementation---software licenses, hardware, training---are only part of the picture. The hidden costs are often far greater. |
Productivity Loss: During the transition period, staff are slower and less efficient. This can have a significant impact on patient throughput and revenue. |
Workforce Burnout: The stress of learning a new system while maintaining patient care can contribute to burnout and staff turnover. |
Workflow Disruption: The implementation process itself can disrupt clinical workflows, leading to delays and errors. |
Customization Costs: Almost no system fits a hospital's workflow perfectly. Customization is almost always necessary, and it is expensive. |
|
9. The System Migration Challenge: A Case Study |
A 2025 case study published in *Discover Health Systems* provides a detailed look at the complexities of migrating from a legacy HIS to a modern, web-based system . The hospital, an educational institution, had been using a monolithic, server-based system for 20 years. The migration was a complete switch, not an incremental upgrade. |
The Challenges: |
Data integrity issues: Ensuring the accuracy and completeness of data during the migration. |
User resistance: Staff were accustomed to the old system and resisted the change. |
Complexities of integrating multiple departments: Coordinating the migration across different clinical and administrative departments. |
The need for problem-solving, decision-making, and adaptability skills: Technical challenges emerged that required immediate, creative solutions. |
The Lessons: |
Careful planning: A detailed, realistic plan is essential. |
Stakeholder engagement: Staff must be involved and their concerns addressed. |
Thorough testing: Testing is not a box to be checked; it is a process that must be done rigorously. |
Continuous support: Support must be available during and after the migration. |
The case study highlights that 'despite the advantages of HIS migration, several limitations were encountered throughout the process,' including 'user resistance and a lack of cooperation' . |
|
10. The Regulatory Gap and the Call for Oversight |
The Cornell University report argues that the lack of regulatory oversight has been a major factor in the implementation struggles of U.S. healthcare IT . |
The Problem: |
- Federal rules did not require real testing of health IT capabilities prior to implementation. |
- There has been no requirement for evaluations to assess whether federal dollars are being used effectively. |
- The system has allowed private equity, venture capital, and Big Tech to profit from health IT without adequate safeguards for patient privacy and security. |
The Call for Action: The authors argue that 'the lessons from 30 years of attempts to set adequate standards for information-sharing in electronic health systems should spur regulators to act quickly and rein in unregulated financial activities in health IT' . |
|
11. The Future: Learning from the Past |
The history of HIS implementation is a sobering one. But it is also a source of valuable lessons. The key insights are: |
Technology is the easy part. The real challenges are human and organizational. |
Leadership matters. Successful implementation requires strong, engaged, and inspirational leadership. |
Engage clinicians early. Resistance is a symptom of being excluded; the solution is inclusion. |
Invest in training. Training is not a cost; it is an investment in success. |
Test thoroughly. Testing is not a box to be checked; it is a process that must be rigorous and continuous. |
Plan for the long haul. Implementation is not a project with a defined end; it is a continuous process of improvement and adaptation. |
Oversight is essential. The public interest requires that health IT be subject to meaningful regulation and evaluation. |
|
Detailed Concluding Summary |
This chapter has provided a comprehensive, plain-English exploration of Implementation Challenges---the human, organizational, and cultural hurdles that make deploying a Hospital Information System one of the most difficult undertakings in healthcare management. We began by framing the problem as fundamentally human, not technical: the real challenges are resistance, misaligned incentives, inadequate training, and cultural inertia. |
We examined the organizational digital divide using a national survey of U.S. hospitals, which found that 81% of hospitals experience at least one minor barrier to exchange and 62% experience a major barrier, with lower-resourced hospitals facing significantly more major barriers . We explored the human cost of flawed systems, drawing on the Cornell University report 'Financialization through Health IT,' which documents how health IT systems have frustrated professionals, contributed to burnout, and enriched private equity and Big Tech without adequate regulatory oversight . |
We presented a detailed U.S. case study: the VA's ongoing EHR modernization struggles, as documented by the VA OIG. The Lovell Federal Health Care Center rollout revealed inadequate documentation, conflicting testing notations, and a lack of functionality with interfaces between VA and the DoD---illustrating the critical importance of thorough testing and clear documentation . |
We synthesized the literature on implementation success factors, identifying management support, clinical staff participation, training, a comprehensive strategy, interdisciplinary groups, addressing resistance, champions, and adequate resources as key elements . We highlighted the importance of inspirational leadership and structured change management in healthcare transformation . We addressed physician resistance as a major barrier and described strategies to address it through involvement, champions, and direct engagement. |
We discussed the hidden costs of implementation, including productivity loss, burnout, workflow disruption, and customization costs. We presented a real-life case study of HIS migration, which underscored the challenges of data integrity issues, user resistance, and departmental integration . Finally, we examined the regulatory gap and the call for oversight, with the Cornell report warning that the lack of safeguards and evaluation requirements has allowed an unregulated industry to monetize patient data and experiment with unproven AI tools . |
|
In conclusion, implementation challenges are not technical problems with technical solutions; they are human problems that require leadership, empathy, engagement, and a realistic understanding that digital transformation in healthcare is a long, iterative, and often messy journey. The history of HIS implementation in the United States is a story of both failure and learning. It is a story that teaches us that the most important element of any HIS implementation is not the software, the hardware, or the data---it is the people who use it, and the culture that supports them. |
cs@easiersoft.com