...

3.1 - Patient Identification

Anchor3.1 - Patient Identification3.1 - Patient IdentificationA patientId may be provided when registering a new patient.  Upon registration, a wmdaId will be assigned and returned.  The wmdaId itself is guaranteed to be globally unique, though it cannot guarantee that the patient is not identified with another wmdaId.  The wmdaId must be used to identify the patient in all calls to the Search, Match & Connect (SMC) service after the initial patient registration.

...

3.2 - Create Patient (Send Patient)

...

3.2 - Create Patient3.2 - Create PatientThe CreatePatientRequest is used to submit a patient to the Search & Match Service.  This call returns a wmdaId for the patient.

Send
CreatePatientRequest
Patient

3.3 - Update Patient

...

3.3 - Update Patient3.3 - Update PatientThe UpdatePatientRequest is used to update a patient with the Search & Match Service.

...

3.5 - Register Patient   

...

There is no registerPatient endpoint.  A patient is registered with a partner registry at the time of request - see the section on Requests. 

3.6 - Update Registered Patient    

...

The updateRegisteredPatientRequest is used to update a registered patient with a partner registry.  Empty / blank fields in the payload will mean deletion.  Missing fields will have no effect.  The central hub can review the contents and update any relevant values that are (already) stored in the Search & Match system.  ??The response of the api will provide results (fields / values) of the updates made.??

...

3.7 - Update Registered Patient Status    

Anchor3.7 Update Patient Status3.7 Update Patient StatusUpdatePatientStatusRequest

...

3.8 - Request More Patient Info 

...

Allows a donor registry to request more details about a patient from the patient registry, e.g. if that extra information is needed in a VT or later maybe a WU request.  Locally developed and managed national rules should indicate which PII is required at which stage of the process.

...