RIZIV / INAMI : eHealthBox - Part Of IOC

eHealthBox is een Delivery Connector van IOC 

Overview

• Change in the Connector ehealth box OUT
  • Remove the existing middleware
  • Better control of the communication with eHealth
    (the middleware doesn’t give a relevant feedback)
  • Increase the throughput to be able to send 1.000.000 messages in 24h
  • Cost reduction : we stop to pay for the middleware
• Needs of the Connector ehealth box OUT
  • The existing communication software’s with eHealth box
    (eHealth connect unified messaging) d
    on’t have the capacity of sending 1.000.000 messages in 24h
    (Nihdi is the only entity that has such needs)
• Architectural setup of a Connector ehealth box OUT
  • This is integrated in the existing component eHealthbox out saga  in the gateway.
  • No change in Deployeable components
• What is changing
  • The component  eHealthbox out sent the message to the middleware (on prem) healthconnect UM and the middleware send the request to eHealth
  • Now the component will send the request directly to eHealth. ( Change Url )
  • We need a specific certificate (to avoid confusion in case of incident) to communicate with eHealth.
  • The InfraReq Changes