...
The SampleRequestRequest (and SampleRequestRetrieve) is used to request a VT for a specific donor/product for a patient. The message, as all requests, has an embedded 'register_patient' part. Next to the actual request informations information the institutions needed are sent explicitly as an embedded 'addressBlock' (6.1).
The message ID (correlationGUID/referenceMessageId) of this message will be used as 'referenceCode' for the rest of the request related message flow.
...
Only one SMP_REQ can be open for a patient / donor pair (please see also the General section about duplicate requests).
The fields ”earliest and latest date of sample reception” represent the lower and upper limit of a period of time in which the blood sample has to be received. If the second date is missing the sample may be received any time after the first date.
...
The address INST_SMP_SENT must not be a P.O. box, since couriers often need a signature upon delivery. Should be part of the addressBlock definition
The SMP_REQ is the only request message where the result also comes from the transplant centre.
The quantity for the first product is optional when requesting DNA from a cord blood unit. In all other requests, the quantity fields for any of the corresponding product fields are required if a product is requested.
...
The maximum amount of material, requested in one sample request or pre-collection sample request, is 100 ml, if not stated otherwise in the national rules. If the number of tubes is unassigned, not given in the request, the default value number of tubes is one.
Duplicate requests on the same day: This issue becomes particularly difficult if SMP_REQs are concerned - sometimes users want to ”correct” their previous request (i.e. forgot to request quantity and product). The correct way of doing this is to cancel the erroneous request first and send the second one later. However, this procedure might also confuse if not carried out on the same working day. In doubt a phone call helps sorting things out.
| Send | Retrieve |
| SampleRequestRequest (comments reffer to changes to the current API definition) | SampleRequestRetrieve |
|
|
...
A request is considered as ”open” as long as the searching recieving registry has neither reported the sample result nor a ”service cannot be performed (NO_RES)” information nor a request cancellation.
...
The message ID (correlationGUID) of this message will be used as 'referenceCode' for the rest of the request related message flow.
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 adding a DONOR_DIFF block to the message STATUS = ”RS”. For all the other patients the donor should be updated by sending a DIFF update to S&M. A delta search will then update the search results for those patients.
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.
...