Stream: implementers
Topic: Appointments
Jose Costa Teixeira (Jun 05 2019 at 12:07):
AppointmentResponse says it implements the Request pattern... Is that intended?
Jose Costa Teixeira (Jun 05 2019 at 12:10):
I'm looking at a simple scheduling: someone asks for an appointment and it gets confirmed or rejected. So I presume I would have an AppointmentRequest and AppointmentResponse. But atm both Appointment and AppointmentResponse implement the Request
Lloyd McKenzie (Jun 05 2019 at 13:14):
Both are describing something that's intended to happen, not something that's actually happened yet.
Jose Costa Teixeira (Jun 05 2019 at 15:06):
it makes sense to see it from that perspective, but i can't figure out the mechanism. this sounds strange:
"The reply process is simply performed by the person/system handing the requests, updating the participant statuses on the appointment as needed. If there are multiple systems involved, then these will create AppointmentResponse entries with the desired statuses.
Once all participants have their participation status created/updated (and the main system marking the appointment participant records with the AppointmentResponse statuses) then the overall status of the Appointment is updated."
Lloyd McKenzie (Jun 05 2019 at 15:07):
AppointmentResponse is really a request to update the Appointment resource to indicate attendance.
Jose Costa Teixeira (Jun 05 2019 at 15:10):
ok, so the one resource that holds the appointment (from initial request/tentative to accepted/rejected) is Appointment. and Response is for tracking, well, the responses of every participant.
Lloyd McKenzie (Jun 05 2019 at 15:24):
Yup
Jose Costa Teixeira (Jun 05 2019 at 15:58):
thanks. I will have to implement this soon and possibly create some ExampleScenarios for explaining these workflows.
Jose Costa Teixeira (Jun 05 2019 at 15:58):
(if that is useful - i mean i will create them for my implementation anyway, but if useful, we can post some examples in the core documentation)
Brian Postlethwaite (Jun 09 2019 at 17:38):
There are sample state workflow on the appointment page showing the transitions and interactions between those resources under differing use cases.
Last updated: Apr 12 2022 at 19:14 UTC
