...
This message is used to notify the of the requesting patient registry if Reservation Request has been confirmed by the donor registry registry.
| Send | Retrieve |
| ReservationResultRequest | ReservationResultRetrieve |
|
|
...
This message is used so the patient registry can notify the donor registry to release a donor reservation when it is no longer needed (e.g. patient deceased or was transplanted with another donor). This should be used if the Reservation Request has been fulfilled, if the Reservation Request has not been fulfilled then a Request Cancellation message should be used.
This is a change request with respect to the current procedure and should be handled as such as it has implications on local systems.
| Send | Retrieve |
| ReservationReleaseRequest | ReservationReleaseRetrieve |
| |
| Send | Retrieve |
| ReservationReleaseRequest | ReservationReleaseRetrieve |
|
|
...
After the Reservation Release message which includes an embedded donor (DONOR_CB) block, a separate update must be made to the Search & Match system with the updated donor data to ensure up-to-date master data
This is a change request with respect to the current procedure and should be handled as such as it has implications on local systems.
----
Consulation items Consulation items from the TWG - Stopping a Search
Consider incorporation of this text somewhere in this chapter:
"
Preference: Requests should be stopped explicitly by the patient registry.
- If the request has been fulfilled, the cancellation will be rejected.
However, in this case, the donor might still be reserved for the patient. In case overall search status is no longer sent, BRG recommends to consider a message to release the donor reservation when it is no longer needed (e.g. patient deceased or was transplanted with another donor). A reason should be provided. - If the request has not yet been fulfilled, the cancellation will be accepted and the donor released from reservation (when applicable).
"
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
Rules
After the Request Rejected (NO_RES) message which includes an embedded donor (DONOR_CB) block, a separate update must be made to the Search & Match system with the updated donor data to ensure up-to-date master data
5.15 - Result Reminder (RES_REM)
Needed
...
5.13 - Request Cancellation
This message is used to cancel a previous request that has been sent to the donor registry. The Request It must have a preceding request that is being cancelled.
| Send | Retrieve |
| RequestCancellationRequest | RequestCancellationRetrieve |
|
|
5.14 - Request Rejected (NO_RES)
This message is used to notify the requesting registry when a request cannot be fulfilled.
| Send | Retrieve |
| RequestRejectedRequest | RequestCancellationRetrieve |
|
|
Rules
After the Request Rejected (NO_RES) message which includes an embedded donor (DONOR_CB) block, a separate update must be made to the Search & Match system with the updated donor data to ensure up-to-date master data
5.15 - Result Reminder (RES_REM)
This message is sent by the requesting registry to the receiving registry to remind the receiving registry of an outstanding results from a previous request.
| Send | Retrieve |
| ResultReminderRequest | ResultReminderRetrieve |
|
|
5.16 - Generic Request
Used to register a patient (by the embedded patientBlock).
Is used for example for direct WU requests until 5.11 is available or to reactivate a closed patient case on recieving registry side.
5.
...
17 Request + Response Flows
Generic
Extended Typing
Infectious Disease Marker
...