Stream: implementers
Topic: Appointment
Nata Samarina (Nov 19 2019 at 12:24):
Hello.
There is a task to store information in the Appointment resource, about who created the Appointment (external service) in order to receive the number of such Appointments in the future.
What is better to use?
René Spronk (Nov 19 2019 at 14:53):
Have you looked at the Provenance resource? If you did, is there a reason as to why that wouldn't work?
Brian Postlethwaite (Jan 02 2020 at 10:42):
Or auditevent
David Hay (Mar 23 2021 at 00:02):
Can I just check my understanding of simple appointments (one patient, one practitioner). Suppose a system allows a client to create an appointment by POSTing an Appointment resource to the Appointment endpoint. The system checks that the time/practitioner is available, and if so creates the Appointment internally but returns an AppointmentResponse resource rather than the updated Appointment resource. Is that correct? (the spec notes differences in operation because of iCal alignment)
If subsequently the status is changed (say the Patient has arrived) then the client will locate the appointment resource, update the status and PUT it back to the Appointment endpoint, The system then makes the change and (optionally) returns the Appointment resource. Is that correct?
Brian Postlethwaite (Jun 07 2021 at 06:30):
It will still return the Appointment with all the data completed correctly.
AppointmentResponse is only for "request" style interactions like when you get one in email, and need to reply that you accept it.
This is very solution dependant how that would work.
Last updated: Apr 12 2022 at 19:14 UTC
