Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for vacation and holidays #925

Open
make-github-pseudonymous-again opened this issue May 4, 2024 · 0 comments
Open

Add support for vacation and holidays #925

make-github-pseudonymous-again opened this issue May 4, 2024 · 0 comments
Labels
feature/agenda This issue is about the agenda functionality ui This issue is about the user interface in general. ux This issue is about the user experience in general.
Projects

Comments

@make-github-pseudonymous-again
Copy link
Contributor

At the very minimum it could just be the creation of events that span the entire day. They would be stored as intervals from 00:00 to 23:59 and displayed with custom logic to span the planned work schedule.

Currently, the user's workaround is to add a long duration to possible appointment durations for a synthetic "vacation" patient, then create multiple events that cover the planned work schedule. It is inconvenient because passed vacation is registered as no-shows for that synthetic patient, which makes past vacation difficult to browse in the agenda itself. You can easily browse past and future vacation through the synthetic patient history though.

@make-github-pseudonymous-again make-github-pseudonymous-again added ui This issue is about the user interface in general. ux This issue is about the user experience in general. feature/agenda This issue is about the agenda functionality labels May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/agenda This issue is about the agenda functionality ui This issue is about the user interface in general. ux This issue is about the user experience in general.
Projects
Development

No branches or pull requests

1 participant