|
Siemens healthcare completed the investigation of the reported event.The investigation was performed based on expert discussions considering the complaint description, customer service reports, system history simulation, and system log files.It was initially reported that during a system check, the collimator of plane b was misaligned after a collision with the table.During the on-site service intervention, it was determined that the collimator rotation potentiometer was damaged, indicating misalignment of the collimator.After the replacement of the malfunctioning potentiometer, the system worked as intended again.Investigation of the log file revealed that the collision occurred during an automatic run while the user moved the table manually in longitudinal and transversal direction.Thereby the collimator of plane b touched the table.The proximity switch of the collimator was activated, and further movement was instantly blocked.To keep the probability of a collision to a minimum, a collision computer continuously monitors the positions of all integrated components of the system with respect to one another and the room.The collision computer detects when defined distances are violated.Since the collimator is normally very close to the patient it is possible that the collimator could potentially contact the patient or the table.Therefore, the collimator is equipped with proximity switch collision sensors.For an automatic run, the movement path is calculated to keep a proper distance to the objects.But as the customer moved the table, the table came into the pathway of the collimator.However, the collision calculator is still working as intended but there is no recalculation of the path for the system to reach its target.Due to the described behavior, the collimator touched the table.This scenario could be reproduced in the factory.However, the simulation could not explain how or why the potentiometer was damaged.It is likely that the functionality of the potentiometer was already slightly impaired before the incident took place.The collision happened during user-controlled system movement.There is no indication for an unintended movement of the system.Collision controls are in place, active and effective.The operator manual contains adequate instructions about system movement and how the operator can avoid a collision.To avoid this kind of scenario, the user should deactivate the automatic run, move the table, and start the automatic run again.The incident described in the adverse event is not classified as a reportable event after a thorough investigation.Neither serious injury, death, nor unexpected prolonged hospitalization of the patient or other person occurred or is to be expected, even if the incident recurs.H11 corrected data: b2: "other or serious or important medical events" was checked in error in the initial report submitted to the fda on september 28, 2022.This field should have been blank.G2: report source "user facility" should not have been checked in the initial report.This was not a user facility mdr.Report source "health professional" should have been checked.Report source "other" should have been checked and japan listed in the corresponding field.H3: device had not been evaluated by manufacturer when the initial report was submitted.This field should have been checked "no" in the initial report.
|