“I Never Would Have Caught That Before”: Pharmacist Perceptions of Using Clinical Decision Support for Antimicrobial Stewardship in the United States

2018 ◽  
Vol 28 (5) ◽  
pp. 745-755 ◽  
Author(s):  
Christopher A. Giuliano ◽  
Juliann Binienda ◽  
Pramodini B. Kale-Pradhan ◽  
Mohamad G. Fakih
2020 ◽  
Vol 12 (1) ◽  
Author(s):  
Lauren Shrader ◽  
Stuart Myerburg ◽  
Eric Larson

Context: In the United States, immunization recommendations and their associated schedules are developed by the Advisory Committee on Immunization Practices (ACIP). To assist with the translation process and better harmonize the outcomes of existing clinical decision support tools, the Centers for Disease Control and Prevention (CDC) created clinical decision support for immunization (CDSi) resources for each set of ACIP recommendations. These resources are continually updated and refined as new vaccine recommendations and clarifications become available and will be available to health information systems for a coronavirus disease 2019 (COVID-19) vaccine when one becomes available for use in the United States. Objectives: To assess awareness of CDSi resources, whether CDSi resources were being used by immunization-related health information systems, and perceived impact of CDSi resources on stakeholders’ work.Design: Online surveys conducted from 2015–2019 including qualitative and quantitative questions.Participants: The main and technical contact from each of the 64 CDC-funded immunization information system (IIS) awardees, IIS vendors, and electronic health record vendors. Results: Awareness of at least one resource increased from 75% of respondents in 2015 to 100% in 2019. Use of at least one CDSi resource also increased from 47% in 2015 to 78% in 2019. About 80% or more of users of CDSi are somewhat or very highly satisfied with the resources and report a somewhat or very positive impact from using them. Conclusion: As awareness and use of CDSi resources increases, the likelihood that patients receive recommended immunizations at the right time will also increase. Rapid and precise integration of vaccine recommendations into health information systems will be particularly important when a COVID-19 vaccine becomes available to help facilitate vaccine implementation.


2017 ◽  
Vol 25 (5) ◽  
pp. 496-506 ◽  
Author(s):  
Adam Wright ◽  
Angela Ai ◽  
Joan Ash ◽  
Jane F Wiesen ◽  
Thu-Trang T Hickman ◽  
...  

Abstract Objective To develop an empirically derived taxonomy of clinical decision support (CDS) alert malfunctions. Materials and Methods We identified CDS alert malfunctions using a mix of qualitative and quantitative methods: (1) site visits with interviews of chief medical informatics officers, CDS developers, clinical leaders, and CDS end users; (2) surveys of chief medical informatics officers; (3) analysis of CDS firing rates; and (4) analysis of CDS overrides. We used a multi-round, manual, iterative card sort to develop a multi-axial, empirically derived taxonomy of CDS malfunctions. Results We analyzed 68 CDS alert malfunction cases from 14 sites across the United States with diverse electronic health record systems. Four primary axes emerged: the cause of the malfunction, its mode of discovery, when it began, and how it affected rule firing. Build errors, conceptualization errors, and the introduction of new concepts or terms were the most frequent causes. User reports were the predominant mode of discovery. Many malfunctions within our database caused rules to fire for patients for whom they should not have (false positives), but the reverse (false negatives) was also common. Discussion Across organizations and electronic health record systems, similar malfunction patterns recurred. Challenges included updates to code sets and values, software issues at the time of system upgrades, difficulties with migration of CDS content between computing environments, and the challenge of correctly conceptualizing and building CDS. Conclusion CDS alert malfunctions are frequent. The empirically derived taxonomy formalizes the common recurring issues that cause these malfunctions, helping CDS developers anticipate and prevent CDS malfunctions before they occur or detect and resolve them expediently.


2021 ◽  
pp. 74-79
Author(s):  
Caitlyn Allen

In the United States, almost 1 million patients with sepsis are admitted to hospitals annually, and the cost of managing sepsis admissions is higher than any other disease state.1 Early identification and treatment are critical for survival, though both are notoriously difficult as symptoms are often nonspecific. Four years ago, WellSpan Health asked, “What if there were a way to provide real-time, meaningful clinical decision support to bedside providers to identify sepsis sooner and start lifesaving treatment?” Meet Margaret D’Ercole, Patricia Everett, Dana Gaultney, Angela Mays, Brenna Simcoe, and Cynthia Yascavage, who share how their Central Alert Team decreased mortality rates, increased bundle compliance, and proved there is a better way.


2018 ◽  
Vol 09 (02) ◽  
pp. 248-260 ◽  
Author(s):  
Mustafa Ozkaynak ◽  
Danny Wu ◽  
Katia Hannah ◽  
Peter Dayan ◽  
Rakesh Mistry

Background Clinical decision support (CDS) embedded into the electronic health record (EHR), is a potentially powerful tool for institution of antimicrobial stewardship programs (ASPs) in emergency departments (EDs). However, design and implementation of CDS systems should be informed by the existing workflow to ensure its congruence with ED practice, which is characterized by erratic workflow, intermittent computer interactions, and variable timing of antibiotic prescription. Objective This article aims to characterize ED workflow for four provider types, to guide future design and implementation of an ED-based ASP using the EHR. Methods Workflow was systematically examined in a single, tertiary-care academic children's hospital ED. Clinicians with four roles (attending, nurse practitioner, physician assistant, resident) were observed over a 3-month period using a tablet computer-based data collection tool. Structural observations were recorded by investigators, and classified using a predetermined set of activities. Clinicians were queried regarding timing of diagnosis and disposition decision points. Results A total of 23 providers were observed for 90 hours. Sixty-four different activities were captured for a total of 6,060 times. Among these activities, nine were conducted at different frequency or time allocation across four roles. Moreover, we identified differences in sequential patterns across roles. Decision points, whereby clinicians then proceeded with treatment, were identified 127 times. The most common decision points identified were: (1) after/during examining or talking to patient or relative; (2) after talking to a specialist; and (3) after diagnostic test/image was resulted and discussed with patient/family. Conclusion The design and implementation of CDS for ASP should support clinicians in various provider roles, despite having different workflow patterns. The clinicians make their decisions about treatment at different points of overall care delivery practice; likewise, the CDS should also support decisions at different points of care.


2011 ◽  
Vol 02 (03) ◽  
pp. 284-303 ◽  
Author(s):  
A. Wright ◽  
M. Burton ◽  
G. Fraser ◽  
M. Krall ◽  
S. Maviglia ◽  
...  

SummaryBackground: Computer-based clinical decision support (CDS) systems have been shown to improve quality of care and workflow efficiency, and health care reform legislation relies on electronic health records and CDS systems to improve the cost and quality of health care in the United States; however, the heterogeneity of CDS content and infrastructure of CDS systems across sites is not well known.Objective: We aimed to determine the scope of CDS content in diabetes care at six sites, assess the capabilities of CDS in use at these sites, characterize the scope of CDS infrastructure at these sites, and determine how the sites use CDS beyond individual patient care in order to identify characteristics of CDS systems and content that have been successfully implemented in diabetes care.Methods: We compared CDS systems in six collaborating sites of the Clinical Decision Support Consortium. We gathered CDS content on care for patients with diabetes mellitus and surveyed institutions on characteristics of their site, the infrastructure of CDS at these sites, and the capabilities of CDS at these sites.Results: The approach to CDS and the characteristics of CDS content varied among sites. Some commonalities included providing customizability by role or user, applying sophisticated exclusion criteria, and using CDS automatically at the time of decision-making. Many messages were actionable recommendations. Most sites had monitoring rules (e.g. assessing hemoglobin A1c), but few had rules to diagnose diabetes or suggest specific treatments. All sites had numerous prevention rules including reminders for providing eye examinations, influenza vaccines, lipid screenings, nephropathy screenings, and pneumococcal vaccines.Conclusion: Computer-based CDS systems vary widely across sites in content and scope, but both institution-created and purchased systems had many similar features and functionality, such as integration of alerts and reminders into the decision-making workflow of the provider and providing messages that are actionable recommendations.


2019 ◽  
Vol 6 (Supplement_2) ◽  
pp. S467-S468
Author(s):  
Mariah Powell ◽  
Michael Gierlach ◽  
Sandra L Werner ◽  
David S Bar-Shain ◽  
Ann Avery

Abstract Background In 2016, MetroHealth System (MHS) launched the FOCUS (Frontlines of Communities in the United States) project to routinize HIV testing in the emergency department (ED). Before 2016, clinical decision support (CDS) for HIV testing was not in place, nor was there a policy to support the importance of opt-out, nontargeted screening. The purpose of this study was to outline the progress of HIV testing after the integration of CDS, as well as describe the implementation challenges, and how certain events impacted HIV testing. Methods HIV testing data from MHS EDs were collected from October 1, 2015 to March 31, 2019 and graphed into a run chart. The dataset was mapped with the following events: project start date, ED testing begins (without CDS), CDS implementation, the staffing of the ED Testing Coordinator (EDTC), and optimization of CDS (Figure 1). To determine whether observed variation in the dataset is due to random or special cause variation, these run chart rules were applied: Run, Shift (Figure 2), and Trend. Results There were 42 data points and 4 runs. With 42 points, the lower limit of runs was 16 and the upper limit of runs was 28. This signals that one or more special cause variations were present. A total of three distinct shifts were observed indicating special cause variation. The run chart did not include any downward or upward trends. Testing increased as much as 3971% (7 tests in October 2015 vs. 285 tests in March 2018). Conclusion HIV testing increased from 7 tests to 86 tests (Shift 1). This coincided with establishment of an ED testing policy in April 2016. Testing increased to 266 tests in October 2016 (Shift 2). This directly related to implementation of CDS in the ED. December 2017 displayed the lowest testing with 117 tests. This was due to lack of policy awareness, and to the rarely-visited location of the HIV screening tool during the triage process. Staff was re-educated and the HIV screening tool was moved to a more visible location. This resulted in 227 tests in February 2018, and was followed by the highest testing month with 285 tests (Shift 3). Continued challenges prohibit sustained upward trends in ED testing. A control chart may be the appropriate next step to identify new control limits Disclosures All authors: No reported disclosures.


2009 ◽  
Vol 42 (12) ◽  
pp. 354-358
Author(s):  
Karin Thursky ◽  
Marion Robertson ◽  
Susan Luu ◽  
James Black ◽  
Michael Richards ◽  
...  

Author(s):  
Kathryn Dzintars ◽  
Valeria M Fabre ◽  
Edina Avdic ◽  
Janessa Smith ◽  
Victoria Adams-Sommer ◽  
...  

Abstract Disclaimer In an effort to expedite the publication of articles related to the COVID-19 pandemic, AJHP is posting these manuscripts online as soon as possible after acceptance. Accepted manuscripts have been peer-reviewed and copyedited, but are posted online before technical formatting and author proofing. These manuscripts are not the final version of record and will be replaced with the final article (formatted per AJHP style and proofed by the authors) at a later time. Purpose The purpose of this manuscript is to describe our experience developing an antimicrobial stewardship (AS) module as a clinical decision support tool in the Epic electronic health record (EHR). Summary Clinical decision support systems within the EHR can be used to decrease use of broad-spectrum antibiotics, improve antibiotic selection and dosing, decrease adverse effects, reduce antibiotic costs, and reduce the development of antibiotic resistance. The Johns Hopkins Hospital constructed an AS module within Epic. Customized stewardship alerts and scoring systems were developed to triage patients requiring stewardship intervention. This required a multidisciplinary approach with a team comprising AS physicians and pharmacists and Epic information technology personnel, with assistance from clinical microbiology and infection control when necessary. In addition, an intervention database was enhanced with stewardship-specific interventions, and workbench reports were developed specific to AS needs. We herein review the process, advantages, and challenges associated with the development of the Epic AS module. Conclusion Customizing an AS module in an EHR requires significant time and expertise in antimicrobials; however, AS modules have the potential to improve the efficiency of AS personnel in performing daily stewardship activities and reporting through a single system.


Sign in / Sign up

Export Citation Format

Share Document