RIZIV / INAMI : NewAttest

7/3/2024

Overview

NewAttest is setup as a 6 Subsystem Solution

Deadline of NewAttest is Asap

We move the IocDs Async Addin logic into our own Project ( WebService) to be ready for the “update” change
We do the .Net 8 migrations together with the Blazor move

Store request
- Encrypt request & store in DWH
  - Encryption = INSZ/NISS conversion to C4 anonymous number
Prep encrypted request
Send request
- This can be two IOCDS Async fluxes (NewAttest_Request_Normal and NewAttest_Request_High) to make the difference between normal and high priority requests which are stored in a different “Send” folder.
IocDs Async Delivers FilePath of Response
The service will scan and pick up the files from the link given by IOCDS Async.
- Import Response into DWH ( Remark: A response from IMA can be data or an error message )
  - Error messages from IMA have not yet been developed in NewAttest and need to check with which type of flux this corresponds in IOCDS Async.
- Not eDos: archive file
Decrypt Data
- Decryption = C4 anonymous number conversion to INSZ/NISS
Enrich Data (from Contact)
- Enrich/Clean DWH with response data (No C4 no RR no GDPR data)
Download response
- Clean Archive/DB/DWH on Request

( Red part is will be removed from the moment DataFlow 2,0 is in PRD )

As new attest is 6 SubSystem solution we’ll seperate the solution into different Git Repo’s

All seperate SubSystems we’ll use the default TFS Deployment pipelines

Comments are closed.