Page History

...

Identifier

Description

patientId

Provided by the local registry system.
Should be worldwide unique.
- Should
be provided as a user-friendly (displayable) id for use on screens and on documentation.Should
- follow the construct of hub code + local patient id.
  - The hub code should be the two-character ISO country code of the registry (e.g.
DE12345
- - DE for Germany)
    - In the case of multiple registries in one country, a replacement code will be assigned.
Should be provided as a user-friendly (displayable) id for use on screens and on documentation.

TODO: Discuss whether patientId should be made required

wmdaId

Generated by the central (SMC) system.
Must be unique.
Must be used for all system-to-system patient identification after the initial patient registration.
Should be displayed on screens and on documentation.

...

Patient Identification	patientId	string nullable: true
Patient HLA	hla	HLA
Patient Diagnosis	diagnosis	DiagnosisRequest
Patient Disease Phase	diseasePhase	string nullable: true
Patient IDMs	idm	IdmRequest
Patient Date of Birth	dateOfBirth	string($date-time) nullable: true
Patient Ethnicity	ethnicity	string nullable: true
Patient's Country Code	poolCountryCode	string nullable: true
Patient Transplant Centre	transplantCentreId	string nullable: true
Patient Blood Group	abo	string nullable: true
Patient Rhesus	rhesus	string nullable: true
Patient Weight	weight	integer($int32) nullable: true
Patient Sex	sex	string nullable: true
Consent	legalTerms	boolean (If you keep the legalTerms value at "false" or don't send it when creating a new patient, you have indicated you will not comply with legal terms and therefore are not allowed to store a pId. In that case the pId is set to the same value as the wmdaId. This behaviour mirrors the behaviour in the web GUI of WMDA Search & Match. If you click on the "No, I don't have consent" button you are also not allowed to store a patient ID or comment.)

Page tree