...
Current structure is:
| donor* | {
} |
ADCU and CBU have similar structure, but adult donor has the ID (GRID) right away.
Suggested structure for the adult donors:
| scd or adult | {
} |
ReferenceCode:
In order to couple messages to the same request, e.g. VT request (SMP_REQ) and its results (SMP_RES) all messages following a request must have a referenceCode as part of the message.
The message ID (correlationGUID) of the request message (TYP_REQ, IDM_REQ, SMP_REQ, RSV_REQ, etc...) will be used as 'referenceCode' for the rest of the request related message flow.
embedded donorBlock:
The following messages are linked to the donor updates:
- InfectiousDiseaseMarkerResultRequest (IDM_RES)
- TypingResponseRequest (TYP_RES)
- NoResultRequest (NO_RES)
- ReservationResultRequest (RSV_RES)
These donor updates are for the receiving registry (patient registry) only and will not be updated in the central HUB. So the sending registry is responsible to send a DIFF upload to the S&M system in parallel to keep information in sync.
Details of the meta block see in
https://apispecs.wmda.info/?urls.primaryName=Search%20%26%20Match#/searches/retrieveFullReportDonors
and
https://apispecs.wmda.info/?urls.primaryName=Search%20%26%20Match#/searches/retrieveFullReportCBUs
In the future another message for ADCUs may come to play.
- Here is the comparison of the DONOR_CB and the API endpoints: EMDIS vs API.xlsx
5.1 - Extended Typing Request
...