{'fraction_non_alphanumeric': 0.016865079365079364, 'fraction_numerical': 0.007936507936507936, 'mean_word_length': 5.509677419354839, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Case Study: Reducing Interruption Fatigue through Improved Alarm Support.

At a clinical alarms summit convened in 2011, hospitals and industry were challenged to join forces in reaching, by 2017, the goal of no patients being harmed by adverse alarm events. Although substantial advances have been made in meeting this challenge, clinicians have reached a roadblock when it comes to managing clinical alarms. This impasse necessitates the need to shift focus to a broader process perspective that includes clinical workflow. According to a substantial body of knowledge, clinical alarms require modification and management. However, the secondary alarm notification stopgaps put in place by hospitals have frequently exacerbated the problem, causing duplication of alarms, including nonactionable and nuisance alarms. The challenge in communicating only essential alarm and alert information to the proper person or care-team is a challenge that recent advances in clinical technology could work to resolve.