Free EMR Thoughts Newsletter Want to receive the latest EMR Thoughts, Healthcare IT happenings, and EMR Market trends sent straight to your email? Join thousands of healthcare pros who subscribe to EMR Thoughts for FREE!

The EMR Complexities

Carl Bergman offered an interesting comment on this post about “When the EMR Is the Problem.” In his comment he creates a list of ways that an EMR company can cause a problem for the end user:

  • Requirements
  • Research
  • User involvement
  • References
  • Hardware
  • Software
  • Usability
  • Customization
  • Configurations
  • Implementation
  • Testing
  • Training and
  • Support

I found this to be a really intriguing list since it highlights many of the complexities associated with creating and implementing EMR into a medical office. There are a lot of points of failure and each has to be addressed to have a beautifully seamless EMR implementation experience.

With so many points of failure, is it any wonder that we have so many “failed” EMR implementations?

It’s a special EMR company that can handle all of this list well (not to mention doing so at scale).

January 25, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 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 InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

Life After EMR Implementation

I spent a lifetime as an IT developer before I landed my present gig as technical writer in a health IT company. I can tell you from experience, that for many development teams, the implementation date is the biggie that the developers are racing against. And yet, the real fun often starts post-implementation. It’s not that different even with EMR implementation, you’ll be happy to know, at least according to this article at CMIO.net

According to the story, here’s what happened at Hospital Sisters Health System in Wisconsin and Illinois: A couple of months after their CPOE (Computerized Physician Order Entry) and EHR went live, the CIO received a letter with listing 38 issues faced by physicians using the EMR, with an ultimatum that these problems be fixed within two weeks. Half were known issues, and another quarter were training related. But even so, “The installation team was taken aback by the letter, including the physician champion.”

Now, not every IT project is like the one described but here are some lessons worth repeating from the Hospital Sisters example:

  • Prepare, prepare, prepare: That there will be unexpected issues is a given. The problem is not that issues crop up. How prepared you are – knowing how, when, who will handle glitches – is the difference between success and failure.
  • Train Your Users: I honestly get turned off when someone utters “It’s self-explanatory, really,” when it’s related to a software product. Yes, it might be, to you, tech geek, but not everyone was born with the chip embedded in their being. Expect to spend some time training your end users. Well-structured training sessions not only impart the know-how but can also be crucial rapport-building occasions with your buyers.
  • Support Your Users: After the initial euphoria of product launch, using your product might actually bring down the productivity some as users get used to using your product on a regular basis.
November 7, 2011 I Written By

Priya Ramachandran is a Maryland based freelance writer. In a former life, she wrote software code and managed Sarbanes Oxley related audits for IT departments. She now writes about healthcare, science and technology as well as traditional news features.

3 Lessons Learned During EMR Implementation

I love first hand blog accounts of people’s EMR implementations. They teach a lot of great lessons about implementing an EMR. Plus, they remind those of us that knew, but forgot. Here’s one of those accounts and here’s his 3 lessons:
1. Don’t forget to decrease patient volume for at least 6 weeks, even if just going from one EMR to another
2. Be ready to make changes on the fly to your EMR
3. Have great support from your vendor on opening day and beyond

Good advice for EHR implementations!

May 4, 2011 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 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 InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.