Siemens had investigated the issue based on the information available at the time complaint received and determined to be not reportable to fda.Investigation ((b)(6) 2015): testing consists of viewing the files sent and identifying instances of samples identified as invalid_message and determining if they have the characteristics of the problem.These characteristics include presence of one or more of the following conditions: 1.Duplication of test results with one appearing out of the normal transmission sequence for the instrument.2.Test results missing one or more of the required fields - in most cases the test name (however, all required fields could be seen on instrument).Conclusion: both supporting communication logs for incident (b)(6) showed examples of both behaviors in samples sent at different times.This supports the proposed root cause of interaction between the software code when building the messages to be sent by the two channels.Further investigation on this issue revealed additional information.3.Potential for a record from one sample data set to be transmitted as a record on a different sample data set.However, this scenario has not been observed by customers and siemens has not been able to reproduce this scenario in-house and it is extremely unlikely to occur.Based on the additional information on this issue, siemens medical affairs determined this issue as a low health risk on june 15, 2015.Siemens performed retrospective review of all complaints associated with the issue to determine their medical device reporting eligibility.Siemens investigated the issue and has identified the root cause; mitigations will be implemented in new software version.There was no report of injury due to this event.
|