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 school
- view/edit school
- remove school

Currently << TO BE REVIEWED BY DATA LEADS

users can associate schools with Programmes
a Programme can be assigned to only one / multiple SchoolsTrainees/trainers never sees the School, so no impact to themSchools 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

School Name

vwProgrammeSchool

Free text

Y

Must be unique
limit to 25 characters

N/A

2

Programme Name

Smart search drop Local Office Owner

vwProgrammeSchool

Drop down

Y

Must must select 1

N/A

3

Programme Number

Derived from programme nameSchool Status

vwProgrammeSchool

Drop down

Y

Must select 1

N/A

4

Local Office Owner

Drop down

Y

must select 1

School Number

vwProgrammeSchool

Smart search drop down

N

free text

N/A

5

School StatusType

vwProgrammeSchool

Drop drop down

YN

Must select 1

N/A

6

Start Date

Calender picker

Y

Must select 1

N/A

7

End Date

Calender picker

Y

Must select 1

N/A

N/A6

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

8

Sites

Smart search School Name

drop down

N

Can add multiplecan only be selected from list

N/A

Scenarios

Process Name

PGSC-1 Create School

Comment

Description

User creates the 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

School group created and available to be reported against

Process Steps

Navigate to reference data space
Select to create new
Enter all mandatory fields
1. School name
2. Programme name
3. Programme number (autopopulated)
4. Local Office Owner
5. School Status
6. Start Date
7. End DateSchool Number
8. School Type
9. Head of School
Save
New School grouping is available within DWacross 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-3247

Jira Legacy

key

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

Audit Log

Create record - who / when

Process Name

PGSC-2 View / Edit School

Comment

Description

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

Actors

HEE Admin

TIS Admin

Pre-Conditinos

Programmes must be defined

User must have appropriate access

Post Conditions

Changes saved to already created School

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-3889

Audit Log

Edit record - who/when

Process Name

PGSC-3 Remove SchoolsSchool Record from Reference Values

Comments

Description

User should be able to remove a Rotation groupingSchool

Actors

Programme / Placement

TIS Admin

HEE Admin

Pre-ConditionsProgrammes must be defined

User must have appropriate access

Post-Conditions

School removed from Reference Table

Process Steps

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

Alternative Flow

N/A

Rules

N/A

JIRA Reference

Jira Legacy

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

Audit Log

Delete record - who/when

Process Nme

SC-4 Assign School to Programme

Description

User should be able to assign a school to a Programme record

Actors

HEE Admin

TIS Admin

Pre-Conditions

Schools must be defined

Programme must be in creation or already defined

Post-Conditions

School is associated with a Programme

Process Steps

Navigate to Programme record (create or edit journey)
Select School from drop down menu
Save to add School association

Alternative Flow

N/A

Rules

only one
must be from drop down list

Jira Reference

Jira Legacy

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

Audit Log

added - who/when
removed - who when
amended - who/when

For Discussion

#	Question	Comment
1	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 3

New Version Current

Key