...
This function will enable HEE administrators to manage the connection of trainees trainee doctors on the GMC's list register to them as a Designated Body (DB). Trainees must be connected to the correct DB in order for that local team to manage their revalidation, therefore it is generally revalidation administrators who deal with any mis-matches between the actual location of the trainee and data held in Intrepid, and those trainees listed as connected to their DB in GMC's records (listed on GMC Connect).
While it is trainees' responsibility to ensure they are connected to the correct DB, local teams are also able to connect and disconnect trainees who do not 'belong' to them.
- Connections - currently done :
- Done in batches as part of the on-boarding process for new trainees
- Ad hoc when a trainee transfers to the DB or has/has been disconnected inappropriately (usually too early at end of training)
- Disconnections
- When trainees have completed their programme (CCT or CCT + Grace Period for higher specialty) - either managed by programme team or revalidation administrator
- When trainees resign from the training programme for another reason (or are released from the programme - ARCP Outcome 4)
- Ad hoc when a trainee is noted to be wrongly connected to the DB (usually too soon at start of training)
Mismatched records are usually due to timing issues e.g. a trainee may connect themselves to a DB before they actually commence a programme, or may be disconnected by an administrator before they have been revalidation revalidated and fully 'signed-off' from being the DB's responsibility.
There are various local processes to manage this including daily monitoring and comparison using spreadsheets and macros or simply manually comparing lists downloaded from GMC Connect and Intrepid on a weekly on monthly basis. Local teams do get notified by the GMC (automatic notification via GMC Connect) if a doctor connects or disconnects from them. Also Intrepid 'match' functionality - see below.
The main trigger for disconnections is that trainees are beyond the end of their training programme, and have an Outcome 4/6 or have resigned, ITD'd etc.
Trainees are usually connected and disconnected directly on GMC Connect (and trainees always use the trainee version of this channel to connect/disconnect themselves). Administrators HEE administrators must connect/disconnect trainees one by one - there is no bulk functionality on GMC Connect (although see note on , although GMC request an annual spreadsheet of trainees to 'refresh' the connections (annual reconciliation) - this was supposed to have been superseded by new Intrepid functionality (see note Intrepid functionality below).
Functionality in GMC Connect
GMC Connect API
GMC Connect's web services (a collection of SOAP XML web methods) enable secure data transfer and interaction with external services.
...
(Source: GMC Revalidation Web Services User Guide v2.0 + GMC Connect user guidance for revalidation - effective 1 July 2016)
Intrepid functionality
Intrepid v10 uses the GMC Connect API to enable revalidation (and other) administrators to add (connect) and remove (disconnect) trainees via the Intrepid revalidation dashboard,and decline connection requests (?? check with JW - ref. ROG proposals document), however it does not allow users to include key information required by GMC (and enabled by the GMC Connect API):
- Doctors to remove - need to include reason for disconnection - options:
- Conflict of interest
- Doctor has retired
- The doctor does not have a connection with this designated body
Intrepid also has Match functionality which compares its trainee list to the list held on GMC Connect as connected to each local team as Designated Body....to be continued...has a bulk update facility. It identifies doctors to add based on comparison of the GMC connect list with Intrepid records and allows you to tick multiple doctors to connect and then click submit for batch connection of these. The same is true for bulk disconnections. It is reported that this functionality is a bit temperamental and therefore not trusted/used.
User needs |
|---|