Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Site approvals in bulk

...

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))

Table of Contents


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 AdminHEE Admins (Any Roles with access to create/update sites)
Pre-Conditions

Site approval notification received off platform

Site creation notification received off platform

period is coming to an end or is not approved at present.


Post-Conditions

A new/existing & approved site is added or amended to the Site reference table list

When Adding placements, user should be able to use the new approved Site.


Process Steps
  1. Navigate to site Site list
  2. Select site Site to edit or create site
  3. Enter Fill in relevant fields (see Approvals list across)update and approvals dates from and to 
  4. Update/Set status to Current (if required)
  5. Link historical sites (if applicable) NOT FOR MVP Post - 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 approvalRules


site Alternative ProcessAP-2 Remove site approval
Rules
  • Site must be approved to become available for use within a post/placement - this is known by the approvals from/to date being valid (i.e. not expired)

JIRA Links
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3465

Audit LogN/A



Process Name

AP-1A Create / Add Site Approvals in Bulk

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 in bulk, i.e. multiple sites as a time
ActorsHEE 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

Existing Site is appended with approval details to the Site reference table

When Adding placements, user should be able to use the new approved Site. - Post MVP


Process Steps
  1. Navigate to bulk uploads area
  2. Select the appropriate template to download and fill for Sites Approvals
  3. Fill in relevant fields and approvals dates from and to
  4. Update/Set status to Current (if required) - Post MVP
  5. Link historical sites (if applicable) NOT FOR MVP Post - MVP
  6. Upload the template to TIS
  7. Sites updated with dates


Alternative ProcessAP - 1
Rules
  • Site must be approved to become available for use within a post/placement - this is known by the approvals from/to date being valid (i.e. not expired) - Post MVP
  • Approved from and to dates are added/amended to existing sites - MVP

JIRA LinksTISDEV-3115<<Ticket here>>>
Audit LogSite last amended/added by who and when.



Process Name

AP-2 Edit/Remove site approval

Comments
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 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 / PlacementsPost - MVP

Site is updated with the dates


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 or
    2. amend start date or
    3. amend end date
    Link historical sites (if applicable)
  4. 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  Yes although not sure how this would work as we just recording dates?

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 ? 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  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
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3465

Audit LogN/A


Process Steps

AP-3 Define Trainer Pathways - NOT FOR MVP

Comments
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? 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 ProcessN/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
  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 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
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
  1. Approval space in Trainer record
  2. Select to define new approval
  3. Define trainer type
  4. Define an approval type
  5. Define approval name
  6. Define start / end dates
  7. Save
  8. 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
no validation for MVP
  • add multiple approvals against a single trainer

Jira Links
TISDEV-3116
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3466

Audit Log
dit Log
  • who created and when
  • who edited and when



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 Links
TISDEV-3118
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3466

Audit Log
  • who edited and when