...
The exception to this is Form R Part B - this is where trainees declare any incidents or complaints that they have been involved in. A version of this has been developed for Intrepid (trainee self-service) but is not widely used.
Much of this information (with the exception of the GMC Concerns list) is reviewed by the panel at the time of ARCP - and the panel will note any things that are of concern on the ARCP Outcome form. Therefore, in theory a revalidation officer is generally interested in reviewing issues and concerns that have arisen since the last ARCP - although some we've spoken to do like to see an overview for the whole revalidation period (i.e. the period between Revalidations - some trainees will have 2 during their time under HEE if initial GMC date is >1 year before their CCT, and in theory could be 3 if their training is extended by a long period).
...
ARCP outcome information is held on Intrepid (including the Outcome 'form' which is held as separate data fields) - it is therefore possible to extract the Panel concerns comments field in addition to the Outcome code.
USER REQUIREMENTS
Checking evidence of incidents and concerns is the central part of the revalidation process - as such, revalidation administrators often become the administrators for this information, even though it is also used for other functions such as trainee support, and especially ARCP.
...
- TIS Revalidation in Beta does not tackle Incidents & Concerns logging but provides functionality simply to note what's viewed elsewhere
- As above, but with a clear plan within wider TIS to add Incidents & Concerns logging so that revalidation administrators can predict improvements in the service that will help with buy-in
- User Intrepid data on Incidents and Concerns to feed into TIS Revalidation and thus provide an incentive for local teams to implement and use this Intrepid functionality. HEE to drive business change within teams involved (wider than just revalidation teams) and to invest in improvements to Intrepid functionality where this is found to be truly 'not fit for purpose'
- Develop an Incidents and Concerns logging function within TIS - initially take feeds from Intrepid where available (e.g. ARCP Outcomes) but with a view to migrating all initial data input to TIS (e.g. Form-R, Trust reports) - initially by HEE administrators to replace their existing local systems, but eventually at the source (e.g. Trusts direct input of their exception reports).
ARCHITECTURE
If we do develop a single Incidents and Concerns logging function, it would make sense for this to sit outside revalidation, as it is a resource that would be shared between a number of HEE Trainee processes, e.g. trainee support, ARCP:
...
NEED A NICE DIAGRAM BY RORY/HUBERT HERE