1.0.2 - release
1.0.2 - release
KisimScheduling - Local Development build (v1.0.2) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
For some patients a client system might receive appointments created in KISIM by an asynchronous AppointmentResponse. This is for example the case for different portal solutions where the patient is known to the portal and patients want to see their appointments. Since the appointment was created in KISIM, the patient might want to move such an appointment. This use-case is described here
Inside KISIM a new appointment is created for a specially flagged patient. Such an appointment is then sent to the client system by appointment response. The client system now has the KISIM Id to move such an appointment. The steps to move an appointment are handled in the Reschedule appointment use-case.
Depending on permissions on the appointment, a client system might not be able to reschedule an appointment created by Kisim. In that case it will get a http status code 400 back. If the client system should be able to reschedule the appointment, the permissions on the server need to be changed accordingly by Cistec.