14.1 - Typing Request
24.2 - Typing Results
34.3 - Sample Request
44.4 - Sample Information
54.5 - Sample Arrival
64.6 - Sample Results
74.7 - Infectious Disease Marker Request
84.8 - Infectious Disease Marker Results
94.9 - Reservation Request
104.10 - Reservation Result
114.11 - Workup Request
124.12 - Workup Status
134.13 - Request Cancellation
144.14 - Request Rejected (NO_RES)
154.15 - Result Reminder (RES_REM)

A register_patient message will be sent together with all requests. This message contains both wmdaId and patientId of the patient.

Provision of the donor ID in every request must be changed.

Current structure is:

donor*

{

description:

Supply one node from the following

grid

string
nullable: true
maxLength: 19
minLength: 19
example: 9991012070433202000

adcu

{

id*	string maxLength: 13 N/A in EMDIS

}

cbu

{

id*	string maxLength: 17 CBU Identification2 CB_ID Opt 17

}

ADCU and CBU have similar structure, but adult donor has the ID (GRID) right away.

Suggested structure for the adult donors:

scd or adult

{

grid*

string
nullable: true
maxLength: 19
minLength: 19
example: 9991012070433202000

}

4.1 - Typing Request

Needed

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.

/post_api_v1_TypingRequestRequest