...
There is no register patient endpoint. Instead, an embedded patient block will accompany all requests. The embedded patient block looks as follows:
| Field | Details |
|---|
| patient | | Expand |
|---|
| | Field | Details |
|---|
| wmdaId* | integer
nullable: false
example: 1234ID provided by the WMDA | | patientId* | string
maxLength: 17
nullable: false
example: P1234XXOrganisation 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: NLISO 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: JohnFirst (given name) of the patient | | lastName | string
maxLength: 30
nullable: true
example: DoeLast (family name) of the patient |
|
|
6.1.4 Embedded Donor Block
In EMDIS, the following messages are linked to the donor updates:
...