Page History

Table of Contents

6.1 Embedded blocks

6.1.1 Embedded Meta block

The additional meta-information "blocks" are added to ensure the receiving registry is aware of:

...

}

6.1.2 Embedded Address block

Original message: Address to broadcast [NEW_ADD]

...

• Institution Type INST_TYPE Req 3
• Institution Identification INST_ID Req 10
• Address Line 1 ADDR_1 Req 40
• Address Line 2 ADDR_2 Opt 40
• Address Line 3 ADDR_3 Opt 40
• Contact person PERSON Opt 40
• ZIP code ZIP Req 10
• City CITY Req 40
• Country COUNTRY Req 2
• Phone Number PHONE Req 20
• Fax Number FAX Opt 20
• Email address EMAIL Opt 60
• Accreditations obtained ACCREDITATION Opt 5
  • Position 1: NetCord-FACT
  • Position 2: AABB
  • Position 3: to be defined
  • Position 4: to be defined
  • Position 5: to be defined

6.1.3 Embedded Patient Block

There is no register patient endpoint.  Instead, an embedded patient block will accompany all requests.  The embedded patient block looks as follows:

• Request

• Patient

  wmdaId*	integer nullable: false example: 1234 ID provided by the WMDA
  patientId*	string maxLength: 17 nullable: false example: P1234XX Organisation unique identifier for patient. Cannot be set unless "legalTerms" is set to "true". Do not use real names here.
  hla*	{...}
  idm	{...}
  dateOfBirth	string($date) nullable: true maxLength: 10 example: 1961-05-27
  diagnosis	{...}
  diseasePhase	string nullable: trueEnum: Array [ 48 ]
  ethnicity	string nullable: trueEnum: Array [ 20 ]
  poolCountryCode	string maxLength: 2 pattern: ^[A-Z]{2} nullable: true example: NL ISO 3166-1 alpha-2 Country Code (capitalized)
  abo	string nullable: trueEnum: Array [ 4 ]
  rhesus	string nullable: trueEnum: Array [ 2 ]
  weight	integer nullable: true minimum: 1 maximum: 999 example: 76
  sex	string nullable: trueEnum: Array [ 2 ]
  firstName	string maxLength: 30 nullable: true example: John First (given name) of the patient
  lastName	string maxLength: 30 nullable: true example: Doe Last (family name) of the patient

6.1.4 Embedded Donor Block

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

...

Here is the comparison of the DONOR_CB and the API endpoints: EMDIS vs API.xlsx

6.

...

2 Message Response

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

...

6.

...

3 Alert message

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

...

6.

...

4 Alert Update message

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.

...