Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleWhy are certain search results returned that seem to be an obvious mismatch?

If this occurs the most likely cause is: 

  • Your patient has homozygous typing at at least 1 locus
  • The potential donor/CBU has low resolution typing at this locus or a MAC code that contains a null allele

The reason this donor/CBU is shown as a potential match and not a mismatch is that the typing for the donor contains a null allele. It is therefore a possibility that the donor actually has a null allele. Since a homozygous typing is generally considered a match with a donor that has one allele that matches the homozygous patient typing and the other is a null allele, Hap-E returns this donor/CBU as a potential match. Please see the slide below from a recent webinar:



Expand
titleWhy is the number of search results so different than in the legacy system?

In the legacy system when running a standard donor search, all returned donors have values for A, B and DRB1. This is different when running a search in the new system. There all donors need to have typing at A, B and at least one other locus (which may or may not be DRB1). This means that donors are returned in the new system that do not have typing at DRB1. This typically explains the majority of the difference in number of search results as mentioned in the search summary. 


You can see all donors by unchecking the default filter. 

Image Added




Expand
titleWhat is asynchronous matching?

Asynchronous matching is a process of running searches in parallel. It allows you to enter a patient and start the search run, and proceed with other activities within the application like entering another patient or reviewing another match list while the search runs in the background. You do not have to wait for the current search to finish before proceeding with other activities.

...