Current implementation

between TIS and Integration service

If the doctor info is filtered out by traineeInfoForConenction.sql, TIS will send a dto with only tcs personId to Integration service, so Integration service only needs to check if gmc number is present for identifying records whose TIS info needs to be detached.

between Integration service and Recommendation service

Previously, in Recommendation service, we use gmc number to identify the ES views again. But as recommendationindex is reindexed from masterdoctorindex and every update from masterdoctorindex should be sent to recommendationindex and update its document, so we can assume the doc ids between these 2 indices always match, so there’s no need to search by gmc number again.

Some previous thinking (not in use):

...