Skip to end of metadata
Go to start of metadata
The current list of scenarios is as follows:
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 expired 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 | - Navigate to site list
- Select site to edit or create site
- Make necessary changes
- Change status to inactive to deactivate or
- amend start date or
- amend end date
- 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 ? Post - MVP
| 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 |
TISNEW-3465
-
Getting issue details...
STATUS
|
|
Audit Log | N/A |
|
Process Steps | | 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 | | 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 | | 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 typeDefine approval name- Define start / end dates
- Save
- Display new approval against trainer record
| 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 | - add multiple approvals against a single trainer
|
|
Jira Links |
TISNEW-3466
-
Getting issue details...
STATUS
|
|
Audit Log | - who created and when
- who edited and when
|
|
Add Comment