Page Comparison

The documentation on this page is currently in an unreviewed state.

Access to data in the the eHealth Infrastructure is governed by its provided Authorization Server (AS). The AS is responsible for handing out tokens that are properly signed with the correct level of detail embedded. Without a token, no access is provided. The eHealth Infrastructure is by intend and design not part of any other existing infrastructure such as the NSP - instead, it integrates to a range of services (among these is services on the NSP).

The eHealth Infrastructure does not provide an IdP meaning that no users by design exist in the infrastructure. Instead, the AS is federated with two services that provide the identity of the users:

- NemLogin
- SEB

NemLogin

NemLogin uses NemID in order to provide the services needed as an IdP endpoint. The NemLogin service is intended to be used by citizens in order to gain access to data in the eHealth Infrastructure.

SEB

SEB is a common platform for user administration of the solutions provided by the National Board of Health Data on both the Internet and the closed Sundhedsdatanettet. SEB is based on a platform that takes into account OIO standards in this area. SEB provides a federation with the regional instances and municipality instances (how this federation is constructed is beyond the scope of the eHealth Infrastructure).

In the relation to the eHealth Infrastructure, SEB primarily serves two purposes:
- Provide a homogenous interface from its federated IdP's towards the eHealth Infrastructure
- Doing the actual federation between the regional instances and the municipality instances

Image Removed

eHealth Infrastructure federation (simplified)

Login flow

The AS supports login using OpenID Connect "code flow" while NemLogin and SEB supports OIO SAML. The AS bridges these security flows by sending back a redirection if no token is provided when interacting with the eHealth Infrastructure (NemLogin and SEB each have their own security realm in the AS meaning that the redirection logic is unambiguously). The sequence of redirects (and SAML AuthRequests/Responses) that takes place between the app and its federated endpoint, before the AS is finally invoked with a SAML AuthResponse, is not of concern to the eHealth Infrastructure (but in the case of SEB, it probably involves redirects from SEB back to the users own IdP and back again). See Login for details.

While NemLogin provides details on the identity of the citizen such as name and civil registration number (the authentication part), SEB also provides details on the user in regards to what roles that apply (both authentication and authorization). It is beyond the scope of the eHealth Infrastructure how and when these roles are applied in the federated setup. It is expected that the authorization part is governed by the IdP itself).

As no roles are issued from NemLogin, it means that citizens by default can only read data marked as theirs/involving them, with a few exceptions. Users (clinical users) however are provided with roles (from SEB or the IdP) scoped within an organization or a careteam (a careteam, in short, is a set of clinical users that provides services to a citizen. Users in careteams are not restricted to origin from the same region/municipality). Users can be in multiple careteams at the same time.

In order to provide a stateless and scalable setup while at the same time comply with the requirements of the eHealth Infrastructure the following security mechanisms come into play:

Detailed parts of the security documentation can be found at the following pages: