October 18, 2009
Roadblocks to EMR Implementations
Written by: JohnSign up to receive all the latest EMR, EHR, Simulus, and Healthcare IT Updates.
I’ve decided that on Sunday’s I’ll just post a few interesting questions and give people the opportunity to share their experience and/or expertise. Hopefully we’ll get a lot of participation and we can all learn from each other in the process. No doubt many of my readers are more knowledgeable and experienced than me.
Today, let’s talk about the roadblocks that people have faced or are facing in their EMR implementations. If you’ve already implemented an EMR, let’s hear the roadblocks and challenges that you faced when implementing and how you might have overcome those challenges. If you’re still deciding whether to implement an EMR, let’s hear what reasons are blocking you from implementing an EMR. EMR vendors and consultants can share the challenges they see from a high level.
Related Articles6 responses to "Roadblocks to EMR Implementations"
Leave a Reply
- » Recent articles
- $3 Billion Ambulatory EHR Market
- Reshuffling of Ambulatory Physicians Favors Large EHR Vendors
- Drummond Group and CCHIT Become First Official ONC EHR Certifying Bodies
- CCHIT Certified EHR Becoming ARRA Certified EHR
- Crazy Legislative Process
- One Way Of Measuring Meaningful Use Productivity Loss
- EMR Billing Matters
- EMR vs EHR
- EMR Vendor Recommendations
- Imagine an EMR without Billing
- Drugs for Sale - The Drug Company
- » Archive Calendar
-
Jobs by SimplyHired
John, as an IT infrastructure vendor (UPS, cooling, racks, power strips) I have encountered countless ambulatory offices that deployed an EMR but severely neglected the hardware side. I’ve seen servers and storage damaged by electrical surges and constantly rebooting routers because of unreliable utility power.
But the most common infrastructure problem related to EMR implementation that I’ve experienced is heat density. A network closet to support wireless, database computing and data storage produces a lot of heat. The building A/C is off at night but the IT network is always running (and eventually, literally, burning up). I’ve seen many box fans in open-door thresholds, which is a dangerous solution when it comes to physical security of data. IT implementation shouldn’t be a doctor’s concern; consultants and EMR vendors need to explain the necessity of a properly designed IT network (regardless of the sticker shock which may jeopardize the EMR sale).
Dan,
I agree with you. I’ve seen and heard about many of the same things. I wonder if I shouldn’t add something about the IT support to the idea I just posted about called the “Provider Bill of Rights.”
In my experience as a trainer/EMR support person, clinicians who are reluctant to learn and use an EMR can be a roadblock to a successful implementation – even if clinic management is behind it 100%.
The first thing the trainer can do is acknowledge to the reluctant user that the sytem is, in fact, difficult to learn and use, and they are not alone in their frustration.
Next, the trainer can work with the individual to find system options that work best forthem — often the EMR software has different methods of accomplishing the same task. The trainer can have the person practice the task using test patients, and write up “cheat sheets” for future reference.
Eventually, they will come around. Sometimes they even begin to like using the system, although they might not admit it!
A fine point Eunice. I’ve seen it happen a few times where the clinician who was the biggest road block learned the system and became one of the people who would help others. However, it does take some time and it’s not always so nice.
Please read the following article. It has some very interesting insights into the state of EMR.
http://www.washingtonpost.com/wp-dyn/content/article/2009/10/24/AR2009102400967_pf.html
Thanks Sekharudu. I’d been given that article and it’s definitely on my list of things to read.