Conversation
| ## Agenda schedule design recommendations | ||
|
|
||
| When designing agenda schedules, the first question to consider is what choices you want to leave to the end users. | ||
|
|
||
| For example, in a system where patients can book doctor visits, the schedule design determines whether users can: | ||
| - Select a specific doctor for their appointment, or | ||
| - Select only the type of appointment, while the system (or another process) assigns the doctor at a later moment. | ||
|
|
||
| The design of agendas for the first kind of system is straightforward: you have an agenda for each doctor, and each | ||
| agenda uses only one resource group in the schedule, that is the group consisting of only that doctor. |
There was a problem hiding this comment.
This part is super interesting, I took the appointment with Rosa yesterday and they actually give me the choice (has the patient) do you want to select the Doctor or do you want to select why you need an appointment
So I had a list of doctor on one side or I could click on "I need a doctor quickly" option then it attributed me to the earliest appointment possible (like a choice of the earliest ones)
There was a problem hiding this comment.
Unfortunately this would have to be done on the frontend; the model would still be an agenda per doctor, then there would be a component on the frontend that checks the availabilities for each agenda in the near future...
There was a problem hiding this comment.
What I mean is that it give the possibility to do both
2 participants
No description provided.