Overview
This function will enable HEE administrators to manage the connection of trainee doctors on the GMC's register to them as a Designated Body (DB).
While it is trainees' responsibility to ensure they are connected to the correct DB, local teams are also able to connect and disconnect trainees.
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 mismatches between the actual location of the trainee and data held in HEE's database, and those trainees listed as connected to their DB in GMC's records (listed on GMC Connect).
- Connections:
- Done in batches as part of the on-boarding process for new foundation trainees
- Ad hoc when a trainee transfers to the DB or has/has been disconnected inappropriately (usually too early at end of training)
- Ad hoc when a trainee transfers to the DB or has/has been disconnected inappropriately (usually too early at end of training)
On-boarding process for new foundation trainees (WIP) DRAFT
" In theory, once (a trainee has) full GMC registration (i.e. following their F1 ARCP and before they start their F2 year), they will be prompted by the GMC to connect to a Designated Body; they would then connect to the Deanery/HEE local team through their GMC Online account.
In practice, we get a few connections this way (I emailed all of the F1 trainees progressing to F2 last year with some guidance and contacts regarding revalidation here, and that seemed to work fairly well), but most of them have been picked up when the GMC do a bulk refresh of our connections in October each year." - Andy Petheridge
- 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)
- Connection to another DB because of a conflict of interest (with agreement)
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 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 or 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). HEE administrators must connect/disconnect trainees one by one - there is no bulk functionality on GMC Connect, 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).
Data mismatch scenarios and related business decision DRAFT
| Data issue | Scenario | Business Decision | |
|---|---|---|---|
| 1 | Not connected to Local Office ____ Start Date of Programme is in the future |
These doctors will have records and assigned to programmes to commence in the future | Connect to relevant DB |
| 2 | No Programme Record | Non-trainee doctors - these are usually Deans / Programme Managers. These are doctors with no Programme record. | Connect to relevant DB |
| 3 | Designated Body Mismatch |
These doctors are classed as being outside the flow of training - whilst an OOP doctor is on absence from a programme, they retain the DB of their last programme. A doctor on a visiting placement will also retain the DB and of their 'home' DB. | Flag up these records to the Revalidation Administrator however ; this is an exception that should not be connected |
| 4 | Designated Body Mismatch | Defence trainees are managed by the Defence Deanery and not HEE | Flag up these records to the Revalidation Administrator however ; this is an exception that should not be connected |
| 5 | No Designated Body | Provisionally registered doctors - F1 placements | Flag up these records to the Revalidation Administrator however ; this is an exception that should not be connected |
User needs |
|---|
| Functionality in TIS to enable a Revalidation Administrator to connect or disconnect individual trainees from the designated body** |
| Functionality in TIS to enable a Revalidation Administrator to bulk connect or disconnect trainees |
Functionality to flag up to a Revalidation Administrator where a trainee is joining a training programme and needs to be connected:
|
Functionality to flag up to a Revalidation Administrator where trainees are not on a training programme with the DB:
|
| Functionality to flag up to a Revalidation Administrator discrepancies between the GMC Connect list and HEE's database of who should be connected to the local team |
| ** As we develop the new core there could/should be functionality to transfer trainees between designated bodies in a single step i.e. not require one local team to disconnect and another team to connect separately. Will need to be built with appropriate approval workflow based on agreed policy and business rules - e.g. which local office (outgoing or incoming) responsible for changing connection NB: IDT's require approval from Postgraduate Deans (Responsible Officers) from both local teams |
Functionality in GMC Connect
Add a doctor
Available from the 'All doctors' screen
'Decline' responsibility
Available from 'All Doctors' or 'Under Notice' screens
GMC Connect API
GMC Connect's web services enable secure data transfer and interaction with external services.
The TryAddDoctor method allows a designated body to add a doctor to their list of connected doctors. Following a successful transaction, the GMC will issue notification to the doctor that they have been connected to the designated body. Designated bodies (local teams) are also be notified by email of the change in connection - this applies when doctors connected or disconnected from the DB (NB - email notifications default to 'on' but admin has the opportunity to turn them off).
The TryRemoveDoctor method allows a designated body to remove a doctor from their list of connected doctors. Following a successful transaction, the GMC will issue notification to the doctor that they have been disconnected from the designated body (and the DB as above).
(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, 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 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.
Add Comment