...

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:

...

• Technical Infrastructure - this This is the computecomputing, 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 party 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 application applications provided with the eHealth Infrastructure, see eHealth Applications.

  • Solution Application BFF - a vendor providing a Telemedicine solution may choose to add an own its backend that consumes the eHealth Infrastructure services whilst providing own 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 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.

...

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.

...

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.

...

The Service, Support and Logistics (SSL) Domain contains services for managing catalogs catalogues of services and devices , and ordering of 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 a number of 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:

• NSP CPR Lookup Stamdata CPR Enkeltopslags Service (SCES) for citizen ID (CPR) lookup - Documentation (In Danish): https://www.nspop.dk/pages/releaseview.action?pageId=1573053NSP Batch Copy (Danish: Stamdata kopiregisterservice, SKRS) , https://www.nspop.dk/display/public/web/SDM+-+Kom+Godt+i+Gang+-+SCES+-+CPR+Enkeltopslags+Service

• NSP Stamdata Kopi Register Service (SKRS) for batch copying citizen data - Documentation (In Danish): https://www.nspop.dk/pages/releaseview.action?pageId=1573053, https://www.nspop.dk/pages/viewpage.action?pageId=94649916

• Sundhedsvæsenets Organisationsregister (SOR) the National Health Organisation Registry (Danish: Sundhedsvæsenets Organisationsregister, SOR) - Documentation (In Danish): https://sundhedsdatastyrelsen.dk/SOR

• KOMBIT Municipal Fælleskommunal Organisation Registry (Danish: KOMBIT (FK Organization) formerly known as Støttesystem Organisation , (STS-ORG) which is Municipal Organization Registry - Documentation (In Danish): https://kombitdigitaliseringskataloget.dk/nyhedsbrev-modtagergrupper/f%C3%A6lleskommunale-st%C3%B8ttesystemerDanish Address Register (Danish: Danmarks adresseregister, DAR) l%C3%B8sninger/organisation

• Danmarks adresseregister (DAR) with Web API (DAWA) which is the Danish Address Registry - Documentation: https://eng.sdfe.dk/products-and-services/the-danish-address-register

The following services are sinks receiving receive information from the eHealth Infrastructure:

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

• NSP Notification Service (Danish: National adivseringsserviceadviseringsservice, NAS) - Documentation (in Danish): https://www.nspop.dk/display/public/web/National+Adviseringsservice+2+%28NAS%29%28NAS2%29+-+Leverancebeskrivelse

• NSP Document Registering Service (Danish: Dokumentregistreringsservice, DRS) - Documentation (in Danish): https://www.nspop.dk/display/public/web/Dokument+Registreringservice+%28DRS%29+-+Leverancebeskrivelse

• Clinically Integrated Home Monitoring XDS Repository (in Danish: Klinisk Integreret Hjemmemonitorering, KIH) - Documentation (in Danish): https://www.medcom.dk/systemforvaltning/kih

• NemSMS - Documentation: https://en.digst.dk/digitisation/nemsms/

• Medcom Joint Video Infrastructure (in Danish: Videoknudepunktet, VDX) - Documentation: 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:

...