Z-2141-2020Class II

Accelerator a3600 Automation System with Advia2120LAS Interface Module (P/N FLX-219-00, FLX-219-10)...

Name: Z-2141-2020 Accelerator a3600 Automation System with Advia2120LAS Interface Module (P/N FLX-219-00, FLX-219-10)...
Creator: Inpeco S.A.
Published: 2020-04-07
License: https://open.fda.gov/license/

Inpeco S.p.A. / initiated 2020-04-07 / Terminated / root cause: software

FDA source

Inpeco S.A. began a recall of Accelerator a3600 Automation System with Advia2120LAS Interface Module (P/N FLX-219-00, FLX-219-10), ImmunoCAP 1000 Interface Module (P/N FLX-226-01... on 2020-04-07. FDA classified it as Class II and gives the reason as "The identified problem is an erroneous association between the carrier and the sample tube caused by a communication error between the firmware of the Interface Modules and the Automation software. This problem can...". As of 2026-09-10, the recall status on record is Terminated, and MDM tags the root cause as software.

Recall record

Recall number: Z-2141-2020
Classification: Class II
Status: Terminated
Initiated: 2020-04-07
Posted: 2020-05-28
Terminated: 2024-02-06
Recalling firm: Inpeco S.p.A.
Product: Accelerator a3600 Automation System with Advia2120LAS Interface Module (P/N FLX-219-00, FLX-219-10), ImmunoCAP 1000 Interface Module (P/N FLX-226-01, FLX-226-10), or StaRRsed Interface Module (P/N FLX-268-00) is a modular system designed to automate Pre-Analytical and Post-Analytical processing, sample handling in order to automate sample processing in the Laboratory. The systems consolidate multiple Analytical instruments into a unified workstation.
Product code: JQP Calculator/Data Processing Module, For Clinical Use
Reason for recall: The identified problem is an erroneous association between the carrier and the sample tube caused by a communication error between the firmware of the Interface Modules and the Automation software. This problem can occur only when one of these Interface Modules is put off-line after a carrier in their secondary lane is physically returned on the main track and then put back on-line when the carrier is used to transport another tube.
Root cause tag: software
FDA root cause: Software design
Action: Urgent: Medical Device Correction notification letters dated 3/30/20 were sent to customers. 1) Visually check that the secondary lane of the Interface Modules listed in Table 1 is empty before sending the Off-line command; or 2) Select the "Going to Off-line" command for the Interface Modules listed in Table 1. This ensures that the Module completes processing samples already inside the Module, releases the tubes and then passes to Off-line status. Your service provider will contact you to schedule the firmware upgrade. Until the service visit please maintain awareness on this notice. Please complete and return the "Customer Letter Receipt Confirmation and Implementation Check form" attached to this letter within 15 days directly to the email address specified in the email communication. Please transfer this notice to whom it might concern. Contact reference person: For any clarification you may need, do not hesitate to contact: Eva Balzarotti - Regulatory Affairs Manager E-mail: [email protected] Phone: (+41) 919118 224
Quantity in commerce: 3 systems
Distribution: US Nationwide including in the states of IL, NY.
Product codes and lots: Serial Numbers: ACP.290 ACP.343 ACP.365

Enforcement reports

One row per recalled product line

FDA enforcement reports joined to recall event Z-2141-2020
Recall number	Class	Status	Voluntary or mandated	Report date	Classified
Z-2140-2020	Class II	Terminated	Voluntary: Firm initiated	2020-06-03	2020-05-28
Z-2141-2020	Class II	Terminated	Voluntary: Firm initiated	2020-06-03	2020-05-28
Z-2142-2020	Class II	Terminated	Voluntary: Firm initiated	2020-06-03	2020-05-28

Product code JQP

K121012Class IIFlexlab 3.6, Accelerator A3600Inpeco S.P.A. / cleared 2012-08-31

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-10-07, the FDA export date for this dataset. Page last changed 2026-09-05. View this recall on fda.gov (opens on fda.gov)