...
| Expand | ||
|---|---|---|
| ||
Hap-E searches may return donors that do not have typing at DRB1, but do have typing at loci A, B and at least one other locus. Since these donors are usually not considered relevant potential donors and there tend to be quite a few of these donors that potentially match the patient, Search & Match applies a default filter which removes all donors that do not have typing at DRB1. You can see this by the little "1" next to the filter.
This means that there is already a filter applied to the results. If you are interested in the donors without DRB1 typing you can remove the filter and see all results. |
| Expand | ||
|---|---|---|
| ||
If this occurs the most likely cause is:
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 | ||
|---|---|---|
| ||
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. |
...