Connection Discrepancies - Background

Previously discussed challenges can be found here - Revalidation Process, Issues & Considerations

Old Manage Connections specification - Manage connections

Context

• There are 3 ways that a connection can be changed          

            1 - The programme membership + region is changed in TIS

            2 - A manual change is made via GMC connect

            3 - A manual change is made via Connections Discrepancies in TIS

Assumptions

In all scenarios, the following is true:            

• updates should be shared to the GMC intra-day

• updates from GMC connect will come in daily

• changes going to GMC should be postively receipted, if not, then moved to exception queue for resubmission

• all changes should be logged (date/timestamped + source)

• all trainee doctors in current programme should be connected to a designated body

Local Office to Designated Body Mapping

In most cases, there is a 1:1:1 relationship between programme membership : local office : designated body, except in jointly (or more) held programmes.

<link if available>

<joint programmes>

<triplicate programmes>

Triggers

There are multiple triggers for these

Location change

• trainee is changing location

 Change via GMC 

• trainee makes a change (correct - changed region & on time)

• trainee makes a change (wrong timing)

• trainee makes a change (no need)

• other?

Change via TIS-Reval-ConnectionsDiscrepancies

• API error (re-send as automated updated failed)

• Discrepancy is flagged relating to (i) another trigger (ii) exception handling

Exceptions

• Military trainees do not need to be managed in TIS

• F1 trainees are not connected to any designated body      

• Associate Deans are not trainees, but do need to be connected to a designated body      

• other?