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) | Current Connections: 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 |
General
Content
Integrations
Add Comment