You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 54 Next »

For more info on this please see the following slides and video from the educational webinar held on 1 September 2022. 

FeatureOptimatchHAP-EATLAS
AB searchYes (separate search)No. Technically possible, but turned off for performance reasons. No. Not possible because donors without DRB1 are not accepted by ATLAS as valid donors. 
ABDR searchYesYesYes
AB Antigen, DRB1 allele match (for cord matching)YesNot yet. Could be implemented if desired. No
Sorting performed by Matching EngineYesNo. WMDA Search and Match performs sorting. Yes, but WMDA will override with own sort parameters
Information about probability of match at other allele at already mismatched locusNoYesYes
Flexible scaling to accommodate periods of high and low use of the engineNoYesYes
g group level matchingYesYesYes (actually "P" group matching)
G group level matching (leading to less populations and lesser performance for some of populations, but better matching for other populations). NoNoYes, but turned off at the moment in favour of g group matching. 
automatic refresh of patient searchesYes

Partially implemented. New and deleted donors are indicated as well as updated donors that remained a potential match. 
To be done: 

  • Mark donors as deleted when updated and no longer matching a patient. 

Scheduled for full implementation upon go-live with ATLAS. 

Delta search to be implemented in Search & Match. 

Scheduled for full implementation as part of official go-live. 

differential results from matching algorithm. → algorithm tells what has changed. NoYesYes
HLA validation of DRB3, DRB4, DRB5, DQA1 and other loci not considered for matchingPossible in Optimatch. Not implemented in WMDA setup for Search & Match v1.Performed as part of v2 setup of Search & Match.Loci other than A, B, C, DRB1, DQB1 and DPB1 are not validated or imported by ATLAS and therefore also not returned. 
Performing a mismatch search will return also (potentially) matched resultsYesYes Yes
Consider combination of serological and DNA typing for match probabilityYesNoNo
support for > 2 mismatchesPossible in Optimatch. Not implemented in WMDA setup for Search & Match v1.Not yet. Will also be 2 or more mismatches on ABDRB1.  >=4/8 
all loci to be considered need to be typed at high resolution for patient. 
yes, but only for donors >= 4/8
HLA imputation based on patient organisation and/or poolPossible in Optimatch. Not implemented in WMDA setup for Search & Match v1.Yes.  Available at go-live. 
mismatches per locus can be sent directly to matching engine? Yes, during actual search and during retrieval. No. Server side filtering needed for API and GUIYes, but not fast. For performance reasons WMDA will perform server side filtering for GUI use. 
null allele handlingOnly considers null alleles with allele frequency higher than 0% in donor population or high resolution null allele.   Will return donors which match haplotype with known null allele or high resolution null allele. ?
TCE handling for DPB1Allele frequency based TCE3Allele frequency based TCE3TCE3 
match grade handling when multiple potential ARDs in donor typingWhen only 1 ARD in ambiguity list occurs in the known haplotypes → allele match ("A")Always "Potential" even if there is only 1 ARD in known haplotypes (100% potential match)
broad serology level matchingyes

No. Split serology will only match same split serology or when donor/patient is broad serology. Not matched when patient/donor has split serology that is different but both share same broad serology. 

e.g. 

  • 26 -> split serology 26, broad serology 10
  • 66:XX -> split serology 66, broad serology 10
  • Hap-E does not consider the shared broad serology as a match
  • Optimatch seems to consider them a match

AB Antigen, DRB1 allele match not supported. 


Lowest probability in search results

1 (0 is very rare circumstances). 

0% match probability for haplotype frequency matching displayed as 1% if allele frequency based matching indicates possible match. 

00
matching probability when donor haplotype cannot be explainedNo match probabilities displayed. No match probabilities displayed. No match probabilities displayed. 
directionality of DPB1 nonpermissive mismatch indicated? YesYes

Yes

Indicate in search result that it is unclear whether allele or antigen mismatchYesNo

No

donors returned with A, B and C and/or DQB1, but not DQB1Yes in AB searchyes but filtered out

donors without DRB1 are never returned

HLA typing other than A, B, C, DRB1, DQB1 and DPB1 (e.g. DRB3/4/5 or DPA1) available in search results and full reportYesyes, only in full report due to design choice in Search & Match

no. 

Meaning of locus-specific match probabilityLocus match probability no matter the amount of overall mismatches

Locus match probability in the case of additional mismatch

additional info

Locus match probability no matter the amount of overall mismatches

  • No labels