18.2 Operations & Information Technology

Blood Bank Information Systems Are Different From A General LIS

A general laboratory information system reports chemistry or hematology results; a blood bank information system (BBIS) does more — it is the software that prevents a patient from receiving an incompatible unit. Because of that safety role, FDA regulates blood bank computer systems as medical devices, and AABB Standards require specific safeguards a general LIS is not required to have:

• Computer (electronic) crossmatch logic — before releasing a unit electronically without a serologic crossmatch, the system must verify: (1) at least two ABO/Rh determinations on record, one from a current sample; (2) no clinically significant antibody detected; (3) no history of a clinically significant antibody; and (4) system logic that compares donor and recipient ABO/Rh and blocks release of an incompatible unit. If any condition fails, the system must force a serologic (tube or gel) crossmatch instead.
• Interface validation — when the BBIS interfaces with the hospital LIS/EHR through HL7, an SBB must validate that patient identifiers, ABO/Rh results, and antibody history transmit correctly and that a mismatch cannot occur silently.
• Downtime procedures — a validated manual (paper) backup process must exist because a blood bank cannot simply wait for the system to come back online during active hemorrhage.

Verification vs. Validation

The exam draws a hard line between two terms that sound similar but mean different things under CLIA (42 CFR 493.1253):

A new gel-based antibody screening method that is FDA-cleared and used exactly per the package insert only needs verification. A laboratory-developed elution procedure, or a BBIS upgrade that changes crossmatch logic, needs full validation — including challenge testing with known-positive and known-negative results before it goes live. Software validation additionally requires testing every clinical decision rule, such as confirming the system correctly blocks release when antibody history exists, and documenting the test cases, expected results, and actual results before the system is released for patient use. 21 CFR Part 11 governs the integrity of electronic records and signatures generated by validated systems.

Preanalytical And Administrative Controls

Blood bank operations depend on administrative controls that catch errors before they reach a patient:

• Positive patient identification (two identifiers) at both specimen collection and product administration.
• Barcode/electronic verification at bedside administration, matching the unit, the crossmatch tag, and the patient wristband.
• Type-and-screen sample requirements — many facilities require a second, independently drawn sample before releasing red cells for patients with no prior ABO/Rh history on file, specifically to catch a wrong-blood-in-tube (WBIT) error, which remains a leading root cause of ABO-incompatible transfusion.

Worked example: A patient's electronic crossmatch is blocked because the BBIS shows a discrepant ABO type between the current sample and a historical record. The correct action is not to override the system — it is to obtain a new, independently collected sample and investigate a possible WBIT or patient misidentification before proceeding.

Facility Design And Cold-Chain Management

An SBB supervisor participates in facility-planning decisions that a bench technologist typically does not:

• Storage equipment — blood bank refrigerators (1-6°C), freezers that vary by product (FFP and cryoprecipitate at ≤-18°C, with some cellular-therapy products requiring ≤-65°C), and platelet incubators with continuous agitation (20-24°C) each require continuous, alarmed temperature monitoring.
• Alarm and contingency planning — audible/visual alarms plus a documented after-hours response plan, and backup power (generator or battery) sized to protect inventory during an outage.
• Workflow and space design — separating donor collection areas, component processing, and testing to reduce contamination risk and support traffic flow, particularly where an apheresis or donor room is co-located with the transfusion service.

Customer Service In The Blood Bank

Blood banks serve two customer populations: internal customers (ordering physicians, nursing units, surgery, the emergency department) who need timely, accurate results and clear communication of testing delays, and external customers (patients and donors) whose experience affects donor retention and patient satisfaction. Effective SBB-level service management includes defined turnaround-time targets communicated to clinical units, a complaint/service-recovery process that documents and closes the loop on service failures, and proactive communication when a testing delay, such as a complex antibody workup, will affect a scheduled surgery.

Data Security And Record Access

Because a BBIS stores both patient results and donor eligibility information, IT governance in the blood bank layers HIPAA privacy and security requirements on top of the FDA device-safety concerns already described. Standard controls an SBB manager oversees or audits include:

• Role-based access control — limiting who can modify a patient's ABO/Rh history, override a computer crossmatch block, or release a unit, with system-generated audit trails that record who made each change and when.
• Unique user logins rather than shared credentials, so every action in the system is individually attributable — a requirement for both patient safety investigations and 21 CFR Part 11 electronic-record integrity.
• Downstream data checks — periodic review that data transmitted to the hospital EHR/HIS matches the BBIS record, catching interface errors before they affect patient care rather than after a discrepancy is noticed at the bedside.

An SBB investigating a reported discrepancy (for example, a unit issued to the wrong patient in the EHR but correctly recorded in the BBIS) uses the audit trail first to establish exactly where in the workflow the two records diverged before assigning a root cause.