Skip to content
Lower risk Medical device recall · FDA · Published May 8, 2026

GE Healthcare AW Server 3.2 ext.6.5: Patient Image Mix-Up Risk

GE Healthcare recalls AW Server 3.2 ext.6.5 software due to potential patient image mix-ups causing misdiagnosis. Affected users should check product details and contact GE for updates.

🇺🇸 FDA recall #Z-2553-2026Medical deviceGE Medical Systems ›
Take action

Contact the company

Recalling firmGE Medical Systems SCS283 rue de la Miniere · Buc, France
✎ GovInfoNow plain-language explainer

GE Healthcare is recalling a specific version of their radiology software because it can display the wrong patient's images when users open applications. This could lead to misdiagnosis and incorrect treatment decisions if not fixed. Read more at govinfonow.com/recall/49194-ge-healthcare-aw-server-3-2-ext-6-5-patient.

Source Summary by GovInfoNow · govinfonow.com/recall/49194-ge-healthcare-aw-server-3-2-ext-6-5-patient · Updated August 10, 2026 · FDA enforcement record: FDA #Z-2553-2026

Cite this page

“GE Healthcare AW Server 3.2 ext.6.5: Patient Image Mix-Up Risk.” GovInfoNow, updated August 10, 2026. https://govinfonow.com/recall/49194-ge-healthcare-aw-server-3-2-ext-6-5-patient. Based on FDA recall #Z-2553-2026 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2553-2026%22&limit=1).

The FDA announced on May 8, 2026, that GE Medical Systems SCS is recalling its GE Healthcare AW Server 3.2 ext.6.5 Radiological Image Processing System due to a context synchronization issue. The hazard involves the system potentially displaying previous patient exams instead of the intended ones, which could lead to misdiagnosis or incorrect clinical decisions.

How to tell if you have it

  • GE Healthcare AW Server 3.2 ext.6.5; Radiological Image Processing System
  • UPC: 00840682102384

The hazard

According to the FDA, a context synchronization issue in AW Server 3.2 ext. 6.5 may cause an interactive application to open the previous patient's exam instead of the intended one when launched from the Web Client worklist. There is no system warning or error notification for this error. If unrecognized, a clinical user could review, interpret, or report images for the wrong patient, potentially leading to misdiagnosis, incorrect clinical decisions, and delayed or incorrect treatment.

Context

GovInfoNow's records show GE Medical Systems SCS has four other recalls on record since March 29, 2018. Other recent recalls of similar products include AWS (Sept. 5, 2025), GE Healthcare Allia IGS 5 Pulse X-ray Systems Recall (March 18, 2024), and GE Medical Systems Senographe Pristina X-ray Machine Recall (Dec. 26, 2023). Other recent recalls of similar products include GE Healthcare Centricity PACS Server V7 Recall (July 31, 2026), GE Healthcare Enterprise Archive V8 Software Recall (July 31, 2026), and GE Healthcare Workflow Core Services V8 Recall (July 31, 2026).

How to tell if you have this one

Check for the software version AW Server 3.2 ext.6.5. The product has a reference number (01)00840682102384(10)AWS03D02E6D5 and GTIN 00840682102384. This version was sold with GE Healthcare systems.

  • Brand
    GE Medical Systems
  • Product
    GE Healthcare AW Server 3.2 ext.6.5; Radiological Image Processing System
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Verify your software version is AW Server 3.2 ext.6.5 by checking the product details.

Where it went and when

Where it was distributed

Distributed nationwide, and outside the U.S.

Alaska: yesAKMaine: yesMEVermont: yesVTNew Hampshire: yesNHWashington: yesWAIdaho: yesIDMontana: yesMTNorth Dakota: yesNDMinnesota: yesMNIllinois: yesILWisconsin: yesWIMichigan: yesMINew York: yesNYRhode Island: yesRIMassachusetts: yesMAOregon: yesORNevada: yesNVWyoming: yesWYSouth Dakota: yesSDIowa: yesIAIndiana: yesINOhio: yesOHPennsylvania: yesPANew Jersey: yesNJConnecticut: yesCTCalifornia: yesCAUtah: yesUTColorado: yesCONebraska: yesNEMissouri: yesMOKentucky: yesKYWest Virginia: yesWVVirginia: yesVAMaryland: yesMDDelaware: yesDEArizona: yesAZNew Mexico: yesNMKansas: yesKSArkansas: yesARTennessee: yesTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: yesOKLouisiana: yesLAMississippi: yesMSAlabama: yesALGeorgia: yesGAHawaii: yesHITexas: yesTXFlorida: yesFL

FDA distribution: “Worldwide distribution - United States Nationwide and the countries of Algeria, Australia, Belarus, Belgium, Benin, Brazil, Bulgaria, Canada, Chile, Colombia, Croatia, Denmark, Finland, France, Germany, Greece, Hungary, India, Indonesia,…” States read from FDA’s own wording; “not listed” means the notice does not name it.

Distributed nationwide, and outside the U.S.

Recall timeline

FDA published this recall 54 days after the firm started it.

1. Firm started the recall: May 8, 202612. FDA classified it Class II: Jun 24, 202623. Published in FDA’s Enforcement Report: Jul 1, 202632026
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report

Dates from the agency record only; steps without a date are left out.

Similar recalls

Latest medical device recalls

Keep exploring

Where this comes from

The facts (hazard, remedy, dates, manufacturer) are pulled from the official FDA recall record. The plain-language summary and step-by-step checklist are written by GovInfoNow to make the official notice easier to act on — they don’t replace it.

  • Official source: FDA Recall #Z-2553-2026 (May 8, 2026) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2553-2026 to see it in context.
  • Plain-language summary written by qwen3:4b on August 10, 2026, from the official record above. Not reviewed by a person — if it conflicts with the FDA notice, the notice is correct. Report an error on this page.
  • GovInfoNow is an independent service and is not a government agency. We republish official FDA recall data; we don’t issue, amend or administer recalls.
GovInfoNow is an independent guide. We are not FDA or any government agency. Always confirm details with the official recall.Data: CPSC · FDA · NHTSA · USDA