The Centers for Disease Control and Prevention recently introduced the concept of mucosal barrier injury (MBI) in an attempt to recognize the possibility of a gastrointestinal source for certain bloodstream infections” Chaftari et al (2016).
BACKGROUND: The Centers for Disease Control and Prevention recently introduced the concept of mucosal barrier injury (MBI) in an attempt to recognize the possibility of a gastrointestinal source for certain bloodstream infections. This could underestimate the central venous catheter (CVC) as the source of central line-associated bloodstream infection (CLABSI) in cancer. The definition of catheter-related bloodstream infection (CRBSI) by the Infectious Diseases Society of America is a more specific and stringent definition that identifies the CVC as the source of infection. In our study, we compared the 2 definitions in cancer patients.
ReTweet if useful... Surveillance definition of CLABSI in cancer patients with mucosal barrier injury http://ctt.ec/97nBV+ @ivteam #ivteam
METHODS: We retrospectively reviewed 149 CLABSI cases that occurred at our center between January 2013 and March 2014 who had 2 simultaneously positive blood cultures drawn from the CVC and peripheral site or concurrent paired tip and blood cultures.
RESULTS: Of the 149 patients with CLABSI, only 70 (47%) had definite CRBSI. CRBSI was identified more commonly in non-MBI CLABSI cases than MBI CLABSI (69% vs 18%, P < .0001).
CONCLUSIONS: The CRBSI definition may be more accurate in identifying the catheter as the source of bloodstream infection in patients with MBI. Because CRBSI continues to occur in patients with MBI, we caution against excluding all MBI patients from CLABSI surveillance.
Chaftari, A.M., Jordan, M., Hachem, R., Al Hamal, Z., Jiang, Y., Yousif, A., Garoge, K., Deshmukh, P. and Raad, I. (2016) A clinical practical approach to the surveillance definition of central line-associated bloodstream infection in cancer patients with mucosal barrier injury. American Journal of Infection Control. April 21st. .
Thank you to our partners for supporting IVTEAM