...
Address block structure (HP's suggestion, requires discussion regarding the accreditation field and extension of the use field):
https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-structures-r4/org/hl7/fhir/r4/model/Address.html
e.g.
The name of the city, town, suburb, village or other community or delivery center. | ||
Country - a nation as commonly understood or generally accepted. | ||
The name of the administrative area (county). | ||
This component contains the house number, apartment number, street name, street direction, P.O. | ||
Time period when address was/is in use. | ||
A postal code designating a region defined by the postal service. | ||
Sub-unit of a country with limited sovereignty in a federally organized country. | ||
Specifies the entire address as it should be displayed e.g. | ||
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. | ||
The purpose of this address. |
Institution Type INST_TYPE Req 3Institution Identification INST_ID Req 10Address Line 1 ADDR_1 Req 40Address Line 2 ADDR_2 Opt 40Address Line 3 ADDR_3 Opt 40Contact person PERSON Opt 40ZIP code ZIP Req 10City CITY Req 40Country COUNTRY Req 2Phone Number PHONE Req 20Fax Number FAX Opt 20Email address EMAIL Opt 60Accreditations obtained ACCREDITATION Opt 5Position 1: NetCord-FACTPosition 2: AABBPosition 3: to be definedPosition 4: to be definedPosition 5: to be defined
...
- Request
Patient
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-27diagnosis {...} 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: 76sex 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.4 Embedded Donor Block
In EMDIS, the following messages are linked to the donor updates:
- InfectiousDiseaseMarkerResultRequest (IDM_RES)
- TypingResponseRequest (TYP_RES)
- NoResultRequest (NO_RES)
- ReservationResultRequest (RSV_RES)
These donor updates are for the receiving registry (patient registry) only and will not be updated in the central HUB. So the sending (donor) registry is responsible to send a DIFF upload to the S&M system in parallel to keep information in sync.
In the future a block for ADCUs may come to play.
| Donor type | Payload | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Adult donor |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CBU |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ADCU |
Here is the comparison of the DONOR_CB and the API endpoints: EMDIS vs API.xlsx
6.5 Message Response
The message response is intended as an automated response to every user generated message. It serves three purposes:
...