Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-1656-2025

Brand Name: CELL-DYN Ruby Product Name: CELL-DYN Ruby Recall

Brand Name: CELL-DYN Ruby Product Name: CELL-DYN Ruby Model/Catalog Number: 04U42-84 Software Version: All software versions Product Description: CELL-DYN Ruby

FDA recall Class II

Ongoing

FDA lists this Class II recall for Brand Name: CELL-DYN Ruby Product Name: CELL-DYN Ruby. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1656-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Mar 18, 2025
FDA report date
Apr 30, 2025
Quantity in commerce
45
Distribution
See key details
FDA cause
Software change control

What is being recalled?

Brand Name: CELL-DYN Ruby Product Name: CELL-DYN Ruby Model/Catalog Number: 04U42-84 Software Version: All software versions Product Description: CELL-DYN Ruby

Affected model & UDI checker

Search the exact identifiers published for Z-1656-2025.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
04U42-84Brand Name: CELL-DYN Ruby Product Name: CELL-DYN RubyCheck source noticeNot specified
Not specifiedBrand Name: CELL-DYN Ruby Product Name: CELL-DYN RubyCheck source notice00380740017170
FDA code information

UDI-DI 00380740017170 SNs: 35939BG 35979BG 36019BG 36103BG 36115BG 36143BG 36171BG 36177BG 36361BG 36788BG 36866BG 54095BG 54431BG 54686BG 54787BG 54900BG 55634BG 55644BG 55656BG 55657BG 55659BG 55662BG 55665BG 55672BG 55673BG 55747BG 55859BG 55879BG 70021BG 70161BG 70204BG 70463BG 70713BG 70931BG 71185BG 71387BG 71388BG 71397BG 71398BG 71476BG 71503BG 71626BG 71637BG 71638BG 71710BG

View the original FDA recall notice

Why was this product recalled?

When expired reagents are scanned or manually entered, the system will change the expiration date to current or future date without notifying user that an expired reagent is being used. Use of expired reagents is against the guidelines of the Operator's Manual.

What actions did ABBOTT LABORATORIES take?

On March 18, 2025, the firm notified customers through "Urgent Medical Device Correction" letters delivered via FedEx. The letters described the product, problem and actions to be taken. The Customers were instructed to not use expired reagents as this may compromise test accuracy. Always use reagents within their valid expiration dates for all testing procedures. The operator must confirm the container labeling matches the data on the reagent log entry screen dialog box. Quality Controls should be run after any reagent lot number change, maintenance, component replacement, field service action, software change, or calibration. This should be done in accordance with your laboratory s quality control program and regulatory requirements. Complete and return the Customer Reply Form via email: PMS@abbott.com or fax: 1-800-777-0051. If you have forwarded the product listed above to other laboratories, please inform them of this Product Correction, provide to them a copy of this letter and retain this letter for your laboratory records. If you or any of the health care providers you serve have questions regarding this information, please contact Customer Service at 1-877-4ABBOTT.

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology