The document discusses key factors for a successful EHR implementation. It emphasizes that the project should be user-driven, not IT-driven, with users rigorously documenting workflows and processes upfront. Users should control aspects like responsibilities, deadlines and interfaces, while IT focuses on computational logic, data, and infrastructure. Failure is common if EHR is used to automate poor existing processes rather than improve workflows. For the project to succeed, users, IT, and vendors must work together from the beginning with a detailed plan focused on usability and meaningful use for clinical staff.

1. Users—Odd Man Out Healthcare IT Strategy [email_address]

2. Why will this EHR implementation be different? Einstein defined insanity as doing the same thing over and over and expecting different results.

3. How high is the risk of failure of this EHR? Plenty if the project is underway and you do not already have a very detailed workflow analysis.

5. What make an EHR successful? Usability Success is not meeting Meaningful Use, Meaningful Use is a byproduct. If EHR is done right, your hospital will define what meaningful use means to them.

6. When you build a new hospital wing… Who decides how many beds it will have, what the clinical staff needs, and what care will be offered? The architect? The builder? Of course not. Why then is EHR any different?

11. What is the work flow issue? The biggest mistake made on EHR projects is to implement EHR to match current work flows. The workflows of every department that touches a medical record should be assessed. Implementing EHR has nothing to do with getting rid of paper. Less paper is a byproduct, not a goal.

12. The atom is split… USERS IT Vendor Internal forces naturally repel individual stakeholders.

13. For EHR to work, the stakeholders must fuse. USERS Vendor IT

16. What should users be doing? Identify all target user groups that currently perform the tasks or processes the EHR will automate. Define the current workflows the users employ to accomplish the tasks or processes Determine what the users do before and after they perform the processes—the interfaces, inputs, & outputs Let the users “play” with the EHR to understand what must be modified