|
ERIKA DE REYNOSA, S.A. DE C.V. STAY SAFE/LUER LOCK CATHETER EXT. 12 IN.; SET, ADMINISTRATION, FOR PERITONEAL DIALYSIS, DISPOSABLE
|
Back to Search Results |
|
| Catalog Number |
050-95004 |
| Medical Device Problem Code |
Fluid/Blood Leak (1250)
|
| Health Effect - Clinical Code |
Peritonitis (2252)
|
| Date of Event |
08/02/2023
|
|
Type of Reportable Event
|
Serious Injury
|
|
Event or Problem Description
|
|
It was reported by a registered nurse (rn) that this patient on peritoneal dialysis (pd) therapy incurred a leak on (b)(6) 2023 when the connection between the extension set and the patient¿s pd catheter became loose while the patient was sleeping.In additional follow-up with the patient¿s pd nurse, the event was confirmed.The patient had the transfer set replaced in the pd clinic and the old set was discarded (lot # unavailable).Furthermore, it was discovered that on (b)(6) 2023, the patient was noted to have cloudy pd effluent during a routine pd clinic appointment.As a result, the patient had a pd culture obtained which grew streptococcus canis and coagulase negative staphylococcus.The patient was initiated on antibiotic therapy with daily ceftazidime and vancomycin (per clinic protocol) intra-peritoneal (ip) on an outpatient basis.Per the nurse, the patient is recovering from the peritonitis event and continues pd therapy with the same cycler and new transfer set without any further issues.The nurse stated it is unknown what caused the loose connection between the fresenius transfer set and the pd catheter (not a fresenius product).However, the nurse indicated that it was highly suspected it was related to a patient issue.Nonetheless, it was reported that the patient¿s peritonitis was likely attributed to the breach in sterile pd pathway due to the reported fluid leak.
|
| |
|
Additional Manufacturer Narrative
|
|
Clinical review: a temporal relationship exists between a fluid leak during pd therapy due to a loose connection between the fresenius stay safe catheter extension set and the patient¿s peritonitis event.Peritonitis is a well-documented complication in patients undergoing pd therapy and may have many potential etiologies.Nonetheless, fluid leaks during a pd treatment are a known potential risk factor for peritonitis due to a breach in the sterile pd pathway.Currently, it cannot be determined what exactly caused the loose connection to occur and the stay safe catheter extensions set involved in the event has been discarded.However, due to the nature of the reported event, the fresenius stay safe catheter extension set cannot be excluded as a cause/contributory factor in the patient¿s event.The plant investigation is in process.A supplemental mdr will be submitted upon completion of this activity.
|
| |
|
Event or Problem Description
|
|
It was reported by a registered nurse (rn) that this patient on peritoneal dialysis (pd) therapy incurred a leak on (b)(6) 2023 when the connection between the extension set and the patient¿s pd catheter became loose while the patient was sleeping.In additional follow-up with the patient¿s pd nurse, the event was confirmed.The patient had the transfer set replaced in the pd clinic and the old set was discarded (lot # unavailable).Furthermore, it was discovered that on (b)(6) 2023, the patient was noted to have cloudy pd effluent during a routine pd clinic appointment.As a result, the patient had a pd culture obtained which grew streptococcus canis and coagulase negative staphylococcus.The patient was initiated on antibiotic therapy with daily ceftazidime and vancomycin (per clinic protocol) intra-peritoneal (ip) on an outpatient basis.Per the nurse, the patient is recovering from the peritonitis event and continues pd therapy with the same cycler and new transfer set without any further issues.The nurse stated it is unknown what caused the loose connection between the fresenius transfer set and the pd catheter (not a fresenius product).However, the nurse indicated that it was highly suspected it was related to a patient issue.Nonetheless, it was reported that the patient¿s peritonitis was likely attributed to the breach in sterile pd pathway due to the reported fluid leak.
|
| |
|
Additional Manufacturer Narrative
|
|
Correction: h.8.
|
| |
|
Event or Problem Description
|
|
It was reported by a registered nurse (rn) that this patient on peritoneal dialysis (pd) therapy incurred a leak on (b)(6)2023 when the connection between the extension set and the patient¿s pd catheter became loose while the patient was sleeping.In additional follow-up with the patient¿s pd nurse, the event was confirmed.The patient had the transfer set replaced in the pd clinic and the old set was discarded (lot # unavailable).Furthermore, it was discovered that on (b)(6)2023, the patient was noted to have cloudy pd effluent during a routine pd clinic appointment.As a result, the patient had a pd culture obtained which grew streptococcus canis and coagulase negative staphylococcus.The patient was initiated on antibiotic therapy with daily ceftazidime and vancomycin (per clinic protocol) intra-peritoneal (ip) on an outpatient basis.Per the nurse, the patient is recovering from the peritonitis event and continues pd therapy with the same cycler and new transfer set without any further issues.The nurse stated it is unknown what caused the loose connection between the fresenius transfer set and the pd catheter (not a fresenius product).However, the nurse indicated that it was highly suspected it was related to a patient issue.Nonetheless, it was reported that the patient¿s peritonitis was likely attributed to the breach in sterile pd pathway due to the reported fluid leak.
|
| |
|
Event or Problem Description
|
|
It was reported by a registered nurse (rn) that this patient on peritoneal dialysis (pd) therapy incurred a leak on (b)(6) 2023 when the connection between the extension set and the patient¿s pd catheter became loose while the patient was sleeping.In additional follow-up with the patient¿s pd nurse, the event was confirmed.The patient had the transfer set replaced in the pd clinic and the old set was discarded (lot # unavailable).Furthermore, it was discovered that on (b)(6) 2023, the patient was noted to have cloudy pd effluent during a routine pd clinic appointment.As a result, the patient had a pd culture obtained which grew streptococcus canis and coagulase negative staphylococcus.The patient was initiated on antibiotic therapy with daily ceftazidime and vancomycin (per clinic protocol) intra-peritoneal (ip) on an outpatient basis.Per the nurse, the patient is recovering from the peritonitis event and continues pd therapy with the same cycler and new transfer set without any further issues.The nurse stated it is unknown what caused the loose connection between the fresenius transfer set and the pd catheter (not a fresenius product).However, the nurse indicated that it was highly suspected it was related to a patient issue.Nonetheless, it was reported that the patient¿s peritonitis was likely attributed to the breach in sterile pd pathway due to the reported fluid leak.
|
| |
|
Additional Manufacturer Narrative
|
|
Plant investigation: the sample was not returned to the manufacturer and the lot number was not provided.A manufacturing review was performed on the products shipped to the patient for the three (3) month time frame which immediately preceded the event occurrence date.This review included the lot numbers for all fresenius liberty cycler sets shipped to this account within the selected time frame.The entire set of lots have been sold and distributed.There were no non-conformances or abnormalities identified during the manufacturing process which could be associated with the reported event.An investigation of the device history records (dhr) was conducted and confirmed that the results of the in-progress and final quality control (qc) testing met all requirements.The product lots involved met all specifications for release.A review of the dhr did not reveal a probable cause for the customer complaint.As a physical evaluation could not be performed, a definitive conclusion regarding the reported incident could not be reached and a cause could not be confirmed.
|
| |
|
Search Alerts/Recalls
|
|
|