|
The reported issue was: "did not burn - no codes thrown"; during a "sleeve" procedure the ligasure "wouldn¿t burn," the issue was discovered at the beginning, a new ligasure was used, there was a 1 minute delay, the procedure was completed, no serious injury, medical intervention, follow-up care, or impact to the patient was reported, and the individual was reported to be "good." during the investigation, the received device was visually inspected and tested for nonconformities per internal procedure; a small amount of clinical debris was observed on the device jaws, charring was observed on the base of the jaws near the device shaft, rfid tag data showed no abnormalities or corrupt data points, and simulated use was performed on beef tripe test media with a covidien forcetriad console.The device completed the first sealing cycle successfully; upon successive sealing cycles, the activation button connection was intermittent, causing the "incomplete seal cycle" error to repeatedly appear, and the device sealed and cut as expected; however, the activation button did not operate as expected.The reported issue was confirmed; the exact root cause of the reported issue could not be determined, and a potential root cause was due to an internal wiring issue with the device, which prevented proper activation.There were no reports of death, serious injury, medical intervention, or follow up care.It has been determined that the reported event could cause or contribute to serious injury if it were to occur again.In an abundance of caution, this is a reportable event.If additional information becomes available this report will be reopened and reevaluated.This medical device report (mdr) is being submitted as part of retrospective review activities, which include review of historical data in accordance with regulations at 21 cfr part 803.The information included in this mdr reflects the information reasonably known to the manufacturer at the time of this retrospective review and submission.
|