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

Brand Name: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis) Recall

Brand Name: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis) Model/Catalog Number: GA60461-2J Software Version: Not applicable Product Description: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis) is intended for use in immunohistochemistry together with the Dako Omnis instrument. This antibody labels cells of the B-cell lineage and is a useful aid for the classification of neoplasms of B-cell derivation. Component: Not applicable

FDA recall Class II

Ongoing

FDA lists this Class II recall for Brand Name: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis). Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-2565-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Aug 11, 2025
FDA report date
Sep 24, 2025
Quantity in commerce
67
Distribution
See key details
FDA cause
Under Investigation by firm

What is being recalled?

Brand Name: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis) Model/Catalog Number: GA60461-2J Software Version: Not applicable Product Description: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis) is intended for use in immunohistochemistry together with the Dako Omnis instrument. This antibody labels cells of the B-cell lineage and is a useful aid for the classification of neoplasms of B-cell derivation. Component: Not applicable

Affected model & UDI checker

Search the exact identifiers published for Z-2565-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
GA60461-2JBrand Name: FLEX Monoclonal Mouse Anti-Human CD20cy, Clone L26, Ready-to-Use (Dako Omnis)Check source noticeNot specified
FDA code information

Lot numbers:41810156, 41741883 GTIN

View the original FDA recall notice

Why was this product recalled?

Their is the potential for weak staining which may result in false negative CD20 identification.

These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.

What actions did Agilent Technologies Denmark ApS take?

On August 11, 2025, Agilent Technologies, issued a Urgent Medical Device Correction Notification to affected consignees via E-Mail. Agilent Technologies ask consignees to take the following actions: 1: Please check your inventory and identify if you have the affected product listed in Table 1. Be aware that these products show potential weak staining, which may lead to false negative CD20 identification when used on CLL/SLL tissue samples. 2. If you experience weak staining, please contact Agilent Technical Support for troubleshooting. 3. Please confirm that you have received, read, and understood this Field Safety Notification by completing and signing the enclosed Acknowledgement Form and returning it to fieldactions.notifications@agilent.com. 4. Share this notice with anyone who needs to be aware within your organization and forward to any organization where potentially affected devices may have been transferred.

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