EMDIS message: TYP_REQ

Description Typing request

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 RESOLUT. The testing has to be performed at the lab of the donor registry (in contrast to the SMP_REQ message where a (blood) sample will be shipped and then the testing will be done in the lab of the transplant centre). The results will be sent back via the message TYP_RES.

EMDIS Fields

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
Remark (REMARK) REMARK Optional A120

Resolution required: Character string with fixed length in which each position locus. The coding of the resolution required for every position is:

S = serological
L = DNA low resolution
M = DNA medium (intermediate) resolution
H = DNA high resolution
A hyphen (’-’) indicates that a locus is not requested.

The string is interpreted from left to right with position 1 as the leftmost position.

Position 1  HLA-A
Position 2  HLA-B
Position 3  HLA-Cw
Position 4  HLA-DRB1
Position 5  HLA-DRB3
Position 6  HLA-DRB4
Position 7  HLA-DRB5
Position 8  DNA-DQA1
Position 9  DNA-DQB1
Position 10 DNA-DPA1
Position 11 DNA-DPB1


HLA-DRB1 low resolution:
HLA-DRB1 serological:
HLA-DRB1 high resolution:
HLA-DRB1 and HLA-DQB1 high resolution:

Intermediate resolution (M) translates to the non-high 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 TYP_RES message. It is not allowed to ”concatenate” / ”summarize” results in a single result message. Multiple typing requests for the same patient / donor pair have to be disjoint (i.e. may not contain the same locus or allele). The occurrence of multiple requests should be an exception. Usually, all loci or alleles required should be requested within one message.

The appropriate action if the TYP_REQ.RESOLUT cannot be accepted or has to be changed by the recipient e.g. due to national rules is to inform the requesting side what was done. If only the resolution was changed (the sender will receive something different than ordered - either more or less) or only a part of the requested loci were accepted (the sender will only receive parts of what was ordered): send WARNING or TXT_MSG. For the complete discussion please see TC Minutes MP2007/12.