The User's Role in EHR

2,533 views
2,427 views

Published on

Users are the odd man out compared to IT and the EHR vendor. How do you regain control?

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,533
On SlideShare
0
From Embeds
0
Number of Embeds
26
Actions
Shares
0
Downloads
84
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

The User's Role in EHR

  1. 1. Users—Odd Man Out Healthcare IT Strategy [email_address]
  2. 2. Why will this EHR implementation be different? Einstein defined insanity as doing the same thing over and over and expecting different results.
  3. 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.
  4. 4. What are the odds of failure? <ul><li>Fifty percent of all IT projects costing more than $15 million dollars fail. </li></ul><ul><li>Failure is defined as one or more of: </li></ul><ul><ul><li>Over budget </li></ul></ul><ul><ul><li>Late </li></ul></ul><ul><ul><li>Not accepted by users </li></ul></ul><ul><li>60-70% of hospital EHR projects fail (NEJM) </li></ul><ul><li>EHRs do not fix poor processes, they automate them—that is why productivity drops </li></ul>
  5. 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. 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?
  7. 7. Whose project is it currently? <ul><li>It is an “IT” project </li></ul><ul><li>Demand to see the project plan: </li></ul><ul><li>Who wrote the plan: </li></ul><ul><ul><li>IT </li></ul></ul><ul><ul><li>IT & the vendor </li></ul></ul><ul><li>Assess the major tasks. The vast majority of tasks will be: </li></ul><ul><ul><li>Build </li></ul></ul><ul><ul><li>Rollout </li></ul></ul>
  8. 8. For this EHR to work… <ul><li>Here are some good rules of thumb. </li></ul><ul><ul><li>The number of USER tasks should be greater than or equal to the tasks of the Vendor + IT </li></ul></ul><ul><ul><li>USER tasks should start before the build </li></ul></ul><ul><ul><li>IT will not simply hand it over the management of the project, especially if they are paying for most or all of the effort. </li></ul></ul>
  9. 9. What are the USER tasks? <ul><li>The user tasks define what IT and the vendors should build. The major user tasks are: </li></ul><ul><li>Oversight </li></ul><ul><li>Communication </li></ul><ul><li>Processes </li></ul><ul><ul><li>Process definition </li></ul></ul><ul><ul><li>Process unification—one way to do each thing </li></ul></ul><ul><ul><li>Process improvement </li></ul></ul><ul><li>Change Management </li></ul><ul><li>Training </li></ul>
  10. 10. Why are you installing EHR? <ul><li>The project is underway for the users, not IT. </li></ul><ul><li>EHR’s goal is to improve many aspects of operations. </li></ul><ul><ul><li>Productivity </li></ul></ul><ul><ul><li>Care </li></ul></ul><ul><ul><li>Safety </li></ul></ul><ul><ul><li>Increased revenues & access </li></ul></ul><ul><ul><li>Reduced errors & cost </li></ul></ul><ul><li>IT does not need an EHR—users do. </li></ul>
  11. 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. 12. The atom is split… USERS IT Vendor Internal forces naturally repel individual stakeholders.
  13. 13. For EHR to work, the stakeholders must fuse. USERS Vendor IT
  14. 14. What is the Users’ Role? <ul><li>Rigorously document the use context of the EHR </li></ul><ul><li>Who will use it </li></ul><ul><ul><li>How often </li></ul></ul><ul><ul><li>Why </li></ul></ul><ul><ul><li>How </li></ul></ul><ul><li>How will each user interact? There are hundreds of interactions. </li></ul>
  15. 15. Before users design anything… <ul><li>Determine what could go wrong or went wrong last time </li></ul><ul><ul><li>Navigation—I can’t figure out how to get it to do what I need it to do </li></ul></ul><ul><ul><li>Workflow—it takes too long to do this </li></ul></ul><ul><ul><li>Communication—it takes me away from my patients </li></ul></ul><ul><ul><li>Wasteful and repetitive </li></ul></ul><ul><ul><li>Incompetent—it does not mimic how I work </li></ul></ul><ul><li>In short, it was not usable. User involvement is your “usability insurance”. </li></ul>
  16. 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
  17. 17. What must users overcome? <ul><li>Inadequate support for cross-functional processes </li></ul><ul><li>Mismatch of EHR functionality and user requirements </li></ul><ul><li>Limited ability to change processes due to inflexibility of EHR </li></ul><ul><li>Lack of visibility of processes </li></ul><ul><li>Inability to support clinical and patient interaction </li></ul><ul><li>Lack of understanding of specialized functionality </li></ul><ul><li>Inability to integrate with other user-specific systems </li></ul>
  18. 18. Processes versus workflows <ul><li>Business Process - A set of one or more linked procedures or activities which collectively realize a business objective or policy goal. </li></ul><ul><li>If the process does not support a business objective, kill it. Do NOT automate it. </li></ul><ul><li>Workflow - The automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules. </li></ul>
  19. 19. What must users control? <ul><li>Users Retain Control of: </li></ul><ul><li>Assignment of Responsibility </li></ul><ul><li>Groups, Roles, Skills </li></ul><ul><li>Deadlines </li></ul><ul><li>Alerts, Reminders, Escalations </li></ul><ul><li>Order of Tasks </li></ul><ul><li>Addition of Manual Tasks </li></ul><ul><li>User Interfaces </li></ul>
  20. 20. What must IT control? <ul><li>IT Retains Control of: </li></ul><ul><li>Computational Logic </li></ul><ul><li>Data Representations </li></ul><ul><li>Scalability / Performance </li></ul><ul><li>Interoperability </li></ul><ul><li>Master Data Management </li></ul>
  21. 21. Users Retain Control of: <ul><li>Users Retain Control of </li></ul><ul><li>Assignment of Responsibility </li></ul><ul><li>Groups, Roles, Skills </li></ul><ul><li>Deadlines </li></ul><ul><li>Alerts, Reminders, Escalations </li></ul><ul><li>Order of Tasks </li></ul><ul><li>Addition of Manual Tasks </li></ul><ul><li>User Interface </li></ul>Depends strongly on who is in each organization. Changes on daily basis Organizational Culture Optimize for each team Respond to market or legislation Related to Training, Experience Who? When?
  22. 22. IT Retains Control of: <ul><li>IT Retains Control of: </li></ul><ul><li>Computational Logic </li></ul><ul><li>Data Representations </li></ul><ul><li>Scalability / Performance </li></ul><ul><li>Interoperability </li></ul><ul><li>Master Data Management </li></ul>Requires expensive technical capabilities Very low or no dependence upon the organizational culture Knowledge of infrastructure

×