Overview
This function will enable HEE administrators to manage the connection of trainees on the GMC's list 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 trainee 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 in batches as part of the on-boarding process for new trainees
- Disconnections - usually managed by programme administrators once trainees have completed their programme (CCT or CCT + Grace Period for higher specialty)
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 and fully 'signed-off' from being the DB's responsibility.
Trainees are usually connected and disconnected directly on GMC Connect (and trainees always use this channel to connect/disconnect themselves). Administrators must connect/disconnect trainees one by one - there is no bulk functionality on GMC Connect (although see note on 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.
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, 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...
Add Comment