|
It was reported that when using the bd pyxis¿ es server multiple discontinued orders continued to appear under admitted and discharged patients.Patient profiles were not displayed correctly in pyxis, particularly for older patient records.The issue affected multiple patients across multiple pyxis devices, requiring users to use workarounds to access medications.The issue occurred after corrective actions for a corrupted file were performed, and orders were not processing correctly following the update.Ephi patient details were provided for investigation.The customer stated that this malfunction caused a delay in dispensing the medications to the patient.However, there were no adverse events or injuries reported based on this event.
|
|
A review of the complaint history for sn (b)(6) was performed in salesforce which did not locate similar complaint(s) with the same failure mode for this serial number.A review of the device history record for sn (b)(6) was performed from the date of manufacture, 17-oct-2023 and confirmed that this device was not previously returned for servicing and there were no production failures which correlates to the customer reported issue.Upon investigation of the actual device used in this incident, it was determined that the device's admit discharge transfer (adt) discharge messages could not be verified as received for the affected patients, and order discontinuation messages were not received from the source system for the affected orders.A technical support specialist (tss) reviewed the reported patient visibility and active order concerns, validated that carefusion coordination engine (cce) processing and interface services were functioning normally with no message backlog, analyzed database records and message traces, and confirmed that the expected admission, discharge, and order discontinuation messages were not received for the affected patients and orders.Further investigation identified that the product support engineer (pse) had been restored from the 08/19 backup as part of the disaster recovery effort, causing previously discontinued orders to reappear as active.Tss reviewed related cases, collaborated with internal resources, and determined that the issue was not caused by es or cce processing, but was associated with missing source-system messages and restored historical data.Existing interface team efforts were already in progress under related cases to assist with discontinuing the affected orders and coordinating resolution with the customer.The system functioned as intended after the technical support specialist troubleshot the device.
|