...
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). 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 Intrepid, and those trainees listed as connected connecte
| Status | ||||||
|---|---|---|---|---|---|---|
|
...
- 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)
once they have 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.
- 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)
...