| Table of Contents |
|---|
Scenarios
| Process Name | PP-1 Navigate | Comments | |
| Description | User can navigate to the People Section of TIS | ||
| Actors | Admins (Local office and Trusts) | ||
| Pre-Conditions | Logged in Security allows access to people records | ||
| Post-Conditions | View people landing page | ||
| Process Steps |
| ||
| Alternative Flow | N/A | ||
| Rules | Page only available to those who have access to 'People' in their role | ||
| JIRA Reference | |||
| Audit Log | N/A |
| Process Name | PP2 - Search Person | Comments |
|---|---|---|
| Description | User can find a person or group of people as required | |
| Actors | Admins (Local office and Trusts) | |
| Pre-conditions | Logged in Security allows access to people records | |
| Post-conditions | View all or filtered people in a screen list (filtered list produced via defined filterable fields) | |
| Process steps | 1. Enter search term [person surname, forename, maiden name, GMC/GDC/Public Health number] 2. Click search 3. Present search results | From People - Field Validation |
| Alternative flow | PP3 - View People List | |
| Rules | Page only available to those who have access to 'People' in their role Certain 'People' only available to those who have access in their role | |
| JIRA Reference | ||
| Audit Log | N/A |
| Process Name | PP3 - View People List | Comments |
|---|---|---|
| Description | User can view a summary list of all people and be able to constrain/sort that view by certain filters; they should also be able to enter into a person record | |
| Actors | Admins (Local office and Trusts) | |
| Pre-conditions | Logged in Security allows access to people records | |
| Post-conditions | View all or searched people in a list | |
| Process steps | 1. View table with column headers defined 2. Click into single line to view detail on a particular person 3. System presents detailed post view |
|
| Alternative flow | PP2 - Search Person | |
| Rules |
| |
| JIRA Reference | TIS-636 | |
| Audit Log | N/A |
| Process Name | PP4 - View / Edit Person | Comments |
|---|---|---|
| Description | User should be able to view a person record and edit as their permission allows | |
| Actors | Local office admins | |
| Pre-conditions | Logged in Authorised user | |
| Post-conditions | View all or filtered/searched people in a list | |
| Process steps | 1. Click through from list view 2. View detail 3. Edit detail in field (including changing status to 'inactive') 4. Save 5. Close | From People - Field Validation |
| Alternative flow | PP3 - View people list | |
| Rules |
| |
| JIRA Reference | TIS-636, TIS-207, TIS 130 | |
| Audit Log | Change made - was/is When Who | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP5 - Create Person (single) | Comments |
|---|---|---|
| Description | Users should be able to manually add an individual person record | |
| Actors | Local office admin | |
| Pre-conditions | Logged in Authorised User | |
| Post-conditions | Searched for person in entire database (searched based on GMC, GDC, Public Health number or Surname) | |
| Process steps | 1. Select to add new person |
on validation table)
data 3. User selects whether to assign a DRN or NTN | From People - Field Validation (when creating a person record only the fields in Personal and Contact and (for a trainee) Programme are required) (IO) How do we differentiate between a medical trainee or other? |
| Alternative flow | PP6 - Bulk upload of people | |
| Rules |
|
|
Suffix option TBC
- CCT = C
- CESR = L
- CESP = ?
- CEGPR = L
- CEGCP ?
| (IO) When should save button be made available? Discussed here but needs to be revisited (People - Field Validation | Activating Save & Errors) (IO) what if there is unknown information, do we need to reduce the number of mandatory fields? | |
JIRA Reference | TIS 629 | |
| Audit Log | Who created the people record and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP6 - Bulk Upload of People | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | A user should be able to add a list of individuals to create multiple person records in one go | Intrepid Excel Template is Intrepid Recruitment Import Template v11.xls For TIS, the only mandatory fields identified in the template are:
The only roles would be 'Doctor in training' and 'Trainee'. | ||||||||
| Actors | Local office admin | |||||||||
| Pre-conditions | Logged in Authorised User | |||||||||
| Post-conditions | Searched for person in entire database | |||||||||
| Process steps |
| From People - Field Validation (when creating a person record only the fields in Personal and Contact and (for a trainee) Programme are required) Fields People - Field Validation has a spreadsheet (bottom of page) that shows the fields GMC/GDC/PH number is the Unique identifier for updating records exist on the system. Foundation trainees - If they do not have a GMC, a second source identifying the person would be the email address. | ||||||||
| Alternative flow | PP5 - Create person (single) | |||||||||
| Rules | Error: this GMC/GDC/Public Health number is already held by a person on this database Error: mandatory fields not completed Error: Structure of the template expected by the import does not match, i.e. file format/column names/order expected do not match Error: Duplicate rows identified in the spreadsheet Error: Duplicate record of a person that already exist on the system to be validated against | Error message appears to let the operator know what the reasons for non import are. The errors should be corrected on the import spreadsheet before the import function is tried again. It is possible to select records to be imported if some of the records are correct but the best course of action is to correct all inaccuracies and import the entire spreadsheet in one go. The error messages should list the the rows and columns for failures. The total number of records that have been imported is shown to the operator. Mandatory fields should be defined on the import spreadsheet to avoid the non import of records. | ||||||||
| JIRA Reference | TIS-642
| |||||||||
| Audit Log | Who created the people record/s and when Who updated the prople record/s and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP6A - Bulk Update People using TIS_Person_ID | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | A user should be able to:
| |||||||||
| Actors | (HEE Admin, HEE Admin Sensitive, HEE Admin Reval, HEE TIS Admin) | |||||||||
| Pre-conditions | Logged in Authorised User | |||||||||
| Post-conditions |
| |||||||||
| Process steps |
| |||||||||
| Alternative flow | PP4 - View/Edit person (single) | |||||||||
| Rules | Error: TIS_Person_ID does not exist on TIS Error: mandatory fields not completed Error: Structure of the template expected by the import does not match, i.e. file format/column names/order expected do not match Error: Duplicate rows identified in the spreadsheet | Error message appears to let the user know what the reasons for non import are. The errors should be corrected on the import spreadsheet before the import function is tried again. It is possible to select records to be imported if some of the records are correct but the best course of action is to correct all inaccuracies and import the entire spreadsheet in one go. The error messages should list the the rows and columns for failures. The total number of records that have been imported is shown to the operator. Mandatory fields should be defined on the import spreadsheet to avoid the non import of records. | ||||||||
| JIRA Reference |
| |||||||||
| Audit Log | Who updated the people record/s, what was updated from what to what and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP7 - Manage Oriel Import of Trainees (This may not be required if all the required fields including Programme are mapped in the import) | Comments |
|---|---|---|
| Description | Users should be able to view a summary of recently imported trainee person records and edit the contents of each one | Note of caution - the reference data in Oriel does not always match the values in Intrepid. i.e. For the specialty if the Oriel value is "General Medicine" and the Intrepid value is "General (internal) Medicine", this data will not be updated automatically. This is the same for all reference data such as Title, Country, Grade, NTN, Nationality, etc. Trainees may already exist on the Intrepid and therefore the existing record will be update |
| Actors | Local office admin | |
| Pre-conditions | Logged in Authorised User | |
| Post-conditions | ||
| Process steps |
| How do you currently view/edit import errors? Joanne Watson (Unlicensed) Need to check this with colleagues who use the Oriel import |
| Alternative flow | PP6-Bulk upload of People | |
| Rules |
| Where mandatory fields are not completed at time of import suggest a quality dashboard/data extract be produced to indicate the missing values in each person record |
| JIRA Reference | TIS-715 | |
| Audit Log | Who created the people record and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP8 - Remove Person from Programme | Comments |
|---|---|---|
| Description | Users are able to update a person record to remove them from a programme | Question for SMLs is 'how can we show that a trainee has left their training programme without completing/achieving their CCT?. |
| Actors | Local office and trust admins (depending on the local office arrangements for managing FP trainees) | |
| Pre-conditions | Logged in Authorised User | |
| Post-conditions | Navigated to trainee record | |
| Process steps |
| |
| Alternative flow | N/A | |
| Rules | ||
| JIRA Reference | TIS-636, TIS-216, TIS-204 | |
| Audit Log | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP9 - Leaver process (Manual?) | Comments |
|---|---|---|
| Description | Users are able to reflect in a trainee's record that they have left their training programme (non-completion of programme and completion of programme) | Question for SMLs is 'how can we show that a trainee has left their training programme without completing/achieving their CCT?. |
| Actors | Local office and trust admins (depending on the local office arrangements for managing FP trainees) | |
| Pre-conditions | Logged in Navigated to trainee record | |
| Post-conditions | Trainee flagged as Inactive | |
| Process steps |
| Should this be automated only? Joanne Watson (Unlicensed) |
| Alternative flow | N/A | |
| Rules | ||
| JIRA Reference | TIS-211, TIS-216 | |
| Audit Log | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP10 - Reporting OUT OF SCOPE | Comments |
|---|---|---|
| Description | Users should be able to configure and pull a report directly from TIS relating to specific requirements |
Dependency on Workshop to be held with Joanne, Ray & Rob - reporting likely to be centrallised outside of TIS |
| Actors | Admins | |
| Pre-conditions | Logged in Authorised User | |
| Post-conditions | ||
| Process steps | ||
| Alternative flow | ||
| Rules | ||
| JIRA Reference | ||
| Audit Log |