|
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.Additional narrative: if information is obtained that was not available for the initial medwatch, a follow-up medwatch 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.If the information is unknown, not available or does not apply, the section/field of the form is left blank.H11 additional narrative: added: g4 [pma/ 510(k)].H3, h6: investigation summary: according to the information received, the issue with the following product: 451611000 sn: (b)(6) was experienced: robot ran into the post of the patient array near the clamp.The camera had to be positioned in the anesthesia area making it hard to keep the patient sterile as well as capture the arrays.Results received from the engineering team: investigation summary: this complaint was found to have two issues : issue #1 - robot ran into the post of the patient array near the clamp.Issue #2 - the camera had to be positioned in the anesthesia area making it hard to keep the patient sterile as well as capture the arrays.Issue #1 - robot ran into the post of the patient array near the clamp.The investigation confirmed "robot ran into the post of the patient array near the clamp." however, the tool holder ran into the connector of the patient array (not the post).The investigation was conducted by the hw and sw team.The investigation showed the patient array exclusion zones were not violated by the software and the software functioned as intended.In the current technical solution, the exclusion zones are defined based on the position of the spheres of the patient array that do not enable to check specific zones of in the 3d space linked to the patient array like the connector.The system responded appropriately to the collision, the arm was stopped and the user was notified via pop-up of the collision.Based on the investigation, an assessment in the quality system for a design improvement has been opened.The user indicated that there was no negative impact to the patient outcome and no patient harm.Issue #2 - the camera had to be positioned in the anesthesia area making it hard to keep the patient sterile as well as capture the arrays.The investigation did not confirm "making it hard to keep the patient sterile".The investigation confirmed "the camera had to be positioned in the anesthesia area making it hard to capture the arrays".The investigation was conducted by the hw and sw team.The investigation showed the user did not follow the ifu or setup recommendation for thoraco-lumbar screw placement, which led to conflicts between the anesthesia area and camera station.(ifu page 114 where the position for thorocolumbar cases is recommended to be at the feet).Based on the investigation the most probable root cause for the issue can be tied to user error.The user indicated that there was no negative impact to the patient outcome and no patient harm.Root cause: issue #1 - robot ran into the post of the patient array near the clamp.Based on the review and analysis of log files, the most probable cause of the reported issue is an inappropriate software design on the definition of the patient array exclusion zones.This software issue has been addressed in a non-conformance.Issue #2 - the camera had to be positioned in the anesthesia area making it hard to keep the patient sterile as well as capture the arrays.Based on the review and analysis of log files, the allegation of keeping the patient sterile was not confirmed.The most probable cause of the reported issue is a not most appropriate or setup for the given indication.Based on the investigation the most probable root cause for the issue can be tied to user error.Additional complaint information monitoring for potential safety signals is conducted through complaint trending as part of post market surveillance.Device history review (dhr): no manufacturing record evaluation required as the issue is software design related.If information is obtained that was not available for the initial medwatch, a follow-up medwatch will be filed as appropriate.
|