Skip to content
Lower risk Medical device recall · FDA · Published June 13, 2017

Merge Eye Care PACS Viewer 5.2: Incorrect Image Rendering Risk

Merge Healthcare recalls PACS Viewer 5.2 software due to potential incorrect study indexing when user preferences aren't set, risking misidentified images in ophthalmic care.

🇺🇸 FDA recall #Z-2754-2017Medical deviceMerge Healthcare ›
Take action

Contact the company

Recalling firmMerge Healthcare, Inc.900 Walnut Ridge Dr · Hartland, WI 53029-8347
✎ GovInfoNow plain-language explainer

What happened, in plain English

Merge Healthcare is recalling its PACS Viewer 5.2 software because it can display images incorrectly if user preferences aren't configured. This could lead to misidentifying eye images as one eye when they're actually the other, potentially causing errors in patient care. Read more at govinfonow.com/recall/73873-merge-eye-care-pacs-viewer-5-2-incorrect-image-rendering.

Source Summary by GovInfoNow · govinfonow.com/recall/73873-merge-eye-care-pacs-viewer-5-2-incorrect-image-rendering · Updated September 22, 2026 · FDA enforcement record: FDA #Z-2754-2017

Cite this page

“Merge Eye Care PACS Viewer 5.2: Incorrect Image Rendering Risk.” GovInfoNow, updated September 22, 2026. https://govinfonow.com/recall/73873-merge-eye-care-pacs-viewer-5-2-incorrect-image-rendering. Based on FDA recall #Z-2754-2017 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2754-2017%22&limit=1).

Why it’s dangerous

The software may show images as one eye (OS) when they're actually the other eye (OD) if user preferences aren't set. This happens when the system doesn't have a sorting order for rendering images, causing incorrect study indexing. The error occurs during deletion attempts, where the system misreads the eye type.

Who’s affected

Healthcare providers using the Merge Eye Care PACS Viewer 5.2 software for ophthalmic imaging. Patients receiving eye care through this system may be at risk if image misidentification occurs.

How to tell if you have this one

The software version 5.2 is used for ophthalmic imaging. It was sold to healthcare providers for managing eye-related patient data and images.

  • Brand
    Merge Healthcare
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Verify if your system is running version 5.2 of the Merge Eye Care PACS Viewer software.

Where it went and when

Where it was distributed

Distributed in 9 states.

Alaska: not listedAKMaine: not listedMEVermont: not listedVTNew Hampshire: not listedNHWashington: not listedWAIdaho: not listedIDMontana: not listedMTNorth Dakota: yesNDMinnesota: not listedMNIllinois: yesILWisconsin: not listedWIMichigan: yesMINew York: yesNYRhode Island: not listedRIMassachusetts: not listedMAOregon: not listedORNevada: not listedNVWyoming: not listedWYSouth Dakota: not listedSDIowa: not listedIAIndiana: not listedINOhio: yesOHPennsylvania: not listedPANew Jersey: not listedNJConnecticut: yesCTCalifornia: yesCAUtah: not listedUTColorado: yesCONebraska: not listedNEMissouri: not listedMOKentucky: not listedKYWest Virginia: not listedWVVirginia: not listedVAMaryland: not listedMDDelaware: not listedDEArizona: not listedAZNew Mexico: not listedNMKansas: not listedKSArkansas: not listedARTennessee: not listedTNNorth Carolina: not listedNCSouth Carolina: not listedSCDistrict of Columbia: not listedDCOklahoma: not listedOKLouisiana: not listedLAMississippi: not listedMSAlabama: not listedALGeorgia: not listedGAHawaii: not listedHITexas: not listedTXFlorida: yesFL

FDA distribution: “FL, IL, CO, MI, CA, NY, ND, OH, CT” States read from FDA’s own wording; “not listed” means the notice does not name it.

States: California, Colorado, Connecticut, Florida, Illinois, Michigan, New York, North Dakota, Ohio.

Recall timeline

FDA terminated this recall 3.3 years after the firm started it.

1. Firm started the recall: Jun 13, 201712. FDA classified it Class II: Jul 20, 201723. Published in FDA’s Enforcement Report: Jul 26, 201734. FDA terminated the recall: Sep 17, 2020420172020
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report
  4. FDA terminated the recall

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-2754-2017 (June 13, 2017) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2754-2017 to see it in context.
  • Plain-language summary written by qwen3:4b on September 22, 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