...
| Send | Retrieve |
| RequestRejectedRequest | RequestRejectedRetrieve |
| Expand |
|---|
| | Field | Details |
|---|
| payload* | | Expand |
|---|
| | Field | Details |
|---|
| patient* | Embedded Patient Block | | donor* | Embedded Donor Block | | referenceCode* | string($uuid) | | requestType* | string maxLength: 3Type of request REQ_TYPE Req 3 | | reason* | string maxLength: 3 minLength: 2Reason REASON Req 3 | | remark | string maxLength: 120 nullable: trueRemark REMARK Opt 120 |
|
| | recipient* | string maximum: 9999 minimum: 0 maxLength: 4 minLength: 4 example: 12344 digit ION of recipient | | correlationGuid* | string($uuid) Sender generated GUID used to correlate response acknowledgement |
|
| Expand |
|---|
| | Field | Details |
|---|
| wmdaResponse | {...} |
|
| | Expand |
|---|
| | No parameters specified |
Meta Block (6.1.1)Payload Request Rejected |
Rules
After the Request Rejected 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
...