WMDA is using the HLA Validator for all the HLA validation in WMDA services including Data Manager. There is a json schema validation to validate the value in json format before reaching the HLA Validator.

There are several validations process involved to better serve this service, and these validations are listed below:

  1. The specification for the endpoint of HLA Validator can be found in the link below:

https://apispecs.wmda.info/?urls.primaryName=HLA%20Validator


       2.  HLA format validation based on json schema

The json schema used is as below, if you are with technique background, then you can doc the schema doc below: 
https://brave-forest-04a379103.azurestaticapps.net/json_schemas/hlaValidator/validateBatchRequestBody.json

As the doc above it too technique, below is the explanation of the format validation that which are NOT supported in the json schema:

LociRule of Regular expression LengthValid value examplesInvalid value examples
SER value for all loci that have SER^\\d{1,4}$|^UUUU$4

1
24
UUUU

"XXXX" is not allowed for ser value
"NNNN" is not allowed for ser value
"NEW" is not allowed
"01" value start with "0" will be rejected

DNA for loci 

A, B, C, E, DRB1, DPA,DPB,DQA,DQB


^\\d{2,}:[A-Z0-9:]{1,}$|^NEW$|^UUUU$

20

01: XX 
01:01
01:03N
01:01:01G
51:01:01:06
01:AB
03:AHWZW
NEW
UUUU

"/" is not allowed: for example01:02/01:03
"*" is not allowed: A*01:02, A*11:FKFNG
value is not start with letters: A01:02
Space is not allowed:  07 :BZEJD
value using small letter "new" is not allowed
Use mixed value is not allowed, for example: NEW:XX
value using small letter "uuuu" is not allowed
DNA for loci DRB3, DRB4, DRB5^\\d{2,}:[A-Z0-9:]{1,}$|^NNNN$|^UUUU$|^XXXX$|^NEW
 
20

All valid value above for DNA
NNNN
XXXX

All the invalid value above for DNA
value below using small letters are not allowed: 
nnnn, xxxx
  • No labels