Catalog Number UNKNOWN |
Device Problems
Nonstandard Device (1420); Microbial Contamination of Device (2303)
|
Patient Problems
Fever (1858); Unspecified Infection (1930); Sepsis (2067)
|
Event Date 03/10/2018 |
Event Type
Injury
|
Manufacturer Narrative
|
Medical device expiration date: unknown.Fda notified?: the fda was made aware of this incident via voluntary medwatch 5076754.This information was communicated to bd on 5/8/2018 by the fda.A device evaluation is anticipated, but has not yet begun.Upon completion of the investigation, a supplemental report will be filed.Device manufacture date: unknown.
|
|
Event Description
|
It was reported that a patient was admitted to a hospital with fever and sepsis.The patient is an oncology patient that was previously in the pediatric icu and had been discharged.The patient had been receiving daily radiation therapy and has a central line.When he presented to the hospital with a fever, blood cultures were taken which grew out serratia marcescens.His isolate was sent to the state health department for pfge testing and was a match to two other patients' serratia marcescens previously reported.An unspecified bd posiflush¿ heparin lock flush syringe was associated with this incident.Out of an abundance of caution and in the interest of public health, bd voluntarily recalled certain lots of bd posiflush¿ heparin lock flush and bd¿ pre-filled normal saline flush syringes due to a potential for contamination with serratia marcescens bacterium.Bd was notified by the u.S.Food and drug administration (fda) and (b)(4) about a potential epidemiological link between catheter related blood stream infections and the s.Marcescens bacterium.Specifically, the fda and (b)(4) identified a potential connection between reports of infection in a small number of patients caused by s.Marcescens across multiple states.(b)(4)¿s initial investigation found that affected patients had received treatment using certain bd flush products.To date, there is no evidence of bd flush product testing positive for this bacterium.Investigations are ongoing by bd, fda, and (b)(4).
|
|
Manufacturer Narrative
|
As both a lot number and sample were unavailable for this incident, a full investigation consisting of a sample analysis and a device history record review could not be completed.Prior to (b)(6) 2018, there was no trend for infection regarding the (b)(4) products.Upon the increase of infection reports beginning in (b)(6) 2018, a corrective and preventive action plan was initiated to address the issue.A review of all lot sterility testing performed for product released between (b)(6) 2015 and (b)(6) 2018 confirmed that no organism growth was identified for any lots released during the shelf life of this product.A direct causation between the reported infections and the (b)(4) product has not been identified.Investigation conclusion: unknown ¿ lot number was not provided.Prior to the report of infection evaluated in (b)(4), there was no trend for infection cases reported for (b)(4) product.This complaint is part of a new trend which began in (b)(6) 2018.(b)(4) was initiated to address this issue.As no lot number was provided, a dhr review could not be completed.Quantity of retained samples used for testing: 0 ¿ although retain samples are available for all lots manufactured in (b)(4), as the lot number was not provided, retain samples were not tested.A review of all lot sterility testing performed for product released between (b)(6) 2015 & (b)(6) 2018 confirmed that no organism growth was identified for any lots released during the shelf-life of this product.The root cause analysis of the reported infection cases under (b)(4) has not identified a direct causation between the infections and the (b)(4) product.
|
|
Search Alerts/Recalls
|
|