Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

3.4 - Update Patient Status


3.5 - Register Patient   

Anchor
3.4 5 - Register Patient
3.4 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    Image Modified

Anchor
3.5 6 - Update Registered Patient
3.5 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.??



Additional fields to be considered (checked items have been added to Swagger):

DescriptionNameTypeComment
  •  Patient Identifier
patientId

string

nullable:  false


  •  Sending Registry
regSend

string

nullable: false

Retrieve message only
  •  Receiving Registry
regReceive

string

nullable: false


  •  Patient First Name
firstName

string

nullable: true


  •  Patient Last Name
lastName

string

nullable: true


3.

...

7 - Update Registered Patient Status    Image Modified

Anchor
3.6 7 Update Patient Status
3.6 7 Update Patient Status

UpdatePatientStatusRequest

...

Sending RegistryregSend

string

nullable: false

Receiving RegistryregReceive

string

nullable: false

WMDA Patient IdentifierwmdaId

integer

nullable: false

Old Patient StatepriorStat

string

nullable: true

New Patient StatenewStat

string

nullable: false

Reason For Changereason

string

nullable: true

3.

...

8 - Request More Patient Info Image Modified

Anchor
3.7 8 - Request More Patient Info
3.7 8 - Request More Patient Info

...

TODO:  Design message flow & elaborate semantic detail.

3.

...

9 - Message Flows