Background
Trainers can be assigned to Programmes, Sites and Trusts
- to support trainee record managment
- to support reporting
This should form a new sub-section within a person record "Associations"
Programmes
- Trainers can be assigned to multiple programmes
- These Trainers will then be available to be assigned to a trainee (if they have a status of "current") as either a clinical or educational supervisor
- Trainer records should show all Trainees assigned to a particular trainer
...
- Trainers will be assigned to Trainees as SupervisorsSupervisors as either a clinical or educational supervisor
- Trainer records should display all placements & trainees currently assigned
...
Sites
- Trainers can have multiple sites against their record
- Site linkage means that TBC trainers not currently supervising a trainee can be identified against their site. This is important for reporting to the GMC while also allows filters to be applied so users don't have to wade through all trainers when assigning a supervisor.
Trusts
- Trainers can be assigned to multiple Trusts
- Trust linkage means that similar to associating against a site but some trainers are able to operate on any site within a trust so makes sense to record at trust level.
Specialties
- Trainers can be assigned to one or more specialties
- Specialty linkage means that we can report the necessary information to the GMC.
Education Group
- Trainers can be assigned to one or more Education Groups
- These groups act as a way to divide trainers within programmes, particularly large ones to facilitate managing placements etc
MVP Scope
- Assign Programme to Trainer Person Record
- Assign Site to Trainer Person Record
- Assign Trust to Trainer Person Record
- Assign Placement to Trainer Person Record
- Assign Specialty to Trainer Person record
- View/Edit Trainers Trainers by Site
- View Placements against a Trainer record
- View Trainees against Trainer Record
- Assign Supervisor to a Trainee
- Assign Education Group to a Trainer record
- View Edit Education Group
Field Validation
NB: These are new fields to be added to existing records
Order | 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) | List (S) / Detail (D) | Notes | Delete (Y / N) |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Associations | ||||||||||||||
1 | Programme Name |
| N | |||||||||||
2 | Programme Number |
| N | |||||||||||
3 | Trainee Name |
| Y - if populated(IO) where is educational supervisor assigned for trainee? Joanne Watson (Unlicensed) / Alistair Pringle (Unlicensed) | |||||||||||
4 | Site Name |
| N | |||||||||||
5 | Site Number |
| N | |||||||||||
6 | Trust Name |
| N | |||||||||||
7 | Trust Number |
| N | |||||||||||
8 | Education Group |
| N | Is defined on Education Groups page (EG-4 Programmes - Educational Groups (Trainers) Field Validation & Scenarios) | ||||||||||
9 | Placement - Post Number |
| Y - if populated | |||||||||||
910 | Placement - Trainee Name |
| Y - if populated | |||||||||||
1011 | Placement - Site |
| Y - if populated | |||||||||||
1112 | Placement - Start Date |
| Y - if populated | |||||||||||
1213 | Placement - End Date |
| Y - if populated | |||||||||||
Associated Trainers & Schools (as part of the Site Reference Table - this is an additional field) | ||||||||||||||
N/A | Trainer Name |
| N | |||||||||||
...
Process | TR-1 Assign/remove Programmes to Trainer Person Record | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Admin can assign a programme or multiple progammes to a Trainer person record | |||||||||
Actors | HEE Admin | |||||||||
Pre-Conditions | Trainer record must be either in creation or already created | |||||||||
Post-Conditions | Programmes assigned to Trainer record Trainer can be made available to select to trainees within that programme | |||||||||
Process Steps |
| |||||||||
Alternative Process | PP4 - View/Edit Peron (People - Scenarios) | |||||||||
Rules |
| |||||||||
JIRA Links |
| |||||||||
Audit Log |
|
...
Process | Tr-4 View/Edit Trainers against Site Record | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Admin can view all trainers assigned to a site within the site reference table | |||||||||
Actors | HEE Admin | |||||||||
Pre-Conditions | Trainer record must be already created | |||||||||
Post-Conditions | Admin views/edits trainers against a site in one go | |||||||||
Process Steps |
| |||||||||
Alternative Process | PP4 - View/Edit Peron (People - Scenarios) | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log |
|
Process | TR-5 View Placements against Trainer Record | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | User should be able to view any placements against a trainer record where they have been assigned as a CLinical Supervisor | |||||||||
Actors | HEE Admin | |||||||||
Pre-Conditions | Trainees must be assigned to Trainer within a Placement | |||||||||
Post-Conditions | Admin can view list of trainees assigned and to what post | |||||||||
Process Steps |
| |||||||||
Alternative Process | PL-5 View/Edit Placement (Placements - Scenarios) | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log | N/A |
Process | TR-6 View Trainees against Trainer Record (as Educational Supervisor) | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | User should be able to see trainees who have been assigned to a Trainer for a particular Programme as Educational Supervisor | |||||||||
actors | HEE Admin | |||||||||
Pre-Conditions | Trainees must be assigned to Trainer within Programme membership | |||||||||
Post-Conditions | Admin can view assigned trainees in trainer record admin can click through to full trainee record and edit | |||||||||
Proces Steps |
| |||||||||
Alternative Process | TR-7 Assign Educational Supervisor to Trainee Programme Membership (edit educational supervisors) | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log | N/A |
Process | TR-7 Assign |
---|
Supervisor to |
---|
Trainee | Comments |
---|---|
Description | User should be able to assign, de-assign and remove |
Supervisors based on a Trainee's |
placements | Needs to be re-written as education supervisor is to be assigned via placement only | |
Actors | HEE Admin | |
Pre-Conditions | Trainee record created and within a current programme Trainers available against the programme and approved | |
Post-Conditions | Trainee and Trainer |
belong to the same programme membership | |
Process Steps |
|
| (IO) is this a field in trainee |
UI? if not, how should trainees be notified? Similar to the placements in Admin UI the Trainee UI will have a placements section which will allow us to show supervisors for each placement where assigned. (IO) can we do email notifications based on activity? Trainer does not need to be notified as they are assigned trainees by the TPD in a separate process. | ||||||||||
Alternative Process | TR-6 View Trainees against Trainer Record (as Educational Supervisor) | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log |
|
Process | TR-8 Assign Specialty to Trainer Person record | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Admin can assign a specialty or multiple specilaities to a Trainer person record | |||||||||
Actors | HEE Admin | |||||||||
Pre-Conditions | Trainer record must be either in creation or already created | |||||||||
Post-Conitions | Specialty or specialties assigned to Trainer record | |||||||||
Process Steps |
| |||||||||
Alternaitve Process | N/A | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log |
|
Process | TR-9 Assign Education Group to a Trainer record | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Admin can assign a education group or multiple education groups to a Trainer person record | |||||||||
Actors | HEE admin | |||||||||
Pre-Confitions | Trainer record must be either in creation or already created Education groups created | |||||||||
Post-Conditions | Education groups assigned to Trainer record | |||||||||
Process Steps |
| |||||||||
Alternative Process | N/A | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log |
|
Process | TR-10 Create / View / Edit Education Group | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Admin can crete, view and edit an education group within reference tables | |||||||||
Actors | HEE Admin | |||||||||
Pre-Conditions | Access to reference table | |||||||||
Post-Conditions | Created new education group Edited education group | |||||||||
Process Steps |
| |||||||||
Alternative Process | N/A | |||||||||
Rules |
| |||||||||
Jira Links |
| |||||||||
Audit Log |
|
For Discussion
# | Question | Comment | Owner |
---|---|---|---|
1 | How is Trainer record owner defined? There can be multiple Trusts and Sites associated with a Trainer, what unique attribute can be shown to define "ownership" of a trainer person record? | Although multiple trusts and sites may be associated with a trainer the trusts and sites will almost always be 'owned' by the same local office. I'm not sure if we can make a link in this way though as I don't believe there will be an owner field against trust or site. | Alistair Pringle (Unlicensed) |