search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
infection control & hospital epidemiology july 2017, vol. 38, no. 7 concise communication


A Simple Microsoft Excel Method to Predict Antibiotic Outbreaks and Underutilization


Cristina Miglis, PharmD;1,2 Nathaniel J. Rhodes, PharmD, MSc;1,2 Sean N. Avedissian, PharmD;1,2 Teresa R. Zembower, MD, MPH;3 Michael Postelnick, RPh;2 Richard G. Wunderink, MD;4 Sarah H. Sutton, MD;3 Marc H. Scheetz, PharmD, MSc1,2


Benchmarking strategies are needed to promote the appropriate use of antibiotics. We have adapted a simple regressive method in Microsoft Excel that is easily implementable and creates predictive indices. This method trends consumption over time and can identify periods of over- and underuse at the hospital level.


Infect Control Hosp Epidemiol 2017;38:860–862


by these organisms are associated with a significant clinical and financial burden worldwide and are responsible for at least 2 million illnesses and 23,000 attributable deaths annually in the United States alone.2 Moreover, the Centers for Diseases Control and Prevention (CDC) estimates that up to 50% of antibiotic prescriptions in the United States are unnecessary.2 As a result of inappropriate overuse, various calls to action


The emergence of antibiotic-resistant bacteria is an increas- ingly serious threat to global public health.1 Infections caused


for antimicrobial stewardship have been sounded. While a need to curtail inappropriate use through stewardship exists, defining this in the hospital setting can be difficult and requires standardization.3,4 One mechanism aimed at benchmarking consumption and evaluating national trends is the CDC Antibiotic Use and Resistance (AUR) module for reporting data to the National Healthcare Safety Network (NHSN). We recently described a methodology to identify potential “antibiotic outbreaks” and periods of underutilization using data compiled by the NHSN AU method. Antibiotic use (ie, consumption) was measured in days of therapy (DOT), which was standardized to days present (DP) in the hospital (ie, DOT/1,000 DP). Over- and under-utilization was defined as a monthly rate of use outside the trend-adjusted prediction window.5 One barrier to implementing our previous metho- dology is the requirement for users to have technical statistical software (eg, Stata, StataCorp LP, College Station, TX) and statistical expertise. In this manuscript, we translate our methodology into a “plug and play strategy” using Microsoft Excel. By using well-known and readily available software, most hospital users should be able to employ these strategies. This method is easy to implement in any hospital that generates longitudinal antimicrobial utilization data, including those who participate in the NHSN AUR module.


For method illustration, data were obtained from North-


western Memorial Hospital, an 897-bed, tertiary-care, aca- demic medical center in Chicago, Illinois. Data regarding intravenous administration of piperacillin-tazobactam were extracted from our medical intensive care unit (MICU) monthly from January 1, 2012, to December 31, 2015. Antibiotic consumption was calculated as antimicrobial days (AD) per 1,000 DP in the ICU and compiled according to the NHSN AU methodology.6 Antimicrobial days and DP facility wide were extracted from the electronic medication record (eMAR) and tallied. Microsoft Excel (2016) standard formulae were used for all calculations, and priority for formulae/code was based on compatibility with older Microsoft Excel versions. A database is supplied as SupplementaryMaterial with formulae for each calculated text box. Interested readers can transfer their own data and generate similar graphics and predictions. Our data were extracted from the NHSN portal as follows.


The “Analysis” portal within the Patient Safety component was accessed, and the “Output options” section was selected. From this portal, the Antimicrobial Use and Resistance module was chosen and directed to Antimicrobial Use data. Using the “CDC defined output,”“Line Listing-All Submitted AU Data by Location” was downloaded (although whole-hospital [FACWIDEIN] is also an option). By modifying the output to comma-separated-value format (*.csv), the data were immediately available in Microsoft Excel.Date data (ie, month of use) are defined in theNHSNdata as “summaryYM.” Numerator data (ie, consumption) were obtained from “IV_Count.” Denominator data (ie, days present) were obtained from “numDaysPresent.” After sorting for location and antibiotic of choice, sequentialmonths were enumerated. Consumption data were then standardized as DOT/1,000 DP in the adjacent columnfor each correspondingmonth using the formula (=cell defining “IV_Count”/cell defining “numDaysPresent” *1,000; see SupplementaryMaterial). Because NHSN data are not universally available to all institutions, any antibiotic consumption data following a


similar format (eg, DOT/1,000 DP) can be modeled using the file available in the Supplementary Material. That is, this document only requires that users insert institution-specific consumption data standardized to 1,000 DP. Formulae are included in the Supplementary Material, and derivations are detailed in Table 1. To investigate antibiotic outbreak thresholds and periods


of underutilization, prediction intervals were defined for each individual time period.5 In this case, an 80% prediction interval was arbitrarily chosen to define potential antibiotic outbreaks; however, percentages can be set to any threshold at the discretion of each institution. We propose that this value has greater utility than the more generally reported 95% confidence interval for the mean, which predicts the


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136