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

Open

Key Components

• Technical Infrastructure

  • Computing, networking, and storage components

• Platform

  • Includes Kubernetes and additional components

  • Handles cross-cutting concerns: Security, Logging, Deployment Model, Messaging

• eHealth Services

  • APIs exposed to third parties for developing Telemedicine Solutions

• Backend-for-Frontend (BFF)

  • Specialised backend tailored to specific user experiences

  • Two types: eHealth Application BFF and Solution Application BFF

• eHealth Applications

  • End-user applications provided as part of the eHealth Infrastructure

• Telemedicine Solutions

  • End-user applications provided by third parties

  • Third-party vendors can create their backend (Solution Application BFF) that consumes eHealth Infrastructure services while providing an API to their application client. Vendors can choose to consume eHealth services directly, use a BFF, or combine both approaches

• Application Client/Service

  • Applications and services (fagsystemer) used by healthcare providers, social providers, or social care providers

  • These consume eHealth Infrastructure services directly, but may also choose to use a BFF

Domains

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

• Clinical Domain

• Administrative Domain

Administrative Domain

The Administrative Domain contains generic services and resources that are not specific to patients or citizens. These include:

• Services for maintaining Plan Definitions (templates)

• Services for maintaining questionnaires

• Services for master data on organisations, employees, and care teams

• Services for maintaining and governing terminology (classifications, allowed values, etc.)

How to interact with these services is elaborated in https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/512950429.

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.

• Patient/citizen demographic information

• Patient/citizen demographic episodes of care and plans

• Submitting measured data (measurement, questionnaire responses, photos, etc.)

• Automated processing of submitted measurements, e.g. triaging measurement data

• Employees' processes in establishing plans, regimes for patient/citizen care

• Employees' processes in monitoring and evaluating measurement data

• Appointment and communications

• Document sharing with the national archives

How to interact with these services is elaborated in https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/539459601.

System Context of eHealth Infrastructure

As shown below, the eHealth Infrastructure integrates with several external systems. Most of these systems are provided by the Danish National Health Data Agency (Sundhedsdatastyrelsen) through the National Service Platform (NSP).

Open

Services that provide information to the eHealth Infrastructure:

1. NSP Stamdata CPR Enkeltopslags Service (SCES) - For citizen ID (CPR) lookup

   1. Documentation (In Danish): 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

   1. Documentation (In Danish): 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 Organisation) - Municipal Organisation Registry (formerly STS-ORG),

   1. Documentation (In Danish): https://digitaliseringskataloget.dk/l%C3%B8sninger/organisation

5. Danmarks adresseregister (DAR) with Web API (DAWA) - The Danish Address Registry

   1. Documentation (In Danish): https://danmarksadresser.dk/om-adresser/danmarks-adresseregister-dar

Services that receive information from the eHealth Infrastructure:

1. NSP MinLog2

   1. Documentation (In Danish): https://www.nspop.dk/display/public/web/MinLog2+-+Leverancebeskrivelse

2. NSP Notification Service (NAS) - National adviseringsservice

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

3. NSP Document Registering Service (DRS) - Dokumentregistreringsservice

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

4. Clinically Integrated Home Monitoring XDS Repository (KIH) - Klinisk Integreret Hjemmemonitorering

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

5. NemSMS

   1. For further reading: https://digst.dk/it-loesninger/nemsms/

6. Medcom Joint Video Infrastructure (VDX) - Videoknudepunktet

   1. For further reading: https://medcom.dk/systemforvaltning/videoknudepunktet-vdx/

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