Processes and Software Building 22: Review of Laboratory Reporting Formats

Principle:

In accordance with the College of American Pathologists’ accreditation standards, all report structures (content, formatting) are reviewed at least biannually and upon modification by staff designated by the Chairperson, DLMP, here the Division Head, Transfusion Medicine/Laboratory Information System.

Policy:

  1. Responsibilities:
    1. The Chairperson, DLMP is ultimately responsible for the report formats, electronic and paper (if applicable) across all areas/divisions/sections of the department.
    2. The Chairperson, DLMP delegates the responsibility for this review to the Head, Laboratory Information Systems LIS.
    3. The Head, LIS reviews/approves the final reporting formats after review/acceptance of the formats by the Division and Section Heads for their respective areas.
  2. Content of the reports:
    1. Headers and footers as required, especially for paper reports
      1. Headers will include full patient name and a unique alphanumerical identifier, age, location, sex, date of testing/reporting, location, and ordering physician.
      2. Footers will include contact information for the site performing the testing and for the Chairperson, DLMP.
    2. Body of the report will include:
      1. Test results
      2. Flags
      3. Reference range
      4. Order and result comments
      5. Corrected/amended/appended results will be clearly marked, including any changes from the initial reports.
  3. Documentation of Review:
    1. Screenshots (electronic) or printout (paper formats) will be collated for one example of each test and reviewed by the Division/Section Heads and documented with a signature/stamp for each test result.
    2. Upon acceptance by the Division/Section Head, a cover letter summarizing the acceptance will be signed, stamped, and dated.
    3. The completed documentation will then be submitted to the Head, LIS for final review and approval.

Reference:

GEN.41077, Content/Format Report Review, CAP Checklist, Current Edition

The following is a sample report I prepared during my tenure at HMC Doha:

On the left-hand side of this composite PDF there are embedded attachments, which can be accessed by clicking on each one.  In this document,  I have shown a sample page from the actual screenshots generated.  The data showing is a dummy test patient (no real patient data is exposed).

Note that our design of Medinfo did not include printing copies of reports.  The only available reports were the screens.  Staff outside Transfusion Medicine viewed the blood bank reports through a separate database viewer.  In the example below, the Medinfo screen appears first followed by the EMR Viewer report.

Diamed/Biorad Profile Cards 1-2-3 for Extended Antigen Typing

Processes and Software Building—Part 21

In any case with nonspecific antibodies and for all new patients who will require chronic transfusions, I perform extended Rh (CcEe)/Kell and the three Diamed (now Biorad) profile cards.

It is very easy in Medinfo to write a process for any group of antigen typings as long as you know the manufacturer’s criteria for accepting results.  Some cards have controls, others do not.  In the latter case, the “control” is a negative reaction in the card or series of cards of the same type.

In Medinfo, one can also look for errors in using the card:  In Profile Card 3, i.e. the MNSsFyaFyb card, one must reject the card if no reactions in any well appear:  Did the technologist forget to add the cells or reagents?  Did he/she use the wrong diluent (i.e. bromelin enzyme) which would destroy the labile antigens?

One can set the acceptable range of reactivity, flag for mixed field, etc. and record these findings in the official record.  One can define which reactions you will accept an automatic reading of the card.  For the other readings, one can force a manual review and result entry.

Note that Profile Cards 1 and 2 both have an internal control whereas Profile Card 3 (enzyme-labile antigens) does not.

Here are the processes for all three profile cards:

23/7/20

Immediate Spin Crossmatch

Principle:

Immediate-spin crossmatch ISXM is an abbreviated compatibility testing that detects most ABO incompatibility.  AABB Standards restricts its use to specific situations as indicated in the Policy section below.

Policy:

  1. Applicability:
    1. ISXM may only be used when ALL of the following conditions are met:
      1. Negative antibody screen
      1. No history of antibodies
      1. No ABO/D antigen typing discrepancies
      1. Less than two (2) ABO/D determinations are on-file.
    2. Use the computer/electronic crossmatch whenever its specific criteria are met.
  2. Testing:
    1. ISXM consists of reacting an RBC suspension with patient/serum or plasma, centrifuging, and immediately reading for agglutination or hemolysis.  THERE IS NO INCUBATION STEP, NO USE OF ANTIHUMAN GLOBULIN AHG REAGENT.
    2. If any hemolysis or agglutination is detected, the crossmatch is incompatible:
      1. Repeat the ISXM.
      2. Repeat the patient ABO/D AND unit ABO/D typings.
      3. Repeat the antibody screen.
      4. Perform full AHG crossmatch AND AHG/enzyme antibody panels.
      5. Refer the case to senior technical staff or a Transfusion Medicine consultant for further instructions.
        1. Case review will be documented in Medinfo HIIG computer system.
      6. DO NOT RELEASE THE RBCS UNTIL SO INSTRUCTED BY SENIOR STAFF.

References:

  1. Technical Manual, Current Edition, AABB, Bethesda, MD, USA
  2. Standards for Blood Banks and Transfusion Services, Current Edition, AABB, Bethesda, MD, USA
  3. Guidelines to the Preparation, Use, and Quality Assurance of Blood Components, European Committee (Partial Agreement) on Blood Transfusion (CD-P-TS), Current Edition

Antiglobulin AHG Phase Crossmatch

The antiglobulin phase crossmatch is the same indirect antiglobulin test IAT used for antibody screening, only instead of reagent RBCs we use the donor’s RBCs.  One question I like to ask my students is to describe the difference between the IAT and the antibody screen.  Most don’t realize they are the same thing, the same procedure, i.e. mixing plasma/serum with RBCs and then detecting a reaction using the AHG reagen

In Medinfo, the AHG phase crossmatch will be required unless the criteria for electronic crossmatch have been met (see my previous post on this topic).  In emergency mode, one can also do a class II release using immediate-spin to detect ABO incompatibility.  Medinfo will check the historical records for previous antibodies.

Notice that the process includes contingencies for room and even lower temperature conditions as well as immediate-spin.

I warn my students that we can make any tube, gel or glass-bead well react if we do not strictly adhere to the manufacturer’s recommendations.  The simplest example is to leave the reaction mixture to incubate longer than the time limit for LISS (e.g. 60 minutes).

If the antiglobulin phase crossmatch is positive (i.e. nonnegative reactions), then the unit is rejected or a least-incompatible crossmatch mode is activated.  The latter requires the transfusion medicine physician to specifically approve the allocation and release of this component.

The following is the Medinfo process I used:

To Be Continued

21/7/20

Antibody Titration including Software Processes

Processes and Software Building—Part 20

My practice across the globe has exposed me different rationales to performing antibody titration.  In my American training and practice (and also at international institutions following the American version of AABB accreditation), I only routinely performed titration of anti-D for Rh(D) hemolytic disease of the newborn and anti-A/anti-B for ABO-incompatible stem cell transplants AND ABO-incompatible renal transplants.

I have had heated arguments with some physicians who insisted they wanted titers for other antibodies.  The AABB Standards do not require this but leave it to the discretion of the Transfusion Service Medical Director.

In my entire career, I never worked in a blood bank or blood center which had optimal staffing or resources.  I focused on what was medically/technically necessary and even then still had shortages.  If performing a test will not change the clinical treatment, why perform it unless you are doing a research project!

Titration is a time-consuming, and until recently, a tedious manual task.  Recently some of the automated immunohematology analyzers offer a titration program.  We used the Ortho Vision Max which could perform both IgG and IgM titers within one hour—walk away!!  However, during that time, the titration procedure monopolized the analyzer.

The ABO-incompatible renal transplant program at HMC Qatar was modelled after Sweden’s Karolinska Institute.  However the latter site performed manual IgG and IgM titrations using Biorad/Diamed gels.

I did not have sufficient resources to commit staff to manual titration at HMC so I did a comparison study between the Ortho Max and the Biorad methods.  We were able to get good correlation and used the automated method for the transplant.

I am still biased against performing titrations for other antibodies.  I always ask, ‘Does the titration correlate with clinical severity?’  Unlike anti-D, antibodies such as anti-Kell and anti-c may be low titer but cause death.  Can anyone show me a definitive study that titers are useful except for transplants and Rh(D) hemolytic disease of the fetus/newborn?

Since the method was working well on the Ortho equipment, I next established an interface to Medinfo.  The test was performed separately for IgG and IgM antibodies.  Medinfo recorded the reactions in all the wells.  The last well showing a 1+ reaction was interpreted as the titer (e.g. if 1:64 were the last 1+ reaction, then the titer was 64 in Medinfo).

The Medinfo process is shown below.

20/7/20

Platelet and Plasma Allocation Rules

Processes and Software Building—Part 20

Medinfo software is rules-based so the institution may set its own custom rules for all processes.  One chooses a framework and then adds any additional rules it needs for optimization.  Turnkey systems do not offer this flexibility.

The rules for platelet and plasma components are much simpler than those for RBCs since usually we only consider ABO type.  There are two modes:  regular and emergency, the latter applying if not all the patient testing (including historical checking) is available.  The components, on the other hand, must meet all criteria before being considered for patient use.

Example rules for plasma follow:

For platelets, note that for adults and anyone else >= 20 kg, I gave any type of platelet pool or plateletpheresis component without regard to ABO matching.  With our production method, I did not give Rh immunoprophylaxis to females of child-bearing age receiving platelets from D-positive donors based on our clean (essentially RBC-free) Reveos automated production process.

Similarly, allocation rules for granulocytes, etc. could be made and enforced by the software.  Low-B-titer group A universal plasma would also be easy to implement.

To Be Continued:

19/7/20

RBC Antigen Matching and Software Processes

Processes and Software Building—Part 19

In the previous post I outlined how Medinfo handled antibody screening and identification.  This post reviews how antigen matching is used based on these results.

There are two modes, regular and emergency.  If the patient has not had at least two ABO/D determinations and/or does not have a recent antibody screen, then emergency mode must be selected with its own rules.  Otherwise, the regular mode applies.

Regular Mode:

In general, if there is a clinically significant antibody, an RBC unit which has not been matched for the corresponding antigen or has the corresponding antigen cannot be routinely selected.  However there is a hierarchy here also:

  1. Absolutely prohibited release—no one can override the logic (e.g. giving group O to a patient with anti-H)—not even the transfusion medicine physician can override this
  2. Restricted release—only certain staff can release the incompatible or untested unit (e.g. giving C-positive unit to someone with anti-C)
  3. Least-incompatible for WAIHA:  requires transfusion medicine physician approval
  4. Informational release:  authorized staff may release antigen-incompatible or untested unit but a pop-up menu appears and asks them to accept (e.g. Lewis untested unit in a patient with anti-Lea).
  5. Antigen-specificity matched—the usual mode for patients with antibodies

Examples of Regular Mode rules follow (these are not the complete lists but just provided to show the complexity of the process).

Emergency Mode:

This is much more restricted for selection of ABO/D and other antigen typings.  An example follows:

A similar hierarchy exits for platelet and plasma allocation and will be considered in a future post.

To Be Continued:

18/7/20

Elution Indications and Software Implementation

Processes and Software Building—Part 17

The direct antiglobulin test DAT may be the first or last place that a delayed hemolytic transfusion reaction can be detected.  In my practice, I always performed it the first time I encountered a patient with a positive DAT.  If the subsequent DAT testing is of the same strength and there is no change in the clinical status of the patient, then I might empirically repeat the elution after 14 days, i.e. just when new antibody emergence may be detected.

In summary, my criteria for elution after a positive DAT are:

  1. First patient encounter with a positive DAT
  2. At least 14 days since the previous elution
  3. DAT strength has increased since the previous exam (at least 1+ increase in strength in either IgG or C3)
  4. Patient shows evidence of hemolysis
  5. Suspected cases of drug-related hemolysis
  6. Transfusion Medicine physician specifically orders it otherwise

In the software processes, the following parameters were recorded:

  1. Technique of elution (acid glycine, dichloromethane, digitonin, ether, etc.)
  2. Number of washes (too many may remove the antibody from the RBCs)
  3. Last wash result (must be negative to accept conclusion)
  4. Manufacturer of the elution kit (if any)
  5. Elution result based on panel testing

Note:

  1. All indeterminate or positive eluates would trigger an antibody identification.
  2. All results would be reviewed by me or the covering Transfusion Medicine physician.  A comment would be entered into the results that could be viewed by the clinician either directly from Medinfo or through the hospital information system.

If the DAT was only positive for complement, it was up to the Transfusion Medicine Consultant to decide whether to proceed with elution.  Personally, I would usually proceed because the eluate is more concentrated and may occasionally detect an antibody that was not noted in the patient’s plasma.

The attached Medinfo workflow shows the process designed by me for use at HMC Doha.

Processes and Software Building: Updated Convalescent COVID-19 Plasma Production

After the initial manual setup of the CCP program, the Medinfo process was set up.  The following workflow shows the production of CCP from the raw apheresis collection, including division into aliquots based on the total volume.  The plasma volumes were kept within the range for riboflavin pathogen inactivation (Mirasol).

The usual safeguards for production were also in effect for CCP.  The product could not be labelled without all criteria (donor screening, collection, marker testing) being met.  Furthermore, the inter-depot and transfusion service processes still applied.  However, all steps were done in quarantine at a location separate from the regular processes.  Also, the actual ordering and release of CCP was restricted to the quarantine hospital blood bank site.

The following outline the production process:

Software Processes for the Antibody Screen

Based on the previous software post, I use the antiglobulin test algorithms to construct the antibody screen ABS, namely an INDIRECT antiglobulin test, i.e. incubate reagent red cells with the donor or patient’s plasma and then perform the DAT.  At HMC Doha and at NGHA in Riyadh, we mainly used three cell screens (no pooled cells for donors). The reactions could be machine-read (we had the interface) but the interpretation of the specificities found was done manually.

Donor ABS:

We screened all donors for irregular antibodies.  I disqualified most donor with non-negative screens from donation (my personal preference).  However, for nonspecific antibodies, I might elect to discard the current collection and then reassess the donor’s status at the next encounter.  Not everyone would agree with this most restrictive approach but I would not use the platelets or plasma in such situations.  I also did not use the donor RBCs, even though they were in SAGM—but I could elect to override this decision in Medinfo if there were a rare blood group (e.g. r’r’).

Example #1 (following) shows a sample donor ABS process:

Patient ABS:

Excluding emergency release, if the patient did not qualify for the electronic (computer) crossmatch, then the AHG crossmatch was required.  A three-cell antibody screen including R1R1, R2R2, and rr RBCs was used that usually included cells homozygous for the Kell, Duffy, Kidd, MNS antigens.  For any case with a non-negative antibody screen, either donor or patient, an antibody identification was performed.

Note that I did not use any other software to make antibody identifications.  I required my technologists to be proficient in identifying basic and intermediate-level testing.  The actual antigen makeup of each lot number of antibody screen or identification panel was NOT stored in Medinfo.  We scanned the antibody screen and panel workups and could store those in Medinfo.

Example #2 (following) shows a sample patient ABS process:

Patient ABS Fix for Interface Regression Caused by HIS:

Regretfully, with a software update from the hospital information system HIS vendor, a major regression occurred.  It would not discard results from Medinfo if more than one antibody result (e.g. anti-E and anti-c) was sent back.  We could see the results in Medinfo, but those outside Transfusion Medicine could not see antibody results.  The entire interface for antibody identification had to be rewritten so that the HIS would see each result uniquely and thus all results could be sent back to it.

Regression Example:

Anti-Kell sent from Medinfo:  one antibody result, HIS would store and show this result.

Anti-E and anti-c sent from Medinfo:  No antibody results shown, both results kicked out.

Regression Fix:

Anti-E sent as Method Type1-Antibody 1 and anti-c sent as Method Type 1-Antibody 2:  both results displayed in HIS.

Example #3 (following) shows the regression fix.