A register_patient message will be sent together with all requests. This message contains both wmdaId and patientId of the patient.
/post_api_v1_PatientRegistration
Provision of the donor ID in every request must be changed.
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 | {
} |
5.0 - DONOR_CB message
It was agreed that we must implement DONOR_CB message API to preserve the original EMDIS logic.
S&M APIs have the DONOR_CB message split into
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.
Proposal: change the Semantics by requesting an "updated donor" message instead of DONOR_CB.
- 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 - Typing Request
Needed
/post_api_v1_TypingRequestRequest
5.2 - Typing Results
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.
5.3 - Sample Request
Needed
https://apispecs.wmda.info/?urls.primaryName=Connect%20API#/Message/post_api_v1_SampleRequestRequest
5.4 - Sample Information
Needed
https://apispecs.wmda.info/?urls.primaryName=Connect%20API#/Message/post_api_v1_SampleInfoRequest
5.5 - Sample Arrival
Needed
https://apispecs.wmda.info/?urls.primaryName=Connect%20API#/Message/post_api_v1_SampleArrivalRequest
5.6 - Sample Results
Needed
5.7 - Infectious Disease Marker Request
Needed
5.8 - Infectious Disease Marker Results
Needed
After the IDM_RES message, a DONOR_CB with the updated donor data is mandatory to ensure up-to-date master data. See 4.0 above.
5.9 - Reservation Request
Needed
5.10 - Reservation Result
Needed
After the RSV_RES message a DONOR_CB with the updated donor status is mandatory to reflect the change. See 4.0 above.
5.11 - Workup Request
Future Phase
5.12 - Workup Status
Future Phase
5.13 - Request Cancellation
Needed
5.14 - Request Rejected (NO_RES)
Needed
https://apispecs.wmda.info/?urls.primaryName=Connect%20API#/Message/post_api_v1_NoResultRequest
If the results cannot be delivered, a NO_RES message followed by a DONOR_CB message is returned which includes the new donor status. See 4.0 above.
5.15 - Result Reminder (RES_REM)
Needed