Electronic (Computer) Crossmatch

This is a revised version of a previous post.

As much as 90% of the RBC component allocation can be performed without an actual crossmatch test (AHG or immediate-spin) provided that certain criteria are met.

Enforcing these rules, however, can be cumbersome unless one has blood bank software that verifies that each rule is met.  In the Medinfo patient module, the transfusion history database is checked automatically.  If the rules are met, then Medinfo allows the selection (allocation) of RBC units without performing a crossmatch test.  Otherwise, it will check to see if the AHG crossmatch has been done within the past 3 days.  If not, it will prompt for new crossmatch testing with a new specimen.  If the situation is urgent, one can go to Emergency Mode and release components without the crossmatch.

Principle:

In selected patient categories, no classical crossmatch may be required for release of RBC components.  The criteria are specified here as applicable in my build of the Medinfo Hematos IIG computer system HIIG.

Policy:

  1. An electronic crossmatch without antiglobulin or immediate-spin phase testing may be used for the following patient categories:
    1. The current ABO/D type matches the historical ABO/D type.
    2. The ABO/D type (forward and reverse) is clearly defined without any discrepancies.
    3. Two determination of the ABO/D group must be made:
      1. One from a current specimen (within the past 72 hours)
      2. The second by one of the following methods:
        1. Testing a second current specimen
        2. Comparison with previous records of ABO/D typing
        3. Retesting the same specimen
    4. The current antibody screen is negative
    5. There is no history of RBC antibodies or a non-negative antibody screen.
  2. If the criteria in #1 are not met, the AHG crossmatch is required in non-emergency situations.
  3. General computer system safeguards:
    1. The system contains the donor unit number, component name, confirmed ABO/D typing, two unique recipient identifiers, recipient ABO/D, antibody screen typing, and interpretation of compatibility
    2. A method exists to verify correct entry of data before release of blood or blood components.
    3. The system contains logic to alert the user to discrepancies between donor ABO/D group on the unit label and those determined by blood confirmatory tests and to ABO incompatibility between the recipient and donor unit.
  4. HIIG will enforce the above rules.

References:

  1. HIIG Workflow 1004, Patient Testing, Latest Version
  2. Section 5.16, Standards for Blood Banks and Transfusion Services, Current Edition, AABB, Bethesda, MD, USA
  3. FDA Guidance for Industry:  Computer Crossmatch (Computer Analysis of the Compatibility between the Donor’s Cell Type and the Recipient’s Serum or Plasma Type), April, 2011