Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-1324-2025

Spectral CT on Rails, Software Version Number 5.1.0 Recall

Spectral CT on Rails, Software Version Number 5.1.0, Model number: 728334;

FDA recall Class II

Ongoing

FDA lists this Class II recall for Spectral CT on Rails, Software Version Number 5.1.0. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1324-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Feb 28, 2025
FDA report date
Mar 19, 2025
Quantity in commerce
1 unit
Distribution
See key details
FDA cause
Under Investigation by firm

What is being recalled?

Spectral CT on Rails, Software Version Number 5.1.0, Model number: 728334;

Affected model & UDI checker

Search the exact identifiers published for Z-1324-2025.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
728334Spectral CT on Rails, Software Version Number 5.1.0Check source noticeNot specified
Not specifiedSpectral CT on Rails, Software Version Number 5.1.0Check source notice00884838103627
FDA code information

Software Version Number 5.1.0; Model number: 728334; UDI-DI: (01)00884838103627(21)1005; Serial Number (SN): 1005;

View the original FDA recall notice

Why was this product recalled?

Multiple problems identified with the software version leading to various scanning and image issues, and unintended device movement.

What actions did PHILIPS MEDICAL SYSTEMS NEDERLAND B.V. take?

On February 28, 2025 URGENT MEDICAL DEVICE CORRECTION letters were sent to customers. Actions that should be taken by the customer / user in order to prevent risks for patients or users. " You may continue to use your system(s) in accordance with the intended use and by following the recommendation listed below. " When you see the warning message No communication with table and C-arm. Avoid collisions, Proceed with caution., acknowledge the message by selecting OK and continue using the CT while observing with extra care, collision with the Gantry and C-arm can be avoided. " To protect the patient and the operator from a potential collision due to an automatic gantry motion during scan and plan box not updated during interventional procedure issues, follow the instructions mentioned in the IFU Section 4 Preparing for an Examination and Sub section Gantry Operation: o During all movements of the gantry (automatic and manual), keep the patient under continuous observation. o Take care to avoid pressing the patient against the gantry or between table parts, as well as to avoid disconnecting any infusion or resuscitation apparatus. o For all patient table types, take care when using attachments to avoid collision with the gantry. o Make sure that the patient is strapped securely to avoid dangling of the hands. Ensure that the patient is placed securely on the patient table and is not in danger of falling. o Auto scan means that automatic motions are expected without using the enable button. Ensure the patient table does not collide with the gantry during movement. o During studies, the gantry movements (if applicable) are automatic. Ensure enough clearance between the patient and the gantry. Before initiating the scan, perform manual movements to check the clearance. " To avoid cone beam auto correction artifacts: 1) Reduce the collimation to 32 for brain study, or reduce the collimation to 112 (or any value below 128) for body imaging, which will turn CBAC off. Refer t

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology