Versions Compared

Key

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

...

3.4 -

...

Register Patient   

...

Anchor
3.4 - Register Patient
3.4 - Register Patient

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

3.5 - Update Registered Patient    Image Added

Anchor
3.5 - Update Registered Patient
3.5 - Update Registered Patient

The registerPatientRequest updateRegisteredPatientRequest is used to register update a registered patient with a partner registry.  This message accompanies all requests.Entire payload may be sent by the sending registry.  The 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.5 - Update Registered Patient    Image Removed

...

The updateRegisteredPatientRequest is used to update a registered patient with a partner registry.

UpdateRegisteredPatientRequest

...


3.6 - Update Registered Patient Status    

...