| Model Number |
00-1026-R |
| Medical Device Problem Code |
Operating System Becomes Nonfunctional (2996)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
04/13/2026
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
This report is based on information provided by philips remote service personnel and will be investigated by the philips complaint handling team.Philips received a complaint on the tempus pro indicating that when powering on the device an error "error-crc" occurred.The device was restarted, but the error continued.Following successful reinstallation of the software the device restarted as expected, however the error remained.A request for additional information regarding the incident has been sent and the response is not yet received.There was no report of actual harm reported with this complaint.
|
| |
|
Additional Manufacturer Narrative
|
|
Event date and become aware date updated to 13apr2026 due to information obtained.
|
| |
|
Event or Problem Description
|
|
This report is based on information provided by philips remote service personnel and has been investigated by the philips complaint handling team.Philips received a complaint on the tempus pro indicating that when powering on the device a "error-crc" (cyclic redundancy check error) occurred.The device was restarted, but the error continued.Following successful reinstallation of the software the device restarted as expected, however the error remained.Information obtained through good faith effort response indicated the device was not in use on a patient at the time of the incident.The incident occurred during a military exercise.No harm or impact occurred.
|
| |
|
Event or Problem Description
|
|
This report is based on information provided by philips remote service personnel and has been investigated by the philips complaint handling team.Philips received a complaint on the tempus pro indicating that when powering on the device a "error-crc" (cyclic redundancy check error) occurred.The device was restarted, but the error continued.Following successful reinstallation of the software the device restarted as expected, however the error remained.Information obtained through good faith effort response indicated the device was not in use on a patient at the time of the incident.The incident occurred during a military exercise.No harm or impact occurred.
|
| |
|
Search Alerts/Recalls
|