Philips Spectral CT on Rails. Recall
Philips Spectral CT on Rails. Model Number: 728334.
FDA recall Class II
Ongoing
FDA lists this Class II recall for Philips Spectral CT on Rails.. Review the affected identifiers, reported reason and manufacturer instructions below.
Recall at a glance
- Recall number
- Z-1825-2026
- Recall classification
- Class II
- Enforcement status
- Ongoing
- Initiation date
- Mar 7, 2026
- FDA report date
- Apr 22, 2026
- Quantity in commerce
- 3 systems
- Distribution
- See key details
- FDA cause
- Under Investigation by firm
What is being recalled?
Philips Spectral CT on Rails. Model Number: 728334.
Affected model & UDI checker
Search the exact identifiers published for Z-1825-2026.
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 number | Product | Lot scope reported | UDI / GTIN |
|---|---|---|---|
| 728334. | Philips Spectral CT on Rails. | Check source notice | 00884838103627 |
| 728334 | Philips Spectral CT on Rails. | Check source notice | Not specified |
FDA code information
Model Number: 728334. UDI: (01)00884838103627(21)1005, (01)00884838103627(21)1006, (01)00884838103627(21)1007. Software Version Number: 5.1.X. Serial Numbers: 1005, 1006, 1007.
Why was this product recalled?
Philips has identified three software issues: 1. During a continuous CT (CCT) scan, there is the potential that the Gantry could remain at the current scan position after pressing Go. 2. Potential where the message of Previous Surview Exists Select Previous Surview? <Yes> or <No> should display but does not appear. 3. After performing Surview and planning the Brain Helical acquisition by setting Brain Area DoseRight Index to increase the dose, there is the potential that the Define Head Area option in the context menu is grayed out.
These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.
What actions did PHILIPS MEDICAL SYSTEMS take?
Philips Medical notified consignees on about 03/07/2026 via letter. Consignees were instructed to identify any affected systems in inventory and specifically for each issue: 1. Issue #1: Ensure to follow the instructions mentioned in the IFU Section 4 Preparing for an Examination and Sub section Gantry Operation. 2. Issue #2: Avoid the Select Previous Surview Unavailable issue, manually remove the patient's middle name while importing the patient detail from HIS/RIS. 3. Issue #3: if Define Head Area option is grayed out with DoseRight Index (DRI) on, review the dose levels displayed on the User Interface, confirm and adjust the dose settings to appropriate levels before executing the scan as instructed in the IFU. Consignees were also instructed to complete and return the response form, to circulate the Urgent Medical Device Correction Letter to all users of the affected device so that they are aware of the issues, and retain the letter with affected system(s) until a solution is installed on each system; ensure the letter is in a place likely to be seen/viewed. Philips will contact each consignee to schedule a time for a Philips Field Service Engineer (FSE) to visit each site and install the solution to resolve the issues (reference FCO72800830).
Read the manufacturer action recorded by FDARecall timeline
Recall initiated by firm
FDA notice posted
FDA classification recorded
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
- FDA recall notice Z-1825-2026
- openFDA enforcement record · Source release Nov 11, 2026 · Retrieved Nov 21, 2026
- openFDA device recall record · Source release Nov 19, 2026 · Retrieved Nov 21, 2026
- FDA enforcement data
First stored snapshot of this source.
- 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