...
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 IntrepidHEE's database, 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.
- Connections:
- Done in batches as part of the on-boarding process for new foundation trainees
...
Data mismatch scenarios and related business decision Status colour Yellow title 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 |
...