Current implementation
Drawio |
---|
mVer | 2 |
---|
zoom | 1 |
---|
simple | 0 |
---|
inComment | 0 |
---|
custContentId | 3871801524 |
---|
pageId | 3859513346 |
---|
lbox | 1 |
---|
diagramDisplayName | Untitled Diagram-1698014056672.drawio |
---|
contentVer | 1 |
---|
revision | 1 |
---|
baseUrl | https://hee-tis.atlassian.net/wiki |
---|
diagramName | Untitled Diagram-1698014056672.drawio |
---|
pCenter | 0 |
---|
width | 1321 |
---|
links | |
---|
tbstyle | |
---|
height | 701.0000000000001 |
---|
|
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):
Drawio |
---|
mVer | 2 |
---|
zoom | 1 |
---|
simple | 0 |
---|
inComment | 0 |
---|
custContentId | 3859513357 |
---|
pageId | 3859513346 |
---|
custContentIdlbox | 38595133571 |
---|
diagramDisplayName | TISRevalUpdates.drawio | lbox | 1 |
---|
contentVer | 12 |
---|
revision | 12 |
---|
baseUrl | https://hee-tis.atlassian.net/wiki |
---|
diagramName | TISRevalUpdates.drawio |
---|
pCenter | 0 |
---|
width | 601 |
---|
links | |
---|
tbstyle | |
---|
height | 541 |
---|
|
NB this is just thinking, not actual implementation