...
- WMDA will implement the endpoints to POST the mentioned reports for each donor type.
- Participating registries will have to implement the above mentioned reports for both GET and POST (instead of DONOR_CB)
- Here is the comparison of the DONOR_CB and the API endpoints: EMDIS vs API.xlsx
5.1 -
...
Extended Typing Request
This message is used to request an extended typing of a donor (adult, adcu, cbu?). It will primarily contain information about what to type and for which donor.
Added to that a patient block (ref) containing up-to-date information about the patient, and an address block (6.1) containing up-to-date contact-information about the needed institution(s).
Expected return message is 'typing result' (5.2) or 'request rejected' (5.14).
Check paragraph '5.16 Generic' and '5.16 Extended Typing' for the related message flows.
| Send | Retrieve |
| TypingRequest | TypingRequestRetrieve |
|
|
...
The appropriate action if the typing request 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 a MSG_RSP containing the warning.
5.2 -
...
Extended Typing Results
This message is used to send the results of the initial ET request back to the requesting registry.
Check paragraph '5.16 Generic' and '5.16 Extended Typing' for the related message flows.
| Send | Retrieve |
| TypingResponse | TypingResponseRetrieve |
|
|
Rules
Needed
/post_api_v1_TypingResponseRequest
After the TYP_RES message, a DONOR_CB with the updated donor data is mandatory to ensure up-to-date master data. See 4.0 above.
...