How to use them and why
Why have two types of session?
Because practice rotering needs to combine the rota of an individual with the additional rota needs of the organisation, we have solved this complexity by splitting the two types out, into two different rota templates and, within those templates, defining the two types of session.
This means that the two types of template can overlap and Tempo can intelligently work out how overlapping sessions interact to create a complete, workable, practice rota.
Org templates only contain organisation type sessions and do not need names assigned to them.
User week templates can contain BOTH org sessions and user sessions.
User sessions are protected. This means they are generally not suitable for transformation into something else, within a rota.
An example of an org type session in a practice rota is a Duty session. That could be GP Duty or something else, such as Pharmacist Duty. The key thing is that, it is a session that usually has to happen, within an organisational rota.
This is distinct from the ‘protected‘ sessions contained within a staff user template
The staff user week template is a design of the weekly plan and expectations of the staff user.
User week templates can contain two types of session: org sessions and non-org, protected sessions.
This ‘org’ or ‘protected’ attribute of a session is set, by the hub, for any session type, within the session type management screen.
https://about-tempo.gpnetworks.co.uk/hub_admin/pcn/session_types
Session type example
In a person’s week design, the org type session is given to those sessions that become the ones that can transfrom into an org session in a practice rota
Rota = where user and org templates come together and create rota sessions and assignments
Pharmacist examples
In one example, a pharmacist for who all her sessions can be transformed into organisation sessions in a rota – the sessions in her week template design are all of a session type that is an ORG session type and the org template contains all these sessions too but without a person associated to the sessions.
In another example, pharmacist with their weeks sessions designed in their user template and the organisation needs a duty pharmacist.
That duty session would be in an org template AND be a session in the users weeks that is using an ORG session type,
This setup tells the rota that the session can be transformed into an org session in a rota.
So, between the design of the user template and the org template, we’re telling Tempo rota how to handle overlap and transformation of a person’s week, to the rota requirements of organisation
