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 15 Next »

Page Contents:

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


Description

All training programmes should be approved by the appropriate regulator, College or other approval giving body or individual. In the case of GP programmes this also includes the practice site and trainer

Component TIS-645


Scope

Manage Site Visits

Manage GP Trainer Re-Accreditation Visits

Manage Re-Accreditation Notifications (GP)


Background

Current Usage

LocationIntrepid UsedVolume of GP / PracticesNo UsersComments
London & South EastYesTBC2
  • Sites entered into Reference Table & Educational Events (site approval)
  • Approval period (start/end) dates entered for Trainers
East MidlandsYes

250 sites

550 trainers

3
  • Sites not entered into Intrepid
  • Accreditation pathway aprovals for Trainers
West MidlandsYes

464 sites

1321 Trainers

6
  • Accreditation pathway used for GPs
  • Update site reference table with dates
East of EnglandYes

600 Sites


3
  • GP / Trainer role is added to the system, use accreditation pathway
  • Record approval date of a site in site reference table
North EastYes

196 Sites

TBC 

TBC 
Yorkshire & HumberYes

TBC Sites

TBC

20
  • Speak to Helan Raynor on accrediation pathway 
  • Accreditation pathway used for GPs & Clinical / Educational Supervisors based in Trusts (3000+)
  • Site approval via reference table
North West Yes

700 trainers

500 sites

6
  • Recording trainer approvals
  • Record site approvals
  • Accreditation pathway
WessexMaybe tbctbc  Clare Frances to confirm points of contact
Thames ValleyYes tbctbc 
  •  Speak to Barbara Gow (01865785583)
South WestYesAlice to confirm2

 Alice Brindle 01752676151 / Andrew Horton 01454252696

  • Accreditation pathway used for trainers & trusts
  • not widely used across the team




Recommendation

  1. Develop solution to support
  2. Manual workaround - use email / spreadsheet system until after March
  3. Allow teams continue as they are
  4. All teams use Hicom supported service



User Journey


JIRA Tickets

https://hee-tis.atlassian.net/secure/RapidBoard.jspa?rapidView=13&projectKey=TIS&view=planning.nodetail&selectedIssue=TIS-645&quickFilter=48&versions=visible&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

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