Page Comparison

Background

Rotations are groupings used to manage large groups of trainees on a single Programme; they are artificial and do not represent any form of reportable data within HEE by themselves.Schools are created in order to link Heads of Schools to Programmes and enable reporting

Scope for TIS

Act as Reference Data
Available as labels / drop downs within relevant components in the Admin UI
Editable by the local office and data leads
Functionality should include -
- create rotationschool
- view/edit rotationschool
- remove rotation
- school

Currently

users can associate rotations with programmes or with posts
so a trainee can be assigned to two different rotations depending on who set it up
trainee never sees the rotation, so no impact to them
however the database will hold two sets of records and any component sing the rotations will need to know which to pick up

Image Removed

These two tables can be consolidated into a single table, then mapped to existing data in TIS:

View file

name	Rotations Table - Consolidation v0.2.pptx
height	250

...

schools with Programmes
a Programme can be assigned to only one Schools at a single point in time
Schools should be displayed within Programme membership of a Person record

Field Validation

Field Sequence

Field name (V10)

DR field

Reference table

Example value

Other fields available in DR

Type (free text, drop down, check box) & Interaction

Mandatory (Y/N)

Validation / Error Messaging

Filter (Y/N)

Search (Y/N)

Sort (Y/N)

Summary (S) / Detail (D)

Notes

Delete (Y / N)

Reference Table

1

Rotation School Name

vwProgrammeSchool

Free text

Y

Must be unique per local office

2

Programme Name

Smartsearch drop unique
limit to 25 characters

N/A

2

Local Office Owner

vwProgrammeSchool

Drop down

Y

Must must select 1

N/A

3

School Status

Programme Number

Derived from programme namevwProgrammeSchool

Drop down

Y

Must select 1

N/A

4

School Number

Rotation Status

Drop down

Y

Must select 1

5

Start Date

Calender picker

Y

Must select 1

6

End Date

Calender picker

Y

Must select 1vwProgrammeSchool

Smart search drop down

N

free text

N/A

5

School Type

vwProgrammeSchool

drop down

N

N/A

6

Head of School

vwPerson

smart search drop down

N

only select from trainer list

It may no be possible to differentiate between role types i.e. Trainer v Trainee

Programme Form

N/A

School Name

drop down

N

can only be selected from list

N/A

Scenarios

Process Name

PGSC-1 Create RotationSchool

Comment

Description

User creates the Rotation School grouping so that this can be used elsewhere in TIS

Actors

HEE Admin

Pre-ConditionsProgrammes must be defined

User must have appropriate access

Post Conditions

Rotation School group created and available to be assigned to Peoplereported against

Process Steps

Navigate to reference data space
Select to create new
Enter all mandatory fields
1. Rotation School name
2. Programme name
3. Programme number (autopopulated)
4. Status
5. Start Date
6. End DateLocal Office Owner
7. School Status
8. School Number
9. School Type
10. Head of School
Save
New rotation School grouping is available across TIS as a reference value

Alternative Flow

N/A

Rules

name is free text
limit to 25 characters
name / number must be unique

JIRA Reference

Jira Legacy

server	System JIRA
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key	TISDEV-31023247

Audit Log

Create record - who / when

Process Name

PGSC-2 View / Edit RotationSchool

Comment

Description

User should be able to view and make edits to existing Rotation School groupings

Actors

HEE Admin

TIS Admin

Pre-ConditinosProgrammes must be defined

User must have appropriate access

Post Conditions

Changes saved to already created RotationSchool

Process Steps

Navigate to reference data space
Select field to be edited
Make changes
Save

Alternative Flow

N/A

Rules

Changes can be made to name or programme linkany/all fields in the record
Display warning message displayed to warn user of potential impact to previously/already linked Programmes, Trainees, Posts etc

JIRA Reference

Jira Legacy

server	System JIRA
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key	TISDEV-31033889

Audit Log

Edit record - who/when

Process Name

PGSC-3 Remove RotationSchool Record from Reference Values

Comments

Description

User should be able to remove a Rotation groupingSchool

ActorsProgramme / Placement

TIS Admin

HEE Admin

Pre-ConditionsProgrammes must be defined

User must have appropriate access

Post-Conditions

Rotation School removed from Reference TableRotation field shows as blank in other records

Process Steps

Navigate to reference data space
Select field to be edited
Change status to inactive
Save

Alternative Flow

N/A

Rules

Downstream data remains as is i.e. Trainee-Placement link remains in place

Display warning message displayed to warn user of potential impact to previously/already linked Programmes, Trainees, Posts etc

Remove display of Rotation label within records where applicableN/A

JIRA Reference

Jira Legacy

server	System JIRA
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key	TISDEV-31043890

Audit Log

Delete record - who/when

Process

Name

Nme

PG

SC-4 Assign

RotationComments

School to Programme
Description	User

can link a rotation grouping to TIS data, such as trainee or post

should be able to assign a school to a Programme record

Actors

HEE Admin

TIS Admin

Pre-Conditions

Record does not contain a link to desired rotation

Schools must be defined

Programme must be in creation or already defined

Post-Conditions

Record contains a link to desired rotation

School is associated with a Programme
Process Steps	Navigate to Programme record (create or edit journey) Select

rotation

School from drop down menu
Save

recordDisplay rotation grouping against record

to add School association
Alternative Flow	N/A
Rules

Only one rotation can be selected per record

Historical view diplayed via audit log

only

Display warning message where rotation field is edited and is linked to another record i.e. Person is in Placement and one of the fields is changed

Only Current rotations can be selected

JIRA

one
must be from drop down list

Jira Reference

Jira Legacy

server	System JIRA
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key	TISDEV-

3336

3891

Audit Log

add rotation

added - who/when
removed - who when

edit rotation

amended - who/when

For Discussion

#	Question	Comment	Owner
1	in TIS, is it actually necessary to assign rotations at both post and programme levels? Alternative would be to expose rotation grouping to all admins and set a rotation group max number so they remain manageable for all users?	No, not necessary under new process - link rotation to programme, then assign rotation to person and/or post	Alistair Pringle (Unlicensed)
2	what other components use rotations?	none	Alistair Pringle (Unlicensed)
3	Is it possible to combine the 2 old rotations tables into one, as well as any new rotations labels created? potential impacts - localised v national views, duplicate labels	yes, see ppt above	Russell Steel (Unlicensed), Alistair Pringle (Unlicensed), Alex Dobre (Unlicensed)
4	how should legacy rotations be displayed in TIS?	As single value against a record	Alistair Pringle (Unlicensed)Are schools purely required for reporting puroses?	No, also for reference to Trainees and Trainers
2	Do they need to be displayed anywhere else on TIS? Does it require more functinality than is described above? i.e. to support educational training?	Programmes should display the school reference Schools should be displayed within Programme Membership L3 for Person record (trainees & trainers)
3	Does school need to be displayed within a Programme form?	Yes (see above)
4

Versions Compared

Old Version 1

New Version Current

Key