...
Process Name | AP-1 Create / Add Site Approvals | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | Admins are to complete that a site is approved within the reference table to make it available for use as a site for a post/placement | |||||||||
| Actors | HEE Admins (Any Roles with access to create/update sites) | |||||||||
| Pre-Conditions | Site approval period is coming to an end or is not approved at present. | |||||||||
| Post-Conditions | A new & approved site is added to the Site reference table list When Adding placements, user should be able to use the new approved Site. | |||||||||
| Process Steps |
| |||||||||
| Alternative Process | AP-2 Remove site approval | |||||||||
| Rules |
| |||||||||
| JIRA LinksTISDEV-3115 |
| |||||||||
| Audit Log | N/A |
| Process Name | AP-2 Edit/Remove site approval | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | Admins are to complete that a site is no longer approved within the reference table to make it unavailable for use as a site for a post/placement | |||||||||
| Actors | System Admin | |||||||||
| Pre-Conditions | Site approval date is exxpiredManual request to make site unavailable receivedexpired that needs to be updated Site has got no start and end dates | |||||||||
| Post-Conditions | Site is unavailable for use within Posts / Placements? Post - MVP Site is updated with the dates | |||||||||
| Process Steps |
| Should anything else be done to remove approval? I suppose as long as we can tie off the dates that is enough. Should site approval be stored historically? Yes although not sure how this would work as we just recording dates? | ||||||||
| Alternative Process | AP-1 Create / Add Site Approvals | |||||||||
| Rules |
| What should happen to a post/placement that is already linked to a site that becomes expired or is no longer approved? Nothing for MVP Should a user be able to see which posts/placements are linked here so they can amend them? Not for MVP | ||||||||
| JIRA LinksTISDEV-3117 |
| |||||||||
| Audit Log | N/A |
| Process Steps | AP-3 Define Trainer Pathways - NOT FOR MVP | Comments |
|---|---|---|
| Description | Admins can define pathway for trainers to be assessed against | |
| Actors | Admin | |
| Pre-Conditions | Trainer record exists within TIS | |
| Post-Conditions | New pathway defined | |
Process Steps |
| Trainer Types Clinical Supervisor Eductional Supervisor Clinical & Educational Supervisor Other? Where should trainer types be defined? Maybe as an interim step? This is a question for SMLs I reckon Where should this function sit? Manage record perhaps? or again we could ask where it would logically sit? Where should domains be defined? Another interim step? New reference table? Are we doing domains as part of MVP? Is this the right process? |
| Alternative Process | N/A | |
| Rules |
| do not include this for MVP |
| Jira Links | ||
| Audit Log |
...
| Process Steps | AP-6 Record Trainer Approval | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | Admin should be able to record approval periods for a trainer in their person record | |||||||||
| Actors | HEE Admin Trainer ( ? ) | |||||||||
| Pre-Conditions | Admin has navigated to Trainer record | |||||||||
| Post-Conditions | Approval dates recorded | |||||||||
| Process Steps |
| NB: there may be more than one approval record per trainer ?? Post - MVP For MVP, decide whether only one set of approval period is required. | ||||||||
| Alternative Process | N/A | |||||||||
| Rules |
| |||||||||
| Jira LinksTISDEV-3116 |
| |||||||||
| Audit Log |
|
...
Process Steps | AP-7 Edit Trainer Approval | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | Admin should be able to record approval periods for a trainer in their person record | |||||||||
| Actors | HEE Admin Trainer | |||||||||
| Pre-Conditions | Admin has navigated to Trainer record | |||||||||
| Post-Conditions | Approval dates recorded | |||||||||
| Process Steps |
| NB: there may be more than one approval record per trainer | ||||||||
| Alternative Process | N/A | |||||||||
| Rules |
| |||||||||
| Jira LinksTISDEV-3118 |
| |||||||||
| Audit Log |
|
...