|
Product complaint # (b)(4) this report is being submitted pursuant to the provisions of 21 cfr, part 803 (and/or part 4, as applicable).This report may be based on information which has not been investigated or verified prior to the required reporting date.This report does not reflect a conclusion by depuy synthes, or its employees that the report constitutes an admission that the product, depuy synthes, or its employees caused or contributed to the potential event described in this report.If information is obtained that was not available for the initial report, a follow-up report will be filed as appropriate.
|
|
Depuy synthes is submitting this report pursuant to the provisions of 21 cfr, part 803.This report may be based on information which depuy synthes has not been able to investigate or verify prior to the required reporting date.This report does not reflect a conclusion by fda, depuy synthes or its employees that the report constitutes an admission that the device, depuy synthes, or its employees caused or contributed to the potential event described in this report.H11 additional narrative: h3, h6 investigation summary: according to the information received, the issue with the following product: 451611000, sn: (b)(6).Customer reported during a spine robotic case l1-s2, during the procedure they moved to s2 the tool holder was violating the safety box of the phantom.Violated safety box during every trajectory.Sending it to next trajectory the robot collided with the patient.Investigation summary: three issues were investigated: issue 1: customer reported during a spine robotic case.L1-s2 during the procedure they moved to s2 the tool holder was violating the safety box of the phantom.Violated safety box during every trajectory.Issue 2: sending it to next trajectory the robot collided with the patient.Issue 3: further log review investigation is under velys robotic-assist station.Issue 1: customer reported during a spine robotic case.L1-s2 during the procedure they moved to s2 the tool holder was violating the safety box of the phantom.Violated safety box during every trajectory.The feature described as a "safety box" in the reported complaint is not a feature of the system.The investigation team is interpreting the "safety box" that is being referred to as the scp (skin contact plane).This is a computational tool used to compute trajectories.It is not a safety box in the sense that the tool holder may enter this zone, by current algorithm design.The log files were reviewed and investigated by the r&d team.Photo activities confirmed the investigation.The investigation showed that the tool holder was going below the patient and table interference volume (also known as scp - skin contact plane).The tool holder entering the scp is expected behavior, the computed trajectory can, under certain conditions, go below the patient and table exclusion zones.Based on the review and analysis of log files, the software behaved as expected - no defect found : the tool holder is allowed to go below the patient and table interference volume (also known as scp - skin contact plane).There were no defects found with the software.The user indicated that there was no negative impact to the patient outcome and no patient harm.Issue 2: sending it to next trajectory the robot collided with the patient.The investigation confirmed "sending it to next trajectory the robot collided with the patient." the log files were reviewed and investigated by the r&d team.Each of the joint positions elected for the joint path do not violate the sdp (safe distance plane).The alignment algorithm is not able to detect potential collisions between the elected joint positions.The ifu includes a warning to the user for the motion to remain under strict control of the surgeon and be stopped if there is a potential collision (per ifu warning on page 188."any robotic arm movement should remain under strict control of the surgeon.If any potential collision is detected, stop motion by releasing ¿footswitch¿ or ¿multifunction¿ buttons.Manual arm manipulation can be used to move away the robotic arm.").There were no defects found with the software.The user indicated a potential bruising could have occur however there was no actual bruising reported.Root cause: issue 1: based on the review and analysis of log files, the software behaved as expected - no defect was found.The tool holder is allowed to go below the patient and table interference volume (also known as scp - skin contact plane).Issue 2: based on the review and analysis of log files, no defect was found in the elected joint path of the robotic arm.One possible cause of the reported issue could be use related.The robotic arm made unintended contact with patient outside of the surgical incision under activation of the actuator and supervision of the surgeon.Additional monitoring for any potential safety signals will be conducted through complaint trending and other post-market safety surveillance activities.Additional complaint information monitoring for potential safety signals is conducted through complaint trending as part of post market surveillance.Device history review: no manufacturing record evaluation required as no manufacturer or service related issue found.If information is obtained that was not available for the initial medwatch, a follow-up medwatch will be filed as appropriate.
|