An outside united states (ous) siemens cse (customer service engineer) reported that the adm (atellica data manager with s/n: (b)(6), connected to dms (data management software), created an unknown patient id and replaced patient demographics with incorrect data and test results.Siemens investigated the event and noted the samples ran in the past, several months ago, and were archived as per system configuration.The customer noted no delay in testing and reporting results, and the event did not affect stat sample testing.The discordant results did not reach the customer lis (laboratory information system).On 11-dec-2023, siemens noted that results were sent from the ats1, causing dms to recognize them as unknown samples and create unknown patient ids.The samples were sent to adm, and it sent them to the lis with the real sample id but the unknown patient id.Since the samples already have a validated result on the lis, and no further results were requested, the system did not take the new results.Siemens is investigating the event.
|
A siemens cse (customer service engineer) reported that the adm (atellica data manager with s/n: (b)(6), connected to dms (data management software), created an unknown patient id and replaced patient demographics with incorrect data and test results.There are no known reports of patient intervention or adverse health consequences due to the event.
|
Siemens filed the initial mdr 2432235-2023-00339 on 27-dec-2023.Additional information on (28-feb-2024): siemens evaluated the information and confirmed that there was no atellica data manager (adm) malfunction and that the results were being sent from the atellica solution, as intended.The adm is working as intended, and there was no product problem.
|