6.1 Embedded blocks 

6.1.1 Embedded Meta Information block

The additional meta-information "blocks" are added to the response to a submitted request and to the retrieved message to ensure that both registries are aware of:

• Assigned message identifier.
• A timestamp.
• Which registry sent the information (sending registry).
• What type of response is provided by the WMDA Match Connect system.
• Any failed validations detected by the Match Connect system.
• A sequence number, so that the receiving registry knows if any message is missing. 
• A message type.

6.1.2 Embedded 'generalInformation' Response block

In addition to the meta block, WMDA will provide a standard response to each retrieve-type message sent to Match-Connect. 

6.1.3 Embedded Address block (NEW_ADD)

With this message block, the contact information of the hub's institutions, namely Financial institutions, Transplant Centers, and Laboratories are shared with the partner hubs. Thus a partner hub has all the required contact information for the Institution contained in Donor Requests. 

• Hubs are required to keep this contact information up to date.
• It’s not only useless but forbidden to give a postbox (POB) in a LAB address since this address is used for the delivery of samples. For the same reason ZIP code, City, and Country are required in the address block.
• The contactPerson is required if the INST_TYPE is ”LAB”.

• Organisation unique identifier for the institution (formerly known as INST_ID):

  • Should remain stable over time and must not be assigned to different institutions.
  • Is a unique reference to an institution.
  • Allows local address management if needed (e.g. for other use cases) by receiving registry and backward compatibility to existing EMDIS implementations. 
  • Provided by the local registry system.  
  • Should be worldwide unique.
    • Should follow the construct of ION + local address id. 
      • The ION to be used is the ION of the patient registering registry (PR).
  • Should be provided as a user-friendly (displayable) id for use on screens and on documentation.

  
  

In the Match-Connect system, the addresses will be embedded in the donor requests. See Chapter Requests for details.

Example of a request with institutionPaying object: see TYP_REQ message.

6.1.4 Embedded Patient Block

There is no "register patient" endpoint. Instead, an embedded patient block will accompany all requests. 

Note: in Connect API the following fields (firstName, lastName, dateOfBirth, diagnosis, sex) are optional compared to EMDIS.

Rules:

• When providing drb3 , drb4 , or drb5, the combination of these loci can have a maximum of two typing fields. If more values are provided, a soft fail occurs. The API will soft fail with HTTP 200. The message will be sent and is retrievable including a warning.
• When providing required hla loci (a, b , drb1), then either dna  or serology  must be provided. If neither is provided, a hard fail occurs. The API will hard fail with HTTP 400

6.1.5 Embedded Donor Block (donor in request)

If the embedded donor block is part of a message type that may not result in updates of donor-related data, the embedded donor block (donor in request block) is used. 

Only sending a grid, cordId or adcuId for message types with static donor information enhances privacy and security through data minimisation.

Rules:

• The API will hard fail with HTTP 400 if the donorId does not match the format required for the selected donorType:
  • The donorId for donorType adult must be grid (minLength: 19, maxLength: 19, example: 9991012070433202000)
  • The donorId for donorType adcu must be adcuId (minLength: 13, maxLength: 13, example: A999916123456)
  • The donorId for donorType cbu must be cordId (minLength: 1, maxLength: 25, example: CB1234567)

6.1.6 Embedded Adult Donor Block (donor in response)

In EMDIS, the following messages are linked to the donor updates:

• TYP_RES
• IDM_RES
• NO_RES

These three will be replaced with the Match-Connect API endpoints that have the donor details embedded in the message. Respective endpoints of IDM_RES and TYP_RES will deliver new IDM and new typing details, and all the mentioned endpoints will also inform the patient registry of the new donor status.

The corresponding endpoints in Match-Connect are:

• extendedTypingDonorResponseRequest
• infectiousDiseaseMarkerDonorResponseRequest
• requestRejectedRequest

These donor updates are for the receiving registry (patient registry) only. So the sending (donor) registry is responsible for sending a DIFF upload to the S&M system in parallel to keep information in sync.

Rules:

• When providing drb3 , drb4 , or drb5, the combination of these loci can have a maximum of two typing fields. If more values are provided, a soft fail occurs. The API will soft fail with HTTP 200. The message will be sent and is retrievable including a warning.
• When providing required hla loci (a, b , drb1), then either dna  or serology  must be provided. If neither is provided, a hard fail occurs. The API will hard fail with HTTP 400

6.1.7 Embedded CBU Block (in response)

In EMDIS, the following messages are linked to the CBU updates:

• TYP_RES
• IDM_RES
• NO_RES

These three will be replaced with the Match-Connect API endpoints that have the CBU details embedded in the message. Respective endpoints of IDM_RES and TYP_RES will deliver new IDM and new typing details, and all the mentioned endpoints will also inform the patient registry of the new CBU status.

The corresponding endpoints in Match-Connect are:

• extendedTypingCbuResponseRequest
• infectiousDiseaseMarkerCbuResponseRequest
• requestRejectedRequest

These CBU updates are for the receiving registry (patient registry) only. So the sending (donor) registry is responsible for sending a DIFF upload to the Search & Match system in parallel to keep information in sync.

6.1.8 Embedded Attachment block

The Embedded Attachment block is used to exchange references (attachmentGuid) of attachments between registries. It contains all the information required by the receiving registry to download files stored in the WMDA blob storage.

Rules

• Each message can include up to 10 Embedded Attachment Blocks.

• Each block represents a single attachment and contains three mandatory fields:

  • attachmentGuid  - the unique identifier of the uploaded file.

  • attachmentDescription - type of the file.

  • fileName - name of the file.

• The receiving registry downloads each file separately using the Download Attachment endpoint

• The block can be part of a request message or the explicit Document Exchange message. The following endpoints contain Embedded Attachment block:

• • /api/v2/extendedTypingRequest (TYP_REQ)
  • /api/v2/extendedTypingResponse (TYP_RES)
  • /api/v2/sampleRequest (SMP_REQ)
  • /api/v2/sampleInfo (SMP_INFO)
  • /api/v2/sampleArrival (SMP_ARR)
  • /api/v2/sampleResponse (SMP_RES)
  • /api/v2/infectiousDiseaseMarkerRequest (IDM_REQ)
  • /api/v2/infectiousDiseaseMarkerResponse (IDM_RES)
  • api/v2/reservationRequest (RSV_REQ)
  • /api/v2/reservationResponse (RSV_RES)
  • /api/v2/reservationRelease
  • /api/v2/requestCancellation (REQ_CAN)
  • /api/v2/requestRejected (NO_RES)
  • /api/v2/resultReminder (RES_REM)
  • /api/v2/GenericRequest
  • /api/v2/infoMessage

6.2 Message Response

The message response is intended as an automated response to every user-generated message. It serves three purposes:

• message acknowledgement
• warning
• message denial

This is a purely machine-to-machine type of message, as compared to EMDIS where such responses can be user-generated. 

Note: The concept of the REF_CODE field used in EMDIS is replaced by the referenceMessageId assigned by the central system to each message. The Message Response must use the referenceMessageId of the original message as the Reference ID in its structure.

6.3 Instruments

6.3.1 Info message

Usage: PR <-> DR

The infoMessage endpoint is useful for conveying notes, comments or attachments about a particular donor, patient/donor pair, or request. To reflect this, the text message must contain a 'donor in request' block that can be supported by a patient and or referenceMessageId.

Note: Since Warnings are going to be automated, we must keep Info Message as the only means for user communication.

6.3.2 Upload and download attachment

The sending registry uploads a file to the WMDA blob storage using the uploadAttachment endpoint and specifies the receiving registry. Once uploaded, the API returns attachmentGuid, which is then shared with the receiving registry to download the file using the downloadAttachment endpoint.

Rules:

• After a successful upload, an attachmentGuid is returned in the response.

• Uploaded file is stored in the WMDA blob storage for a maximum of 90 days after upload. 
• If it was not downloaded within 90 days, it will be automatically deleted and must be uploaded again if it is still needed to be sent.
• After the first successful download, the document can be downloaded multiple times within the next 72 hours. Once this period expires, the document is deleted from WMDA storage and must be requested again if needed.

• The attachmentGuid must be shared with the receiving registry through endpoints that include an Embedded Attachment block.

• The receiving registry uses the downloadAttachment endpoint to download the file from blob storage.

• Only one file can be uploaded or downloaded at a time.

• Each file must be uploaded separately using the uploadAttachment endpoint.

• Each uploaded file can be linked to only one receiving registry.

• If a file needs to be shared with another registry, it must be uploaded again specifically for that registry.

• Maximum file size: 10 MB.

• Supported file format: PDF only.

6.4 Alert message (new message, to be implemented in v2.2)

The Alert message is used to broadcast some important information about the system, like a planned service outage. Messages are generated centrally by WMDA. Members are expected to display them to the users.

6.5 Alert Update message (new message, to be implemented in v2.2)

The Alert Update message is used to broadcast an update about some previous alert. Messages are generated centrally by WMDA. Members are expected to display them to the users.

6.6 Available Messages

6.6.1 Available Messages

This endpoint allows end users to retrieve an overview of all messages ready to be downloaded, including their corresponding sequence numbers. This information can be used to retrieve the messages from their respective *retrieve endpoints. If desired, the messages can be pulled in chronological order, given by the sequence numbers. Each "retrieve" endpoint will have the optional parameter "sequenceNumber", which allows for an individual collection of the corresponding message(s). If that parameter is left empty, all available messages are retrieved (according to the limit set in the parameters). 

6.6.2 All Available Messages /* Proposed - not yet implemented */

This endpoint allows end users to retrieve an array of all messages ready to be downloaded, including their content. This would allow a registry to call just one endpoint to collect all messages.

Limitations:
This option does not work for all applications/tooling, like defining custom API connectors in the 365 PowerPlatform. In those cases the same static structure for all call responses on a specific endpoint is not only IBP, but also required. 

6.7 Recover Messages

To recover or "restore" a soft-deleted message, users can call the "recoverMessages" endpoint. This endpoint allows users to bring back messages that were soft-deleted within a 72-hour timeframe.

This approach provides an additional safety measure for end users. If a message was mistakenly deleted during the retrieval process, or if there is a need to recover soft-deleted data, this mechanism allows for data recovery without permanent loss.

Users should be aware that the functionality to restore messages is limited to 72 hours. After this window, the soft-deleted messages are permanently removed from the system. Also see: section 2.4.7 Message storage retention policies in the Technical Guidelines chapter.