Skip to end of metadata
  • Created by Former user , last modified on 24 Nov 2017
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »


The current list of scenarios is as follows:

  1. Create/Add site approvals
  2. Remove site approval
  3. Define pathways
  4. edit trainer pathway
  5. Assign pathways
  6. Confirm accreditation
  7. Expiry notification


These need to be validated with BMs / SMLs  (Alistair Pringle (Unlicensed))


Process Name
AP-1 Create / Add Site Approvals
Comments
DescriptionAdmins 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
ActorsSystem 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
  1. Navigate to site list
  2. Select site to edit or create site
  3. Enter relevant fields (see Approvals list across)
  4. update status to Current (if required)
  5. Link historical sites (if applicable) NOT FOR MVP
  6. 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 ProcessAP-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 LinksTISDEV-3115
Audit Log


Process NameAP-2 Edit/Remove site approvalComments
DescriptionAdmins 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
ActorsSystem Admin
Pre-Conditions

Site approval date is exxpired

Manual request to make site unavailable received


Post-ConditionsSite is unavailable for use within Posts / Placements
Process Steps
  1. Navigate to site list
  2. Select site to edit or create site
  3. Make necessary changes
    1. Change status to inactive to deactivate
    2. amend start date
    3. amend end date
  4. Link historical sites (if applicable)
  5. Save

Should anything else be done to remove approval? 

Should site approval be stored historically? 

Alternative ProcessAP-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? 

Should a user be able to see which posts/placements are linked here so they can amend them?

JIRA LinksTISDEV-3117
Audit Log


Process StepsAP-3 Define Trainer Pathways - NOT FOR MVPComments
DescriptionAdmins can define pathway for trainers to be assessed against
ActorsAdmin
Pre-ConditionsTrainer record exists within TIS
Post-ConditionsNew pathway defined
Process Steps
  1. Navigate to Pathway Definition space in Trainer record
  2. Select to define new approval
  3. Define an approval type
  4. Define approval name
  5. Define start / end dates
  6. Save

Trainer Types

Clinical Supervisor

Eductional Supervisor

Clinical & Educational Supervisor

Other?


Where should trainer types be defined? Maybe as an interim step?

Where should this function sit?

Where should domains be defined? Another interim step? New reference table?

Is this the right process?

Alternative ProcessN/A
Rules
  • Trainer cannot be linked to trainees if they are not approved
Confirm if true
Jira Links

Audit Log


Process StepsAP-4 Edit Trainer Pathway - NOT FOR MVPComments
Description

Actors

Pre-Conditions

Post-Conditions

Process Steps
  1. Navigate to Pathway Definiion space
  2. Select pathway
  3. Define a pathway name
  4. Select trainer type
    1. add from list
    2. add new trainer type
  5. Assign domains (from reference table)
  6. Save

Alternative Process

Rules

Jira Links

Audit Log


Process StepsAP-5 Expiry NotificationComments
Description

Actors

Pre-Conditions

Post-Conditions

Process Steps

Alternative Process

Rules

Jira Links

Audit Log

Process StepsAP-6 Record Trainer ApprovalComments
DescriptionAdmin should be able to record approval periods for a trainer in their person record
Actors

HEE Admin

Trainer ( ? )


Pre-ConditionsAdmin has navigated to Trainer record
Post-ConditionsApproval dates recorded
Process Steps
  1. Navigate to Pathway Definition space in Trainer record
  2. Select to define new approval
  3. Define an approval type
  4. Define approval name
  5. Define start / end dates
  6. Save
  7. Display new approval
NB: there may be more than one approval record per trainer
Alternative Process N/A
Rules
  • no validation for MVP

Jira LinksTISDEV-3116
Audit Log

dit Log

Process Steps
AP-7 Edit Trainer Approval
Comments
DescriptionAdmin should be able to record approval periods for a trainer in their person record
Actors

HEE Admin

Trainer ( ? )


Pre-ConditionsAdmin has navigated to Trainer record
Post-ConditionsApproval dates recorded
Process Steps
  1. Navigate to Pathway Definition space in Trainer record
  2. Select existing approval
  3. edit relevant field
    1. Define an approval type
    2. Define approval name
    3. Define start / end dates
  4. Save
  5. Display updated approval
NB: there may be more than one approval record per trainer
Alternative Process N/A
Rules
  • no validation for MVP

Jira LinksTISDEV-3118
Audit Log

  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213