The customer reported that the patient information center ix system was down hospital wide.This report is based on information provided by philips remote service engineer (rse) and has been investigated by the philips complaint handling team.The device was reported to be in use on a patient, but no adverse event to patient or user was reported.The following functional tests were performed: the rse tested the connection to the surveillance from the server using hostname and ip address which was successful.The rse then tested the dns name and ip address, and they were successful.The cpu was then checked, and a spike was found around 11:55pm to 00:08am local time on the server.Results of functional testing indicate the host was communicating with the server, but the return time was in wait time and that took a longer time for some of the host to connect due to time wait.Based on the information available and the testing conducted, the cause of the reported problem was a cpu spike on the primary server.The reported problem was confirmed.Based on the information available and results of additional analysis further action has been initiated.A review of the risk management file was performed and determined that while philips devices provide mitigations related to the loss of centralized wireless monitoring (ie ¿no central mon¿ inop, visual and audible tones, local monitoring for mx40), a malfunction that leads to the loss of monitoring for numerous patients using mixed wireless devices may result in a delayed response to an individual patient requiring emergent care.The device was operational after the rse rebooted all the surveillance and the overview.After the reboot was performed all the surveillance started connecting, and once connected they were going into service mode, the rse reconnected to monitoring mode resolving the issue.The investigation concludes that no further action is required at this time.
|