Revolution Ascend
K213938GE Healthcare Japan Corporation · cleared 2022-02-04 · product code JAK · Radiology
Premarket evidence — what FDA accepted
source quote (p.6)
“The Revolution Ascend is a head and whole-body CT system composed of a gantry, patient table, operator console with a host computer, power distribution unit, and interconnecting cables. The system also includes image acquisition and reconstruction hardware/software, general system software, accompanying documents, and associated accessories/interconnections. The proposed device carries over all the features, options and specifications of the predicate device, including the Deep Learning Iterative Recon (DLIR) cleared via K212067 without change.”
source quote (p.6)
“The proposed device carries over all the features, options and specifications of the predicate device, including the Deep Learning Iterative Recon (DLIR) cleared via K212067 without change.”
Validation studies (1)
Bench
sample size not stated
endpoints: overall system performance; image quality equivalence
standards: AAMI/ANSI ES 60601-1, IEC 60601-1 Ed. 3.1, IEC 60601-1-2 Ed 4.0, IEC 60601-1-3 Ed 2.1, IEC 60601-2-28 Ed 3.0, IEC 60601-2-44 Ed. 3.2, IEC 61223-3-5 Ed. 2.0, NEMA XR-25, NEMA XR-26, NEMA XR-28, 21 CFR Subchapter J
Reported performance (0 observations)
FDA source did not state a quantitative performance metric — non-reporting is itself the signal.
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
- recall_reason_pattern
Software/algorithm-related recall in product code JAK (GE Medical Systems, LLC, initiated 2026-03-26): "GE HealthCare has become aware of a potential security vulnerability impacting AW Server deployed via Edison Health Link (EHL) based CT Smart Subscription used in conjunction with " Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98738
- recall_reason_pattern
Software/algorithm-related recall in product code JAK (PHILIPS MEDICAL SYSTEMS, initiated 2026-03-07): "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" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98588
- recall_reason_pattern
Software/algorithm-related recall in product code JAK (Siemens Medical Solutions USA, Inc, initiated 2025-12-19): "To remove the software applications from certain CT systems as the applications have not received FDA 510(k) clearance." Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98206
- recall_reason_pattern
Software/algorithm-related recall in product code JAK (PHILIPS MEDICAL SYSTEMS, initiated 2025-09-25): "Issue 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/Axia" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:97699
- recall_reason_pattern
Software/algorithm-related recall in product code JAK (Philips North America Llc, initiated 2025-05-29): "Devices with affected software may experience two unintended motion issues that may lead to contact between the Gantry or table with the operator or patient, along with additional " Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:97010
- recall_reason_pattern
Software/algorithm-related recall in product code JAK (, initiated 2025-05-23): "Due to a software bug the robotic arm may incorrectly guide the instrument compared to the planning defined by user." Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:96967
- …and 3 more.
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).