/
Readers Guide per audience

Readers Guide per audience

Owned by John Schneider
Last updated: 26-05-2025

This is a suggestion on how the site can be structured. This needs to be aligned with FUT-S.

What is eHealth Infrastructure (likely only read once)

  • What is the ehealth infrastructure

  • Concepts - services, FHIR, SSL, telemedicine solution, KAM

  • Archictecture

  • Integrations - how is the integration connected to what NSP, SEB and KOMBIT Environments

 

Capabilities (what infrastructure can do / business services provided / to be known by all )

  • Security Model - eHealth federated authentication

  • CareTeam / responsibility model

  • Automatic import of organisations from SOR and FK Organisation

  • Integration of CPR

  • Reminders for appointments

  • Reminders for activities

  • Video calls

  • NAS integrations

  • Document sharing to KIH

  • Controls performed by Infrastructure - missing measurement,

  • Automated processing of submitted measurements

  • Automatic registration in minlog 2

  • …

 

Getting started - the first things developers must do (hello world) - this can be extended with code examples and more “running code” if either CCR0249 or CCR0277 is ordered

  • Get access by service request til FUT-S

  • Test access - Get a test user and log in to KAM

  • Local call to Infrastructure services

    • Get client ID

    • Enable login in application

    • Calling first services.

  • Deply and run on eHealth Infrastructure

    • Set up and test the deployment pipeline

    • Kubernetes stuff - helm chart, probes, docker images

    • GitLab

    • Deploy your first application

    • Test the first deployment

 

 

Guides

  • For developers - more advanced stuff

    • Designing eHealth applications

    • Establishing the login flow

    • Establishing a service to be deployed to the eHealth Infrastructure

    • Establishing the observability of a service

    • Interacting with eHealth FHIR services

    • (Interacting with eHealth SSL services)

    • ….

  • Guides for testers

    • Envinroments

    • test users

    • ….

  • Guides for administrators

    • Managing eHealth roles in the KOMBIT FK administration module

    • Pages relevant for people managing terminology in the eHealth Infrastructure

 

References - things you refer to again and again

  • RBAC - List of roles and permissions

  • ABAC - Access control

  • Rererence APIs - event and rest:

    • Implementation Guide

    • (SSL API )

    • Key Value store

    • KAM API

    • Events

    • …

    …

 

Getting help

  • Reference on support is through FUT-S support

  • Things to include in support requests

  • etc.