Recall Register

Food, drugs, devices › Merge Healthcare, Inc.

Device recall: Merge PACS software. The firm name on the label is Merge Healthcare, Hartland, WI.

FDA enforcement event 76260 · Class II · initiated 4 Apr 2016 · status Terminated · terminated 8 Apr 2019

DeviceVoluntary: Firm initiated1 product recordHartland, WI

Merge Healthcare, Inc. (Hartland, WI) initiated this device recall on 4 Apr 2016; FDA lists 1 product record under event 76260, classified Class II.

FDA defines Class II as a situation in which use of or exposure to a violative product may cause temporary or medically reversible adverse health consequences or where the probability of serious adverse health consequences is remote. 91% of the 1,232 device enforcement events initiated in 2016 carry the same class.

Status: Terminated, terminated 8 Apr 2019. Initiation: voluntary: firm initiated. Merge Healthcare, Inc. has 84 enforcement events on this register, with a median of 1 product record per event.

Recall classification reflects the relative degree of health hazard. Text in quotation marks is FDA's. openFDA export dated 28 Sep 2026.

Recalling firm

Merge Healthcare, Inc., Hartland, WI.

Reason for recall

"Potential exists for an incorrect patient image being displayed which could result in the delay in diagnosis or treatment."

Distribution

"Distribution was made to medical facilities in AZ, CA, CO, FL, HI, IL, MA, MD, MI, MO, NY, OH, PA, SC, TN, UT, and WI. There was no foreign/government/military distribution."

Product records

Recall numberProductQuantityClassStatusReport date
Z-1176-2017Merge PACS software. The firm name on the label is Merge Healthcare, Hartland, WI.29 sites have the potentially affected softwareClass IITerminated15 Feb 2017

Context

91%of 2016 device events are Class II1,232 events that year
1product record in this eventfirm median: 1
84events on this register for the firm

Other enforcement events for Merge Healthcare, Inc.

InitiatedProduct (first record)TypeClassRecords
22 Jul 2026Merge PACS and Merge OrthoPACS, medical imaging diagnostic workstationDeviceClass II1
30 Jun 2026Merge PACS, medical imaging diagnostic workstationDeviceClass II2
11 Aug 2025Merge Hemo, Model RCSV2, Model/Catalog Number 99-01172-00, software versions 11.1 and 11.1.1 Product Description: The MeDeviceClass II1
19 Feb 2025VERICIS, Merge Cardio, Model/Catalog Number: Version 9.x, Software Version: 9.0.6 and 9.0.8; VERICIS is an integrated caDeviceClass II5
23 Jul 2021Merge Hemo, Software packages 10.2, 10.3, and 10.4DeviceClass II1
6 Aug 2020Merge PACSDeviceClass II1
8 May 2020Merge Healthcare Merge Application Server Software Release and Merge Healthcare Merge Cardio Workstation Software ReleasDeviceClass II1
11 Jul 2019Merge PACS versions 7.3, 7.3.1, 8.0 and 8.0.1DeviceClass II2
20 Dec 2018The WinStation Retinal Imager, also known as Merge Eye Station. DCF-1024 & DCF-512 Digital Imaging System Product Usage:DeviceClass II1
14 Aug 2017Merge Unity software, formerly known as DR Systems Unity PACS software. The firm name on the label is Merge Healthcare, DeviceClass II1

All 84 events for Merge Healthcare, Inc.

Questions and answers

Why was this device recalled?

FDA's record gives the reason for recall as: "Potential exists for an incorrect patient image being displayed which could result in the delay in diagnosis or treatment."

What does Class II mean?

FDA classifies recalls by relative degree of health hazard. Class II is a situation in which use of or exposure to a violative product may cause temporary or medically reversible adverse health consequences or where the probability of serious adverse health consequences is remote.

Where was the product distributed?

FDA's distribution pattern field reads: "Distribution was made to medical facilities in AZ, CA, CO, FL, HI, IL, MA, MD, MI, MO, NY, OH, PA, SC, TN, UT, and WI. There was no foreign/government/military distribution."

Is the recall still ongoing?

FDA lists the status as Terminated; the termination date is 8 Apr 2019. "Terminated" means FDA has determined that all reasonable efforts to remove or correct the product have been made.

Where does this data come from?

openFDA enforcement reports (food, drug and device), CC0, export dated 28 Sep 2026. Text in quotation marks is FDA's. The FDA enforcement report linked above is authoritative.

Provenance

Source: openFDA device enforcement reports (CC0), export dated 28 Sep 2026; records grouped by FDA event number. The class shown for the event is the most severe class among its records. Errors in processing are corrected at the next build; see corrections.