Versions Compared

Old Version 8

changes.mady.by.user Tayo Okuyedi (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Ashley Ransoo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Content

Table of Contents

Background

The scope of TIS was developed in 2015 through a requirements gathering process that involved all teams.  A lot has happened since 2015, so we need to re-verify what we understand to be TIS.  This will help us plan the future objectively.  Part of the future planning will be process alignment, so that when we start to look at new developments we do so with assurance that we have already agreed a standard approach. 

Agenda

Link to Agenda

Attendees

Link to Attendee list

Case Study - Post Funding

Work to address Post Funding:

  • Settled on when trying to work out a Post occupancy report
  • Revealed Inconsistencies in Data due to variation in practice across teams.
  • Invlove National Finance to get their steer

...

Morning session - High priority components


#Component (in no particular order)High level requirements (from most to least no. of BV 1s by component)Jira ComponentRoadmap (Current, Near, Further, Future, Ongoing)Jira Story
1F09 – Trainer user interface (portal) and management

...

  1. Forms and managing Return to work

Training management / merits a new component

  1. ?

2F02 – Assessment
  1. Auditing when recording assessments (Story)
  2. Deleting assessments

...

  1. (tied into managing deletions analysis)
  2. Deleting assessments (tied into managing deletions development)
  3. Mandatory fields
  4. Appeals Process
  5. E-Portfolio interface (analysis)
  6. E-Portfolio interface
  7. Flagging - ARCPs due, gateway for end of training year (notifications?)

Training management

  1. Current
  2. Current
  3. Near
  4. Future
  5. Future
  6. Further
  7. Future
  8. Future
  1. TBC
  2. TISNEW-1427, TISNEW-1440
3F20 – Reporting and analytics
  1. Record Audit (Epic)
  2. NDW - making all fields available in for reporting (analysis)
  3. NDW - making all fields available in for reporting (development)
  4. Have a near real-time NDW (analysis - feasibility)
  5. Have a near real-time NDW (possible development)

Training management / Merits a new component

  1. Current
  2. Near
  3. Further
  4. Near
  5. Future
  1. TBC
  2. TISNEW-94

Placement
  1. Placement manager / Rotation Planning tool MVP
  2. Placement manager / Rotation Planning tool MMF
  3. NDW needs date placement added, date placement amended - links to audit function
  4. Recording of Notes / Comments against post. To record details about where they are (Char limit - initially using whatever was in Intrepid)
  5. Publish placements (this is linked to Placement manager above - uncertain whether to go down this route - will come out of analysis of Placement Planning tool)

  1. Further
  2. Future
  3. Near
  4. Near
  5. Future

4F05 – Course and event management (including study leave) - (classed between M/H)
  1. Analysis (complete work for either walking dev team through it, or approaching external agency/COTS)
  2. Development (in-house or procurement?)


  • Build evaluations and certificates
  • Approval chain management centrally, linked to posts / sites / programmes / specialty and option to link to trainee
  • Applicant portal for Study leave
  • Compliance with GDC Guidelines
  • Online payment provider on course/event management

Training management / Retiring of Intrepid Module

  1. Current
  2. Near

5F12 – Post management

...

  1. Standard approach to recording vacant posts (incl in process alignment work - Naz)
  2. Allowing changes to posts to be made in bulk

...

  1. Being able to filter on Employing body / Training body on post list
  2. Posts Funding - Understand Funding body

Post management

  1. Near
  2. Future (from Mar / Apr 2019)
  3. ? Future
  4. Future

6F17 – Trust Access
  1. Overall review of Trust access (e.g. ARCPs)
  2. To be able to add courses e.g. when run by the Trust
  3. Relocation input (e.g. expenses)

Trust UI

  1. Near
  2. Future
  3. Future

7F08 – Trainee Access
  1. Analysis of structuring of a Trainee UI
  2. Flow of relevant data from Oriel into trainee record (Oriel up for reprocurement 2019 / 2020)
  3. Filling in Form R 
  4. Ability to view on browsers other than Chrome
  5. Review and amend contact details 

Training management / Merits a new component

  1. Near
  2. Future
  3. Future
  4. Future
  5. Future


Accessibility
  1. Extending access to other browsers

  1. Future

Additional notes:

  • Reference tables management raised as an issue to be addressed
  • Show & Tell - Priority of requirements to be raised with Business Managers and Show & Tell, or speaking to Rob Pink. 
  • Priority of new developments against stabilisation of existing functionality was raised. Upon discussion, only 1 person found it of a priority to prioritise stabilisation over new developments. 

  • Case Study - Post Funding, work to address Post Funding:

    • Settled on when trying to work out a Post occupancy report
    • Revealed Inconsistencies in Data due to variation in practice across teams.
    • Invlove National Finance to get their steer

Afternoon session - Process Alignment notes

...

Interim Assessments

  • Recording of PYAs - process for recording this on TIS requires alignment (Joanne Watson (Unlicensed))
  • Terminology alignment and National Taxonomy definition for TIS
  • Recording of Interim Assessments v.s. Educational reviews
    • Do we need to record Interim type?
    • Interim assessment is not an assessment but an event and should ideally be part of event recording
    • Agreement by the audience was - Do not record interim reviews.
    • SOP to be reviewed to reflect these and communicated. Sharepoint to be updated.
    • Educate Local area staffs on Procedures
  • API - Integration with E-portfolio, this required require data sets to be analysed and agreed as a Longer term piece of work to avoid duplication of work in recording assessment. Link to share information.

Trainee leavers Process

  • Leaving destination - recording where trainees are going
  • Why do we need to record this? - To track retention rates for Programmes
  • Leaving Destination to be a list of rationalised Reference values for TIS
  • Leaving reason v.s. Leaving destination
    • Leaving training v.s. leaving due to a higher ranked competing Programme preferences (upgrade) to a different Programme.
    • How to record this on TIS as part of the Programme membership?
    • This would eliminate the need to record Status of the Trainee INACTIVE/DELETE etc. 
  • IDT Data Process alignment required (Joanne Watson (Unlicensed))
  • ESR - How is this captured on ESR?
  • Programme Resignation Form raised as a suggestion
    • Difficulty in recording this with an Assessment Outcome of 6
  • SOPs to be clear and communication regarding the Trainees Leavers Process (Rob & team)
  • Agreement was to get rid of recording Status field for trainees.
  • Programme End Date - to be considered when building an Archiving Process. 
    • Programme End Date to be the only date to be recorded on TIS.
    • Automatic updated of Placement dates and other dates as a result of updating Programme End date raised as a requirement
  • Model of trainee flow for Academic Curriculum was an idea raised - for this to be shared when we have one.
  • Status if 'DELETE' - There's been previous work done with the data leads to rationalise how records are deleted on TIS and where to maintain a status of DELETE. Further details can be found here

Placements - ITP Posts

  • ITP posts are GP focused
  • Definition of ITP posts is to be agreed
  • ITP Posts Vs Accrued Annual Leave
  • Dave Rayner gave a description of ITP posts being one where there is splitting of sites and is a complex post
  • 'Main site' and 'Other sites' recorded within placement is not currently sufficient to capture such Post/Placement
  • Ability to record multiple funding within the Post
  • Naming of the 'Other sites' was raised as a possibility to record ITP, however James mentioned that this should not be confused with the actual purpose of recording 'Other site' on TIS for GP posts.
  • An Additional Site within Placement/Post raised as a suggestion  for recording ITP.
  • London have Posts specific to record ITP placements
  • ITP is for Placement not Posts.
  • Local variations is okay if it  satisfies the below: 
    • Consistent Recording across Regions
    • Ability to report Nationally  

Placement types (additional)

  • Period of Grace - no additional type required
  • Accrued Period of Leave
    • Taken after parental leave for GPs
    • Trusts are required to know
    • Needed for Public health as well (London SE)
    • How to record this and is it actually needed? Is there a possible national requirement?
      • It was agreed for this to be looked at how to record this at a Regional Level on TIS
    • How many Local Offices have a Lead Employer?
      • How is this information recorded on ESR?
      • Positions can be recorded on ESR with Lead or Host Employer information, however this is not consistently being recorded on ESR.
      • Where this detail exists and positions have been created with, these flow in the TIS-ESR interface 

Walls/Pictures/Post-it's

Gallery
columns6