Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Internal test environment

INTTEST

test

test-nemlog-in.dk

External test

adgangsstyring.eksterntest-stoettesystemerne.dk

t-seb

http://t-seb.dkseb.dk

External test environment

EXTTEST

test

test-nemlog-in.dk

External test

adgangsstyring.eksterntest-stoettesystemerne.dk

t-seb

http://t-seb.dkseb.dk

Vendor environment

DEVENVCGI

test

test-nemlog-in.dk

External test

adgangsstyring.eksterntest-stoettesystemerne.dk

t-seb

http://t-seb.dkseb.dk

Education environment

TEST002

test

test-nemlog-in.dk

External test

adgangsstyring.eksterntest-stoettesystemerne.dk

t-seb

http://t-seb.dkseb.dk

Pre-production environment

PREPROD

test

test-nemlog-in.dk

External test

adgangsstyring.eksterntest-stoettesystemerne.dk

t-seb

http://t-seb.dkseb.dk

Production environment

PROD

prod

login.nemlog-in.dk

Prod

adgangsstyring.stoettesystemerne.dk

Prod

http://seb.dkseb.dk

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 Environment Type

eHealth Environment

KOMBIT Environment

fk organisation

Internal test environment

INTTEST

eksternal test

External test environment

EXTTEST

eksternal test

Vendor environment

DEVENVCGI

eksternal test

Education environment

TEST002

eksternal test

Pre-production environment

PREPROD

eksternal test

Production environment

PROD

prod

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 for use in conjunction with different NSP (National Service ) environments.

NSP and KIH Test Environments

NSP has several test environments. See also:

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

...

eHealth Environment Type

...

eHealth Environment

...

TEST1

INTTEST

DEVENVCGI

EXTTEST

TEST002

PREPROD

PROD

Internal test environment

INTTEST

Vendor development environment

External test environment

Education environment

Pre-production environment

EXTTEST

TEST2

Vendor development environment

DEVENVCGI

TEST1

Education environment

TEST002

TEST2

Pre-production environment

PREPROD

PRODTEST

Production environment

PROD

PROD

...

Production environment

Aftale DRS (ITI41)

Municipality
DROS
TEST1

Regional
DRS
TEST1

Regional
DRS
TEST2

Regional
DRS
TEST1

Regional
DRS
PRODTEST

Municipality
DRS
PROD

DDS Registry (ITI18)

Municipality
DDS
TEST1

Municipality
DDS
TEST1

Municipality
DDS
TEST2

Municipality
DDS
TEST1

Municipality
DDS
PRODTEST

Municipality
DDS
PROD

DDS Registry (ITI47)

Municipality
DROS
TEST1

Municipality
DDS
TEST1

Municipality
DDS
TEST2

Municipality
DDS
TEST1

Municipality
DDS
PRODTEST

Municipality
DDS
PROD

DDS Repository (ITI43)

Municipality
DDS
TEST1

Municipality
DDS
TEST1

Municipality
DDS
TEST2

Municipality
DDS
TEST1

Municipality
DDS
PRODTEST

Municipality
DDS
PROD

KIH Repository (ITI41)

KIH
TEST2

KIH
TEST2

KIH
TEST2

KIH
TEST2

KIH
TEST2

Not configured

Info

Note, the following differences:

  1. INTTEST uses DROS for ITI41 and ITI47, but not for ITI18 (warning).

  2. PREPROD used KIH TEST2, and not KIH PRODTEST. (warning)

  3. DEVENVCGI, EXTTEST, TEST002, PREPROD, uses Regional DRS, not Municipality DRS (warning)

  4. INTTEST, DEVENVCGI and TEST002 uses TEST1, and not TEST2 (warning)

Component and Data Lifecycle in Environments

...

  • 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.

...