I was wondering if anyone else has had a chance to demo Waitlist and DonorNet in Beta Portal, that now reflects the upcoming changes to the HLA equivalency tables? They've added many more alleles to the dropdown menus for both candidate and donor typing, and also to the unacceptable antigen boxes.

https://optn.transplant.hrsa.gov/governance/public-comment/update-hla-equivalency-tables/

betaportal.unos.org/

Basically, I'm encountering a potential problem with the programming logic linking antigens and alleles in a match run. I created dummy recipient and donors and entered different combinations of allele or antigen level typing. Then I ran match runs as the OPO with different scenarios. For me, it seems that if the candidate and donor typing are both entered at the allele level and the alleles are mismatched, they do not appear as 0MM on the match run even though they are actually matched at the serological/antigen level.

I attached a screenshot of one example scenario.

Other issues I encountered are:

1. In Waitlist, if you list a patient with typing at the allele level (A*02:01), you can block the antigen level (A2) with no warning. You do get a warning ("Are you sure?") if you go the other direction.

2. The cPRA calculator does not factor in alleles of A, B and most DR, DQ; but alleles of DRB345 reflect the same cPRA as the whole antigen.

I was wondering if anyone has encountered the same issues?

Nicole

Nicole Valenzuela, PhD, D(ABHI)

UCLA Immunogenetics Center