With this message type all kind of HLA typing requests are transmitted to a remote donor registry. The details of the HLA typing to be performed are defined in the field
|Field description (WMDA dictionary field)||EMDIS field code||Required||Field Type|
|Sending EMDIS registry (REG_SND)||REG_SND||Optional||N4|
|Receiving EMDIS registry (REG_RCV)||REG_RCV||Optional||N4|
|Patient identification (Patient Identification)||P_ID||Required||A17|
|Donor identification (Donor Identification ( to be replaced by GRID))||D_ID||Required||A17|
|Global registration identifier for donors (GRID)||D_GRID||Optional||A19|
|Request date (Request date)||REQ_DATE||Required||D8|
|Reference code (REF_CODE)||REF_CODE||Required||A15|
|Resolution required (RESOLUT)||RESOLUT||Required||A11|
|Institution paying (Invoice institution)||INST_PAY||Required||A10|
|Urgent request (Urgency)||URGENT||Optional||A1|
|Acknowledgement ID (Acknowledgment ID)||ACK_ID||Optional||A17|
Resolution required: Character string with fixed length in which each position locus. The coding of the resolution required for every position is:
The string is interpreted from left to right with position 1 as the leftmost position.
Intermediate resolution (
The coding schema theoretically allows more combinations than the previous bitstring (e.g. non-high DRB1 typing). The actually valid combinations have to be published in the national rules of each registry. The local user interfaces will have to take care that no invalid or previously undefined requests are issued.
Combinations are possible i.e. several loci may be requested in one message.
Several distinct requests for the same patient / donor pair at a time are possible e.g. a DRB1 high and a class I DNA, but each request has to be answered by a
The appropriate action if the