Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SendRetrieve
ReservationResultRequestReservationResultRetrieve
  • Reservation Result
    • patient (wmdaId)
    • donor
      • type (adult, adcu, cbu)
      • id (grid, id)
    • referenceCode 
    • expirationDate
    • confirmed
    • remark
  • Donor Block (6.1.4)
  • Meta Block (6.1.1)
  • Payload Reservation Result

...

After the ReservationResult (RSV_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.

...

11 - Donor Release Request (Reservation Release)

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.

...

SendRetrieve
ReservationReleaseRequestReservationReleaseRetrieve
  • Reservation Release
    • patient (wmdaId)
    • donor
      • type (adult, adcu, cbu)
      • id (grid, id)
    • referenceCode 
    • requestDate
    • reason
    • remark
  • Meta Block (6.1.1)
  • Payload Reservation Release

...

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. 

5.

...

12 - Workup Request

Future Phase

5.

...

13 - Workup Status

Future Phase

5.

...

14 - 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.

...

SendRetrieve
RequestCancellationRequestRequestCancellationRetrieve
  • Request Cancellation
    • patient (wmdaId)
    • donor
      • type (adult, adcu, cbu)
      • id (grid, id)
    • referenceCode 
    • requestType
    • reason
    • remark
  • Meta Block (6.1.1)
  • Payload Request Cancellation

5.

...

15 - Request Rejected (NO_RES)

This message is used to notify the requesting registry when a request cannot be fulfilled.

...

SendRetrieve
RequestRejectedRequestRequestRejectedRetrieve
  • Request Rejected
    • patient (wmdaId)
    • donor
      • type (adult, adcu, cbu)
      • id (grid, id)
    • referenceCode 
    • requestType
    • reason
    • remark
  • Meta Block (6.1.1)
  • Payload Request Rejected

...

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.

...

16 - 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.

SendRetrieve
ResultReminderRequestResultReminderRetrieve
  • Result Reminder
    • patient (wmdaId)
    • donor
      • type (adult, adcu, cbu)
      • id (grid, id)
    • referenceCode 
    • requestDate
    • resultType
    • expirationDate
    • remark
  • Meta Block (6.1.1)
  • Payload Result Reminder


5.

...

17 - 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.

...

18 Request + Response Flows

Generic 

Extended Typing 

Infectious Disease Marker

...