search

argonautproject / scheduling

Argonaut Scheduling and Appointments: This project supports basic patient and provider access to a provider's calendar and appointment requests, including APIs and guidance for searching and publishing a providers schedule andrequesting, cancelling or updating an appointment.
http://www.fhir.org/guides/argonaut/scheduling/
15 stars 2 forks source link

Do we need a separate scheduling update ('renegotiation') workflow? #29

Open Healthedata1 opened 7 years ago

Healthedata1 commented 7 years ago

We have been working with the assumptions that rescheduling is a two step process of cancelling and booking. The alternative is to create a whole update ('renegotiation') workflow instead of cancelling and starting over.

Is this a valid working assumption?

brandon-larue-zocdoc commented 6 years ago

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)

Healthedata1 commented 6 years ago

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)??