Page History

...

• A patient registration embedded block is sent together with each request. This block contains both the wmdaId and the patientId of the patient.

• Next to the actual request information, whenever institutions are needed, they are sent explicitly as an Embedded Address Block.

• The requested donor has to be reserved at the remote hub and reported back to the requesting registry by an embedded donor block with the donor status reflecting the change (a.k.a. DONOR_CB with D_STATUS = ”RS”).

• All changes in the donors (change of status, updated typing, or IDMs) resulting from the requests are reported back in an embedded donor block. A separate update must be made to the Search & Match system with the updated donor data to ensure up-to-date master data. More information on how to do so may be found here.
• ReferenceCode: In order to couple messages to the same request, e.g. Sample Request and its results, all the request-related messages following the initial request must have a referenceMessageId as part of the message.

  • The message ID (referenceMessageId) of the request message is used as a reference code for the rest of the request-related message flow.

  • Next to the technical referenceMessageId requests, a human-readable reference code (requestingRegistryReferenceCode) is used for end-user recognition (communication outside the automated system)
    • The requestingRegistryReferenceCode is optional
      
    • The requestingRegistryReferenceCode is part of the original message block
      
    • The requestingRegistryReferenceCode will be generated by the sending registry
    • The requestingRegistryReferenceCode will only be used for human-to-human communication (e.g. could be used on printed invoices)
• Each field inherited from EMDIS Semantics contains a comment describing its purpose in EMDIS and its original name to assist in the transition from EMDIS to Match-Connect.
• Paragraph Request + Response Flows depicts the new message flows.

...

This message is used to request an extended typing of a donor (adult, ADCU, CBU). It primarily contains information about what to type and for which donor.
Expected The expected return message is Extended Typing Results or Request Rejected.

...

• The fields ”earliest and latest date of sample reception” represent the lower and upper limit of the 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 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.
• A number of tubes requested in a sample request or marrow request:
  • 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 of the donor registry.
  • If the number of tubes is unassigned, and not given in the request, the default value number of tubes is one.

...

• The message can only be exchanged in one direction: from the donor side to the 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” and the donor is reserved for this patient after the sample request.
• A request is considered”open” considered ”open” as long as the patient registry has neither reported the sample results nor a Request Rejected message 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.

...

• The common use of the IDM Results message is in response to the Sample Request message, in addition to the shipment of the donor blood sample. Please note there may be a charge involved with this service. If a fee is charged, it may come as a separate item or might be included in the price of the sample shipment. Such IDM Results messages can be sent via a regular EMDIS message - the remote hub must be able to handle it appropriately. The IDM Results must have the same referenceCode as the Sample Request message.
• IDM Results message can be generated in response to two different message requests:
  • Sample Request does not specify what set of infectious disease markers to be tested
  • IDM Request does specify what set of infectious disease markers to be tested
• The field marker is a required field.
• For those hubs reporting infectious disease markers during verification typing, the marker field should contain the IDMs actually tested. There is a fixed-length binary field for the IDM Results message. The blood group may also be reported.
• IDM results can also be reported as a part of the Sample Results message by the hub (transplant center) that requested the blood sample. This is to give the transplant centers the possibility to report the results of IDMs they might have tested.

...

There is no response to this message except for the automated acknowledgementacknowledgment.

...