3 Alert Fatigue Suggestions

Many of you will remember my previous post about Patient Alert Fatigue. Managing alert fatigue with patients, doctors, nurses, and other healthcare professionals is a really important subject. Let me offer some suggestions that will hopefully help those creating EMR and other healthcare software deal with alert fatigue.

These three simple suggestions will go along way to ensuring you don’t encounter alert fatigue: Provide Value, Meet Expectations, and Allow Customization.

Provide Value – It seems like a simple concept, but it’s extremely important. The key here is to avoid alerts that don’t provide value. The challenge is that it’s often hard to know which type of alert will provide value and which ones won’t. In the case of patients, you should probably error on the side of missing some alerts that could have provided value. In the case of doctors, you should probably error on the side of a few extra alerts that they can dismiss quickly if not appropriate.

Meet Expectations – Related to this is the impression you give the end user about the alerts. Have you created an expectation that they’ll get every alert? If that’s the case, then you better deliver on that expectation. However, if the end user realizes that the alerts won’t cover everything, then they will not depend on an alert. It’s the alert dependency that causes problems. Once someone expects an alert and you don’t deliver, you’re in deep trouble.

Allow Customization – As discussed above, each person has a different tolerance for alerts. So, allowing them to customize their alert preference is key. Plus, the next generation of digital natives are keenly aware of adjusting their alert preferences. This means that the need to be able to customize alert preferences is only going to grow. Plus, each institution has its own alert preferences as well. Over time I expect that healthcare’s alert preferences will become really sophisticated.

There’s a lot of art involved in managing alert fatigue. However, if you follow these three suggestions, you will go a long way to mastering the alert fatigue art.

About the author

John Lynn

John Lynn is the Founder of HealthcareScene.com, a network of leading Healthcare IT resources. The flagship blog, Healthcare IT Today, contains over 13,000 articles with over half of the articles written by John. These EMR and Healthcare IT related articles have been viewed over 20 million times.

John manages Healthcare IT Central, the leading career Health IT job board. He also organizes the first of its kind conference and community focused on healthcare marketing, Healthcare and IT Marketing Conference, and a healthcare IT conference, EXPO.health, focused on practical healthcare IT innovation. John is an advisor to multiple healthcare IT companies. John is highly involved in social media, and in addition to his blogs can be found on Twitter: @techguy.

3 Comments

  • More tips. The alert should be:
    1. Free of clutter.
    2. Easy to see what the interaction or problem is.
    3. Have the same exact format every time.
    You’d think this would be obvious…

  • At First Databank (FDB), we have been working to minimize alert fatigue for our customers for several years now. We have developed a Web-based solution, FDB AlertSpace, which allows for the customization you suggest here in EHR systems using FDB drug knowledge. End user institutions can customize drug-drug, dosing, drug-allergy interactions and more drug domain data as they see fit at their organization and based on their clinician’s preference. We have also have worked with the ONC on a DDIM (drug interaction) subset which will provide a “starter set” of the most important and relevant alert customizations. Happy to provide more information for interested parties.

Click here to post a comment
   

Categories