/
Technical Space

Technical Space

The technical space containing descriptions of the architecture, APIs, security, testing, environments and more. This space is intended for anyone interested in the technical aspects, for instance architects, developers, operators, and testers.

  • Guidance to Telemedicine Solution Providers and Third Party Suppliers — The documentation serves as a guide for integrating with the eHealth Infrastructure, aimed at telemedicine solution providers and third-party suppliers.
  • Technical Descriptions — The page contains descriptions of the architecture, eHealth architecture, security, and APIs. This space is intended for anyone interested in the technical aspects, for instance, architects, developers, operators, and testers.
    • Architecture and Domains — This page provides an overview of the eHealth Infrastructure's architecture, highlighting its key technical components, service layers, and domain structure.
    • Security Mechanisms — This page outlines the security architecture of the eHealth Infrastructure, focusing on how authentication and authorisation are managed across different user domains. It explains the use of federated identity systems, JSON Web Tokens (JWT), and role- and attribute-based access control (RBAC and ABAC) to ensure secure access to healthcare data and services. The page also details how various login flows are handled through OpenID Connect and SAML protocols, tailored for citizens and clinicians.
    • Services and Endpoints
    • APIs and Events — This is a description of the overall eHealth Infrastructures Application Programming Interfaces (API) and business and technical events produced by the eHealth Infrastructure.
    • Interactions with eHealth Services
    • Modelling overview
    • Multitenancy — The eHealth infrastructure is a multitenancy solution allowing data sharing between Telemedicine solutions, but also mark data as belonging to a specific solution. This page describes the mechanism for Telemedicine Solutions to tag information and search for these tags to separate those owned by a single Telemedicine Solution.
  • Developing on the eHealth Platform — Audience: eHealth infrastructure architects and developers. 
    • Technical Requirements for Developing Telemedicine Solutions — This page describes the rules for developing telemedicine solutions to be deployed on or use of the infrastructure.
    • Designing Telemedicine solutions — Examples of different application types that can be built using the eHealth infrastructure.
    • Best Practices and Design Guidelines — Catalogue of design guides and best practices for developing Telemetric solutions using the eHealth infrastructure.
    • Development and deployment cycle — Description of the eHealth development and deployment cycle, including description of the use of eHealth environments and flow. 
    • Overview of Tools in eHealth infrastructure — This is an overview of tools in the eHealth infrastructure available for Infrastructure Development and Development of Telemedicine solutions.
    • Useful third-party tools in the eHealth Infrastructure — This page describes the third-party tools (e.g. Jeager, Docker Repository, Splunk) used e.g. log analysis and tracing.
    • Logging model — This page describes the logging model for developing eHealth services or Telemedicine solutions. The intended audience is architects and developers.
    • Call Tracing — The eHealth infrastructure enables the tracing of all actions across various services and components. This is implemented using Istio and OpenTracing with Jaeger. The Call Tracing applies to both Telemedicine Solutions (3rd party) and eHealth Services (Infrastructure Provider)
    • Docker Base Images — Docker Base Images are the images that all applications running on the Infrastructure must build.
    • Canary deployment
    • Application Metrics — Application and services can expose application metrics in Prometheus format and have the metrics collected by the infrastructure.
    • URLs to access eHealth services — This page describes the URLs application vendors shall use to access eHealth infrastructure services.
    • Helm Charts — A helm chart is needed for installing an application on the eHealth Platform in a docker container ( https://helm.sh/docs/developing_charts/ https://helm.sh/docs/developing_charts/ ).
    • Using secrets from Vault
  • Testing on the eHealth Infrastructure — Information relevant for testing on the eHealth infrastructure for example test users and test patients.
    • Environments — The eHealth system has separate environments for testing and production use. These environments help developers build, test, and launch eHealth solutions. Here's what each environment offers, who can use it, how to access it, and how it connects with other systems.
    • FHIR Implementation Guide Test Data Guide — This guide explains how to incorporate and manage test data in FHIR Implementation Guides, with a specific focus on FUT's Implementation Guide. The need for comprehensive test data is twofold: to exemplify profiling work and to accelerate development processes for both client and server implementations.
    • Testing the Security Federation — Provides help and information on tools to ease the inspection and testing the federated security and login flow.
  • Frequently Asked Questions — Provides questions and answers for developing Telemedicine Solutions for the eHealth Infrastructure.
  • Terms and Definitions — This page lists the terms and definitions used throughout the documentation.