Versions Compared

Key

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

Reminder: Elasticsearch Fields

masterdoctorindex Fields

Required by Recommendations

Required by Connections

id

tcsPersonId

gmcReferenceNumber

doctorFirstName

doctorLastName

submissionDate

ProgrammeName

membershipType

designatedBody

gmcStatus

tisStatus

admin

lastupdatedDate

underNotice

tcsDesignatedBody

programmeOwner

curriculumEndDate

connectionStatus

membershipStartDate

membershipEndDate

existsInGmc

exceptionReason*

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

Implementation Notes

Scenario description

Cross Reference: Connections Logic - Discussions with Users

Trigger/Action - Where does this data come from? What Services and methods are involved?

Note - this column is for existing architecture only, not for architecture proposals!

How does this affect what’s shown in Connections and Discrepancies?

Other Notes

Related tickets

F1 Doctor

Military Doctor

Update made via GMC Connect

Doctor is Connected to a DBC (Add connection)

Drawio
mVer2
zoom1
simple0
inComment0
pageId3702784003
custContentId3702587425
lbox1
diagramDisplayNameUntitled Diagram-1674721032202.drawio
contentVer3
revision3
baseUrlhttps://hee-tis.atlassian.net/wiki
diagramNameUntitled Diagram-1674721032202.drawio
pCenter0
width711
links
tbstyle
height451.5

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 && currentConnection == No

or

WHERE TIS DBC != to DoctorsForDB (GMC) DBC

Update made via GMC Connect

Doctor is disconnected from a DBC (Remove connection)

DBC removed/remove connection

DBC not matching for both TIS and GMC

Programme membership not matching

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