Z-1398-2025Class II

VERICIS, Merge Cardio, Model/Catalog Number: Version 9.x, Software Version: 9.0.6 and 9.0.8; VERICIS is an...

Name: Z-1398-2025 VERICIS, Merge Cardio, Model/Catalog Number: Version 9.x, Software Version: 9.0.6 and 9.0.8; VERICIS is an...
Creator: Merge Healthcare, Inc.
Published: 2025-02-19
License: https://open.fda.gov/license/

Merge Healthcare Incorporated / initiated 2025-02-19 / Open, Classified / root cause: software

FDA source

Merge Healthcare, Inc. began a recall of VERICIS, Merge Cardio, Model/Catalog Number: Version 9.x, Software Version: 9.0.6 and 9.0.8; VERICIS is an integrated cardiovascular information system... on 2025-02-19. FDA classified it as Class II and gives the reason as "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...". As of 2026-09-10, the recall status on record is Open, Classified, and MDM tags the root cause as software.

Recall record

Recall number: Z-1398-2025
Classification: Class II
Status: Open, Classified
Initiated: 2025-02-19
Posted: 2025-03-20
Recalling firm: Merge Healthcare Incorporated
Product: VERICIS, Merge Cardio, Model/Catalog Number: Version 9.x, Software Version: 9.0.6 and 9.0.8; VERICIS is an integrated cardiovascular information system classified as a picture archiving and communications system.
Product code: LLZ System, Image Processing, Radiological
Reason for recall: 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.
Root cause tag: software
FDA root cause: Software design
Action: Merge Healthcare issued an Urgent Field Safety Notice to it's consignees on 02/19/2025 via email. The notice explained the issue, risk to patients, provided a workaround to immediately address the issue, and recommended clinicians check measurements in the final report to ensure that they accurately reflect the patient's condition pending software update. Required Actions: Merge Healthcare Support will contact all customers to: i) Confirm that you have read and understood this Urgent Field Safety Notice. ii) Schedule an update to implement the configuration change on your system. For more information, please contact Merge Healthcare Support at 1-877-741-5369 (available 24 hours a day, 7 days a week) or visit our website: https://www.merative.com/support/merge. Please forward this notice to any individuals within your organization that may need to be aware of this notification. Customers should alert any other affiliated parties that may be affected by this Urgent Field Safety Notice. The firm identified a missing software version (11.0.2) and issued the corrected notice on 03/03/2025.
Quantity in commerce: 2
Distribution: US
Product codes and lots: The following versions were introduced prior to the implementation of UDI. Version Numbers: 9.0.6, 9.0.8, Part Numbers: 88-00061-00, 88-00062-00, 88-00063-00, 88-00054-00, 88-00064-00.

Enforcement reports

One row per recalled product line

FDA enforcement reports joined to recall event Z-1398-2025
Recall number	Class	Status	Voluntary or mandated	Report date	Classified
Z-1398-2025	Class II	Ongoing	Voluntary: Firm initiated	2025-03-26	2025-03-20
Z-1399-2025	Class II	Ongoing	Voluntary: Firm initiated	2025-03-26	2025-03-20
Z-1400-2025	Class II	Ongoing	Voluntary: Firm initiated	2025-03-26	2025-03-20
Z-1401-2025	Class II	Ongoing	Voluntary: Firm initiated	2025-03-26	2025-03-20
Z-1402-2025	Class II	Ongoing	Voluntary: Firm initiated	2025-03-26	2025-03-20

Product code LLZ

K051649Class IIVericis Cardiovascular Image and Information System, Model 4.0Camtronics Medical Systems / cleared 2005-08-02

MDM coverage of this record lists here, newest first.

About this record

Sourced from the FDA device recall database and the FDA enforcement reports, both ingested from openFDA. The recall record supplies the product, the reason and the product code; the enforcement report supplies the classification. The two datasets are exported by FDA on different days, and the date above is the older of the two, so nothing on this page is newer than it says.

MDM adds the root cause tag, derived from FDA’s own root cause text, and the cross-links to the product code, the clearances named on the record and MDM coverage. Where a recall has not been joined to an enforcement report, no classification is shown.

Data as of 2026-09-30, the FDA export date for this dataset. Page last changed 2026-09-05. View this recall on fda.gov (opens on fda.gov)