Approvals - Scenarios

The current list of scenarios is as follows:

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	System Admin
Pre-Conditions	Site approval notification received off platform Site creation notification received off platform
Post-Conditions	A new & approved site is added to the Site reference table list
Process Steps	Navigate to site list Select site to edit or create site Enter relevant fields (see Approvals list across) update status to Current (if required) Link historical sites (if applicable) NOT FOR MVP Save	Site Creation site name site number site known as trust (from ref table) local office (from ref table) telephone number address post code status historically linked programmes comments Approvals from date to date programme NOT FOR MVP site type (from ref table) NOT FOR MVP contact name NOT FOR MVP contact telephone number NOT FOR MVP document uploads NOT FOR MVP
Alternative Process	AP-2 Remove site approval
Rules	site must be approved to become available for use within a post - this is known by the approvals from / to date being valid (i.e. not expired)
JIRA Links	TISDEV-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 exxpired Manual request to make site unavailable received
Post-Conditions	Site is unavailable for use within Posts / Placements
Process Steps	Navigate to site list Select site to edit or create site Make necessary changes Change status to inactive to deactivate amend start date amend end date Link historical sites (if applicable) Save	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	once site has been made inactive, it should not be available to add to posts warn users about already linked posts/placements	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 Links	TISDEV-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	Navigate to Pathway Definition space in Trainer record Select to define new approval Define an approval type Define approval name Define start / end dates Save	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	Trainer cannot be linked to trainees if they are not approved	do not include this for MVP
Jira Links
Audit Log

Process Steps	AP-4 Edit Trainer Pathway - NOT FOR MVP	Comments
Description
Actors
Pre-Conditions
Post-Conditions
Process Steps	Navigate to Pathway Definiion space Select pathway Define a pathway name Select trainer type add from list add new trainer type Assign domains (from reference table) Save
Alternative Process
Rules
Jira Links
Audit Log

Process Steps	AP-5 Expiry Notification - NOT FOR MVP	Comments
Description
Actors
Pre-Conditions
Post-Conditions
Process Steps
Alternative Process
Rules
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	Navigate to Approval space in Trainer record Select to define new approval Define trainer type Define an approval type Define approval name Define start / end dates Save Display new approval against trainer record	NB: there may be more than one approval record per trainer
Alternative Process	N/A
Rules	add multiple approvals against a single trainer
Jira Links	TISDEV-3116
Audit Log	who created and when who edited and when

dit 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	Navigate to Pathway Definition space in Trainer record Select existing approval edit relevant field Define an approval type Define approval name Define start / end dates Save Display updated approval	NB: there may be more than one approval record per trainer
Alternative Process	N/A
Rules	no validation for MVP
Jira Links	TISDEV-3118
Audit Log	who edited and when