Terms and Definitions

This page lists the terms and definitions used throughout the documentation.

This section defines terms, acronyms or abbreviations that might be unfamiliar to the target audience. This includes both business terms and technology / architectural terms.

Term	Definition

Term	Definition
eHealth Infrastructure	The eHealth Infrastructure consists of: Technical Infrastructure - computer, network, etc. Platform Services - generic technical services such as databases, Kubernetes etc. eHealth Services - The eHealth domain services are exposed to third parties for developing Telemedicine Solutions.
Technical Infrastructure	The technical infrastructure is the compute, networking and storage part.
Platform	This is the generic infrastructure that runs the eHealth services. This is Kubernetes, databases and more.
eHealth Services	The eHealth services are exposed to third parties for developing Telemedicine Solutions.
eHealth Application	End-user application provided as part of the eHealth Infrastructure.
Backend-for-frontend (BFF)	A pattern for providing one backend per user experience rather than having a general-purpose API. See also Sam Newman - Backends For Frontends
Administrative Domain	The Administrative Domain contains generic services and resources, that is, services and resources that are not specific to patients/citizens
Clinical Domain	The Clinical Domain contains services that provide patient/citizen-related resources.
Telemedicine Solution (Danish: Anvenderløsning)	Solutions or applications provided by 3rd party. This includes Patient application - Applications used by patients in their homes to Submit measurements from medical devices, communicate with doctors, etc. Employee application - Applications are used by employees, e.g. to administer telemedicine treatments, monitor and analyse measurements submitted by patients, and other clinical tasks.
Application Vendor	Organisation or company delivering one or more Telemedicine Solutions using the eHealth Infrastructure.
Domain	A Domain or Subdomain is part of the eHealth model is a sub-area of knowledge or activity; especially one that somebody is responsible for. The eHealth infrastructure is divided into the following 3 domains: Administrative Domain Clinical Domain Support, Service and Logistic Domain Each domain contains several services.
API	Application Programming Interfaces
FHIR-based infrastructure	FHIR-based infrastructure is a common term for the Clinical Domain and the Administrative Domain that exposes services and resources based on the FHIR standard.
Key Value Store	The Key/Value store is available for storing properties and configuration values that do not fit into the FHIR-based infrastructure
Infrastructure Provider	The organisation is responsible for providing the eHealth infrastructure.
SRE	Site Reliability Engineering The SRE (Site Reliability Engineering) team helps the development teams to maintain and improve the application.
AS	eHealth Infrastructure Authorisation Server
NemLogin	The NemLogin service is intended to be used by citizens in order to gain access to data in the eHealth Infrastructure.
IdP	Identity Provider
SEB	Sundhedsvæsenets Elektroniske Brugerstyring https://services.nsi.dk/seb
Context Handler	The KOMBIT Context Handler The KOMBIT Context Handler acts as a proxy for the municipalities' Identity Providers and translates one user job function roles to user system roles.
OIDC	OpenID Connect (OIDC) is an open authentication protocol that profiles and extends OAuth 2.0 to add an identity layer. eHealth Infrastructure uses OIDC flow for authentication.
SAML	Security Assertion Markup Language (SAML) is a Login Standard To Help Users Access Apps. SAML is used “outside” the eHealth Infrastructure. The eHealth Infrastructure can translate the SAML to a JWT token used internally in the infrastructure.
JWT	JSON Web Token (JWT) is a means of representing claims to be transferred between two parties in JSON format.