Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

Safety Issues Remain Long After EMR Rollout

Posted on June 24, 2014 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 years of industry experience. Zieger formerly served as editor-in-chief of FierceHealthcare.com and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. Contact her at @ziegerhealth on Twitter or visit her site at Zieger Healthcare.

The following is a bit depressing, but shouldn’t come as a surprise. A new study published in the Journal of the American Medical Informatics Association has concluded that patient safety issues relate to EMR rollouts continue long after the EMR has been implemented, according to a report in iHealthBeat.

Now, it’s worth noting that the study focused solely on the Veterans Health Administration’s EMR, which doubtless has quirks of its own. That being said, the analysis is worth a look.

To do the study, researchers used the Veterans Health Administration’s Informatics Patient Safety Office, which has tracked EMR safety issues since the VA’s EMR was implemented in 1999.  Researchers chose 100 closed patient safety investigations related to the EMR that took place between August 2009 and May 2013, which covered 344 incidents.

Researchers analyzed not only safety problems related to EMR technology, but also human operational factors such as workflow demands, organizational guidelines and user behavior, according to a BMJ release.

After reviewing the data, researchers found that 74 events related to safety problems with EMR technology, including false alarms, computer glitches and system failures. They also discovered problems with “hidden dependencies,” situation which a change in one part of the EMR system inadvertently changed important aspects in another part of the system.

The data also suggested that 25 other events were related to the unsafe use of technology, including mistakes in interpreting screens or human input errors.

All told, 70% of the investigations had found at least two reasons for each problem.

Commonly found safety issues included data transmission between different parts of the EMR system, problems related to software upgrades and EMR information display issues (the most commonly identified  problem), iHealthBeat noted.

After digging into this data, researchers recommended that healthcare organizations should build “a robust infrastructure to monitor and learn from” EMRs, because EMR-related safety concerns have complicated social and technical origins. They stressed that this infrastructure is valuable not only for providers with newly installed EMRs, but also for those with EMRs said that in place for a while, as both convey significant safety concerns.

They concede, however, that building such an infrastructure could prove quite difficult at this time, with organizations struggling with meaningful use compliance and the transition from ICD-9 to ICD-10.

However, the takeaway from this is that providers probably need to put safety monitoring — for both human and technical factors — closer to the top of their list of concerns. It stands to reason that both newly-installed and mature EMR implementations should face points of failure such as those described in the study, and they should not be ignored. (In the meantime, here’s one research effort going on which might be worth exploring.)

Doctor Describes 15+- Year EMR Integration Project

Posted on May 11, 2012 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 years of industry experience. Zieger formerly served as editor-in-chief of FierceHealthcare.com and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. Contact her at @ziegerhealth on Twitter or visit her site at Zieger Healthcare.

Wouldn’t it be great if you rolled your EMR and, bam, all of the problems you hoped to solve were solved, just like that?  Sure, but in most cases the technical rollout will do little to solve workflow problems unless you have them analyzed in advance, according to one doctor who’s taken part in a long, slow rollout. Here’s a quick overview of his organization’s progress: see what you think.

Going live is a far cry from having truly adopted an EMR,  and getting to adoption is a very long, drawn-out process, said Dr. Fred M. Kusumoto, who spoke at a recent meeting of the Heart Rhythm Society.

Dr. Kusumoto, who’s with the Mayo Clinic Jacksonville Electrophysiology and Pacing Services, conceded that EMRs can help smooth communication between systems. The thing is, he noted, integrating systems won’t happen over night. After all, the workflow of doing integration is very complex, so much so that years hardly suffice.  His organization began serving as “guinea pig” for its EMR vendor in 1996 and will as of 2013, will have one database using structured data, he said.

So, the million-dollar question is this: Has all of this effort been worthwhile?  Dr. Kusumoto actually didn’t say, if the CMIO article I reviewed is accurate.  Interesting. But he’s clearly learned a great deal, regardless of whether his rollout works out for Mayo. Here’s some of his suggestions on how to improve returns from your maturing EMR:

*  Make sure all stakeholders are involved as the EMR migration, including administrators and IT staffers.

* Bear in mind that EMR rollouts are at their most flexible in the first few years, so don’t miss your chance to get involved early.

* EMR implementations (typically) involve a scanning phase where the institution captures written records and plans for turning the records into structured data. Make sure you leave enough time to do this right.