Authorized purpose: Revolution Ascend produces axial, cine, helical, cardiac, and gated CT images from X-ray transmission data with or without contrast, with post-processing and analysis for head, whole-body, cardiac, and vascular diagnosis, therapy planning, guidance, and monitoring.
Clinical role
CT acquisition, reconstruction, visualization, image processing, and examination-planning support under professional review.
Images and patients
CT/CTA · Head, whole body, cardiac, and vascular anatomy
Key limitation
Keep in mind: Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: Revolution Ascend produces axial, cine, helical, cardiac, and gated CT images from X-ray transmission data with or without contrast, with post-processing and analysis for head, whole-body, cardiac, and vascular diagnosis, therapy planning, guidance, and monitoring.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head, whole body, cardiac, and vascular anatomy Input: X-ray transmission or projection data acquired under supported patient, protocol, contrast, dose, and reconstruction conditions.
Who uses it?Intended users: Qualified CT technologists and trained interpreting or treating physicians.
What does the software produce?Output: Cross-sectional CT images, reformats, measurements, quantitative results, and planning datasets for professional review.
What is its most important limitation?Key limitation: Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
Clinical takeaway. Clinical role: Revolution Ascend produces axial, cine, helical, cardiac, and gated CT images from X-ray transmission data with or without contrast, with post-processing and analysis for head, whole-body, cardiac, and vascular diagnosis, therapy planning, guidance, and monitoring.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports only non-clinical testing: risk management, software verification and validation, and image quality evaluation, including general IQ performance testing per IEC 61223-3-5 Ed. 2, a phantom-based IQ comparison with the predicate, and re-substantiation of DLIR imaging performance on the subject device. Non-clinical bench test results demonstrated that the subject device performs equivalently to the predicate. Results are as reported in the FDA submission, not independent validation.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
Revolution Ascend produces axial, cine, helical, cardiac, and gated CT images from X-ray transmission data with or without contrast, with post-processing and analysis for head, whole-body, cardiac, and vascular diagnosis, therapy planning, guidance, and monitoring.
Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
The exact FDA document reports only non-clinical testing: risk management, software verification and validation, and image quality evaluation, including general IQ performance testing per IEC 61223-3-5 Ed. 2, a phantom-based IQ comparison with the predicate, and re-substantiation of DLIR imaging performance on the subject device. Non-clinical bench test results demonstrated that the subject device performs equivalently to the predicate. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The verification and validation testing have been successfully completed as required by design control procedures under GE Healthcare’s quality system." … "This includes risk management, software verification and validation testing as well as image quality performance evaluation using well established metrics and methods.". Read from the exact FDA decision document on 2026-11-14.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
The exact FDA document reports only non-clinical testing: risk management, software verification and validation, and image quality evaluation, including general IQ performance testing per IEC 61223-3-5 Ed. 2, a phantom-based IQ comparison with the predicate, and re-substantiation of DLIR imaging performance on the subject device. Non-clinical bench test results demonstrated that the subject device performs equivalently to the predicate. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "The verification and validation testing have been successfully completed as required by design control procedures under GE Healthcare’s quality system." … "This includes risk management, software verification and validation testing as well as image quality performance evaluation using well established metrics and methods.". Read from the exact FDA decision document on 2026-11-14.
No exact submission-linked sensitivity endpoint with a verified population, threshold, tested version, and source was promoted.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact submission-linked specificity endpoint with a verified population, threshold, tested version, and source was promoted.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K213938 FDA evidence package for Revolution Ascend
DesignFDA 510(k) decision evidence package reviewed for exact submission identity and labeled scope
PopulationLabeled population and configuration described in the K213938 FDA decision material
Scopeexact submission
Tested versionRevolution Ascend configuration described in K213938
IndependenceSponsor or vendor study
K213938
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
2 exact-submission FDA recall records matched K213938 in the 2026-09-02 openFDA snapshot. Confirm affected model, version, units, correction, and current manufacturer instructions locally. FDA recall Z-2149-2026 is Open, Classified for Revolution Ascend, computed tomography, Model Numbers 6969000-100 and 6969000-300. FDA reason: 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 certain Revolution Apex, Revolution Ascend, and Revolution CT systems. FDA action: An URGENT MEDICAL DEVICE CORRECTION notification letter dated 3/26/26 was sent to customers. Actions to be taken by Customer/User Pending corrections by GE HealthCare, you can continue to use your system by following security and cybersecurity best practices. Before the interim solution (see Product Correction section below) is applied, please follow the instructions below as identified in the respective CT system User Manuals: CAUTION: 3D or slab reconstructions provide additional supplemental information, complementing diagnosis that should be based on classical techniques. WARNING: Do not use 3D or slab views only to perform any measurements (distance, angle, region of interest, report cursor, area, volume, etc.). Always check measurement points position and refer to 2D baseline views (acquisition images or reformatted images of minimal thickness) to confirm measurements. Please ensure all potential users in your facility are made aware of this safety notification and the recommended actions. Please retain this document for your records. Please complete and return the attached acknowledgement form electronically via (https://gehealthcare-svc.my.site.com/publicForm/s/?formId=aGjUr000002jnD7) or print, fill out manually, scan and email to recall.23015@gehealthcare.com Product Correction GE HealthCare will correct all affected products at no cost to you in two steps. A GE HealthCare representative will contact you to arrange for an interim solution to deactivate AW Server authentication through the CT system on the EHL-based Smart Subscription, and later, to install a CT software update. Note: With the interim solution, all alternative authentication mechanisms (direct application launch from CT console user interface, login using users defined in AW Server... FDA recall Z-0605-2025 is Open, Classified for GE Healthcare Revolution Ascend, Model number 6969000-100; X-ray/computed tomography system. FDA reason: GE HealthCare has become aware of a potential issue on certain Discovery, Optima, Revolution series CT systems, and certain operator console upgrades that can result in rotated CT images. Particularly with helical, cine, and cardiac (if applicable) scan modes, after the first image of an exam, each subsequent image can be rotated by an increasing amount. The amount of progressive image rotation is dependent on the gantry speed and the duration of the scan. The final image in the exam can be rotated up to a maximum of ~56 degrees. The entire anatomy rotates as a whole by equal degrees, without distortion, and the anatomical positioning and z-axis of the images remains correct. Small degrees of image rotation might not be noticed. If image rotation is noticed and necessitates a rescan of the patient, the same image rotation will reoccur. FDA action: GE HealthCare issued an URGENT MEDICAL DEVICE notice to its consignees on 11/05/2024 via mailing using a traceable means. The notice explained the issue, potential safety issue, and requested the following actions be taken: " You can continue to use your system. When utilizing helical, cine, and cardiac scan modes, review the image data set for any potential rotation. When using these modes during interventional procedures or radiation therapy planning, adhere to standard clinical quality checks and workflows. If image rotation is detected, consult with the physician to determine whether a rescan is necessary or if the images need to be corrected during post-processing to ensure accurate interpretation and planning. Please ensure all potential users in your facility are made aware of this safety notification and the recommended actions." A GE HealthCare representative will contact the consignee to arrange for the correction. For questions or concerns: please contact GE HealthCare Service at 1-800-437-1171 or your local Service Representative.
FDA source
Exact FDA submission
Checked 2026-09-04
Each published event was manually matched to the exact FDA submission and affected product or version; a recall does not establish an AI-algorithm defect or current site exposure unless the event states that scope.
Native exact-submission identifier match from the openFDA candidate snapshot accessed 2026-09-04 with source snapshot date 2026-09-02. Source URL: https://api.fda.gov/device/recall.json?search=product_res_number.exact%3A%22Z-2149-2026%22&limit=1. This does not establish exact installed serial, lot, unit, or software-version applicability. The FDA record does not establish an AI-algorithm defect unless it says so.
Native exact-submission identifier match from the openFDA candidate snapshot accessed 2026-09-04 with source snapshot date 2026-09-02. Source URL: https://api.fda.gov/device/recall.json?search=product_res_number.exact%3A%22Z-0605-2025%22&limit=1. This does not establish exact installed serial, lot, unit, or software-version applicability. The FDA record does not establish an AI-algorithm defect unless it says so.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: X-ray transmission or projection data acquired under supported patient, protocol, contrast, dose, and reconstruction conditions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish a complete local integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Cross-sectional CT images, reformats, measurements, quantitative results, and planning datasets for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Cross-sectional CT images, reformats, measurements, quantitative results, and planning datasets for professional review.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
GE HealthCare's Product Security Portal is described as a credentialed global portal giving customers security updates, vulnerability status and required actions for GE HealthCare products potentially impacted by critical vulnerabilities, plus historical patch views; GE HealthCare references its Cybersecurity Risk Management System and publishes a Coordinated Vulnerability Disclosure Statement for reporting vulnerabilities in GE HealthCare products.
Vendor-wide
Checked 2026-10-26
Vendor statement, not an attestation. Identity bridge: GE HealthCare's own offices page on gehealthcare.com names GE HealthCare Japan Corporation. Corporate program statement; portal content is credentialed; exact-release scope is not established.
Only qualified ct technologists and trained interpreting or treating physicians should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in reviewed public material; productivity or value claims require local evidence.
Monitor by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. An exact-submission recall match exists; confirm affected model, version, units, correction, and completion status before acceptance.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-04Last searched
27Fields reviewed
13Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. 2 FDA recall candidates were manually reviewed: 2 published and 0 rejected as a neighboring or otherwise inapplicable version. Native FDA recall identifiers produced 2 postmarket candidate records; 2 have been reviewed (2 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, acr ai central product, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish a complete local integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Installation timeline: Not yet reviewed
Monitoring: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision and checked recall snapshot do not establish a complete local postmarket monitoring protocol. Track version, population, anatomy, protocol, input quality, edits, failures, repeats, downstream effects, downtime, incidents, recalls, and updates locally.
Authorized purpose: Deep Learning Image Reconstruction is a deep-learning reconstruction method that produces cross-sectional images of the head and whole body from X-ray transmission data acquired at different angles and planes, including axial, helical or volumetric, and cardiac acquisitions for all ages. It can be used for head, whole-body, cardiac, and vascular CT applications.
Authorized purpose: An extension for syngo.via that assists trained physicians with automated and semi-automated analysis, visualization and reporting of cardiac CT angiography volume datasets for coronary-lesion evaluation, documentation, follow-up and treatment planning.
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.