|
(b)(6).(b)(4).Visual analysis found the device was returned with the basket overextended.The working length was found kinked at distal end.Functional inspection found the thumb wheel moved freely in both directions, but the basket did not move.The device was disassembled for further investigation and found the pull wire had been broken at its proximal end.The broken end was inspected under magnification and evidence of bending was observed.Based on all available information, it is most likely that procedural or anatomical factors encountered during the procedure could have affected the device's performance and integrity.Handling and manipulation of the device during its use can lead to the working length kinking, and it could have impacted the overall performance of the device.Moreover, the pull wire being broken could have been caused due to force applied to the handle in order to rotate the basket.The broken end of the pull wire had evidence of bending, indicating the device was submitted to bending forces which could have contributed to the breakage and the device's ability to open/close the basket properly.Therefore, the most probable root cause is adverse event related to procedure.A review of the device history record (dhr) confirmed that the device met all material, assembly, and product specifications at the time of release to distribution.A labeling review was performed and, from the information available, this device was not used per the instructions for use (ifu) / product label as the device was expired when used.
|
|
It was reported to boston scientific corporation that an optiflex retrieval basket was used in the ureter during a ureterolithotripsy procedure performed on (b)(6) 2020.According to the complainant, during the procedure, the basket failed to open.Another optiflex basket was used to complete the procedure.There were no patient complications as a result of this event.The patient's condition following the procedure was reported to be stable.The investigation results revealed the pull wire was broken; therefore, this is now an mdr reportable event.
|