Back to search
FDAFDA · Food and drugs·Recall number Z-0645-2013

ABX PENTRA ML, Software Versions: V8.0.x and Below; V.9.0.1 and V9.0.2

Published January 16, 2013 · Recall initiated: September 20, 2012

Summary

FDA records medical device Class II recall Z-0645-2013, published January 16, 2013 and initiated September 20, 2012. Recalling firm: Horiba Instruments, Inc dba Horiba Medical; Status: Terminated; Reported quantity: 10 units; Lot: Lot/Serial# PML0937. Class II means possible temporary or medically reversible effects, or a remote probability of serious health consequences.

Status when published: Terminated — openFDA updates weekly, so this field may not reflect the current status. Always confirm with the official notice.

What's the hazard

Horiba Medical is recalling ABX PENTRA ML because they have confirmed an issue with the ABX PENTRA ML data management and validation system. An incorrect patient result is transmitted to the Laboratory Information System. This result is from a previous run of the same patient that is stored in the ML database. This issue occurs in a very rare sequence of specific events. The affected software

What to do

Voluntary: Firm initiated · Letter

Get an email when a new FDA recall like this is published

Free. We only write when there's a new recall that matches. Unsubscribe in one click.

Recall details

Manufacturer
Horiba Instruments, Inc dba Horiba Medical
Distributor
Nationwide in the US, including the states of CA, MI, IN, FL, and GA. Center Recall Depth is Retail.
Lot
Lot/Serial# PML0937
Risk classification
Class II
Area (FDA)
device
Country
United States

Related recalls

Questions about this recall

Was ABX PENTRA ML, Software Versions: V8.0.x and Below; V.9.0.1 and V9.0.2 recalled?

Yes. FDA published recall Z-0645-2013 on January 16, 2013. Reported hazard: Horiba Medical is recalling ABX PENTRA ML because they have confirmed an issue with the ABX PENTRA ML data management and validation system. An incorrect patient result is transmitted to the Laboratory Information System. This result is from a previous run of the same patient that is stored in the ML database. This issue occurs in a very rare sequence of specific events. The affected software

What should I do if I have this product?

Voluntary: Firm initiated · Letter