Background
...
- 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 rotationschool
- assign rotation
CurrentlyCurrently << TO BE REVIEWED BY DATA LEADS
- users can associate rotations with programmes or with postsso a trainee schools with Programmes
- a Programme can be assigned to two different rotations depending on who set it uptrainee only one / multiple Schools
- Trainees/trainers never sees the rotationSchool, 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
These two tables can be consolidated into a single table, then mapped to existing data in TIS:
View file | ||||
---|---|---|---|---|
|
...
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) |
1 | Rotation School Name |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
2 | Programme Name |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
3 | Programme Number |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
4Rotation | Local Office Owner |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
5 | School Status |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
6 | Start Date |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
7 | End Date |
| Y |
| N/A | N/A | N/A | N/A | N/A | N/A | ||||
8 | Sites |
| N |
| N/A | N/A | N/A | N/A | N/A | N/A |
Scenarios
Process Name | PG-1 Create RotationSchool | Comment | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | User creates the Rotation School grouping so that this can be used elsewhere in TIS | |||||||||||||||||
Actors | HEE Admin | |||||||||||||||||
Pre-Conditions | Programmes must be defined User must have appropriate access | |||||||||||||||||
Post Conditions | Rotation School group created and available to be assigned to Peoplereported against | |||||||||||||||||
Process Steps |
| |||||||||||||||||
Alternative Flow | N/A | |||||||||||||||||
Rules |
| |||||||||||||||||
JIRA Reference |
| |||||||||||||||||
Audit Log |
|
...
Process Name | PG-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-Conditinos | Programmes must be defined User must have appropriate access | |
Post Conditions | Changes saved to already created RotationSchool | |
Process Steps |
| |
Alternative Flow | N/A | |
Rules |
| |
JIRA Reference Jira Legacy | | server | System JIRA
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 | |
key | TISDEV-3103 | |
Audit Log |
|
Process Name | PG-3 Remove RotationSchools | Comments | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | User should be able to remove a Rotation grouping | ||||||||||||
Actors | Programme / Placement Admin | ||||||||||||
Pre-Conditions | Programmes must be defined User must have appropriate access | ||||||||||||
Post-Conditions | Rotation School removed from Reference Table Rotation field shows as blank in other records | ||||||||||||
Process Steps |
| ||||||||||||
Alternative Flow | N/A | ||||||||||||
Rules |
| JIRA Reference |
| Audit Log |
|
- Navigate to record
- Select rotation from drop down
- Save record
- Display rotation grouping against record
- 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 Legacy | ||||||
---|---|---|---|---|---|---|
|
N/A | ||
JIRA Reference | ||
Audit Log |
|
For Discussion
# | Question | Comment | Owner | ||
---|---|---|---|---|---|
1 |
| No, not necessary under new process - link rotation to programme, then assign rotation to person and/or post | |||
2 |
| none | |||
3 |
| yes, see ppt above | |||
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? | ||
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? | ||||
3 | Does school need to be displayed within a Programme form? | ||||
4 |