A modify patient operation takes place in the module and in the server webservices. Before this operation is fired, the client should be able to identify the context where the operation is taking place (patientId and departmentId) as well as the set of patient fields that the patient should see updated. To execute this operation the client should:

  1. Identify the patientId and departmentId context for the operation. To find a valid execution context, the web service operations module.searchPatient , which returns patientIds for a department, and module.getPatientById , which returns details on a patient, can be used. 
  2. The user should know the valid patient fields in the context of the department where the modify action shall take place. This information can be obtained by consuming the module.getPatientFields service.
  3. Execute a call to module.modifyPatient service providing (i) the context determined in (1.) - (patientId and departmentId) ; and (ii)  a sparse set of  patient field data  that should be modified. As illustrated in the soap-request-reply page.
  4. Execute a call to the server.modifyPatient service providing the data that module.modifyPatient returned in 3.  As illustrated in the soap-request-reply page.

 

If you do not save our patient IDs in the client application but use your own patient identifier (MRN), to identify a patient, you must be careful when a user changes that MRN.
When a user in the client application changes the MRN, you have to search the patient in our system with the old MRN, call modifyPatient providing the new MRN and only now you can discard the old MRN in the client application. Else you will loose the link to the patient between client and server.