RIZIV / INAMI : eDosServices

Reason

• eDos is a dossier applications for the Medical Control and Study Department inspecting Care Personnel/Institution on (para)-medical prestations. ​
• eDos is also Accessible  to concerned and also representative (magistrate/lawyers) via eDosServices
• eDos is a Case 360 Migration project
• eDos project is seperated in Appian ( eDos ) and .Net (eDosServices)
  • eDosServices
    • As there are multiple issues connecting the FO and BO to Appian the team has created a full .Net Setup connected through the API with Appian.
    • The full .Net structure has been delayed ( See Appian current history) and now the Architecture has to be ARB- Reviewed

Overview

eDosServices is setup as a Default 3 layer application into the eDos landscape

• 3 layer
  • WebFrontEnd
    • Blazor BackOffice ( BO )
    • Blazor FrontOffice ( FO )
  • BackEnd 
    • API : .Net 8 API as connection with Appian and the own Database ( not shared )
    • ZipService : a separated WebService special for Zipping – Linked With the dossier to allow download of the full content of the dossier documents by external parties​
  • SQL Database

Planning

• Team is getting ready for TST deployment 
• Deadline is end of August in PRD