Commentary

Paul Cerrato
Editor, InformationWeek Healthcare  

EHR Worst Practices

Just a partial list of EHR snafus emphasizes the need for a better system of tracking errors.

We need the equivalent of the National Transportation Safety Board to monitor EHRs, according to Dean Sittig, PhD, a member of the faculty at the School of Biomedical Informatics, the University of Texas Health Science Center at Houston (UTHealth). After listening to his presentation at this week's American Medical Informatics Association (AMIA) Scientific Sessions, I can see the wisdom of that suggestion.

NTSB was launched in 1926, when the automotive industry was in its infancy and few people thought about all the fatalities that lie ahead. Over the years, it has been responsible for insisting on speed limits, seatbelts, airbags, and a host of other invaluable safety measures.


More Healthcare Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

An NTSB-like organization for EHRs would at the very least provide a reporting mechanism to keep track of incidents and life-threatening consequences of misusing e-records. More importantly, it could police vendors and healthcare providers who repeatedly ignore these dangers.

During his presentation, Sittig was quick to point at that errors can occur at any stage in the life cycle of an EHR, during design and development, implementation, or post-installment evaluation. He went on to describe several areas in which one can expect to see problems, which are not limited to computer glitches. Many problems are due to the way humans interact with machines. But unless we have a NTSB-like system to track all the errors and categorize them, EHR designers and end users will have a much harder time systematically fixing them.

[ For more background on e-prescribing tools, see 6 E-Prescribing Vendors To Watch. ]

And statistics suggest we are doing a poor job of tracking these snafus without some sort of government or industry oversight. Over the last 18 years, for instance, the FDA has received reports of only 120 EHR-specific errors. There is no way that number can be accurate; it only tells us that such errors are grossly underreported.

One problem that needs to be tracked is missing or inaccurate clinical content within an EHR. Probably the most notorious mistake that Sittig mentioned occurred because of a mapping error in England's National Health Service. It resulted in patients who were supposed to get a prescription for Zyban, a medication to help them stop smoking, being prescribed Viagra instead.

Other reports suggest that even when an EHR churns out correct information, it's not always reaching the clinicians who need to know, or they are simply not acting on the information. In one study, of the 1,163 lab results that were sent out as electronic alerts, about one of every 10 were ignored by physicians. Worse yet, in a separate investigation, 7-8% of abnormal imaging results were never followed up by physicians.

Another pain point for IT managers and clinicians: EHR-generated alerts sometimes have unintended consequences. An experiment done at the University of Pennsylvania showed that a hard-stop alert can reduce the likelihood of ordering dangerous meds. But the investigators also found that in some cases, these roadblocks actually resulted in dangerous delays in ordering meds for some patients who really needed them.

These are only a few of the snafus one can expect to see when computers and people interact, which is all the more reason for IT departments to thoroughly measure and monitor the performance of their e-record systems. Our EHRs need seatbelts, speed limits, airbags, and a variety of still unimagined features if we ever hope to safely navigate this new highway.

As IT pervades every aspect of healthcare, complying with federal regulations on patient privacy and security is becoming increasingly difficult. Our webcast will help attendees navigate the latest HIPAA privacy and security requirements, proposals, and penalties and provide insight into what healthcare providers need to do to be compliant. It happens Oct. 27. Register now. (Free registration required.)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links