Riziv / Inami : Operational Data Integration

Work File : DataDistributionOptions.xlsx
Part 1 : options : CT_2024_11_29_DataDistribution 1.pptx
File 2 : CT_2025_03_07_Operational Data Integration_Part2.pptx
File 3: CT_2025_05_19_Operational Data Integration_Part3.pptx

We decided that following propositions are selected to go further on following 3 propositions

• High count Records
  • Enterprise bus
  • Cross DB Bulk Queries ( materialized Indexed Views ) on Replicated Databases
• Low Count Records
  • Redis Cache 

ct_2024_11_29_operational_data_integration.pptx
File Size:	595 kb
File Type:	pptx

Download File

---

Decision matrix : when to use which option 

Part 2 : CT_2025_03_07_Operational Data Integration_Part2 

1. Matrix is Accepted
   1. Materialized View : ServiceBus : ( Who will create Initial Package and setup ) 
      1. John will check what is possible here with ok from Arnaud
   2. Replicated DB :
      1. I&O are using Azure SQL DB so this option is not on the table with current Choices 
   3. Caching : Wilke will make a study if Redis ( that is used in Community version ) is the right match as this eliminates the 2 best Caching options ( Read-through and refresh-ahead  ) => Arnaud has given the Pragmatic Go

ct_2025_02_xx_operational_data_integration_part2_version2.pptx
File Size:	485 kb
File Type:	pptx

Download File

---

Part 3 2025_05 

Decided: 

1. Materialized View : ServiceBus : ( Who will create Initial Package and setup ) 
   1. John will check what is possible here with ok from Arnaud
2. Caching : Wilke will make a study if Redis ( that is used in Community version ) is the right match as this eliminates the 2 best Caching options ( Read-through and refresh-ahead  ) => Arnaud has given the Pragmatic Go

ct_2025_05_xx_operational_data_integration_part3.pptx
File Size:	635 kb
File Type:	pptx

Download File

---

Discussion was made around the 4 options on how we will communicate the Mutations ( Page 7 ) 

1. Minimalistic : This was clearly a noGO 
2. Pragmatic : Chosen for All GDPR data Mutations
3. Mutated Data : Chosen for second best and can be used for Non GDPR data mutations
4. Full Data : This was clearly a noGO 

Next step : 

• John will create Nihdi.Common.Integrations.Mutations Contract examples 
• John will check examples with Gabriel of Contact / Atlas to have real feedback 
• Wilke will Document the Redis naming conventions ( we notice that RefData is already stored multiple times ... )