Versions Compared

Key

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

...

  • A patient registration Embedded Patient 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.
  • (warning) The requested donor has to be reserved at the remote hub and reported back to the requesting registry by a Embedded Donor Block within a Reservation Response reflecting the changed donor status (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 within the respective message, e.g. updated HLA information resulting from a typing request Extended Typing Request in a Extended Typing Result. 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 responding to the original 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.

...