Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Examples of different applications types that can be built using the eHealth infrastructure.

Deployment models represents a specific type of deployment of Telemedicine Solutions..

  • Single Page Application (SPA) or server-side generation of web pages

  • All logic in browser or server-side components such as BFF

  • Using the KAM micro frontend architecture

  • Thick clients such as native mobile applications

  • etc.

There are several way to develop and deploy Telemedicine Solutions:

Single page application

The server returns a single page that is manipulated in the browser using e.g., JavaScript API. The content of the single page based on calls to eHealth services from the browser.

Applications may be simple web server (delivering web content to browser) delivering a single page to the browser.

The browser is then requesting data from backend, and updating the single page based on the content returned.

If no logic is needed then a simple application serving web content to a browser is perfect. E.g. just a simple web application hosting a single page app based on Angular and typescript in browser.

Application using a BFF

Singe Page Application is executed in the browser, requests data from backend-for-frontend, that provides an API optimized for the application.

The "Telemedicine Solution" is split into

  • a front-end (UI) that serves SPA.

  • a backend/backend-for-frontend 

BFF is a variation of API gateway pattern.

  • API gateway is the single entry point for (all) clients.

  • BFF provide specific backend have one backend per user experience (Instead have a general-purpose API backend)

The BFF handles requests in one of several ways.

  • Some requests are simply proxied/routed to the appropriate service.

  • API gateway handles other requests by fanning out to multiple services (orchestration / choreography)

  • API gateway maintain data consistency across multiple services  

  • API gateway converts FHIR request and responses to proprietary protocol

  • ….

Applications uses FUT/KAM micro frontends

The clinical administrative module named KAM is built as an application with individual micro-frontends, that are integrated in the browser.

KAM has a number of endpoints where the browser can retrieve KAM components from. Currently it consists of:

  • common workplace,

  • careteam,

  • questionnaire editor,

  • plan template editor and

  • pickers.

These are micro-frontends, not micro-services.

KAM elements are then put together in the browser. That is, the user will download an application consisting of five components, which will run in the browser and will send request to the eHealth services

Server side generation of the web pages

Solution is hosted on the eHealth infrastructure and generates web pages based on requests from the browser.

The Telemedicine solution is hosted on the eHealth infrastructure that generate web pages. The browser is then requesting data / new pages from the Telemedicine Solution. The application generates new pages on the server by requesting data from eHealth services.

  • No labels