Preventing and containing hospital-associated outbreaks requires timely identification and investigation of possible transmission events. Current methods used by most hospitals to identify clustering of pathogens rely on manual detection of temporal or spatial clustering of a limited number of prespecified pathogens, often using arbitrary criteria, such as ≥3 patients with new methicillin-resistant Staphylococcus aureus (MRSA) nosocomial results on a hospital unit within a 2-week period.Reference Baker, Huang and Letourneau1,Reference Mellmann, Friedrich and Rosenkotter2 This approach to outbreak detection is problematic for several reasons: (1) It fails to identify outbreaks occurring in pathogens not under routine surveillance. (2) Rule-based thresholds for identifying an outbreak, such as a minimum number of cases in a fixed time, can fail to detect some clinically important outbreaks and can also yield false-positive signals. (3) Current methods rely on subjective judgement to determine whether an outbreak exists.
Ideally, hospital-based outbreak detection would utilize automated statistically-based methods to identify clusters across all pathogens, locations, and services, taking into account antimicrobial susceptibility patterns and adjusting for background rates of occurrence.Reference Huang, Yokoe and Stelling3 For instance, the minimum number of new isolates that would constitute a cluster would be substantially larger for an endemic organism like methicillin-sensitive Staphylococcus aureus than the minimum number for a lower prevalence organism such as a Gram-negative bacillus with an unusual antimicrobial susceptibility pattern.
The use of space-time and higher dimensional scan statistics has been used to detect geographic and temporal clustering of events.Reference Huang, Yokoe and Stelling3–Reference Natale, Stelling, Meledandri, Messenger and D’Ancona8 SaTScan (www.satscan.org) is a free disease-surveillance software containing various spatial and space–time scan statistics.Reference Kulldorff9 This software is widely used to detect and evaluate geographical disease clusters, including applications to detect community disease outbreaks.Reference Green, Peterson, Kapell, Fine and Kulldorff10 We integrated SaTScan with WHONET,Reference Stelling and O’Brien11 software that was developed for management and descriptive analysis of microbiology data.Reference Huang, Yokoe and Stelling3 It is available from the World Health Organization (WHO) Collaborating Centre for Surveillance of Antimicrobial Resistance. WHONET includes a data-conversion utility (BacLink) that standardizes and imports data from many different microbiology systems into WHONET format. Focusing on microbiology based outcomes in a healthcare microenvironment provides an optimal setting for a statistically-based cluster detection program.
Previous work that applied integrated WHONET-SaTScan software to 5 years of daily microbiology laboratory data from one 750-bed academic medical center identified an average of 12 clusters annually.Reference Huang, Yokoe and Stelling3 All were deemed to be of clinical interest by hospital epidemiologist reviewers, and one-third would have warranted investigation or active intervention had the alerts occurred in real time. In this study, we retrospectively applied this automated outbreak detection system to hospital microbiology data from 43 hospitals to identify statistically significant clustering of pathogens and asked participating hospitals’ infection preventionists and hospital epidemiologists to assess the relevance of each cluster from an operational infection prevention perspective.
Methods
In total, 43 hospitals using Premier SafetySurveillor software, an infection prevention surveillance system, participated in this retrospective study, which utilized microbiology and census location data streams routinely sent to Premier for infection prevention surveillance and reporting. Microbiology data were limited to finalized results from specimens obtained >2 days after admission in order to focus on hospital-acquired infections. Hospital microbiology results were processed through WHONET software. We searched for potential clusters of a broad set of microorganisms that have been associated with clusters of hospital-acquired pathogens (Table 1). Only first isolates of a specific organism per hospitalized patient were included and surveillance screens were excluded because screening is often performed for routine purposes on 1 day of the week in limited units and practices may change over time, leading to false-positive clusters. Patient-specific data (patient identifier and date of admission) were linked to microbiology data (pathogen name and date of collection). Unit and service 2 days prior to specimen collection were also collected to identify the location where the organism was likely acquired, consistent with Centers for Disease Control and Prevention (CDC) guidance.12
Priority Pathogens
a Previously Clostridium.
b Previously Propionibacterium.
c Klebsiella aerogenes included with Enterobacter spp, previously classified as Enterobacter aerogenes.
Mimicking daily real-time surveillance, we retrospectively applied WHONET-SaTScan to 2 to 3 years of available admission, discharge and transfer and microbiology data accessible through each hospital’s Premier SafetySurveillor system data repository. We performed a simulated prospective assessment by adding retrospective data day-by-day to identify when a cluster signaled or progressed. We used WHONET-SaTScan to identify statistically-based clusters, taking into account background rates at each hospital and accounting for multiple testing. We identified clusters of organisms based on hospital microbiology results, where clusters were defined by statistically significant increases in pathogens that shared at least 1 of the following: antimicrobial resistance profile, unit, meta-unit, specialty service, meta-service, and whole inpatient hospital. We defined meta-units and meta-services as hospital units and services that commonly share staff and patients such that pathogens could be transmitted between them; for example, a meta-unit might include a cardiology critical care unit and a cardiac surgery intensive care unit.
WHONET-SaTScan parameters were based upon prior studies.Reference Huang, Yokoe and Stelling3,Reference Kleinman, Lazarus and Platt13 The maximum length over which a group of isolates could contribute to a detected cluster was set at 60 days; however, there was no restriction on the duration of a cluster if cases continued to accrue with temporally overlapping clusters. Statistical significance was measured using a recurrence interval, which estimated the likelihood that the cluster signal would occur by chance.Reference Kleinman, Lazarus and Platt13 We used a threshold recurrence interval of 365 days, meaning that a cluster of this type of organism with the observed number and that distribution of cases would be expected to occur by chance less than once per year. Clusters were also restricted to have at least 3 patients.
Infection prevention staff at each hospital were asked to review and assess the value of knowing about cluster signals from WHONET-SaTScan in simulated “real time” using a standardized online survey tool that reflected alerts, if any, day by day. The alerts included a summary of the cluster including organism, duration, ward, service, recurrence interval and a line list of the specimens including date, specimen type, and resistance pattern when available. They were asked if they would have wanted to have been notified about the cluster, their level of concern, and how they would intervene. They were also asked if they had previously been aware of the cluster. If WHONET-SaTScan signaled a second time, meaning that the cluster had expanded, accruing another case, they answered another set of similar questions about the cluster. Finally, they were asked how this automated outbreak detection tool might affect outbreak detection and response at their institution.
We used multivariable logistic regression analysis to assess the association between cluster characteristics and the level of concern about the cluster (moderate or high concern versus low or no concern). Variables included in the model were cluster size (3–4 cases, ≥5 cases); statistical significance, measured by the recurrence interval (≤3 years, >3 years); commensal organisms (yes or no); and pathogen type. Pathogen type was divided into (1) Clostridioides difficile, (2) multidrug-resistant organisms (MRSA, vancomycin-resistant Enterococcus, and multidrug-resistant Gram-negative rods), (3) and all other pathogens. Analyses were performed with SAS version 9.4 software (SAS Institute, Cary, NC).
In addition, a convenience sample of hospitals also provided a list and description of clusters that were previously detected using those hospitals’ routine cluster definitions and surveillance methods. Routinely detected clusters were compared to the clusters identified through WHONET-SaTScan. Many of the hospitals did not have complete records of clusters that had been identified and investigated.
Results
Overall, 43 hospitals participated in the study; these included both academic and community hospitals with a mean bed size of 286 (range, 25–913) (Table 2). The hospitals included 42 acute-care and 1 long-term acute-care facility and were located in 9 US states.
Characteristics of the Participating Hospitals
a 1 long-term acute-care facility was not included due to potential identifiability.
Using WHONET-SaTScan, we detected 230 clusters involving a broad range of pathogens with an average of 1 cluster per 100 beds per year (range, 0–4). Of the 230 clusters, 100 consisted of Gram-positive bacteria, 106 consisted of Gram-negative bacteria, and 24 were clusters of fungi. The pathogens associated with identified clusters are summarized in Table 3 and cluster characteristics are found in Table 4. Clusters were most commonly due to Enterococcus spp, Staphylococcus aureus, Escherichia coli, and Pseudomonas aeruginosa. Most clusters consisted of 3–5 patients, but 59 (26%) were larger clusters. Also, 112 clusters had a recurrence interval ranging between 1 and 3 years, and the remaining half were even more statistically uncommon.
Clusters
Note. VRE, vancomycin-resistant Enterococcus; MRSA, methicillin—resistant Staphylococcus aureus.
a Klebsiella aerogenes included with Enterobacter spp, previously classified as Enterobacter aerogenes.
b Previously Clostridium.
c Previously Propionibacterium.
Characteristics of Clusters
Infection prevention programs would have liked to have been notified about 187 (81%) of the clusters and were moderately or highly concerned about 107 (47%) of the clusters (Table 5). They reported being aware of only 24 (10%) of the clusters based upon routine surveillance.
Assessment of Clusters
Note. IP, infection prevention.
In the multivariate logistic regression analysis, factors associated with whether a cluster was considered moderately or highly concerning included greater statistical significance (recurrence interval >3 years (OR, 1.87; 95% CI, 1.01–3.44)), a large cluster (OR, 4.82; 95% CI 2.47–9.41), and a cluster of Clostridioides difficile (OR, 21.71, 95% CI 2.67–176.39) or multidrug-resistant organisms (OR, 2.88; 95% CI, 1.29–6.43) (Table 6). A cluster involving common skin commensal organisms (eg, Staphylococcus epidermidis) was categorized as not important or of low importance (OR, 0.19; 95% CI, 0.07–0.55).
Factors for Consideration of Cluster as Moderately or Highly Concerning
Note. OR, odds ratio; CI, confidence interval; MDRO, multidrug-resistant organism; MRSA, methicillin—resistant Staphylococcus aureus.VRE, vancomycin-resistant Enterococcus; GNR, Gram-negative rods.
Nearly half of the clusters (n = 114) accumulated additional cases after the initial WHONET-SaTScan alert. Of these clusters, 66 (58%) were considered to be of moderate to high concern and were assessed as warranting intervention. Of these 66 clusters, 41 (62%) involved a pathogen that was not routinely targeted by the hospital’s surveillance program. Had the notifications come in real time and the infection preventionists intervened as they indicated, 237 of 559 cases could potentially have been avoided if interventions successfully prevented further transmission.
In the 10 hospitals that provided a list of clusters identified through routine surveillance, WHONET-SaTScan found that only 9 of 51 (18%) of routinely detected clusters had a recurrence interval of a year or greater. In addition, WHONET-SaTScan detected an additional 70 clusters that were not previously identified by those hospitals, including 58 (83%) involving pathogens not generally targeted by routine surveillance at those hospitals (eg, methicillin-sensitive Staphylococcus aureus). Among these 10 hospitals, 36 (46%) of the clusters were considered to be of moderate or high concern.
Infection prevention programs from 26 of the 29 hospitals with at least 1 cluster detected by the automated cluster detection system noted that they would value the ability to expand the focus of surveillance beyond just multidrug-resistant organisms. All noted the potential for WHONET-SaTScan to improve outbreak detection and to streamline their work. Of the 29 hospitals, 22 (76%) thought WHONET-SaTScan would improve outbreak detection to a moderate or large extent and 18 (62%) thought it would streamline their work to a moderate or large extent.
Discussion
Application of WHONET-SaTScan enhanced the ability of hospitals to detect clusters of hospital-acquired microorganisms by expanding surveillance to include a broad range of pathogens and by automatically assessing for statistically significant clustering of these pathogens by unit, service, and resistance pattern compared to each hospital’s baseline data. This outbreak detection tool enabled efficient daily assessments for potential clusters involving 31 pathogens. The tool also provided statistically derived alerts (eg, potential outbreaks) that were considered to be of epidemiological importance by infection preventionists at the designed frequency (1 cluster per 100 beds per year).
Application of WHONET-SaTScan in a geographically diverse group of community and teaching hospitals demonstrated that a large number of statistically significant clusters occur across a variety of units, services, and pathogens that are missed by current methods that infection prevention programs use to detect possible outbreaks. An automated outbreak detection tool could allow infection preventionists to identify clusters of pathogens that might otherwise be difficult to recognize because they involve organisms that are not routinely targeted for surveillance (eg, methicillin-sensitive Staphylococcus aureus). Because nearly all hospitals limit their surveillance to focus on MRSA, vancomycin-resistant Enterococcus, Gram-negative extended-spectrum β-lactamase producers, carbapenem-resistant Enterobacteriaceae, and Clostridioides difficile for possible outbreaks,Reference Baker, Huang and Letourneau1 it is not surprising that clusters due to other pathogens were missed. More than half of the clusters included organisms not under routine targeted surveillance, and infection preventionists reported that they would have wanted to be notified about most of these clusters. In addition, infection preventionists were significantly more likely to judge clusters involving drug-resistant organisms and Clostridioides difficile to be moderately or highly concerning, suggesting that infection prevention programs may be less likely to respond to clusters involving other types of pathogens. This tool would greatly expand the outbreak detection capabilities of many hospitals but would require additional education regarding the potential for clusters of relatively antimicrobial-susceptible organisms to also cause hospital-associated outbreaks that increase morbidity and costs.
Many clusters previously identified through hospitals’ routine surveillance were not found to be statistically unusual compared to those hospitals’ baseline data. Statistically-based cluster detection would allow focusing of efforts on evaluating and intervening on clusters that are more likely to be clinically significant. Early detection of clusters could enable more rapid implementation of interventions to prevent expansion of hospital-based outbreaks. In this study, ~50% of the clusters continued to accumulate cases after the initial statistical alert, suggesting the potential for early interventions triggered by the first cluster signals to prevent subsequent transmission events.
Limitations of the current study include the retrospective nature of these analyses. Although results were provided in simulated real time, survey responses by infection prevention staff may have been different had the assessments been made prospectively. In addition, other than the 10 hospitals that kept records of work-ups for potential outbreaks, many infection prevention programs did not recall or have records about prior clusters for comparison purposes. When WHONET-SaTScan identified a cluster that was also found by routine surveillance, we were often unable to determine the relative timing of the detection due to lack of precise records. Nevertheless, WHONET-SaTScan identified many outbreaks that were not found by routine surveillance.
Automated, statistically-based outbreak detection has the potential to increase the consistency, scope, and comprehensiveness of hospital-associated cluster detection, including clusters due to pathogens not routinely targeted by surveillance. This publicly available tool could be used to trigger rapid responses by infection prevention staff, leading to earlier containment of hospital outbreaks.
Acknowledgments
We thank Premier, Inc, ChristianaCare, Fairview Health Services, HealthEast Care System, McLeod Health, Meridian Health, Mountain States Health Alliance, Summa Health System, Texas Health Resources, University of California, Irvine, and University Hospitals for their collaboration in this research.
Financial support
This work was supported by the Centers for Disease Control and Prevention (CDC) Epicenters Program (grant no. 1U54 CK000172-01) and the National Institutes of Health (NIH grant nos. RR025040 and U01CA207167).
Conflict of interest
All authors report no conflicts of interest relevant to this article.
