Additional information has been provided to siemens on december 20, 2019 that the patient's death was not caused by the siemens system.As this event is under investigation, a root cause has not yet been determined.A supplement report will be filed upon completion of the investigation.
|
Siemens has completed an investigation of the reported event.The root cause was determined to be a hardware error.The incident described in the complaint is was investigated as two claims: claim1: sensis dmc system frozen: the customer claimed the system froze for 7-8 minutes during exam, however, log files show that the system froze for 3,5 and 4 minutes during the procedure.There were no waveforms on the dialog monitor computer (dmc) and real time computer (rtc) during the issue.The system was able to recover from the error by itself and the user continued the procedure on the sensis.Claim2: patient death during the procedure: after the issue occurred the user continued the study for around 50 minutes and then performed closing of the study.There were user actions on the sensis system once the system recovered from error and in the logs we can see that there were hard rate alarm events being created with valid hard rate values which indicates that the patient was alive after the initial dmc freeze.Therefore, vital sign monitoring was available prior to and at the time of the patient death and the user would have been aware of a decline in the patient's health.As per discussions between the service technician and the physician who performed the procedure, the sensis issue did not cause or contribute to the patient death.The main permanent storage device on the sensis dmc-pc is a solid state drive (ssd), and the application runs off of this drive.If this ssd becomes non-functional, the sensis user interface becomes frozen.The user must wait a few minutes for the system to recover and continue working normally.As the ssd was not available immediately, the service technician replaced the full hp system on site to resolve the issue.The manufacturer is not considering further actions resulting from this event as no systematic error has been recognized.
|