You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the clinical reports report HLA codes like "HLA-B*08:YETY" that don't match our expected four digit resolution like HLA-\w*\d{2}:\d{2}
This site contains a list of ambiguity codes and the alleles they match up with. https://hml.nmdp.org/MacUI/
For example, HLA-B*08:YETY translates to three options: HLA-B*08:01/HLA-B*08:19N/HLA-B*08:109
The goal is to update the hla_consensus.wdl code to handle these intelligently by:
disambiguating any codes from the clinical HLA typing inputs
comparing the possibilities to those reported by Optitype or Phlat and choosing the alleles that match
if there is no disambiguation, or there is no match, drop the ambiguous coded allele and handle the rest in the same way as is currently done (unique union?)
The text was updated successfully, but these errors were encountered:
Sometimes the clinical reports report HLA codes like "HLA-B*08:YETY" that don't match our expected four digit resolution like
HLA-\w*\d{2}:\d{2}
This site contains a list of ambiguity codes and the alleles they match up with. https://hml.nmdp.org/MacUI/
For example,
HLA-B*08:YETY
translates to three options:HLA-B*08:01/HLA-B*08:19N/HLA-B*08:109
The goal is to update the
hla_consensus.wdl
code to handle these intelligently by:The text was updated successfully, but these errors were encountered: