Context start date
end date
site
grade
specialty
placement type
statusContext xyz
Process Name | PL1 - Navigate to Placements | Comments |
Description | User can access placement management tools | |
Actors | HEE Admins | |
Pre-conditions | Logged in Security allows access to placement manager | |
Post-conditions | View options to create / edit placements | |
Process steps | 1. Hover over Placements in nav bar 2. Select either Bulk Upload or Placement Manager 3. System presents create/edit screens as requested | |
Alternative flow | PL3 - Create Placement from Person record | |
Rules | Page only available to those who have access to 'Placements' in their role | |
JIRA Reference | ||
Audit Log | N/a |
...
Process Name | PL2 - Search | Comments |
---|---|---|
Description | User should be able to find placement details by searching for a person or post number | |
Actors | HEE Admin | |
Pre-Conditions | Logged in Security allows access to Posts, People or Placement Manager | |
Post-Conditions | User is able to find specified data around a Placement User is told there are no details related to their particular search | |
Process Steps |
| |
Alternative Flow | N/A | |
Rules | ||
JIRA Reference | ||
Audit Log |
...
Process Name | PL5 - View/Edit Placement | Comments |
---|---|---|
Description | User can view and edit current/future placement data already created | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to People, Posts, Placement Manager | |
Post-conditions | User views placement detail (past / current / future) User edits placement detail (current / future) | |
Process steps |
| Editable fields include: TBC
|
Alternative flow | PL8 - Manage Placements with Slot Share | |
Rules | System prevents user from editing past placement detail | |
JIRA Reference | ||
Audit Log |
...
Process Name | PL6 - Manage Multiple Placements | Comments |
---|---|---|
Description | User can link / unlink posts for multiple trainees to create multiple placements in one view | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to Placement Manager | |
Post-conditions | Placement created for a group of individuals Placement confirmed to relevant Trust | |
Process steps |
| Rotations can be created in Person TBC Posts detail in view
Person detail in view
|
Alternative flow | ||
Rules | Trainees and Posts avaiable should be constrained to the local view only Filter out "trainees in post" | Is this true? it's likely that admins will want only to view the posts that they are responsible for making placements in. |
JIRA Reference | ||
Audit Log |
Process Name | PL7 - Unlink Placement | Comments |
---|---|---|
Description | User is able to remove Person from a Placement with immediate effect | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to People, Posts, Placement Manager | |
Post-conditions | User is removed from Placement | |
Process steps |
| What detail should be sent to Trust? E.g. start date, new end date, post number, trainee first name, trainee last name Does a reason need to be provided?all this detail is specified in the ESR guide I believe. We do not have jurisdiction over the data transfer as I believe it was agreed with trusts. their change process is basically non-existent. |
Alternative flow | PL9 - Placement Ends | |
Rules | ||
JIRA Reference | ||
Audit Log |
...
Process Name | PL8 - Manage Placements with Slot Share | Comments |
---|---|---|
Description | User can view and edit current/future placement data already created; specifially related to Slot Share details | Not sure we need this as a separate scenario. Unless we go down the route of outlining every possible type of placement etc? |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to People, Posts, Placement Manager | |
Post-conditions | User edits slot share information in placement detail (current / future) | |
Process steps |
| |
Alternative flow | N/A | |
Rules | Slot share must always be 0.5 + 0.1 for both trainees sharing a single slot (to account for handover time) System prevents user from editing past placement detail | |
JIRA Reference | ||
Audit Log |
...