510(k) Report

510(k) · Cleared

Recalled · Class II · 2026

Philips Incisive CT

K212441510(k) TraditionalCleared Apr 27, 2022266-day reviewClass II21 CFR 892.1750Recalls 17

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

Philips Healthcare (Suzhou) Co., Ltd. · JAK System, X-Ray, Tomography, Computed

Cleared on Apr 27, 2022 as substantially equivalent to K160743 (Philips Medical Systems (Cleveland), Inc., 2016) and 1 other predicate after a 266-day review. Its family tree reaches back 7 generations to 1993. 3 later devices descend from it. It has been recalled 17 times.

Decided
Apr 27, 2022
Review
266 days
Class
Class II
Product code
JAK
Recalls
17
Predicates
2

Its longest line of descent runs back 7 generations to K930090 (1993). 12 ancestors in all. 3 later devices descend from it, 2 citing it directly.

  1. Root · 7 generations backK930090 HelicatElscint, Inc. · 1993
  2. 6 generations backK961464 Select/SPElscint, Inc. · 1996 · Recalled
  3. 5 generations backK982060 Volumax CT Imaging SystemElscint, Inc. · 1998
  4. 4 generations backK012009 MX8000 Idt CT SystemMarconi Medical Systems, Inc. · 2001 · Recalled
  5. 3 generations backK033326 Philips Plus Computed Tomography SystemPhilips Medical Systems, Inc. · 2003 · Recalled
  6. 2 generations backK160743 Philips Ingenuity CTPhilips Medical Systems (Cleveland), Inc. · 2016 · Recalled
  7. 1 generation backK180015 Philips Incisive CTPhilips Healthcare (Suzhou) Co., Ltd. · 2018 · Recalled
  8. This deviceK212441 Philips Incisive CTPhilips Healthcare (Suzhou) Co., Ltd. · 2022
  9. Descendant · cites it directly · 1 of its ownK232491 CT 5300Philips Healthcare (Suzhou) Co., Ltd. · 2024 · Recalled
  10. Descendant · 2 generations on · 0 of its ownK252992 CT Rembra RT; CT Areta RT; CT RembraPhilips Healthcare (Suzhou) Co., Ltd. · 2026
  11. Descendant · cites it directly · 0 of its ownK223311 Philips CT 3500Philips Healthcare (Suzhou) Co., Ltd. · 2022

Most influential descendants

Showing 3 of 3 · See all
  • K232491CT 5300Philips Healthcare (Suzhou) Co., Ltd. · 2024 · cites it directly1descendant
  • K252992CT Rembra RT; CT Areta RT; CT RembraPhilips Healthcare (Suzhou) Co., Ltd. · 2026 · 2 generations on0descendants
  • K223311Philips CT 3500Philips Healthcare (Suzhou) Co., Ltd. · 2022 · cites it directly0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−7K930090HelicatElscint, Inc.1993—
−6K961464Select/SPElscint, Inc.19963
−5K982060Volumax CT Imaging SystemElscint, Inc.1998—
−4K012009MX8000 Idt CT SystemMarconi Medical Systems, Inc.200161
−3K033326Philips Plus Computed Tomography SystemPhilips Medical Systems, Inc.2003131
−2K160743Philips Ingenuity CTPhilips Medical Systems (Cleveland), Inc.201624
−1K180015Philips Incisive CTPhilips Healthcare (Suzhou) Co., Ltd.201823
0 (this device)K212441Philips Incisive CTPhilips Healthcare (Suzhou) Co., Ltd.2022—
+1K232491CT 5300Philips Healthcare (Suzhou) Co., Ltd.20245
+2K252992CT Rembra RT; CT Areta RT; CT RembraPhilips Healthcare (Suzhou) Co., Ltd.2026—
+1K223311Philips CT 3500Philips Healthcare (Suzhou) Co., Ltd.2022—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
199420
199510
199710
200110

Descendants by year cleared

Year clearedDevicesWith a Class I recall
202210
202410
202610
FIG. 1 — Lineage of K212441, 1993–2026Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.

Planning a device in JAK? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

Top candidate predicates for a new JAK device

  1. #1 K230223 iCAC Devicescore 23.5 · 12 generations · no Class I recall
  2. #2 Held for the reportin the report
  3. #3 Held for the reportin the report
Get a 510(k) Report

What was it cleared against? (2)

Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.

TypeNumberDeviceApplicantDecidedRecalls
*K160743Philips Ingenuity CT
Summary page 4
…Philips Medical Systems (Cleveland), Inc. 510(k) Clearance: K160743 Classification Regulation: 21CFR 892.1750 Classification name:…
Philips Medical Systems (Cleveland), Inc.201624
*K180015Philips Incisive CT
Summary page 4
…Philips Healthcare (Suzhou) Co., Ltd. 510(k) Clearance: K180015 Classification Regulation: 21CFR 892.1750 Classification name:…
Philips Healthcare (Suzhou) Co., Ltd.201823

Also cleared against K160743: 2 other devices →

What descends from it? (3)

2 later devices cite it directly; ranked here by how many devices descend from each in turn.

NumberDeviceApplicantDecidedDescendants
K232491CT 5300Philips Healthcare (Suzhou) Co., Ltd.20241
K223311Philips CT 3500Philips Healthcare (Suzhou) Co., Ltd.20220

Has anything in its family been recalled? (0 Class I)

Recalls of this device

DateClassRecallRoot causeReason
Jun 26, 2026Class IIZ-2988-2026Radiation Control for Health and Safety ActPotential of failing to trigger clinical scan during Bolus Tracking.
Dec 3, 2025Class IIZ-1003-2026Radiation Control for Health and Safety ActPotential for incomplete scan due to unstable connection inside of floating sensor.
Oct 29, 2025Class IIZ-0881-2026Under Investigation by firmIf the screws of tube heat exchanger on the rotating scanner are not tightened well after replacing. This component may become detached and make contact with other components located within the Incisive CT systems during rotation. Other…
Sep 25, 2025Class IIZ-0375-2026Under Investigation by firmIssue 1: The potential for unintentional continued gantry/couch movement when a specific button series is used requiring use of manual stop. Issue 2. When performing a helical/Axial scan with ORI (Dose Right index)/ DOM (Dose Modulation)…
Sep 25, 2025Class IIZ-0376-2026Under Investigation by firmIssue 1: The potential for unintentional continued gantry/couch movement when a specific button series is used requiring use of manual stop. Issue 2. When performing a helical/Axial scan with ORI (Dose Right index)/ DOM (Dose Modulation)…
Sep 25, 2025Class IIZ-0377-2026Under Investigation by firmIssue 1: The potential for unintentional continued gantry/couch movement when a specific button series is used requiring use of manual stop. Issue 2. When performing a helical/Axial scan with ORI (Dose Right index)/ DOM (Dose Modulation)…
Apr 15, 2024Class IIZ-1872-2024Under Investigation by firmMetal mounting box on the rotating scanner on rotor (heat change box) located within the Incisive CT system, may become compromised, resulting in potential contact with other gantry components located within the Incisive CT system during…
Dec 7, 2023Class IIZ-0719-2024Component design/selectionIf the Patient Interface Monitor (PIM) Cable is plugged/unplugged frequently as part of daily operation, the connector and wire may disconnect from the welding point, which may result in intermittent loss of the ECG signal. Loss of ECG…
Aug 2, 2023Class IIZ-2520-2023Radiation Control for Health and Safety ActPhilips has identified three software issues with compliance concerns to Subchapter J: Issue 1: Coronary Computed Tomography Angiography (CTA) scan may not be triggered at the optimal time. Issue 2: Use of aborted surview for scan…
Apr 12, 2023Class IIZ-1625-2023Software designPotential for Incorrect Image Orientation resulting images may be flipped or reversed result in misdiagnosis, incorrect treatment of a condition, or additional radiation exposure if a rescan is required
Apr 12, 2023Class IIZ-1623-2023Software designPotential for Incorrect Image Orientation resulting images may be flipped or reversed result in misdiagnosis, incorrect treatment of a condition, or additional radiation exposure if a rescan is required
Apr 12, 2023Class IIZ-1622-2023Software designPotential for Incorrect Image Orientation resulting images may be flipped or reversed result in misdiagnosis, incorrect treatment of a condition, or additional radiation exposure if a rescan is required
Apr 12, 2023Class IIZ-1624-2023Software designPotential for Incorrect Image Orientation resulting images may be flipped or reversed result in misdiagnosis, incorrect treatment of a condition, or additional radiation exposure if a rescan is required
Mar 20, 2023Class IIZ-1585-2023Under Investigation by firmMulti-Function Foot Switch Unload Pedal Foot Entrapment-Pressing the Unload Pedal of the foot switch to perform the unload function may cause entrapment of the operator's foot and injury
Mar 20, 2023Class IIZ-1586-2023Under Investigation by firmMulti-Function Foot Switch Unload Pedal Foot Entrapment-Pressing the Unload Pedal of the foot switch to perform the unload function may cause entrapment of the operator's foot and injury
Dec 23, 2022Class IIZ-0640-2024Software designMultiple software issues which have the potential to lead to misdiagnosis due to image artifacts or incorrect image orientation labels, or the need for a CT rescan. These include: 1. Artifacts may occur on perfusion images, 2. Orientation…
Mar 29, 2022Class IIZ-0576-2024Software designThree software issues affecting incorrect image display, error interpreting patient images due to image reporting, and patient exposure to incorrect image/function during clinical use.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 29 years and passes through 5 companies; a new generation was cleared every 3.0 years on median.
  • 6 of the 12 ancestors have a recall of any class.
  • Of its descendants, K232491 (Philips Healthcare (Suzhou) Co., Ltd., 2024) has gone furthest, with 1 descendant of its own.
  • 2 other devices also cite its predicate K160743.

How does its category compare?

All JAK devices

JAK System, X-Ray, Tomography, Computed: FDA decisions, review times, recalls and adverse event reports over 20 years. 2022, this device’s year, is highlighted.

FDA decisions per year · JAK

27in 2025

2007: 142008: 262009: 152010: 72011: 162012: 282013: 172014: 302015: 302016: 252017: 292018: 242019: 282020: 302021: 202022: 302023: 272024: 262025: 272026 (partial year): 21
2007high 30 (2014) · low 7 (2010)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · JAK

141in 2025

2007: 27 days median2008: 42 days median2009: 31 days median2010: 92 days median2011: 155 days median2012: 121 days median2013: 132 days median2014: 200 days median2015: 140 days median2016: 129 days median2017: 96 days median2018: 114 days median2019: 94 days median2020: 112 days median2021: 145 days median2022: 131 days median2023: 139 days median2024: 141 days median2025: 141 days median2026 (partial year): 167 days median
2007high 200 (2014) · low 27 (2007)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · JAK

17in 2025

2007: 112008: 162009: 292010: 512011: 342012: 232013: 112014: 102015: 282016: 442017: 332018: 102019: 52020: 82021: 152022: 92023: 92024: 202025: 172026 (partial year): 23
2007high 51 (2010) · low 5 (2019)2026

Class I (0 since 2007) Class II/III not classified

Adverse event reports per year · JAK

219in 2025

2007: 762008: 1202009: 1052010: 1192011: 2052012: 1922013: 4142014: 3082015: 4542016: 3652017: 3382018: 5432019: 2332020: 1772021: 2612022: 1992023: 3102024: 2122025: 219
2007high 543 (2018) · low 76 (2007)2025

MAUDE reports naming product code JAK, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
200714271176
2008264216120
2009153129105
201079251119
20111615534205
20122812123192
20131713211414
20143020010308
20153014028454
20162512944365
2017299633338
20182411410543
201928945233
2020301128177
20212014515261
2022301319199
2023271399310
20242614120212
20252714117219
20262116723—

What is it indicated for?

The Incisive CT is a Computed Tomography X-Ray System intended to produce images of the head and body by computer reconstruction of x-ray transmission data taken at different angles and planes. These devices may include signal analysis and display equipment, patient and equipment supports, components and accessories. The Incisive CT is indicated for head, whole body, cardiac and vascular X-ray Computed Tomography applications in patients of all ages.…

Read the full statement (152 words)

The Incisive CT is a Computed Tomography X-Ray System intended to produce images of the head and body by computer reconstruction of x-ray transmission data taken at different angles and planes. These devices may include signal analysis and display equipment, patient and equipment supports, components and accessories. The Incisive CT is indicated for head, whole body, cardiac and vascular X-ray Computed Tomography applications in patients of all ages.

These scanners are intended to be used for diagnostic imaging and for low dose CT lung cancer screening for the early detection of lung nodules that may represent cancer*. The screening must be performed within the established inclusion criteria of programs / protocols that have been approved and published by either a governmental body or professional medical society.

*Please refer to clinical literature, including the results of the National Lung Screening Trial (N Engl J Med 2011; 365:395-409) and subsequent literature, for further information.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K212441: Philips Incisive CT.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K212441

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

Record history
  • FDA decision record loaded May 2, 2026
  • Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026