Reminder: Elasticsearch Fields
masterdoctorindex Fields | Source of Truth (which service has final say) | Required by Recommendations | Required by Connections |
|---|---|---|---|
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 | 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 | ✅ |
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? | 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) | 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 Discrepancies 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 |
0 Comments