- The Match-Connect technical specifications consist of the API documentation and the documents listed below. When developing a Match-Connect implementation all content of the following documents is relevant and needs to be considered:
- The Semantics of Match-Connect Messages
- Match-Connect Data Dictionary
The reference code (REF_CODE) must be unique over all types of messages at the side of the sending partner.- A Donor_DIFF block is embedded in every result message, i.e. TYP_RES, IDM_RES, SMP_RES, RSV_RES or NO_RES message as the donor record is changing in its source.
- More generally: every time data on a match list that was provided by donor upload changes, a DIFF upload becomes necessary to update the master data.
- The term ”donor” in this document usually means ”adult donor” or ”cord blood unit” or "adult donor cryopreserved unit".
- The institution paying (INST_PAY) has to be of the institution type (INST_TYPE) FIN.
- It is required to transmit every known field value every time. If a field is not sent, its contents are to be deleted at the receiver.
- The WMDA nomenclature files (http://hla.alleles.org/wmda/index.html) must be used for all HLA fields. The recipient may reject messages with invalid values. The details are described in the WMDA Guidelines for use of HLA Nomenclature (https://www.nature.com/articles/bmt201393; follow the link ”Supplementary information”).
- The Match-Connect semantics for the WMDA approved additional codes are defined as follows:
...