Balancing EHR Change vs Train

Posted on May 21, 2013 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I was talking with Heather Haugen from The Breakaway Group (A Xerox company) today and in our discussion she used the word “train”, but I heard the word “change”. I always love a good play on words and so it was interesting for me to consider the difference between change and train in an EHR implementation.

Every EHR implementation I’ve been apart of walks a fine line between users wanting the EHR software to change versus the need for an EHR user to change. One of the most common phrases out of a doctor’s mouth during an EHR implementation is, “Why did the EHR vendor implement that feature like this? Did they not talk to a doctor? This makes no sense.” We’ve dug in previously to the concept of EHR vendors consulting doctors during their EHR development so we won’t go into that further now. Every EHR vendor consults doctors, but no two doctors practice alike. So, it’s normal that every doctor would wonder why certain features are implemented the way they are implemented.

When faced with this issue, the doctor is faced with an important decision with two options. The first option is to work with the EHR vendor and convince them to change how their EHR works. In a large hospital EHR vendor situation, this can be almost impossible. Plus, even if that EHR vendor does like your suggested change it’s going to take months and sometimes years before that change is implemented in the EHR software, tested, and released all the way to you the end user. Yes, these changes can go faster with a SaaS EHR, but it still will likely take months before the change reaches the end user.

In some cases, you can wait for the change to be made before using that EHR feature. However, more often than not a doctor is going to have to train on how the EHR vendor has implemented the feature. This highlights to me why having great EHR training is so important. Sure, many of the things in an EHR will be intuitive, but great EHR training is still always beneficial. EHR software is too complex to just pickup and use. Plus, even if you can use the basic EHR features, good training points out the ways to optimize the EHR workflow.

Most doctors don’t understand why various parts of an EHR workflow can’t be easily changed. They just think change should happen easily. Ironically, the doctor then proceeds to resist any change to how they want to work.