TEXT IN RED MAY BE OUT OF DATE OR INCORRECT
Recommended Reading:
Connections Logic - Discussions with Users
Connections Data Models
GMC’s API
The GMC provide the following methods pertaining to connections:
...
Therefore from the overnight sync job we only get a snapshot of current connections from GMC’s point of view. Any disconnections that may have occurred from outside of our system would have to be inferred by a negative (“if doctor not in this list”) - this is potentially partially implemented via the “hide all doctors” step of the overnight sync job - but this only sets a flag to hide/show in the recommendations list, it does not alter the connection status.
TIS Change Data Capture
The connections microservice also receives data from TIS via the CDC system based on application events.
The following logic is currently implemented (as of 23/08/2022):
If curriculum membership is null - disconnected
if programme membership is null (or pm dates are null) - disconnected
if programme start date is after today - disconnected
if programme end date is before today - disconnected
Otherwise - connected
Source (note that this logic is implemented in TCS, not connection service):
...