<!DOCTYPE article
PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD with MathML3 v1.2 20190208//EN" "JATS-archivearticle1-mathml3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" article-type="research-article"><?properties manuscript?><front><journal-meta><journal-id journal-id-type="nlm-journal-id">8004854</journal-id><journal-id journal-id-type="pubmed-jr-id">536</journal-id><journal-id journal-id-type="nlm-ta">Am J Infect Control</journal-id><journal-id journal-id-type="iso-abbrev">Am J Infect Control</journal-id><journal-title-group><journal-title>American journal of infection control</journal-title></journal-title-group><issn pub-type="ppub">0196-6553</issn><issn pub-type="epub">1527-3296</issn></journal-meta><article-meta><article-id pub-id-type="pmid">32284161</article-id><article-id pub-id-type="pmc">7894041</article-id><article-id pub-id-type="doi">10.1016/j.ajic.2020.02.013</article-id><article-id pub-id-type="manuscript">HHSPA1666568</article-id><article-categories><subj-group subj-group-type="heading"><subject>Article</subject></subj-group></article-categories><title-group><article-title>Outbreaks and infection control breaches in health care settings: Considerations for patient notification</article-title></title-group><contrib-group><contrib contrib-type="author"><name><surname>Schaefer</surname><given-names>Melissa K.</given-names></name><degrees>MD</degrees><xref rid="CR1" ref-type="corresp">*</xref></contrib><contrib contrib-type="author"><name><surname>Perkins</surname><given-names>Kiran M.</given-names></name><degrees>MD</degrees></contrib><contrib contrib-type="author"><name><surname>Link-Gelles</surname><given-names>Ruth</given-names></name><degrees>PhD</degrees></contrib><contrib contrib-type="author"><name><surname>Kallen</surname><given-names>Alexander J.</given-names></name><degrees>MD</degrees></contrib><contrib contrib-type="author"><name><surname>Patel</surname><given-names>Priti R.</given-names></name><degrees>MD</degrees></contrib><contrib contrib-type="author"><name><surname>Perz</surname><given-names>Joseph F.</given-names></name><degrees>DrPH</degrees></contrib><aff id="A1">Division of Healthcare Quality Promotion, Centers for Disease Control and Prevention (CDC), Atlanta, GA</aff></contrib-group><author-notes><corresp id="CR1"><label>*</label>Address correspondence to Melissa K. Schaefer, MD, Division of Healthcare Quality Promotion, National Center for Emerging and Zoonotic Diseases, Centers for Disease Control and Prevention, 1600 Clifton Rd NE, MS H16-3, Atlanta, GA 30333. <email>mschaefer@cdc.gov</email> ( M.K. Schaefer).</corresp></author-notes><pub-date pub-type="nihms-submitted"><day>1</day><month>2</month><year>2021</year></pub-date><pub-date pub-type="epub"><day>10</day><month>4</month><year>2020</year></pub-date><pub-date pub-type="ppub"><month>6</month><year>2020</year></pub-date><pub-date pub-type="pmc-release"><day>01</day><month>6</month><year>2021</year></pub-date><volume>48</volume><issue>6</issue><fpage>718</fpage><lpage>724</lpage><!--elocation-id from pubmed: 10.1016/j.ajic.2020.02.013--><kwd-group><kwd>Patient communication</kwd><kwd>Infection control infringement</kwd><kwd>Health care</kwd></kwd-group></article-meta></front><body><sec id="S1"><title>BACKGROUND</title><p id="P1">The Division of Healthcare Quality Promotion (DHQP), within the Centers for Disease Control and Prevention (CDC), provides assistance to health departments and health care facilities investigating potential outbreaks and infection control breaches.<sup><xref rid="R1" ref-type="bibr">1</xref>&#x02013;<xref rid="R3" ref-type="bibr">3</xref></sup> These consultations typically involve assessments regarding potential risk of pathogen transmission and need for patient notification (ie, informing affected individuals about the outbreak or breach).<sup><xref rid="R4" ref-type="bibr">4</xref>&#x02013;<xref rid="R6" ref-type="bibr">6</xref></sup> These assessments can be challenging. The available information might not be sufficient to clearly characterize patient harms and infection risks. Accepted standards regarding patient notification in these situations are lacking. Stakeholder consensus on the best path forward can be difficult to obtain as the expectations of patients, health care providers, health care facilities, and public health do not always align.</p><p id="P2">CDC/DHQP previously published a framework describing a qualitative approach to the assessment of infection control breaches that occur in the absence of documented pathogen transmission.<sup><xref rid="R4" ref-type="bibr">4</xref></sup> The framework highlighted exposures such as syringe reuse that clearly pose high risk of bloodborne pathogen transmission and warrant notification and testing of patients. Emphasis was placed on bloodborne pathogen risks as these infections can have serious long-term consequences but are often silent. Patients might not know they are infected or receive appropriate care absent notification and testing. The framework clarified the importance of notifying patients for breaches that have been shown in the past to result in bloodborne pathogen transmission (ie, Category A breach). Less clear in the framework were the triggers for patient notification in response to breaches that pose lower or uncertain risk of bloodborne pathogen transmission (ie, Category B breaches) or other breaches or health care exposures (eg, contaminated medical product) that might not pose risk of bloodborne pathogen transmission but could still potentially transmit bacteria or other pathogens. Notification of patients as part of outbreak investigations was also not addressed in the previous framework.</p><p id="P3">CDC/DHQP favors a transparent and proactive approach to patient notification for health care-associated infection control breaches and outbreak investigations.<sup><xref rid="R7" ref-type="bibr">7</xref></sup> In this paper, we offer an expanded framework based on ethical principles,<sup><xref rid="R8" ref-type="bibr">8</xref></sup> including Transparency (truth telling), Beneficence (moral duty to act in patients&#x02019; best interests), and Autonomy (respect patients&#x02019; ability and right to make decisions and manage their own health). This framework can be employed during the investigation of serious infection control breaches and outbreaks (both potential and confirmed) and builds on previous work regarding notifying patients about medical errors.<sup><xref rid="R9" ref-type="bibr">9</xref>&#x02013;<xref rid="R12" ref-type="bibr">12</xref></sup> It also adds specificity to existing codes of ethics for physicians<sup><xref rid="R13" ref-type="bibr">13</xref></sup> and nurses,<sup><xref rid="R14" ref-type="bibr">14</xref></sup> such as the Code of Medical Ethics from the American Medical Association which states that &#x0201c;Even when new information regarding the medical error will not alter the patient&#x02019;s medical treatment or therapeutic options, individual physicians who have been involved in a (possible) medical error should: Disclose the occurrence of the error, explain the nature of the (potential) harm, and provide the information needed to enable the patient to make informed decisions about future medical care&#x02026;&#x0201d;<sup><xref rid="R13" ref-type="bibr">13</xref></sup> In this expanded framework, we describe 3 primary triggers for performing patient notification and then use scenarios to illustrate their application. Triggers for public disclosures (ie, alerting people not immediately affected by the outbreak or breach) and the process for performing a patient notification are beyond the scope of this framework.</p></sec><sec id="S2"><title>TRIGGERS FOR PERFORMING PATIENT NOTIFICATION IN THE CONTEXT OF A HEALTH CARE-ASSOCIATED OUTBREAK OR INFECTION CONTROL BREACH</title><p id="P4">We describe 3 main triggers to perform patient notification when investigating a possible health care-associated outbreak or infection control breach. The triggers identified here are advisory in nature and create no new legal obligations for health care facilities. Rather, in this context and arising from existing ethical principles,<sup><xref rid="R8" ref-type="bibr">8</xref></sup> codes of medical ethics,<sup><xref rid="R13" ref-type="bibr">13</xref>,<xref rid="R14" ref-type="bibr">14</xref></sup> and patient preferences,<sup><xref rid="R9" ref-type="bibr">9</xref>,<xref rid="R12" ref-type="bibr">12</xref></sup> triggers for notifying patients (or their surrogate decision maker if the patient or resident lacks decision-making capacity) include when patients: (1) have experienced harm, (2) require information to identify and/or mitigate a potential harm, or (3) their care is altered. The following actions would address these 3 triggers.</p><sec id="S3"><label>1</label><title>Notify patients when they have experienced harm, including explaining how the harm or change to their health care status likely occurred.</title><p id="P5">Within the context of this framework, harm refers primarily to developing an infection; we have extended it more broadly, here, to include becoming colonized with an emerging highly antibiotic-resistant pathogen (eg, carbapenem-resistant <italic>Enterobacteriaceae</italic> [CRE]). This type of notification often takes the form of a conversation with the patient or their surrogate, as part of routine clinical care.</p></sec><sec id="S4"><label>2</label><title>Provide information patients need to identify and/or mitigate a potential harm, including available information regarding the breach or outbreak.</title><p id="P6">When an outbreak or infection control breach is first suspected or identified, the extent of patient harm is usually not evident. At-risk patients might have already developed signs or symptoms of infection but either have not sought care or have presented at a facility other than the index facility. Alternatively, at-risk patients might need to undergo screening (eg, surveillance cultures or bloodborne pathogen testing) or be made aware of signs and symptoms that could indicate infection. Signs and symptoms of infection with nontuberculous mycobacteria (NTM), for example, may take a long time to manifest following exposure. Further, most patients with newly acquired hepatitis B virus or hepatitis C virus (HCV) infection do not manifest signs or symptoms of acute infection; likewise, early signs and symptoms of acute human immunodeficiency virus (HIV) infection may be mistaken for a self-limited viral illness. In situations where bloodborne pathogen risk is present, patient notification is important so patients can obtain appropriate testing.<sup><xref rid="R15" ref-type="bibr">15</xref></sup> For some pathogens, testing before the development of signs and symptoms of infection might not be reliable; however, notification remains advisable so patients can be counseled about monitoring for signs and symptoms and the action(s) to take if they develop. In either situation (ie, proactive testing, counseling for signs and symptoms), patients should receive plain language information explaining why they are being contacted as well as any actions they might need to take to protect others (eg, advising patients with respiratory infection to practice respiratory hygiene and cough etiquette). This outreach might also be important early in an investigation to support case finding, helping to confirm the presence of an outbreak or better define its magnitude and scope. Of note, identifying at-risk patients can be challenging compared with identifying those who have been harmed (trigger 1) or those who have experienced an alteration in care (trigger 3) when relevant exposures are not well documented in patient charts or billing records.</p></sec><sec id="S5"><label>3</label><title>Notify patients when they have experienced an alteration in care that results from an outbreak or infection control breach.</title><p id="P7">Patients who develop an infection and, often, patients who become colonized with an antibiotic-resistant pathogen will experience an alteration in care. This might include receipt of antibiotics that they would not otherwise have received or use of additional infection control precautions (eg, the use of gowns or masks, restricting the patient to their room) during the current or future health care encounters. Further, alterations in care might not be isolated only to patients who develop infection or colonization; in a long-term care facility, for example, outbreak control measures may include decisions to restrict visitors or limit group activities, which could affect all facility residents.<sup><xref rid="R16" ref-type="bibr">16</xref></sup></p></sec></sec><sec id="S6"><title>PATIENT NOTIFICATION SCENARIOS</title><p id="P8">The scenarios that follow describe application of our patient notification triggers in a variety of real-world (<xref ref-type="sec" rid="S8">Scenarios 1</xref>,<xref ref-type="sec" rid="S9">2</xref>,<xref ref-type="sec" rid="S11">4</xref>&#x02013;<xref ref-type="sec" rid="S13">6</xref>,<xref ref-type="sec" rid="S19">11</xref>) and hypothetical situations (<xref ref-type="sec" rid="S10">Scenarios 3</xref>,<xref ref-type="sec" rid="S15">7</xref>&#x02013;<xref ref-type="sec" rid="S18">10</xref>,<xref ref-type="sec" rid="S21">12</xref>) that reflect some of the breaches and considerations raised during notification consultations. The scenarios do not necessarily take into account any jurisdictional requirements<sup><xref rid="R17" ref-type="bibr">17</xref>,<xref rid="R18" ref-type="bibr">18</xref></sup> that might influence decisions regarding patient notification.</p></sec><sec id="S7"><title>OUTBREAKS</title><sec id="S8"><label>1</label><title>Outbreak in an oncology clinic:</title><p id="P9">A local hospital infection preventionist notified the health department of 4 patients admitted to the hospital with <italic>Pseudomonas aeruginosa</italic> bloodstream infection (BSI); 2 of these patients also had <italic>Klebsiella pneumoniae</italic> BSI.<sup><xref rid="R19" ref-type="bibr">19</xref></sup> All 4 patients had an indwelling infusion port and were receiving infusion services at a physician-owned outpatient oncology clinic. As the health department&#x02019;s investigation began, 4 additional clinic patients were admitted to the hospital with catheter-associated BSIs; the clinic was closed under a public health order. All current patients receiving infusion services at the clinic were contacted by the health department, informed of the outbreak, and assessed for symptoms of infection; their primary care physicians were also notified of the risk and asked to monitor for and report any infections. Communication was also maintained with area hospitals to identify additional hospital admissions for these patients. An assessment of infection control practices identified serious longstanding breaches in handling of injectable medications, including overt reuse of syringes for more than 1 patient. A letter was sent to all patients who had ever received care at the clinic informing them of their potential exposure to unsafe injection practices and advising them to seek bloodborne pathogen testing, which was offered for free at county health clinics. All 3 notification triggers applied in this scenario.</p></sec><sec id="S9"><label>2</label><title>Outbreak in a neonatal intensive care unit:</title><p id="P10">A cluster of 4 patients with infections caused by <italic>Staphylococcus aureus</italic> strains that had a similar morphology and antibiogram were identified in a 7-day period.<sup><xref rid="R20" ref-type="bibr">20</xref></sup> An investigation was launched by the facility and steps were taken to limit further spread within the unit, including use of screening cultures; cohorting; Transmission-Based Precautions for patients found to be colonized or infected; and mupirocin treatment for patients and staff. Parents of patients in the neonatal intensive care unit were given a letter notifying them of the outbreak and outlining the rationale for screening cultures, cohorting, and mupirocin treatment. They were also advised regarding recommended infection prevention practices (eg, hand hygiene) to prevent transmission on the unit. All 3 notification triggers applied in this scenario.</p></sec><sec id="S10"><label>3</label><title>Outbreak in a nursing home:</title><p id="P11">A nursing home identified acute respiratory illness among 4 residents on the same unit. The cause of the infections was unknown. The nursing home immediately contacted the health department and implemented measures to prevent further transmission. Infected residents were placed on Contact and Droplet Precautions (including eye protection to be worn by health care personnel caring for infected residents), in either a single room or cohorted with other infected residents. All residents and health care personnel were notified, in person and through posted signs, about the emergence of respiratory infections in the facility and the need to monitor for and immediately report any signs or symptoms of respiratory infection. Active surveillance for new infections was also implemented. Although the source of the outbreak was unknown, unvaccinated residents and staff were offered influenza vaccine. New admissions to the unit were suspended and group activities were cancelled, including meals in the dining hall. Signs and supplies emphasizing respiratory hygiene and cough etiquette were posted throughout the facility; letters were sent to family members informing them about the outbreak and reminding them not to visit when ill. All 3 notification triggers applied in this scenario.</p></sec><sec id="S11"><label>4</label><title>Outbreak associated with contaminated medication:</title><p id="P12">The health department received a report of a single case of fungal meningitis in an immunocompetent adult after an epidural steroid injection at an outpatient clinic.<sup><xref rid="R21" ref-type="bibr">21</xref></sup> Initially, the health department conducted outreach to the clinic and area hospitals to search for additional cases and determine if an outbreak existed or if this was an isolated infection. A multistate outbreak was ultimately confirmed and the source of the infections (contaminated pharmacy-compounded steroid medication) was identified. Early information suggested that presenting symptoms of fungal meningitis were often vague, leading to delayed diagnosis and high risk of mortality and other severe outcomes. An aggressive effort was then undertaken by health departments and the facilities that administered the contaminated medications to directly contact exposed patients (eg, by telephone), informing them of the signs and symptoms of infection that should prompt them to seek care. In addition, public health investigators provided physicians with guidance that would allow them to properly diagnose and treat the infections. Notification of patients who had already developed infection was also critical to ensure they and their physicians knew their infection was likely fungal in origin and to direct them to treatment guidance. Notification triggers 1 and 2 primarily applied in this scenario.</p></sec><sec id="S12"><label>5</label><title>Outbreak associated with heater-cooler devices:</title><p id="P13">A cluster of invasive NTM infections among open-heart surgery patients at a single hospital was reported to public health.<sup><xref rid="R22" ref-type="bibr">22</xref></sup> The ensuing investigation identified an association between the infections and exposure to the LivaNova 3T heater-cooler device used during cardiac surgery procedures requiring cardiopulmonary bypass (consistent with a recent report from Switzerland). The hospital notified approximately 1,300 open heart-surgery patients who were exposed to the device over the preceding four years. Patients were counseled about the signs and symptoms that could signal the presence of NTM infection; similar guidance was provided to area physicians. The facility also contacted patients who had been previously diagnosed with an NTM infection, along with the family members of case-patients who had died, to notify them about the infections and provide additional information. The likely source of the NTM, <italic>Mycobacterium chimaera</italic>, was later found to be contamination of the 3T heater-cooler device at the manufacturing site, suggesting that additional cardiac surgery patients at other facilities using the same device were at risk. Patients infected with <italic>M. chimaera</italic> through open-chest cardiac surgery can develop general or nonspecific symptoms that can take months to years to develop; diagnosis of these infections can be missed or delayed, making these infections more difficult to treat. Ultimately, CDC recommended that all facilities in the United States using 3T heater-cooler devices (whether or not they had a documented case) notify (by letter) all patients potentially exposed to these devices to counsel them about signs and symptoms of infection to ensure prompt recognition and treatment of these serious infections.<sup><xref rid="R23" ref-type="bibr">23</xref></sup> Notification triggers 1 and 2 primarily applied in this scenario.</p></sec><sec id="S13"><label>6</label><title>Outbreak associated with contaminated duodenoscopes:</title><p id="P14">Six patients with a history of admission to the same hospital had New Delhi metallo-<italic>&#x003b2;</italic>-lactamase (NDM)-producing CRE isolated from clinical cultures over a 5-month period.<sup><xref rid="R24" ref-type="bibr">24</xref></sup> An investigation to identify the source of the organism and to assess for transmission within the facility was launched. Patients epidemiologically linked to case-patients (eg, roommates, patients admitted to the same ward where the first patient was treated) were notified and offered CRE rectal screening. A history of endoscopic retrograde cholangiopancreatography procedures involving a duodenoscope was strongly associated with being a case-patient. Review of reprocessing procedures did not identify protocol lapses; however, NDM-producing <italic>Escherichia coli</italic> and <italic>Klebsiella pneumoniae</italic> carbapenemase-producing <italic>K. pneumoniae</italic> were isolated from cultures obtained from the duodenoscope used on several case-patients. Based on these findings, the facility notified all patients who underwent a procedure with any duodenoscope at the hospital during the outbreak period. Patients were informed about the potential exposure to CRE and offered CRE rectal screening and bloodborne pathogen testing. Testing identified an additional 27 patients colonized with CRE; bloodborne pathogen testing did not identify previously undiagnosed infections among patients who returned for screening. Notification triggers 1 and 2 primarily applied in this scenario.</p></sec></sec><sec id="S14"><title>BREACHES WITH DEVICE REPROCESSING</title><sec id="S15"><label>7</label><title>Breaches in bronchoscope reprocessing:</title><p id="P15">A nurse noticed debris at the biopsy-port cap of a bronchoscope that had been reprocessed and was about to be used for a patient procedure in a hospital bronchoscopy suite. This prompted a review of bronchoscope reprocessing procedures, which identified several infection control breaches. The bronchoscope channel was not brushed as part of manual cleaning by a reprocessing technician who had been working in the suite for the last month. Further, the facility had recently purchased a new automated endoscope reprocessor (AER). The AER connectors were not compatible with the bronchoscope, which meant the scope channel was not flushed with glutaraldehyde disinfectant solution or rinsed. The water filter in the new AER had not been changed at the interval recommended by the manufacturer. The facility contacted the health department for assistance with a risk assessment, which concluded there could be risk of both bacterial and bloodborne pathogen infections. The facility sent letters to all patients who had undergone a bronchoscopy over the prior 8 months, which was when the new AER had been purchased. Patients were informed about the breaches in reprocessing and counseled that the breaches may have put them at risk of infection. Patients were informed about the signs and symptoms of respiratory infection and were also advised to return to the hospital for bloodborne pathogen testing. Notification trigger 2 applied in this scenario.</p></sec><sec id="S16"><label>8</label><title>Breaches in cystoscope reprocessing:</title><p id="P16">A routine assessment of infection control at an outpatient urology clinic identified multiple breaches in cystoscope reprocessing. The facility failed to soak the cystoscope in cleaning solution for the recommended length of time; they did not immerse the entire cystoscope in the glutaraldehyde solution that was used to perform high-level disinfection; the cystoscope was rinsed in a bath of initially sterile water that was only replaced when it became cloudy or began to smell. The facility contacted the health department to discuss the risks posed by identified breaches; the health department recommended a patient notification be performed. The facility sent letters to all patients who had undergone cystoscopy at the clinic since the last routine assessment had occurred (6 months prior). Patients were informed that the identified breaches could have placed them at increased risk of developing a bacterial infection following their procedure. They were instructed to contact the clinic if they developed signs and symptoms of a urinary tract or BSI. Patients who had undergone cystoscopy in the prior 2 weeks were also contacted by phone as, if infection were to occur, it would most likely manifest within 2 weeks following the procedure. The infection control breaches were not believed to pose risk of bloodborne pathogen transmission; however, the clinic agreed to provide such testing if a patient requested it. Notification trigger 2 applied in this scenario.</p></sec><sec id="S17"><label>9</label><title>Breaches in a dental clinic:</title><p id="P17">A patient filed a complaint with the state dental board about concerning practices at a dental clinic. The dental board, in collaboration with the health department, conducted a site visit at the clinic. During the site visit, they observed multiple breaches in infection control including: the autoclave that was reportedly used to sterilize dental instruments was broken&#x02014;the dentist could not provide maintenance records for the autoclave to demonstrate when it had last been properly working and there were no logs to show that equipment had been sterilized; in lieu of the autoclave, dental staff wiped the used dental equipment with a bleach wipe; &#x0201c;clean&#x0201d; dental equipment was stored, unwrapped, next to the sink where dirty equipment was cleaned. Based on findings from the site visit, the dental clinic was closed and the dentist&#x02019;s license was suspended. At this point, the dentist refused to cooperate further with the investigators or turn over patient records. Because of the delay in obtaining patient records, the health department elected to move forward with a public notification through the local media advising any patient who had ever received care from the dentist to seek bloodborne pathogen testing from their primary care physician. Guidance on recommended tests was posted on the health department website. In addition, patients who did not have a primary care provider were offered testing at the local health department. Notification trigger 2 applied in this scenario.</p></sec><sec id="S18"><label>10</label><title>Breach in surgical instrument reprocessing:</title><p id="P18">As part of an accreditation survey, surveyors found that a hospital&#x02019;s newly acquired satellite clinic was not performing biologic indicator testing as part of their instrument sterilization process. This raised concerns that the lack of testing meant that sterility of instruments could not be guaranteed and was reported to the state health department. The health department assisted with a risk assessment and performed a detailed review of the clinic&#x02019;s sterilization practices. Following a surgical procedure, instruments were immediately transported in a closed container to the reprocessing room. Appropriate manual cleaning with a brush and enzymatic cleaner was performed; instruments were rinsed, wrapped, and steam sterilized following recommended parameters (eg, time, temperature); mechanical and chemical indicators were used to monitor the sterilization process. The facility had never used biologic indicators. During the health department visit, a typical sterilization cycle was run with a biological indicator; the biologic indicator was negative. The facility was instructed to commence using biologic indicators at least weekly. Based on the infection control assessment, a risk to patients was not identified. The facility was advised, for transparency, they could consider notifying patients; however, they elected not to perform a patient notification. No notification triggers were clearly met in this scenario.</p></sec></sec><sec id="S19"><title>BREACHES INVOLVING MEDICATION SAFETY (IE, SYRINGE REUSE AND DRUG TAMPERING)</title><sec id="S20"><label>11</label><title>Breach involving syringe reuse:</title><p id="P19">A hospital telemetry unit nurse was observed to frequently leave a partially filled syringe of saline flush near a computer work station.<sup><xref rid="R25" ref-type="bibr">25</xref></sup> The hospital questioned the nurse about this practice and she reported reusing syringes for more than 1 patient over the previous 6 months. She erroneously believed this was a safe, cost-saving measure if no fluids were withdrawn into the syringe before injection. At the time the breach was identified, the facility was unaware of any infections associated with the practice. The hospital notified all potentially exposed patients (by both certified and registered mail) and provided free bloodborne pathogen testing. As a result of the outreach, HCV transmission was documented as having occurred on at least one occasion from a patient with known chronic infection to a susceptible patient whose stay overlapped with the source patient. Notification trigger 2 applied in this scenario.</p></sec><sec id="S21"><label>12</label><title>Identification of drug tampering:</title><p id="P20">An operating room nurse observed a surgical technician taking a syringe filled with fentanyl and replacing it with a syringe containing a similar appearing liquid. The technician was immediately confronted and the incident was reported to law enforcement and public health authorities. The technician admitted he had been stealing syringes of fentanyl and swapping them with syringes of saline over the prior month. He stated he always replaced the fentanyl syringes with new syringes that he filled with sterile saline from a multidose vial he kept in his locker. He was asked to undergo bloodborne pathogen testing and was found to be immune by vaccination to hepatitis B virus but negative for HCV and HIV. The hospital elected to contact all patients who had surgery on the dates the technician was working since he was hired (4 months prior). The notification letter informed patients that drug tampering by an employee had been identified and, because of the employee&#x02019;s behavior, they may not have received fentanyl during their procedure. Patients were advised that the technician had tested negative for bloodborne pathogens and, based on his reported method of diversion, there was not believed to be a risk of infection. However, because they were relying on self-reported, unconfirmed behavior, they could not be certain there was not a risk (eg, patient-to-patient transmission of bloodborne pathogens from reused syringes or bacterial infections from nonsterile saline). Patients were encouraged to contact the hospital if they developed any possible signs or symptoms of bacterial infection (eg, fever, chills, pain, or redness at the injection site) and advised that, if they had concerns, the hospital would provide bloodborne pathogen testing at no charge. The hospital also adjusted patient bills to remove charges for sedating medications used during their procedures. Notification triggers 1 and 2 applied in this scenario.</p></sec></sec><sec id="S22"><title>DISCUSSION</title><p id="P21">Decisions about patient notification are often not straightforward and can be subject to differing interpretations. In presenting this expanded framework, we have described triggers for patient notification in the context of a possible health care-associated outbreak or infection control breach that arise from existing ethical principles, codes of medical ethics, and patient preferences.<sup><xref rid="R8" ref-type="bibr">8</xref>&#x02013;<xref rid="R14" ref-type="bibr">14</xref></sup> These include situations when patients have experienced harm (Trigger 1); when patients require information to identify and/or mitigate a potential harm (Trigger 2); or when a patient&#x02019;s care has been altered (Trigger 3).</p><p id="P22">All 3 notification triggers typically come into play in the context of a confirmed outbreak or an infection control breach where pathogen transmission has been confirmed. In those scenarios, there are patients who have experienced harm; there are often additional exposed patients who require information to identify and/or mitigate a potential harm; and there are usually patients who have experienced alterations in their care as a result of the exposure (eg, receipt of antibiotics). Trigger 2 typically applies when investigating a potential outbreak and in the context of an infection control breach, absent initial reports of pathogen transmission. In those scenarios, it may not be clear if an infection is part of a larger outbreak or if the identified breach or contaminated medication posed risk of pathogen transmission. Risk to patients can often only be ascertained through active outreach to potentially exposed patients to identify harm (ie, case finding). Notifications in these situations might initially focus on the highest risk groups. For example, initial outreach might focus on patients who received similar procedures on the same day as the index patient or underwent procedures in the days spanning when a breach was first identified. If done in a timely manner, this action can generate information that helps confirm the presence of an outbreak, clarifies the need to notify additional patients, and informs the evidence base and recommended standard approach for similar events in the future.</p><p id="P23">In our experience, there are 3 concerns that are often raised regarding the need for patient notification. First, there may be concern about the anxiety the notification process could cause affected patients, particularly when the risk is small, exposure is uncertain, or there is not a recommended action for them to take. Second, there may be concern that the notification will result in negative publicity or loss of trust in the health care facility or willingness of patients to seek medical care in the future; liability and financial repercussions might also be factors here. Third, there may be concern about the resources needed to perform a patient notification. While these concerns may have validity, experience and research increasingly favor full transparency and notification regarding medical errors and adverse events.<sup><xref rid="R9" ref-type="bibr">9</xref>&#x02013;<xref rid="R14" ref-type="bibr">14</xref></sup></p><p id="P24">Even if harm was unlikely and there is not an action to recommend, patients have a reasonable expectation to be informed when their health care provider or health care facility failed to meet standards of care.<sup><xref rid="R9" ref-type="bibr">9</xref>&#x02013;<xref rid="R12" ref-type="bibr">12</xref></sup> Further, even if a patient is already aware of their infection or colonization status (and receiving appropriate follow-up and management), they should still be informed if they are believed to be part of a larger outbreak. This is a step that, if overlooked, can result in damaged reputations and loss of trust in the facility or provider.<sup><xref rid="R26" ref-type="bibr">26</xref></sup> Patients surveyed following a notification conducted in response to a breach in endoscope reprocessing felt they had a right to know about anything that might impact the quality of their care and that such communication is important to maintain confidence in a particular institution.<sup><xref rid="R9" ref-type="bibr">9</xref></sup> While approximately 28% of respondents agreed it would make them nervous to be told about an error in their health care, more than 90% agreed that facilities should tell patients about any error in their care, even if the chance of harm was extremely low. Following the notification, the majority of patients surveyed had an improved perception of the facility&#x02019;s honesty and integrity. Other research has not identified long-term reductions in patients seeking care at hospitals where quality concerns were publicly reported.<sup><xref rid="R27" ref-type="bibr">27</xref></sup></p><p id="P25">In addition, while patients will often have been counseled that infection is a known risk of a procedure and to watch for and report signs of infection as part of the routine consent process for their medical procedures, this does not obviate the need to perform a patient notification. The risk of infection communicated to the patient during the consent process assumes that the provider will meet the expected standard of care. Even if the actions recommended as part of the original consent process are unchanged (ie, watch for and report signs and symptoms of infection), patients want to know if their risk of infection has changed as the direct result of deviations from standard care practices or if they are part of a larger outbreak.<sup><xref rid="R9" ref-type="bibr">9</xref>,<xref rid="R12" ref-type="bibr">12</xref></sup></p><p id="P26">The possibility of bloodborne pathogen transmission is a frequent consideration during the evaluation of infection control breaches. If an infection control breach is believed to pose risk of bloodborne pathogen transmission, patients should be counseled about the need for proactive testing; in some situations, postexposure prophylaxis may also be warranted, making timely notification critical. A strong recommendation for testing should accompany exposures to breaches where there is a clear and well-established risk (eg, in the context of a health care-associated hepatitis C outbreak, Category A breach, Category B breaches where neither cleaning nor high-level disinfection or sterilization were performed; see <xref ref-type="sec" rid="S8">Scenarios 1</xref>, <xref ref-type="sec" rid="S15">7</xref>, <xref ref-type="sec" rid="S17">9</xref>, and <xref ref-type="sec" rid="S20">11</xref>). On the other hand, for breaches believed to pose low or uncertain risk, it may be appropriate and reasonable to forego a firm recommendation for testing and instead offer counseling and testing if requested by the individual patient (see <xref ref-type="sec" rid="S13">Scenarios 6</xref>, <xref ref-type="sec" rid="S16">8</xref>, and <xref ref-type="sec" rid="S21">12</xref>). The strength of a recommendation for bloodborne pathogen testing or testing for other pathogens should be clearly communicated to patients along with the rationale for the recommendation.</p><p id="P27">As demonstrated in the scenarios, the mode of patient notification can vary from an individual notification (eg, phone call, letter, or in the moment conversation with a patient if a breach is identified as part of their health care encounter), group notification (eg, a notice at the entrance to a facility or unit), or a public notification (eg, press release or notice on a facility or health department website). While patients prefer individual notification, ideally through a face-to-face visit or phone call,<sup><xref rid="R12" ref-type="bibr">12</xref>,<xref rid="R28" ref-type="bibr">28</xref></sup> this is not always possible or practical. In certain circumstances, such as when patient records are not complete or there is an urgent need to broadly disseminate guidance to health care personnel on how to diagnose and manage exposed patients, public notification may be the preferred initial route of communication. For example, in <xref ref-type="sec" rid="S17">Scenario 9</xref>, which involved breaches in sterilization of dental equipment and concerns for bloodborne pathogen transmission, patient records were not immediately available so the health department elected to move forward with a broader public notification via a press release followed by letters if/when the records were obtained.</p><p id="P28">The third concern raised regarding need for patient notification relates to the resources needed. Patient notifications can be both resource and labor-intensive, particularly for free-standing outpatient clinics or other settings that might not have ready access to the risk management or communication infrastructure available in larger hospital systems. Under prevailing ethical and professional practices,<sup><xref rid="R8" ref-type="bibr">8</xref>&#x02013;<xref rid="R14" ref-type="bibr">14</xref></sup> however, this does not obviate the need to perform patient notification when one is warranted. However, not all breaches pose the same level of risk to all patients and there may be opportunities to balance the desire for transparency with the potential to divert resources and attention from other initiatives and pressing matters. For example, if patient notification was performed every time an opportunity for hand hygiene was missed, the majority of patients could require notification after each health care encounter. While all infection control breaches warrant correction and education of health care personnel at the facility to prevent future occurrences, formal patient notification might not be warranted for every instance of an infection control breach (as was described in <xref ref-type="sec" rid="S18">Scenario 10</xref>, in which biological indicators were not used but all other aspects of instrument sterilization were deemed adequate).</p><p id="P29">While this paper focused on triggers for notifying patients, this process always entails engagement of additional stakeholders including health care personnel, facility leadership, and public health. Regulatory authorities such as the state survey agency, medical, nursing or pharmacy boards, and law enforcement&#x02014;as well as accrediting organizations&#x02014;may also need to be included in the notification process depending on the event. Health care personnel are the first line of communication with patients and also need to understand the event and messaging to properly address questions raised by patients and their families. In some instances, such as <xref ref-type="sec" rid="S10">Scenario 3</xref>, which involved an undiagnosed respiratory illness outbreak in a nursing home, health care personnel may also be at risk and need to be informed about signs and symptoms of infection or recommended actions to protect themselves and patients. They also require information about recommended infection prevention practices to prevent further transmission (eg, implementing Transmission-Based Precautions). Depending on the events, communications may need to extend beyond health care personnel working at the affected facility. For example, in <xref ref-type="sec" rid="S11">Scenario 4</xref>, notification efforts extended broadly to the medical community caring for exposed patients. Because presenting symptoms were often vague and there was limited experience in diagnosing and treating the fungus, physicians required guidance on how to effectively evaluate and care for exposed patients. Further, as part of a response to multidrug-resistant organisms, interfacility communication is critical to ensure receiving facilities are aware of a patient&#x02019;s multidrug-resistant organisms&#x02019; status and the level of Transmission-Based Precautions necessary to prevent transmission in the facility.<sup><xref rid="R29" ref-type="bibr">29</xref></sup></p><p id="P30">By working with internal (eg, facility leadership, risk management) and external stakeholders (eg, public health) prior to conducting a notification, facilities can ensure that infrastructure is in place to manage the process. In addition to crafting appropriate messaging for the initial outreach (eg, letter, phone call), there is a need to establish a mechanism to address patient questions and concerns (eg, call center). There may also be a need to arrange for laboratory testing or other evaluation of exposed patients. Identifying how or why the event occurred (eg, lack of training of health care personnel; lack of access to necessary patient care supplies) is critical for preventing future occurrences. While the primary responsibility for patient notification rests with the health care facility/provider, the health care-associated infections program in the health department is an important partner that can provide useful guidance, particularly for notifications associated with outbreaks, which are required to be reported in most states.<sup><xref rid="R30" ref-type="bibr">30</xref>,<xref rid="R31" ref-type="bibr">31</xref></sup> They can offer expertise with investigation and risk assessment and assist with best practices for conducting patient notification. CDC is also available for consultation in conjunction with the health department. For example, in 2018, CDC/DHQP provided technical assistance for more than 300 health care-associated outbreaks and infection control breach assessments, including on the ground investigative support for 10 of these events (CDC, unpublished data). CDC and partners, including the Council for Outbreak Response: Healthcare-Associated Infections and Antimicrobial-Resistant Pathogens have also developed an array of patient notification resources including toolkits, sample patient notification letters, scripts for communicating information to patients, and guides for defining and investigating outbreaks.<sup><xref rid="R29" ref-type="bibr">29</xref>,<xref rid="R32" ref-type="bibr">32</xref>&#x02013;<xref rid="R34" ref-type="bibr">34</xref></sup></p><p id="P31">Ultimately, a strong infection prevention and control program that includes education of health care personnel, methods to prevent and monitor for diversion of controlled substances, and a process to verify ongoing adherence to recommended practices can help avoid a large-scale patient notification.<sup><xref rid="R35" ref-type="bibr">35</xref></sup> Such activities can help prevent the infection control breaches or other unsafe practices that contribute to outbreaks and health care-associated infection risks. Regular auditing of practices and encouraging staff to promptly report concerns can also be helpful in limiting the timeframe and scope for a potential notification. For example, in <xref ref-type="sec" rid="S16">Scenario 8</xref>, breaches in cystoscope reprocessing were identified as part of a routine assessment of infection control in the facility. When determining the timeframe for a patient notification, the facility notified all cystoscopy patients over the prior 6 months, which was when the last infection control assessment documenting appropriate practices had been performed. This notification could have been avoided or the timeframe could have been narrowed if the facility had performed more frequent assessments. CDC has developed a number of setting-specific resources health care facilities can use to routinely assess infection prevention practices.<sup><xref rid="R36" ref-type="bibr">36</xref></sup></p><p id="P32">This expanded framework clarifies triggers for patient notification in the context of health care-associated outbreaks and breaches in infection control. Application of these triggers may result in a more consistent, less arbitrary approach to patient notifications. Ensuring transparency in these situations is important to ensure patients have the information they need to protect their health and make informed decisions about their care and helps build trust in their providers.</p></sec></body><back><fn-group><fn fn-type="COI-statement" id="FN1"><p id="P33">Conflicts of interest: None to report.</p></fn></fn-group><ref-list><title>References</title><ref id="R1"><label>1.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Outbreak investigations in healthcare settings</source>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hai/outbreaks/index.html">https://www.cdc.gov/hai/outbreaks/index.html</ext-link>.</comment>
<date-in-citation>Accessed October 25, 2019</date-in-citation>.</mixed-citation></ref><ref id="R2"><label>2.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Resources for state health departments investigating healthcare-associated infection outbreaks and patient notifications</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hai/outbreaks/outbreak-resources.html">https://www.cdc.gov/hai/outbreaks/outbreak-resources.html</ext-link>.</comment>
<date-in-citation>Accessed October 25, 2019</date-in-citation>.</mixed-citation></ref><ref id="R3"><label>3.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Steps for evaluating an infection control breach</source>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hai/outbreaks/steps_for_eval_ic_breach.html">https://www.cdc.gov/hai/outbreaks/steps_for_eval_ic_breach.html</ext-link>.</comment>
<date-in-citation>Accessed October 25, 2019</date-in-citation>.</mixed-citation></ref><ref id="R4"><label>4.</label><mixed-citation publication-type="journal"><name><surname>Patel</surname><given-names>PR</given-names></name>, <name><surname>Srinivasan</surname><given-names>A</given-names></name>, <name><surname>Perz</surname><given-names>JP</given-names></name>. <article-title>Developing a broader approach to management of infection control breaches in health care settings</article-title>. <source>AJIC</source>. <year>2008</year>;<volume>36</volume>:<fpage>685</fpage>&#x02013;<lpage>690</lpage>.</mixed-citation></ref><ref id="R5"><label>5.</label><mixed-citation publication-type="journal"><name><surname>Guh</surname><given-names>AY</given-names></name>, <name><surname>Thompson</surname><given-names>ND</given-names></name>, <name><surname>Schaefer</surname><given-names>MK</given-names></name>, <name><surname>Patel</surname><given-names>PR</given-names></name>, <name><surname>Perz</surname><given-names>JF</given-names></name>. <article-title>Patient notification for bloodborne pathogen testing due to unsafe injection practices in US health care settings, 2001-2011</article-title>. <source>Med Care</source>. <year>2012</year>;<volume>50</volume>:<fpage>785</fpage>&#x02013;<lpage>791</lpage>.<pub-id pub-id-type="pmid">22525612</pub-id></mixed-citation></ref><ref id="R6"><label>6.</label><mixed-citation publication-type="journal"><name><surname>Schaefer</surname><given-names>MK</given-names></name>, <name><surname>Perkins</surname><given-names>KM</given-names></name>, <name><surname>Perz</surname><given-names>JF</given-names></name>. <article-title>Patient notification events due to syringe reuse and mishandling of injectable medications by healthcare personnel&#x02014;United States, 2012-2018: summary and recommended actions for prevention and response</article-title>. <source>Mayo Clin Proc</source>. <year>2020</year>;<volume>95</volume>:<fpage>243</fpage>&#x02013;<lpage>254</lpage>.<pub-id pub-id-type="pmid">31883694</pub-id></mixed-citation></ref><ref id="R7"><label>7.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>DHQP response and outbreak consultation guidance</source>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hai/pdfs/outbreaks/DHQP-Response-Outbreak-Consultation-Guidance-P.pdf">https://www.cdc.gov/hai/pdfs/outbreaks/DHQP-Response-Outbreak-Consultation-Guidance-P.pdf</ext-link>.</comment>
<date-in-citation>Accessed October 25, 2019</date-in-citation>.</mixed-citation></ref><ref id="R8"><label>8.</label><mixed-citation publication-type="book"><name><surname>Barrett</surname><given-names>DH</given-names></name>, <name><surname>Ortmann</surname><given-names>LW</given-names></name>, <name><surname>Dawson</surname><given-names>A</given-names></name>, <etal/>
<source>Public Health Ethics: Cases Spanning the Globe</source>. <publisher-name>SpringerOpen</publisher-name>; <year>2016</year>.</mixed-citation></ref><ref id="R9"><label>9.</label><mixed-citation publication-type="journal"><name><surname>Prouty</surname><given-names>CD</given-names></name>, <name><surname>Foglia</surname><given-names>M</given-names></name>, <name><surname>Gallagher</surname><given-names>TH</given-names></name>. <article-title>Patients&#x02019; experiences with disclosure of a large-scale adverse event</article-title>.<source>J Clin Ethics</source>. <year>2013</year>;<volume>24</volume>:<fpage>353</fpage>&#x02013;<lpage>363</lpage>.<pub-id pub-id-type="pmid">24597423</pub-id></mixed-citation></ref><ref id="R10"><label>10.</label><mixed-citation publication-type="journal"><name><surname>Dudzinski</surname><given-names>DM</given-names></name>, <name><surname>Herbert</surname><given-names>PC</given-names></name>, <name><surname>Foglia</surname><given-names>MB</given-names></name>, <name><surname>Gallagher</surname><given-names>TH</given-names></name>. <article-title>The disclosure dilemma&#x02014;large-scale adverse events</article-title>. <source>NEJM</source>. <year>2010</year>;<volume>363</volume>:<fpage>978</fpage>&#x02013;<lpage>986</lpage>.<pub-id pub-id-type="pmid">20818911</pub-id></mixed-citation></ref><ref id="R11"><label>11.</label><mixed-citation publication-type="journal"><name><surname>Gallagher</surname><given-names>TH</given-names></name>, <name><surname>Studdert</surname><given-names>D</given-names></name>, <name><surname>Levinson</surname><given-names>W</given-names></name>. <article-title>Disclosing harmful medical errors to patients</article-title>. <source>NEJM</source>. <year>2007</year>;<volume>356</volume>:<fpage>2713</fpage>&#x02013;<lpage>2719</lpage>.<pub-id pub-id-type="pmid">17596606</pub-id></mixed-citation></ref><ref id="R12"><label>12.</label><mixed-citation publication-type="journal"><name><surname>Mazor</surname><given-names>KM</given-names></name>, <name><surname>Simon</surname><given-names>SR</given-names></name>, <name><surname>Yood</surname><given-names>RA</given-names></name>, <etal/>
<article-title>Health plan members&#x02019; views about disclosure of medical errors</article-title>. <source>Ann Intern Med</source>. <year>2004</year>;<volume>140</volume>:<fpage>409</fpage>&#x02013;<lpage>418</lpage>.<pub-id pub-id-type="pmid">15023706</pub-id></mixed-citation></ref><ref id="R13"><label>13.</label><mixed-citation publication-type="web"><collab>American Medical Association</collab>. <source>Code of medical ethics opinion 8.6</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.ama-assn.org/delivering-care/ethics/promoting-patient-safety">https://www.ama-assn.org/delivering-care/ethics/promoting-patient-safety</ext-link>.</comment>
<date-in-citation>Accessed October 25, 2019</date-in-citation>.</mixed-citation></ref><ref id="R14"><label>14.</label><mixed-citation publication-type="web"><collab>American Nurses Association</collab>. <source>Code of ethics for nurses with interpretive statements</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.nursingworld.org/coe-view-only">https://www.nursingworld.org/coe-view-only</ext-link>.</comment>
<date-in-citation>Accessed October 28, 2019</date-in-citation>.</mixed-citation></ref><ref id="R15"><label>15.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Healthcare notification and testing toolkit</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hepatitis/outbreaks/toolkit.htm">https://www.cdc.gov/hepatitis/outbreaks/toolkit.htm</ext-link>.</comment>
<date-in-citation>Accessed October 25, 2019</date-in-citation>.</mixed-citation></ref><ref id="R16"><label>16.</label><mixed-citation publication-type="journal"><name><surname>Ibrahim</surname><given-names>S</given-names></name>, <name><surname>Scott</surname><given-names>M</given-names></name>, <name><surname>Bixler</surname><given-names>D</given-names></name>, <etal/>
<article-title>Outbreaks of human metapneumovirus in two skilled nursing facilities&#x02014;West Virginia and Idaho, 2011-2012</article-title>. <source>MMWR</source>. <year>2013</year>;<volume>62</volume>:<fpage>909</fpage>&#x02013;<lpage>913</lpage>.<pub-id pub-id-type="pmid">24257198</pub-id></mixed-citation></ref><ref id="R17"><label>17.</label><mixed-citation publication-type="web"><collab>Pennsylvania General Assembly</collab>. <source>Medical Care Availability and Reduction of Error (MCARE) Act. Section 308. Reporting and notification</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.legis.state.pa.us/cfdocs/legis/li/uconsCheck.cfm?yr=2002&#x00026;sessInd=0&#x00026;act=13">https://www.legis.state.pa.us/cfdocs/legis/li/uconsCheck.cfm?yr=2002&#x00026;sessInd=0&#x00026;act=13</ext-link>.</comment>
<date-in-citation>Accessed November 20, 2019</date-in-citation>.</mixed-citation></ref><ref id="R18"><label>18.</label><mixed-citation publication-type="web"><comment><ext-link ext-link-type="uri" xlink:href="http://QuPS.org">QuPS.org</ext-link></comment>
<source>Summary of states&#x02019; policy toward disclosure</source>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://qups.org/">http://qups.org/</ext-link>.</comment>
<date-in-citation>Accessed November 20, 2019</date-in-citation>.</mixed-citation></ref><ref id="R19"><label>19.</label><mixed-citation publication-type="journal"><name><surname>Dobbs</surname><given-names>TE</given-names></name>, <name><surname>Guh</surname><given-names>AY</given-names></name>, <name><surname>Oakes</surname><given-names>P</given-names></name>, <etal/>
<article-title>Outbreak of pseudomonas aeruginosa and Klebsiella pneumonia bloodstream infections at an outpatient chemotherapy center</article-title>. <source>AJIC</source>. <year>2014</year>;<volume>42</volume>:<fpage>731</fpage>&#x02013;<lpage>734</lpage>.</mixed-citation></ref><ref id="R20"><label>20.</label><mixed-citation publication-type="journal"><name><surname>Lally</surname><given-names>RT</given-names></name>, <name><surname>Lanz</surname><given-names>E</given-names></name>, <name><surname>Schrock</surname><given-names>CG</given-names></name>. <article-title>Rapid control of an outbreak of Staphylococcus aureus on a neonatal intensive care department using standard infection control practices and nasal mupirocin</article-title>. <source>AJIC</source>. <year>2004</year>;<volume>32</volume>:<fpage>44</fpage>&#x02013;<lpage>47</lpage>.</mixed-citation></ref><ref id="R21"><label>21.</label><mixed-citation publication-type="journal"><name><surname>Smith</surname><given-names>RM</given-names></name>, <name><surname>Schaefer</surname><given-names>MK</given-names></name>, <name><surname>Kainer</surname><given-names>MA</given-names></name>, <etal/>
<article-title>Fungal infections associated with contaminated methylprednisolone injections&#x02014;preliminary report</article-title>. <source>NEJM</source>. <year>2012</year>;<volume>369</volume>: <fpage>1598</fpage>&#x02013;<lpage>1609</lpage>.<pub-id pub-id-type="pmid">23252499</pub-id></mixed-citation></ref><ref id="R22"><label>22.</label><mixed-citation publication-type="journal"><name><surname>Perkins</surname><given-names>KM</given-names></name>, <name><surname>Lawsin</surname><given-names>A</given-names></name>, <name><surname>Hasan</surname><given-names>NA</given-names></name>, <etal/>
<article-title>Notes from the field: Mycobacterium chimaera contamination of heater-cooler devices used in cardiac surgery&#x02014;United States</article-title>. <source>MMWR</source>. <year>2016</year>;<volume>65</volume>:<fpage>1117</fpage>&#x02013;<lpage>1118</lpage>.<pub-id pub-id-type="pmid">27740609</pub-id></mixed-citation></ref><ref id="R23"><label>23.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <article-title>CDC advises hospitals to alert patients at risk from contaminated heater-cooler devices used during cardiac surgery</article-title>. <source>Health Alert Network</source>. <year>2016</year> Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://emergency.cdc.gov/han/han00397.asp">https://emergency.cdc.gov/han/han00397.asp</ext-link>.</comment>
<date-in-citation>Accessed August 8, 2019</date-in-citation>.</mixed-citation></ref><ref id="R24"><label>24.</label><mixed-citation publication-type="journal"><name><surname>Epstein</surname><given-names>L</given-names></name>, <name><surname>Hunter</surname><given-names>JC</given-names></name>, <name><surname>Arwady</surname><given-names>A</given-names></name>, <etal/>
<article-title>New Delhi Metallo-<italic>&#x003b2;</italic>-Lactamase-producing carbapenem-resistant <italic>Escherichia coli</italic> associated with exposure to duodenoscopes</article-title>. <source>JAMA</source>. <year>2014</year>;<volume>312</volume>:<fpage>1447</fpage>&#x02013;<lpage>1455</lpage>.<pub-id pub-id-type="pmid">25291580</pub-id></mixed-citation></ref><ref id="R25"><label>25.</label><mixed-citation publication-type="journal"><name><surname>Arnold</surname><given-names>S</given-names></name>, <name><surname>Melville</surname><given-names>SK</given-names></name>, <name><surname>Morehead</surname><given-names>B</given-names></name>, <etal/>
<article-title>Notes from the field: hepatitis C transmission from inappropriate reuse of saline flush syringes for multiple patients in an acute care general hospital&#x02014;Texas, 2015</article-title>. <source>MMWR</source>. <year>2017</year>;<volume>66</volume>:<fpage>258</fpage>&#x02013;<lpage>260</lpage>.<pub-id pub-id-type="pmid">28278142</pub-id></mixed-citation></ref><ref id="R26"><label>26.</label><mixed-citation publication-type="book"><name><surname>Catalanello</surname><given-names>R</given-names></name>
<source>Children&#x02019;s hospital: &#x02018;we failed to do what we should have done&#x02019;</source>. <publisher-name>The Times-Picayune.</publisher-name>
<year>2014</year> Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.nola.com/entertainment_life/health_fitness/article_cfdeabd8-d18f-5d69-8cbb-8dc10cb3060a.html">https://www.nola.com/entertainment_life/health_fitness/article_cfdeabd8-d18f-5d69-8cbb-8dc10cb3060a.html</ext-link>.</comment>
<date-in-citation>Accessed August 8, 2019</date-in-citation>.</mixed-citation></ref><ref id="R27"><label>27.</label><mixed-citation publication-type="journal"><name><surname>Laverty</surname><given-names>AA</given-names></name>, <name><surname>Smith</surname><given-names>PC</given-names></name>, <name><surname>Pape</surname><given-names>UJ</given-names></name>, <etal/>
<article-title>High-profile investigations into hospital safety problems in England did not prompt patients to switch providers</article-title>. <source>Health Aff</source>. <year>2012</year>;<volume>31</volume>:<fpage>593</fpage>&#x02013;<lpage>601</lpage>.</mixed-citation></ref><ref id="R28"><label>28.</label><mixed-citation publication-type="journal"><name><surname>Schneider</surname><given-names>AK</given-names></name>, <name><surname>Brinsley-Rainisch</surname><given-names>KJ</given-names></name>, <name><surname>Schaefer</surname><given-names>MK</given-names></name>, <etal/>
<article-title>Public perceptions and preferences for patient notification after an unsafe injection</article-title>. <source>J Patient Saf</source>. <year>2013</year>;<volume>9</volume>:<fpage>8</fpage>&#x02013;<lpage>12</lpage>.<pub-id pub-id-type="pmid">23007243</pub-id></mixed-citation></ref><ref id="R29"><label>29.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Containment strategy responding to emerging AR threats</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hai/containment/index.html">https://www.cdc.gov/hai/containment/index.html</ext-link>.</comment>
<date-in-citation>Accessed August 8, 2019</date-in-citation>.</mixed-citation></ref><ref id="R30"><label>30.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>State-based HAI prevention</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/hai/state-based/index.html">https://www.cdc.gov/hai/state-based/index.html</ext-link>.</comment>
<date-in-citation>Accessed November 20, 2019</date-in-citation>.</mixed-citation></ref><ref id="R31"><label>31.</label><mixed-citation publication-type="web"><source>CSTE Surveillance/informatics: SRCA query tools</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cste.org/group/SRCAQueryRes">https://www.cste.org/group/SRCAQueryRes</ext-link>.</comment>
<date-in-citation>Accessed November 20, 2019</date-in-citation>.</mixed-citation></ref><ref id="R32"><label>32.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Patient notification toolkit</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/injectionsafety/pntoolkit/index.html">https://www.cdc.gov/injectionsafety/pntoolkit/index.html</ext-link>.</comment>
<date-in-citation>Accessed August 8, 2019</date-in-citation>.</mixed-citation></ref><ref id="R33"><label>33.</label><mixed-citation publication-type="web"><collab>AHRQ</collab>. <source>Communication and optimal resolution (CANDOR)</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.ahrq.gov/patient-safety/capacity/candor/index.html">https://www.ahrq.gov/patient-safety/capacity/candor/index.html</ext-link>.</comment>
<date-in-citation>Accessed August 23, 2019</date-in-citation>.</mixed-citation></ref><ref id="R34"><label>34.</label><mixed-citation publication-type="web"><source>Council for Outbreak Response: Healthcare-Associated Infections and Antimicrobial-Resistant Pathogens. Resources and products</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://corha.org/resources-and-products/">https://corha.org/resources-and-products/</ext-link>.</comment>
<date-in-citation>Accessed September 5, 2019</date-in-citation>.</mixed-citation></ref><ref id="R35"><label>35.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Infection control</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/infectioncontrol/index.html">https://www.cdc.gov/infectioncontrol/index.html</ext-link>.</comment>
<date-in-citation>Accessed November 20,2019</date-in-citation>.</mixed-citation></ref><ref id="R36"><label>36.</label><mixed-citation publication-type="web"><collab>CDC</collab>. <source>Tools for healthcare settings</source>. Available at: <comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/infectioncontrol/tools/index.html">https://www.cdc.gov/infectioncontrol/tools/index.html</ext-link>.</comment>
<date-in-citation>Accessed August 8, 2019</date-in-citation>.</mixed-citation></ref></ref-list></back></article>