|
The following functional tests were performed: philips was notified on (b)(6) 2025, but all the logs from the event date (31 oct 2024) had been overwritten and the only logs that could be retrieved was the one collected by the customer.The field service engineer (fse) provided an analysis of those logs.For the event table for (b)(6) 2024 between 08:00 and 09:00.223 events, 0 events not transmitted, 22 escalations.The philips field service engineer, support (b)(6), philips technical manager in charge and the customer senior biomedical technician conducted performance verification testing onsite.The customer's alarm configuration of careevent was tested and verified.In addition, the review stated that the "auto remove ended events" feature was unchecked.As configured, this setting automated the deletion of completed events in the phone history, resulting in the disappearance of some events from the history.This could explain the customer's observations.After restarting the virtual server and checking the points stated in the service manual, it showed that the careevent system was operating per specifications.Alarms that are set to be sent to phones are being sent.Escalations are triggered after the configured time of one minute on the defined phones.Users designated for delegation are notified at the same time as first-level users.The system stops sending notifications if users are logged out or if the phone is running out of battery.Logout/reconnect notifications are generated on the phone and are found in the history.No malfunction was observed during the tests.Based on the information available and the testing conducted we were unable to replicate the reported problem.The reported problem was not confirmed.The device was confirmed to be operating per specifications and no failure was identified.The customer was provided with information from review.The investigation concludes that no further action is required at this time.If additional information is received the complaint file will be reopened.
|