Architecture and Domains

Owned by Erik Nielsen
Last updated: 14-08-2024 by Gliffy Diagram for Confluence
4 min read

Defines the eHealth infrastructure’s architecturally significant functional elements.

Page Content

eHealth Architecture

Throughout the documentation, the term eHealth Infrastructure refers to the services provided on the platform.

Starting from the bottom of the figure, the system contains:

Image source: https://ehealth-dk.atlassian.net/wiki/spaces/PI/pages/2585100300/Gliffy+Drawings

 

  • Technical Infrastructure - This is the computing, networking and storage part.

  • Platform - this is Kubernetes, internal databases and more

  • Platform cross-cutting concerns:

    • Security

    • Logging

    • Deployment Model

    • Messaging

  • eHealth Services - The eHealth services are exposed to third parties for developing Telemedicine Solutions.

  • eHealth Applications - End-user application provided as part of the eHealth Infrastructure.

  • Telemedicine Solutions - End-user application provided by a third party.

  • Backend-for-frontend (BFF) - Design Pattern for rather than having a general-purpose API backend, a BFF expose a specialized backend per user experiences.

    • eHealth Application BFF - backends for applications provided with the eHealth Infrastructure, see eHealth Applications.

    • Solution Application BFF - a vendor providing a Telemedicine solution may choose to add its backend that consumes the eHealth Infrastructure services whilst providing an API towards the application client. The vendor may choose to let the application consume eHealth services directly or use a hybrid between BFF and direct invocation.

  • Application Client/Service - It is expected that applications/services (Danish: fagsystemer) used by healthcare providers, social providers or social care providers will consume eHealth Infrastructure services directly, but they, too, may choose to use a BFF.

Domains

Overall, the services of the eHealth Infrastructure are divided into three domains elaborated in the following.

 

Administrative Domain

The Administrative Domain contains generic services and resources, that is, services and resources that are not specific to patients/citizens.

 

How to interact with these services is elaborated in Interacting with Services in the Administrative Domain.

Clinical Domain

The Clinical Domain contains services that provide patient/citizen-related resources. They make use of the services and resources in the Administrative Domain.

 

How to interact with these services is elaborated in Interacting with Services in the Clinical Domain.

Service, Support and Logistics (SSL) Domain

The Service, Support and Logistics (SSL) Domain contains services for managing catalogues of services and devices and ordering these services and devices.

 

How to interact with these services is elaborated in Interacting with Services in the SSL Domain

System Context of eHealth Infrastructure

As depicted below, the eHealth Infrastructure is integrated with several external systems, most of which are provided by the Danish National Health Data Agency (Danish: Sundhedsdatastyrelsen) through the National Service Platform (NSP).

 

The following services are sources of information consumed by the eHealth Infrastructure:

 

The following services receive information from the eHealth Infrastructure:

 

The following service(s) are legacy wrapped by service(s) in the eHealth Infrastructure:

 

Additional architecture artifacts about the eHealth Infrastructure are available in the eHealth Architecture Repository.