EHR Implementation, VT Medical Society 2007


Published on

Top 10 Considerations when implementing an ambulatory EHR

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

EHR Implementation, VT Medical Society 2007

  1. 2. Electronic Health Records An opportunity 900 years in the making…. Tim Burdick MD Family Physician, Montpelier Health Center Medical Director, Outpatient EHR, CVMC
  2. 3. Castle Urquhart, Loch Ness The year is 1207. The technology is paper and pen.
  3. 4. The Age of Electronic Records: 1940: Dartmouth College – first computer to be controlled telephonically 1951: UNIVAC – first commercially-available, mass-produced computer (US Census) 1951: LEO – first computer built for private, commercial use (large bakery firm) 1559: ERMA – GE machine purchased by Bank of America 1964: SABRE – IBM computer for American Airlines reservation tracking 1969: COSTAR – Harvard’s Computer Stored Ambulatory Record 1970: PROMIS – Medical Center Hospital of VT computer problem-oriented medical records, drug-drug interactions, and guidelines for diagnosis & treatment of 600 conditions 1973: RMRS – Regenstrief Medical Records System in continuous operation for 34 years, now covering the entire population of Indianapolis Yet 38 yrs later, >60% of charts are still paper…..
  4. 5. EHR Selection So many choices! How do I know which one to pick?
  5. 6. 10. You can please 1% of the doctors some of the time. Ask 10 doctors for their opinions and you will get 12 different answers. Nevertheless, get several physicians involved in the selection process Include primary care & medical and surgical specialties. Improved selection and increased buy-in. Speak with other physicians already using the system, preferably not just the practices mentioned by the vendor as good contacts.
  6. 7. 9. With great power comes great responsibility. Be careful what you ask for – it might come true. A large EHR with infinite flexibility and capacity may come at a cost. Hardware, training, maintenance fees, tech support, provider time. A powerful system which fails implementation is worse than a simple system which is adopted fully. Sometimes less really is more.
  7. 8. 8. I’ll gladly pay you tomorrow for a hamburger today. Vendors make great sales pitches with lots of promises. If it’s only a promise for the future version, it’s vaporware not software. Identify the system requirements that are keystones for your organization. Have the vendor demonstrate the capability with the current software. Verify with a user that the capability is functional.
  8. 9. 7. Read my lips: no new taxes. “It’s covered with a one-time application license. Trust me.” Contracts exist to prevent misunderstandings between parties. EHR contracts are a unique beast. Get somebody qualified to review it. Everything is negotiable. Vendors often have penalties for delays with implementation deadlines. (so they can move on to the next customer with cash). Be sure that delays caused by the vendor itself are exempted!
  9. 10. EHR Implementation The reality is that the implementation, despite the technology of 2007, is still costly and full of unknown monsters lurking beneath the surface. Implementation and interface flow diagram for MPI & ADT.
  10. 11. 6. Don’t buy the extended services... Unless the service is extra training. Training is one of the most expensive parts of implementation. Neglecting training is one of the leading causes of EHR failure. In larger organizations, training will be an ongoing concern. This person is eager for more training.
  11. 12. 5. Pandora’s box is EHR customization. Customization allows all the joy and all the grief of EHRs. Customization allows providers to make the system feel comfortable and familiar. Customization by individual users can corrupt some systems quickly. Customization by HIT can be expensive, slow, and clinically irrelevant. Pandora’s jar (proper translation of pithos ) by Nicolas Regnier c.1626 <ul><li>Ask the questions: </li></ul><ul><li>Which fields can be customized? </li></ul><ul><li>2) Can System Admin limit customization of certain fields? </li></ul><ul><li>3) When a field is customized, is it changed for the user </li></ul><ul><li>or the system? </li></ul><ul><li>4) Who will do the customization in your organization? </li></ul>
  12. 13. 4. It takes a village to raise an electronic health record: HIT department -project manager -software programmers -hardware techies -medical director QA analysts/P4P leaders Billing, coding specialists Office staff -office managers -nurse managers Hospital department liasons -diagnostic imaging -laboratory (micro, path) Financial -CEO, CFO, VPs Physicians -team leader -office super-users
  13. 14. 3. If you ask a barber for help, you get a haircut: HIT staff will build a logical system designed for efficient programming, not for clinical relevance. Don’t leave the EHR process to a group of people who have never seen a patient, never stayed 3 hours after work to finish dictations and prior authorizations. HIT departments may assume all doctors want EHR, can use a computer, are willing and able to teach themselves the new technology. Successful implementation requires finding a physician to sit behind the computer and work alongside the HIT staff during the entire process.
  14. 15. 2. One person’s treasure in is another person’s garbage out. Building the EHR database does not lead to improved clinical care. Quality improvement using the EHR, as always, requires constant re-evaluation, feedback, and willingness to change our practices.
  15. 16. 1. Let us not be afraid to chase after new possibilities.
  16. 17. Resources: Academy of Family Physicians http:// / Medical Economics American Medical Association US Dept Health & Human Services Certification Commission for HIT (CCHIT)