...
| Identifier | Description |
|---|---|
| patientId |
Risk of nullable is that duplicate patients may be created. Some transplant centers or patient registries may have concerns with sharing a patientId before the point of donor request. If we make patientId required then we should also consider enforcing uniqueness. Decision on nullability deferred to the business requirements group. Proposal: Make patientId required where possible. WMDA office to investigate making mandatory in existing Search & Match Service. If there are legitimate reasons not to (amongst TCs or other), we can add a requirement that the patientId become required at the point of request. |
| wmdaId |
|
...
The updateRegisteredPatientRequest is used to update a registered patient with a partner registry.
TODO: Discuss whether we need this message. Does the requesting registry take responsibility for sending updates to the partners it wants OR does SMC take responsibility for updating patients with all registries with which the patient has been shared?
UpdateRegisteredPatientRequest
...
| Sending Registry | regSend | string nullable: false |
| Receiving Registry | regReceive | string nullable: false |
| WMDA Patient Identifier | wmdaId | integer nullable: false |
| Old Patient State | priorStat | string nullable: true |
| New Patient State | newStat | string nullable: false |
| Reason For Change | reason | string nullable: true |
3.7 - Register Patient with local partners
This came from the Miro board. I don't know exactly what was meant by 'local' partners. But - I think this may be covered by Patient Registration above(?).
...
3.8 - Replace EMDIS PAT_UPD msg
...