List of eHealth environments

The environment for KL Gateway is described here: KL Gateway environments

Actors in the eHealth Environments

A breakdown of the different actors and their roles within the eHealth environments:

Development Team

• Infrastructure Development Teams: Responsible for developing the platform and eHealth services.

• Telemedicine Solution Provider: Engaged in the development of Telemedicine Solutions.

Test Users: Users used for testing Telemedicine Solutions and the eHealth Infrastructure. Test users can be used by:

• Telemedicine Solution Providers: Tests the Telemedicine Solution integration to the eHealth infrastructure primarily in the External Test Environment (EXTTEST).

• Customers: Tests the eHealth infrastructure primarily in the External Test Environment (EXTTEST).

• Infrastructure Provider: Tests the eHealth infrastructure primarily in the Internal Test Environment (INTTEST).

End Users: Individuals who currently use or intend to use Telemedicine Solutions for their healthcare needs.

Operation Teams

• Infrastructure Operations: In charge of operating the eHealth infrastructure, specifically deploying to PRODUCTION.

• Telemedicine Solution Provider: Responsible for operating the Telemedicine Solution and deploying Telemedicine Solutions to PRODUCTION.

The diagram below visually depicts the various actors end-users, solution developers, and operations, utilizing and accessing the eHealth infrastructure environments.

Accessing the environments

The end user and test user login to the eHealth Infrastructure involves the following external systems:

1. Nemlogin: Used for the federated login of Citizens.

2. SEB: Utilized for federated login purposes by Employees in regions and municipalities.

3. KOMBIT STS: Employed for federated login by Employees in municipalities.

The process for logging in follows a specific flow, which is detailed across the following pages: 

• Security Mechanisms

• Client Application Login and Logout to eHealth Infrastructure

eHealth environments connection to SEB, NemLogin and KOMBIT access management (Danish: adgangsstyring)

The following provides an overview of how eHealth environments are connected to both testing and production systems concerning the login process, highlighting the connections between these environments and the respective systems utilized for authentication purposes.

eHealth Environments connection to KOMBIT Environments

The mapping provided below serves as a guiding reference for eHealth environments connection to the KOMBIT FK Organisation service.

eHealth Environments connection to NSP Environments

The mapping provided below serves as a guiding reference for determining the suitable types of environments to be used in conjunction with different NSP (National Service ) environments.

The mapping is intended as a reference to assist in understanding which types of environments correspond or align best with the respective NSP environment.

See https://www.nspop.dk/pages/releaseview.action?pageId=102397438

Component and Data Lifecycle in Environments

The diagram below provides a visual overview of the lifecycle of components and data within the eHealth infrastructure environments. It outlines the progression of components as they are promoted through different environments and depicts the mechanisms for exporting and importing data across these environments.

Key Observations:

• Component Promotion: The diagram illustrates the progression of components through various environments, showcasing how they are promoted across different stages within the eHealth infrastructure.

• Data Export/Import Process: It demonstrates the flow of data, highlighting the export and import procedures between different environments. Notably, Packages (such as questionnaires, activity definitions, and plan definitions) follow a distinct flow. These packages can be developed or created in the EXTTEST environment, exported from there, and subsequently imported into the PRODUCTION environment, and vice versa.

This unique flow for Packages signifies their flexibility in being developed or initiated in one environment and seamlessly transferred to another, facilitating their movement between testing and production environments.