Intended Audience: This description caters primarily to third-party providers seeking a fundamental understanding of eHealth infrastructure environments. It aims to elucidate the purpose, user base, accessibility, and integration aspects of these environments to facilitate better collaboration and integration efforts within the eHealth ecosystem.
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:
Nemlogin: Used for the federated login of Citizens.
SEB: Utilized for federated login purposes by Employees in regions and municipalities.
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:
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 Environment Type | eHealth Environment | NemLogin Environment | KOMBIT Adgangsstyring | SEB Sundhedsvæsenets Elektroniske Brugerstyring |
|---|---|---|---|---|
Internal test environment | INTTEST | Test environment | External test | Test (t-seb) |
External test environment | EXTTEST | Test environment | External test | Test (t-seb) |
Vendor development environment | DEVENVCGI | Test environment | External test | Test (t-seb) |
Education environment | TEST002 | Test environment | External test | Test (t-seb) |
Pre-production environment | PREPROD | Test environment | External test | Test (t-seb) |
Production environment | PROD | prod | Prod | Prod |
eHealth Environments connection to FK Organisation
The mapping provided below serves as a guiding reference for eHealth environments connection to the FK Organisation service.
eHealth Environment Type | eHealth Environment | KOMBIT Environment FK Organisation |
|---|---|---|
Internal test environment | INTTEST | external test
|
External test environment | EXTTEST | external test
|
Vendor environment | DEVENVCGI | external test
|
Education environment | TEST002 | external test
|
Pre-production environment | PREPROD | external test
|
Production environment | PROD | prod
|
eHealth Environments connection to NSP Environments
The following mapping serves as a clear reference to assist in selecting the appropriate types of environments to complement various NSP (National Service) environments.
NSP and KIH Test Environments
NSP has several test environments. These are described here:
From https://www.nspop.dk/pages/viewpage.action?pageId=4839407 cNSP is used for municipalities and dNSP for regions. This reference is used in the following
NSP Environment | Municipalities Endpoint (central) | Regions Endpoint | DROS Paths | DDS Paths | DRS Path | KIH Endpoint |
|---|---|---|---|---|---|---|
TEST1 |
|
|
| KIH Not available in test 1 | ||
TEST2 |
|
|
| http://kih.test.xdsrepositoryb.medcom.dk:8020/axis2/services/xdsrepositoryb | ||
PRODTEST |
|
|
| http://kihrepository-test.npi.nsi.dsdn.dk:8020/axis2/services/xdsrepository | ||
UDD |
|
|
| http://kihrepository-udd.npi.nsi.dsdn.dk:8020/axis2/services/xdsrepositoryb |
Connections from eHealth Environments
The provided mapping is intended as a reference to help understand the alignment between different types of environments and their compatibility with respective NSP environments:
eHealth Environment | Environment Type | Appointment Repository
| KIH Repository (ITI-41)
| Document Sharing Service registry (ITI-18)
| Document Sharing Service repository (ITI-43)
| Metadata Update (ITI-57)
|
|---|---|---|---|---|---|---|
INTTEST | Internal test environment | NSP test2 Central NSP
|
| NSP test2 Central NSP
| NSP test2 Central NSP
| NSP test2 Central NSP
|
DEVENVCGI | Vendor development environment | NSP test2 Central NSP
|
| NSP test2 Central NSP
| NSP test2 Central NSP
| NSP test2 Central NSP
|
EXTTEST | External test environment | NSP test2 Central NSP
|
| NSP test2 Central NSP
| NSP test2 Central NSP
| NSP test2 Central NSP
|
TEST002 | Education environment | NSP test2 Central NSP
|
| NSP test2 Central NSP
| NSP test2 Central NSP
| NSP test2 Central NSP
|
PREPROD | Pre-production environment | NSP Prodtest Central NSP
|
| NSP Prodtest Central NSP
| NSP Prodtest Central NSP
| NSP Prodtest Central NSP
|
PROD | Production environment | NSP PROD Central NSP
| Not configured yet. | NSP PROD Central NSP
| NSP Prod Central NSP
| NSP Prodtest Central NSP
|
Note, the following differences:
INTTEST uses DROS for ITI-41 and ITI-57, but does not use DROS for ITI-18 and ITI-43.
PREPROD used KIH TEST2, and not KIH PRODTEST.
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. 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.
