Stream: argonaut
Topic: scheduling / Issue #29 Do we need a separate scheduling u...
argo-scheduling-bot (Jan 03 2018 at 17:18):
brandon-larue-zocdoc commented on Issue #29
Leaving rescheduling as a two step cancel/book process keeps things simple, but the server will lose any event tracking on the appointment object. A scheduler looking at the new appointment won't have any context that it was rescheduled.
It also introduces some complex failure states. What if the booking fails for some reason, but the previous appointment is already canceled? (which raises a larger question as to how failures should be handled in general)
argo-scheduling-bot (Jan 03 2018 at 20:41):
Healthedata1 commented on Issue #29
When rebook add an optional parameter of cancelled appt id over for. - add to documentation.
failures: option to leave up to client. add/document- prescribe best practices. + technical operations. ( check list of steps -e.g. Client SHALL verify successful cancellation prior to rebooking ) any outside resources (like a functional model)??
argo-scheduling-bot (Jan 03 2018 at 21:16):
Healthedata1 labeled Issue #29
argo-scheduling-bot (Mar 21 2018 at 18:14):
Healthedata1 labeled Issue #29
Last updated: Apr 12 2022 at 19:14 UTC
