What’s about #H Infrastructure

Thanks to POR Campania 2014-2020 grants, #Healthing and Webgenesys, can apply and invest in a new process to develop a new solution compliant with the organizational guidelines containing the “Digital model for the implementation of home care”  published by Minister of Health and signed 29 April 2022 , after acquiring the favorable opinion of the State-Regions Conference.

The #Healthing telemedicine platform was developed with a microservices architecture, like in the follow figure:

It is possible to connect to the platform via the #Healthing web/mobile app or via services compliant with the HL7 FHIR standard.

A reverse proxy forwards incoming traffic to the microservice of interest (BE, FE and IAM) and offers load balancing features when the microservice replica is greater than 1.

The reverse proxy used is Traefik which integrates perfectly with the exposed microservices. The choice of the reverse proxy is not binding and depends on the desired deployment. The main microservices exposed are the Gateway backend, the Frontend and Keycloak IAM.

The Frontend responds to the pointing of the chosen domain returning a Single Page Application (SPA) developed in React with components compliant with the AgID guidelines (Italia UI kit v2 https://developers.italia.it/it/designers/).

#H responds to the pointing of the chosen domain returning a Single Page Application (SPA) developed in React with components compliant with the AgID guidelines (Italia UI kit v2 https://developers.italia.it/it/designers/).

The Frontend interrogates, in a typical flow, the Backend through requests that will be managed by the Backend gateway.

The Backend gateway manages all requests addressed to the backend, correctly forwarding the request to the corresponding microservice.

• Core: it is the main microservice of the system, which manages the basic functions such as user authentication, session management, data management and communication with other microservices.
• Notification: it is the microservice that manages the sending of notifications to system users, for example “notifications of access by a new user”.
• Event-manager: it is the microservice that manages system events, for example the registration of new patients, the creation of new entities or the modification of existing data; this component also includes the ability to customize event handling via scripts.
• Logger: it is the microservice that manages the recording of the system logs, ie the information relating to the activities and operations carried out by the various microservices.
• Keycloak-admin client: This is the microservice that allows you to manage users, profiles and roles of system users using the Keycloak authentication server.
• Firebase client: it is the microservice that allows you to use Firebase features, such as sending push notifications.
• HAPI FHIR client: it is the microservice that allows you to use the HAPI FHIR functions, for the management of health data.
• Ownload client: is the microservice that allows you to use the features of OwnCloud, repository and collaboration tool for clinical documentation management.
• Mobile: it is the microservice that manages the functions of the system’s mobile application, such as data display, notification management and communication with other microservices.
• Data: is the microservice that manages the storage and management of system data and communicates with the database.

The new #Healthing System offers: