Skip to end of metadata
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 17 Next »

Page Contents:

  • Description
  • Scope
  • Background
  • User Journey
  • Scenarios
  • Field Validation
  • Related JIRA ticket links
  • For Discussion & Assumptions
  • Agreed Next Steps


Description

The management and recording of any absence undertaken by a learner or trainer.

Component TIS-632


Scope

Request Leave (Trainee)

Approve Leave

Approve Leave (Study Leave)

Manage Leave Approvers

Track Study Leave Allocation & Funding (by Trainee)

Track Study Leave Allocation & Funding (by Trust)

View Consolidated Leave Information (by Team)

OOP


Background

Current Usage

LocationIntrepid UsedVolumes of Request (per month)No UsersComments
London & South EastNo  N/A  N/A 
East MidlandsYes 115050 (ad-hoc)
  • Leave Manager Plus used
  • Leave approvers use this primarily to approve requests that have come in
  • TPDs are exception approvers, in addition to rota coordintator
  • Allows automated approval
West MidlandsNo   N/A N/A 
East of EnglandNo  N/AN/A 
North EastNo   N/A N/A 
Yorkshire & HumberNo   N/A N/A  
North West No   N/A N/A  
WessexMaybe50030
  •  Use whole leave approver process
  • Trainers are approvers
Thames ValleyYes Unknown2
  • Used for study leave in a single Trust (Oxford Health, 80 trainees)
  • awaiting feedback from Lisa via Marie
South WestYes TBC (Alice) 7 + 36 trust admins
  • Used for all trainees aside from Foundation
  • Also used for expenses


Recommendation

The Leave Manager module is used by 3 Local Offices, however there is no consistent usage process between them. 


  1. Develop leave management tool as part of TIS for all teams
  2. Manual workaround for a fixed period of time
  3. Teams continue as they are
  4. Develop Hicom advanced tool for all teams


User Journey


JIRA Tickets

https://hee-tis.atlassian.net/secure/RapidBoard.jspa?rapidView=13&projectKey=TIS&view=planning&selectedIssue=TIS-360&quickFilter=41&selectedVersion=11700


Discussion & Assumptions

#QuestionCommentOwner
1










Agreed Next Steps

  • map user journey
  • review scenarios and write up in detail
  • specify field validation changes & rules
  • refine stories to reflect user journey, scenarios and field validation
  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.