id

Elasticsearch (Auto Id)

✅

✅

tcsPersonId

TCS

✅

✅

gmcReferenceNumber

GMC

✅

✅

doctorFirstName

GMC

✅

✅

doctorLastName

GMC

✅

✅

submissionDate

GMC

✅

✅

ProgrammeName

TIS

✅

✅

membershipType

TIS

✅

✅

designatedBody

GMC

✅

✅

gmcStatus

GMC

✅

tisStatus

REVAL

✅

admin

REVAL

✅

lastupdatedDate

REVAL

✅

underNotice

GMC

✅

tcsDesignatedBody

TIS

✅

programmeOwner

TIS

✅

curriculumEndDate

TIS

✅

connectionStatus

*this should be renamed “tisConnectionStatus” and refers to TIS' “point of view” about the connection, and is set to “No” in the following circumstance:
Objects.isNull(curriculumMembership) ||
Objects.isNull(programmeMembership) || Objects.isNull(programmeMembership.getProgrammeStartDate()) || Objects.isNull(programmeMembership.getProgrammeEndDate()) || programmeMembership.getProgrammeStartDate().isAfter(currentDate) || programmeMembership.getProgrammeEndDate().isBefore(currentDate);

TIS

✅

membershipStartDate

TIS

✅

membershipEndDate

TIS

✅

existsInGmc

GMC

✅

exceptionReason*

*this field is currently in the code in connections but doesn’t exist in masterdoctorindex, appears to have been overlooked

TIS/REVAL

✅

F1 Doctor

Military Doctor

Update made via GMC Connect

Doctor is Connected to a DBC (Add connection)

Change in GMC Designated Body code is picked up by Reval system. If doctor was previously disconnected, “existsInGmc” field will be changed from false to true

Current Connections:
WHERE existsInGmc = true

Discrepancies
WHERE existsInGmc == true && connectionStatus== No

or

WHERE TIS DBC != to DoctorsForDB (GMC) DBC

If a doctor is connected to a DBC via GMC connect, this change will come through to our Revalidation system via the GMC sync.

The discrepancy occurs because the TIS system is not updated accordingly

We need to be able to:

1. Flag where the TIS DBC is different from the GMC DBC when a new change is made

2. Flag where the TIS DBC is different from the GMC DBC for historic/existing data in our system

Update made via GMC Connect

Doctor is disconnected from a DBC (Remove connection)

Change in GMC Designated Body code is picked up by Reval system. If doctor was previously disconnected, “existsInGmc” field will be changed from false to true

Current Connections:
Not shown

Discrepancies
WHERE existsInGmc == false && connectionStatus == Yes

or

WHERE TIS DBC != to DoctorsForDB (GMC) DBC

If a doctor is disconnected from a DBC via GMC connect, this change will come through to our Revalidation system via the GMC sync.

The discrepancy occurs because the TIS system is not updated accordingly

We need to be able to:

1. Flag where the TIS DBC is different from the GMC DBC when a new change is made

2. Flag where the TIS DBC is different from the GMC DBC for historic/existing data in our system

DBC removed/remove connection

TODO: diagram to show TIS CDC and ES Sync

Basically, the connectionStatus field

DBC not matching for both TIS and GMC

TODO: diagram to show TIS CDC and ES Sync

Basically, the connectionStatus field

Programme membership not matching

TODO: diagram to show TIS CDC and ES Sync

Basically, the connectionStatus field

GMC number not matching

No GMC number in TIS

GMC send a GMC number for a doctor who had no GMC number in TIS

GMC provide doctor not in TIS

Doctor has current programme membership in TIS, not connected to DBC & programme end date is today or in the future

Doctor Connected to a DBC and Programme Membership not expired

Doctor Connected to a DBC and Programme membership Expired

TIS to GMC API failure

Overlapping programmes in 2 regions

INACTIVE Doctors in TIS

Hide doctor with current connection

NEW: License to Practice removed due to suspension

Sanity check data on Prod