ImmuLINK (v3.3)
Device Facts
| Record ID | BK251256 |
|---|---|
| Device Name | ImmuLINK (v3.3) |
| Applicant | Immucor, Inc. Norcross, Georgia 30071 |
| Product Code | MMH · Hematology |
| Decision Date | Oct 24, 2025 |
| Decision | SESE |
| Regulation | 21 CFR 864.9165 |
| Device Class | Class 2 |
| Attributes | Software as a Medical Device |
Indications for Use
ImmuLINK is software intended for use in a blood banking environment as an aid in interfacing and managing data between blood bank instruments, Blood Establishment Computer Software, and Laboratory Information Systems. ImmuLINK includes the following features and/or functions: - It provides the ability to create and print reports of tests and results. - It supports the ability to compare current results with previous results. - It supports the automatic ordering of reflex tests. - It provides a tool so that test results produced by a testing platform can be remotely validated prior to delivery to an LIS. Results can also be viewed remotely and edited prior to delivery to an LIS. - It provides bi-directional communication between an LIS and instrument platform(s). - It provides a tool to assist with antibody exclusion and identification that is based upon the approach recommended in the Technical Manual (AABB). ImmuLINK does not provide diagnostic interpretations of antibodies; final interpretation of results must be performed by a trained user.
Device Story
ImmuLINK is middleware software facilitating data integration between blood bank instruments (e.g., Immucor Galileo/Echo systems, BioArray AIS) and Laboratory Information Systems (LIS). It collects sample, donor, and patient data; provides tools for customizable reporting, reflex test ordering, and remote result validation. Operators (laboratory staff) access the web-based interface via PC workstations to review, edit, and electronically sign results before LIS transmission. The system includes an Antibody ID tool assisting in exclusion/identification based on AABB Technical Manual guidelines; it does not provide diagnostic interpretations. Bi-directional communication allows LIS test orders to be sent to instruments. Benefits include improved workflow efficiency, remote validation capabilities, and centralized data management.
Clinical Evidence
No clinical data provided. Substantial equivalence is based on technological characteristics and performance testing of software functionality.
Technological Characteristics
Middleware software; web-based architecture; Windows Server 2022 or Windows 11 Professional; Microsoft SQL Server 2019/2022; thin-client deployment; bi-directional LIS/instrument connectivity; rules-based decision processing; supports serology and molecular result display; electronic signature capability.
Indications for Use
Indicated for use in blood banking environments to interface and manage data between blood bank instruments, Blood Establishment Computer Software, and Laboratory Information Systems. Intended for use by trained laboratory personnel for data integration, remote result validation, and antibody exclusion/identification assistance.
Regulatory Classification
Identification
Blood establishment computer software (BECS) is a device used in the manufacture of blood and blood components to assist in the prevention of disease in humans by identifying ineligible donors, by preventing the release of unsuitable blood and blood components for transfusion or for further manufacturing into products for human treatment or diagnosis, by performing compatibility testing between donor and recipient, or by performing positive identification of patients and blood components at the point of transfusion to prevent transfusion reactions. This generic type of device may include a BECS accessory, a device intended for use with BECS to augment the performance of the BECS or to expand or modify its indications for use.
Special Controls
*Classification.* Class II (special controls). The special controls for these devices are:(1) Software performance and functional requirements including detailed design specifications ( *e.g.,* algorithms or control characteristics, alarms, device limitations, and safety requirements).(2) Verification and validation testing and hazard analysis must be performed. (3) Labeling must include: (i) Software limitations; (ii) Unresolved anomalies, annotated with an explanation of the impact on safety or effectiveness; (iii) Revision history; and (iv) Hardware and peripheral specifications. (4) Traceability matrix must be performed. (5) Performance testing to ensure the safety and effectiveness of the system must be performed, including when adding new functional requirements ( *e.g.,* electrical safety, electromagnetic compatibility, or wireless coexistence).
Predicate Devices
- ImmuLINK (v3.2) (BK241080)