Basic rostering support

Description

From https://openvpms.org/project/rostering

Provide basic rostering support:

  • users are rostered to an Area, which is linked to a practice Location

  • Areas can have zero or more Schedules

  • user availability is determined by roster events, which have a start time, end time and Area

  • extend the Booking API to enable clinician availability to be queried

Rostering will performed in a new Rostering workspace. Two views will be provided:
1. roster by Area, showing who is rostered on
2. roster by user, showing when they are rostered on, and to which Area

Booking API

A v2 booking API will be provided, that includes user methods.
User availability will indicate which schedules a user may be assigned to in bookings.
A user may be available for multiple schedules at a given time, but once assigned to a booking, they will be marked busy.

Locations

Users at location

User locations

User availability at location

Submitting a booking for a particular user

Where booking.json contains:

Environment

None

Status

Assignee

Tim Anderson

Reporter

Tim Anderson

Labels

None

Time tracking

0m

Components

Fix versions

Priority

Major
Configure