Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: v1.01

Table of Contents
absoluteUrltrue

2.1 RulesRules 

  • The Match-Connect technical specifications consist of an OpenAPI specification 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
    • The Match-Connect Data Dictionary
  • A Donor 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 changes in its source.
    • More generally: every time data on a match list provided by donor upload changes, a DIFF upload becomes necessary to update the master data.
  • The term" donor" in this document usually refers to "adult donor", "cord blood unit", or "adult donor cryopreserved unit." 
  • The paying institution (INST_PAY) has to be of the institution type (INST_TYPE) FIN.
  • Empty/blank/missing fields in the payload mean deletion. 
    • Consequently, empty/blank integer or float values must be provided as null values.
  • The WMDA nomenclature files (http://hla.alleles.org/wmda/index.html) must be used for all HLA fields. The central hub and/or the receiving registry 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:

...