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:

Open

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

Key Components

• Technical Infrastructure

  • Computing, networking and storage components.

• Platform

  • Includes Kubernetes and more

  • cross-cutting concerns: Security Logging Deployment Model Messaging

• eHealth Services

  • Exposed to third parties for developing Telemedicine Solutions.

• Backend-for-frontend (BFF)

  • Specialized backend per user experiences.

  • Two types: eHealth Application BFF and Solution Application BFF.

• eHealth Applications

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

• Telemedicine Solutions

  • End-user application provided by a third party.

  • 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

  • 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.

Open

Administrative Domain

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

Open

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.

Open

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.

Open

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).

Open

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

1. NSP Stamdata CPR Enkeltopslags Service (SCES) for citizen ID (CPR) lookup - Documentation (In Danish)

   • See also: https://www.nspop.dk/pages/releaseview.action?pageId=1573053, https://www.nspop.dk/display/public/web/SDM+-+Kom+Godt+i+Gang+-+SCES+-+CPR+Enkeltopslags+Service

2. NSP Stamdata Kopi Register Service (SKRS) for batch copying citizen data - Documentation (In Danish)

   1. For further reading: https://www.nspop.dk/pages/releaseview.action?pageId=1573053, https://www.nspop.dk/pages/viewpage.action?pageId=94649916

3. Sundhedsvæsenets Organisationsregister (SOR) the National Health Organisation Registry

   1. For further reading (In Danish): https://sundhedsdatastyrelsen.dk/SOR

4. KOMBIT Fælleskommunal Organisation (FK Organization) formerly known as Støttesystem Organisation (STS-ORG), is Municipal Organization Registry

   1. For further reading: https://digitaliseringskataloget.dk/l%C3%B8sninger/organisation

5. Danmarks adresseregister (DAR) with Web API (DAWA), which is the Danish Address Registry

   1. For further reading: https://eng.sdfe.dk/products-and-services/the-danish-address-register

The following services receive information from the eHealth Infrastructure:

1. NSP MinLog2

   1. For further reading: https://www.nspop.dk/display/public/web/MinLog2+-+Leverancebeskrivelse

2. NSP Notification Service (Danish: National adviseringsservice, NAS)

   1. For further reading (in Danish): https://www.nspop.dk/display/public/web/National+Adviseringsservice+2+%28NAS2%29+-+Leverancebeskrivelse

3. NSP Document Registering Service (Danish: Dokumentregistreringsservice, DRS)

   1. For further reading (in Danish): https://www.nspop.dk/display/public/web/Dokument+Registreringservice+%28DRS%29+-+Leverancebeskrivelse

4. Clinically Integrated Home Monitoring XDS Repository (in Danish: Klinisk Integreret Hjemmemonitorering, KIH)

   1. For further reading (in Danish): https://www.medcom.dk/systemforvaltning/kih

5. NemSMS

   1. For further reading: https://en.digst.dk/digitisation/nemsms/

6. Medcom Joint Video Infrastructure (in Danish: Videoknudepunktet, VDX)

   1. For further reading: https://www.medcom.dk/medcom-in-english/national-activities/system-management/the-joint-video-infrastructure-vdx

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

• NSP Document Sharing Service (Danish: Dokumentdelingsservice, DDS)

  • For further reading https://www.nspop.dk/pages/releaseview.action?pageId=12226648