⚠Due to planned maintenance you will experience short (<30 min) downtime between 08:00 - 08:30 CET.
...
Expand | ||
---|---|---|
| ||
This can happen only if the difference in resolution is not considered sufficiently relevant in the given context by Hap-E Search and ATLAS. Below are some possible (not mutually exclusive) reasons:
|
CASE STUDIES
Expand | ||
---|---|---|
| ||
In rare cases the match program cannot decide which of two B locus results are a mismatch, in those cases both are given in bold. For example, the patient is B*27:05, 44:03; the donor is B*44:ABYM, 44*AFFK. In this case both multiple allele codes include 44:03 therefore the match program cannot choose between them. See example image below where donor 12 on the search report is being marked as having two HLA-B mismatches, when actually it is only a single mismatch. |
CASE STUDIES
Expand | ||
---|---|---|
| ||
The patient's 5 locus phenotype (10/10) cannot be explained by the haplotypes used for probability matching. The algorithm tries to fall back to 4 locus phenotypes (8/8) and 3 locus phenotypes (6/6). |
| ||
| ||
Expand | ||
---|---|---|
| ||
|
...
Expand | ||
---|---|---|
| ||
Currently, 10/10, An 8/8 and 6/6 lists are reserved for donors that have no known mismatches. Donors that have known mismatches for your patients will only be returned when you select "Run a Mismatch Search" and then select to view a 9/10 or 7/8 match type results list.search does not consider DQB1 and therefore will not show whether a donor has or does not have a mismatch for DQB1. If the donor only has a known mismatch at DQB1, this donor will show up in the search results as a potential 8/8 match. |
Expand | ||
---|---|---|
| ||
A*02:01 (2) vs. 02:03 (203) is an allele mismatch because A203 is an associated antigen to A2. B*15:01 (62) vs. B15:03 (72) is an antigen mismatch. |
...