...
| Send | Retrieve |
| SampleRequestRequest (comments reffer to changes to the current API definition) | SampleRequestRetrieve |
|
|
5.4 - Sample Information
The SampleInfoRequest (and SampleInfoRetrieve) is used to sent relevant secondary information which may arise in the context of sample request.
The referenceCode is the 'massageId' from the request message.
EMDIS Semantic:
The SMP_INFO message can only be exchanged in one direction: from donor side to patient side.
Sample information is always referencing a sample request.
Sample information is only valid as long as the referenced sample request is considered as ”open” or the donor is reserved for this patient after the sample request.
A request is considered as ”open” as long as the searching registry has neither reported the sample result nor a ”service cannot be performed (NO_RES)” information nor a request cancellation.
There might be several sample information messages within the context of one sample request. Subsequent sample information is regarded as new or additional information and not as updates.
|
5.4 - Sample Information
The SampleInfoRequest (and SampleInfoRetrieve) is used to sent relevant secondary information which may arise in the context of sample request.
The referenceCode is the 'massageId' from the request message.
EMDIS Semantic:
The SMP_INFO message can only be exchanged in one direction: from donor side to patient side.
Sample information is always referencing a sample request.
Sample information is only valid as long as the referenced sample request is considered as ”open” or the donor is reserved for this patient after the sample request.
A request is considered as ”open” as long as the searching registry has neither reported the sample result nor a ”service cannot be performed (NO_RES)” information nor a request cancellation.
There might be several sample information messages within the context of one sample request. Subsequent sample information is regarded as new or additional information and not as updates.
| Send | Retrieve |
| SampleInfoRequest (comments reffer to changes to the current API definition) | SampleInfoRetrieve |
|
|
5.5 - Sample Arrival
The SampleArrivalRequest (and SampleArrivalRetrieve) is used to transmit proposed date of sample arrival.
The message ID (correlationGUID) of this message will be used as 'referenceCode' for the rest of the request related message flow.
EMDIS Semantic:
This message is sent in response to a SMP_REQ and indicates the arrival date of the sample.
| Send | Retrieve |
| SampleArrivalRequest (comments reffer | |
| Send | Retrieve |
| SampleInfoRequest (comments reffer to changes to the current API definition) | SampleInfoRetrieveSampleArrivalRetrieve |
|
|
5.5 - Sample Arrival
|
|
5.6 - Sample Results
The SampleResponseRequest (and SampleResponseRetrieve) is used to transmit the results of the sample requestThe SampleArrivalRequest (and SampleArrivalRetrieve) is used to transmit proposed date of sample arrival.
The message ID (correlationGUID) of this message will be used as 'referenceCode' for the rest of the request related message flow.
EMDIS Semantic:
This message is sent in response to a SMP_REQ and indicates the arrival date of the sample.
...
- Payload
- patient (just the wmdaID)
- donor (format change see above)
- referenceCode (see text above)
- arrivalDate
- collectionDate
acknowledgementId(not needed anymore → MSG_RSP)- labelId (is there a usecase for this ID, where it is not the donor ID?)
- aampleType (missing: was this field dropped by purpose?)
- remark
...
- MetaInformation
- Payload
- patient (just the wmdaID)
- donor (format change see above)
- referenceCode (see text above)
- arrivalDate
- collectionDate
acknowledgementId(not needed anymore → MSG_RSP)- labelId (is there a usecase for this ID, where it is not the donor ID?)
- aampleType (missing: was this field dropped by purpose?)
- remark
The fields for the infectious disease markers are included in this message in order to give the transplant centres the possibility to report the results of IDMs they might have tested. DON_ACCPT = ”N” means: donor can be released immediately.
DON_ACCPT = ”Y” means: please reserve the donor according to your national rules. If possible, the donor should be reserved at the remote hub and reported back to the requesting hub by a DONOR_CB with D_STATUS = ”RS”. All the other patients the donor might have been reported for should receive a DONOR_CB with D_STATUS = ”OP”.
If no SMP_RES can be sent then a NO_RES should be sent with the reason field populated to explain why.
| Send | Retrieve |
| SampleResponseRequest (comments reffer to changes to the current API definition) | SampleResponseRetrieve |
5.6 - Sample Results
The SampleResponseRequest (and SampleResponseRetrieve) is used to transmit the results of the sample request.
The message ID (correlationGUID) of this message will be used as 'referenceCode' for the rest of the request related message flow.
EMDIS Semantic:
The fields for the infectious disease markers are included in this message in order to give the transplant centres the possibility to report the results of IDMs they might have tested. DON_ACCPT = ”N” means: donor can be released immediately.
DON_ACCPT = ”Y” means: please reserve the donor according to your national rules. If possible, the donor should be reserved at the remote hub and reported back to the requesting hub by a DONOR_CB with D_STATUS = ”RS”. All the other patients the donor might have been reported for should receive a DONOR_CB with D_STATUS = ”OP”.
If no SMP_RES can be sent then a NO_RES should be sent with the reason field populated to explain why.
| Send | Retrieve | |
| SampleResponseRequest (comments reffer to changes to the current API definition) | SampleResponseRetrieve | |
|
|
|
5.7 - Infectious Disease Marker Request
...