Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Connections - currently done in bulk 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.

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, and where relevant, the doctor’s previous designated body will also be notified of the change in connection. 

When a doctor is successfully added through this method, the doctor’s revalidation submission date will be returned to the calling system.

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. 

(Source: GMC Revalidation Web Services User Guide v2.0)

Intrepid functionality