Terms and Definitions

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 exposed to third party 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 exposed to third party for developing Telemedicine Solutions.

eHealth Application

End user application provided as part of the eHealth Infrastructure.

Backend-for-frontend (BFF)

Pattern for providing one backend per user experience rather than have 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.

Service, Support & Logistics Domain

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

Telemedicine Solution (Danish: Anvenderløsning)

Solutions or Application 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 analyze measurements submitted by
  patients, and other clinical tasks.

Application Vendor

Organization 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 a number of 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 does not fit into the FHIR based infrastructure

Infrastructure Provider

The organisation 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 Authorization 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 JWT token used internal in the infrastructure.

JWT

JSON Web Token (JWT) is a mean of representing claims to be transferred between two parties in JSON format.