What the FDA actually posted
On September 1, 2026, the FDA posted four separate Class II recall records for Philips CT systems, filed under the same underlying issue. Philips's own language in the filings is consistent across all four: the company "identified an unintended radiation issue with the Philips IQon, iCT, Ingenuity, and Brilliance CT 64 systems that could affect the performance of the equipment." Philips initiated the correction on August 7, 2026, and distribution is listed as the US and US territories.
As Radiology Business reported, the affected platforms — IQon Spectral CT, the Brilliance iCT family, Ingenuity CT, and Brilliance CT 64 — are among the most widely installed CT platforms in US hospitals, which is why the recall reads as significant even though the FDA's public record doesn't disclose how many individual scanners are affected.
Critically, this is not a device-removal recall. Philips is correcting the issue with a free software update, delivered through an Electronic Product Radiation Correction notice, and is scheduling the update with customers directly rather than pulling machines from the field. The recall coverage is explicit that patients should not cancel medically necessary scans over the notice — delaying imaging for time-sensitive conditions carries its own risk.
The four recalls, side by side
Each affected platform got its own recall number because each runs a different software line. As of the posting date, the FDA listed all four as "Open, Classified" — meaning correction was underway but not complete across the installed base.
| System | Software line | FDA recall number |
|---|---|---|
| Brilliance iCT / iCT Upgrades / iCT SP | 4.1.10.x | Z-3040-2026 |
| IQon Spectral CT | 4.7.7.x | Z-3041-2026 |
| Ingenuity CT (Upgrades / China / Core 128 Elite) | 4.4.10.x | Z-3042-2026 |
| Brilliance CT 64-Channel / Upgrades | 4.1.10.x | Z-3043-2026 |
Source: FDA Medical Device Recall database records Z-3040-2026 through Z-3043-2026, posted September 1, 2026.
What "Class II" actually buys you
The FDA defines a Class II recall as one where a product "may cause temporary or medically reversible adverse health consequences," or where the probability of serious harm is remote — the middle of three severity tiers, below Class I (reasonable probability of serious injury or death) and above Class III (unlikely to cause any adverse health effect). That classification is why this recall generated a software patch and a customer notification rather than an urgent stop-use order.
That's the right regulatory outcome for the safety question. But "not urgent enough to stop scanning" and "zero operational impact" are two different claims. A software correction on an in-service CT console still typically means a scheduled visit from a field service engineer, a period where that unit isn't scanning patients, and validation testing before it's released back to the schedule. Multiply that across four platforms and however many individual scanners a given health system runs, and the rollout itself becomes a scheduling exercise — one that has to happen without a formal deadline pressuring it, since the FDA record sets no fixed completion date.
The angle that matters operationally: hardware down, reporting still owed
Imaging centers have handled hardware downtime before — a tube failure, a service contract lapse, a scheduled upgrade. The pattern is familiar: whatever scanner capacity is lost gets absorbed one of three ways. Patients get rescheduled to a later slot on the same machine once it's back online. They get diverted to a sister scanner or another site, if one exists. Or referring physicians and patients simply wait longer for the exam.
What doesn't shrink to match reduced scanner capacity is the reporting obligation. Every study that does get acquired — whether it's scanned on schedule, squeezed into a reopened slot after a service window closes, or shifted to a scanner that's now running above its normal volume to cover for one down for the update — still needs a read, a report, and a radiologist's signature on the same clinical timeline as before. A multi-platform, multi-facility software rollout with no fixed completion date is exactly the kind of event that produces uneven, bursty scan volume: quiet stretches while a unit is down, followed by a compressed backlog once it's validated and reopened.
That unevenness is a reporting-throughput problem before it's anything else. A fixed radiologist roster sized for average daily volume doesn't flex well against a burst — which is exactly the mismatch that already stretches turnaround times in normal operations, before a recall-driven scheduling shuffle adds variance on top of it.
Where AI-assisted reporting fits
This is a case where the fix belongs on the reporting side, not the imaging side. AI CT reporting doesn't touch the hardware recall at all — that's squarely Philips's and the FDA's lane. What it changes is how a center absorbs a volume burst once the scans do land: a foundation-model system can draft a structured, comprehensive report the moment a study lands in the queue, xAID's in-house radiologist reviews every preliminary, and it reaches the reading radiologist ready-to-sign rather than ready-to-dictate from a blank page. That compresses the part of the turnaround clock a center actually controls — the drafting and review step — so a burst of rescheduled studies doesn't automatically become a multi-day backlog. It's the same elasticity centers already reach for during ordinary demand spikes or when covering gaps with after-hours coverage — applied to a hardware-driven one instead.
Frequently asked questions
What did the FDA recall involving Philips CT scanners cover?
On September 1, 2026, the FDA posted four Class II recall records (Z-3040-2026 through Z-3043-2026) covering the Philips Brilliance iCT family, IQon Spectral CT, Ingenuity CT, and Brilliance CT 64. Philips identified an unintended radiation issue that could affect equipment performance and initiated the correction on August 7, 2026. The fix is a free software update, distributed in the US and US territories.
Do hospitals have to take the affected CT scanners out of service?
No. Philips is not removing the affected systems from the field. It is notifying customers and scheduling the software correction on-site, and coverage of the recall notes that patients should not cancel medically necessary scans over a recall notice. In practice, each scanner still needs a service window to receive and validate the update, and as of the recall posting the correction was listed as open — meaning not every affected unit had been updated yet.
What does an FDA Class II recall mean for patient risk?
The FDA defines a Class II recall as one where a product may cause temporary or medically reversible health consequences, or where the probability of serious harm is remote. It is the middle of the FDA's three severity tiers, below Class I (reasonable probability of serious injury or death) and above Class III (unlikely to cause any adverse health consequence).
How does a CT hardware recall affect radiology report turnaround times?
Not directly — the recall is a device-radiation issue, not a reporting issue. But when scanners go offline in shifts for a service update, or patients get shifted to fewer available machines, the studies that do get scanned tend to arrive in denser bursts. Reporting capacity, not scanner capacity, is what absorbs that unevenness, since a radiologist or reporting pipeline still has to turn around every study regardless of when in the day or week it was acquired.
Source: FDA Medical Device Recall database (records Z-3040-2026 through Z-3043-2026), Radiology Business, and Medical Daily. FDA recall classification definitions per the FDA's recalls background and definitions page. Figures are rounded as reported.