Home
BYTE Newsletter
Keep up with all the BYTE News and Reviews

Subscribe
Paul Cerrato

Paul Cerrato

Editor, InformationWeek Healthcare
Editor, InformationWeek Healthcare

Medication Alert Fatigue Is Curable

Comments | Paul Cerrato, InformationWeek | September 06, 2012 10:14 AM


Medication alerts within EHRs can save lives, but as many clinicians are quick to point out, these alerts can also prove to be a major headache. The alerts sometimes note potential adverse effects that even first year medical students would know. While there's no perfect system, we can do better.

Given that between 33% and 96% of medical alerts are ignored, there's little doubt that providers need help in this regard. A good place to start is with a core set of critically important drug/drug interactions (DDIs) that everyone in your healthcare system needs to watch.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

With that in mind, researcher Shobba Phansalkar, from Brigham and Women's Hospital in Boston, along with colleagues from Harvard, Rand Corp., and UCLA, did an exhaustive review of medication databases to compile a must-have list of severe DDIs. They came up with 15 essential interactions that all your clinicians should probably have access to in a clinical decision support system (CDSS). The list, published in the latest issue of Journal of Medical Informatics Association, was derived from Partners Healthcare System Medication database; commercial databases, including Micromedex, First Data Bank, and Drugs.com; and from academic research papers written by experts in the field.

Once you have a core list in place, the next logical step is to expand it with less critical but useful alerts, and then decide how to alert physicians to the entire data set. Typically a CDSS prioritizes medical alerts into three tiers. The most serious, life threatening DDIs, are set up as a hard stops in the system. As Phansalkar explains in the JAMIA paper, that requires the med order be cancelled or that one of the two interacting drugs be discontinued. In tier two, clinicians would have to give a reason for overriding an alert for a moderately serious DDI. Tier 3 is reserved for non-interruptive yet useful alerts.

Deciding where to place a medical alert in a three-tier system is only one of the related issues. IT managers and clinical leaders have to join forces to decide which type of clinician needs to see which alerts. It doesn't make sense for a physician to see an alert that's only relevant for a pharmacist, for instance. In other words, we need role-specific drug alerts.

That point was driven home in a study published in April issue of International Journal of Medical Informatics. V.A. and Regenstrief healthcare researchers observed 30 physicians, nurse practitioners, and pharmacists entering and processing a total of 320 outpatient prescription orders. They found that prescribing clinicians often were confused about why the EHR delivered alerts and determined that the electronic warnings tended to be oriented more toward pharmacists than those who write prescriptions.

The researchers also found that prescribers spent too much time retrieving data in response to an alert, suggesting that EHR systems should automatically deliver relevant information from patient records, such as test results and documentation about adverse reactions to certain medications. "Prescribers wanted more patient-specific alerts, and were particularly appreciative of alerts triggered by a patient's laboratory values," said the article.

Because the medication alert system at Regenstrief is home grown and more readily customizable, it allows alerts to be tweaked based on lab data from individual patients. In a recent interview published in American Medical News, Jon D. Duke, MD, assistant professor at the Indiana University School of Medicine, talks about Regenstrief's Context-Aware Drug-to-Drug Interaction (CADDI) alert system, which is capable of such specificity. "... if there’s an interaction between a medication like an ACE inhibitor and a potassium supplement, which is a common interaction associated with hyperkalemia, the system goes and checks the [patient’s] last potassium level and is able to then increase or decrease the intensity of the alert based on whether there was any abnormal baseline levels."

It's likely clinicians will keep complaining about alert fatigue for some time to come. But as medical informatics specialists get better at designing medication databases, we'll eventually find the right balance between patient safety and clinician convenience.

See the future of business technology at Interop New York Oct. 1-5. It's the best place to learn about next-generation technologies including cloud computing, BYOD, big data, and virtualization. End of Summer Discounts end Sept. 5. Save up to $800 on Interop New York Conference Passes with code WEYLBQNY07.



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

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE 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. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events