Merge PACS software. The firm name on the label is Merge Healthcare, Hartland, WI.
Class I - DangerousWhat Should You Do?
- Check if you have this product: Versions 7.0.2.1, 7.0.2.2, 7.0.2.3, 7.0.2.3 P1, and 7.0.2.3 P2
- Do not eat it: Even if it looks and smells fine, do not consume this product.
- Throw it away or return it: You can return the product to the store for a full refund.
- Seek medical attention if needed: If you've consumed this product and feel unwell, contact your doctor immediately.
- Report problems: Report any issues to the FDA's Safety Reporting Portal.
⚠️ Emergency: If you experience severe symptoms after consuming this product, call 911 or Poison Control at 1-800-222-1222.
Recall Details
- Company:
- Merge Healthcare, Inc.
- Reason for Recall:
- Merge PACS did not show unviewed images when the last view was skipped. There is a potential risk to health of a physician misdiagnosis because not all images are available for viewing.
- Classification:
- Class I - Dangerous
Dangerous or defective products that predictably could cause serious health problems or death.
- Status:
- terminated
Product Information
Full Description:
Merge PACS software. The firm name on the label is Merge Healthcare, Hartland, WI.
Product Codes/Lot Numbers:
Versions 7.0.2.1, 7.0.2.2, 7.0.2.3, 7.0.2.3 P1, and 7.0.2.3 P2
Official Source
Always verify recall information with the official FDA source:
View on FDA.govFDA Recall Number: Z-2590-2017
Related Recalls
Merge Healthcare has been informed by Schiller AG (Baar, Switzerland) of an issue with the Schiller ARGUS PB-3000 Patient Data Module (PDM) where certain units trigger an error message on the Merge Hemo Client ( Pressure Sensor Defective ) during non-invasive blood pressure (NIBP) measurements, specifically when the initial inflation pressure is set in the high-pressure range (>240 mmHg). The ARGUS PB-3000 is a vital signs monitoring instrument intended to be integrated into the Merge Hemo System. No other components of the Merge Hemo System are affected.
When following a specific less typical workflow in which the user remeasures using the ultrasound device or manually edits primitive or derived measurement values directly in Clinical Reporting, derived measurements may be inconsistent with the associated primitive measurements in the final patient report.
When following a specific less typical workflow in which the user remeasures using the ultrasound device or manually edits primitive or derived measurement values directly in Clinical Reporting, derived measurements may be inconsistent with the associated primitive measurements in the final patient report.