You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 6, 2025. It is now read-only.
Users should be able to do scheduling of appointments directly in the calendar. We need fields to attach to an appointment
starttime
endtime
name of the appointment
appointment type -> the user should be able to pre-define certain appointment times for easier scheduling ("presets")
a patient should be associated to the appointment -> Do we need a patient object for that? @felixevers
the user should be able to create different "columns" per day to keep e.g. appointments with certain doctors or diagnostic units seperate (e.g. two columns for the two doctors and one column for EKG unit scheduling). Users should be able to configure that themselves
Future development potential:
we could have the patient as an object represented in the app and enable assigning an appointment directly to the patient
we could have defined interventions and appointment types which could be assigned to the appointment for automated setting of duration etc.
Why is this feature needed?
Users requested a calendar functionality in AzD. They want to do scheduling directly in AzD and actually use it as a calendar for their practice. In my opinion, this offers a lot of potential for automation of appointment scheduling, information management and communication.
Describe the feature
Users should be able to do scheduling of appointments directly in the calendar. We need fields to attach to an appointment
Future development potential:
Why is this feature needed?
Users requested a calendar functionality in AzD. They want to do scheduling directly in AzD and actually use it as a calendar for their practice. In my opinion, this offers a lot of potential for automation of appointment scheduling, information management and communication.
Additional context
No response