Page tree
Skip to end of metadata
Go to start of metadata

Goal of the current page

Offer an overview of the eHDSI documentation reference that could be used in the eHealth Digital Service Infrastructure (eHDSI) induction process for new comers, in order to ensure the easy access and understanding of the eHDSI landscape.

  • For each section, the eHDSI Responsible is defined; this is the eHDSI body who can give detailed information about each specific topic.

If you want to know more about eHDSI, check the following:

eHDSI Overview

  • Interest: You want to get a quick overview of eHDSI mission, objectives and activities
  • Information Owner: eHDSI Solution Provider

Last updated: Aug 11, 2021 14:52

Table of Contents

If you need assistance, contact eHDSI Support Team: @ Central Service Desk

Member States Go-live Timeline

eHDSI Governance

  • Interest: You want to get informed about the eHDSI Governance model and the responsible bodies within eHDSI
  • Information Owner: eHealth Network (eHN)

view eHDSI Governance Model (Wiki page)

eHDSI Governance Body

eHDSI Responsible
eHealth Network (eHN)eHealth Policy Owner
eHealth Policy SecretariatEuropean Commission - DG SANTE (B3)
eHDSI Owner and Co-OwnerEuropean Commission - DG SANTE (Directorate B), CNECT (Directorate H)
Operational Management Board (eHOMB)

European Commission - DG SANTE (B3, A4), CNECT (H3), DIGIT

Chair and co-chairs of eHMSEG

Member States Expert Group (eHMSEG)

Managers responsible for implementing the eHealth National Contact Point, nominated by the participating Member States (MS)

Rules of Procedure of eHMSEG

eHDSI Solution ProviderEuropean Commission - SANTE (A4), DIGIT (A3, B4)
eHDSI Communities

Main Legal References

  • Interest: You want to know more about the Legal framework applicable to the eHDSI landscape
  • Information Owner: eHDSI Owner

Document Name

(and link)


Directive 2011/24/UE

Cross-border Healthcare Directive

Implementing Directive 2012/52/EUDirective on the recognition of medical prescriptions issued in another Member State
Regulation 1316/2013Regulation establishing the Connecting Europe Facility
CEF Telecom guidelines Regulation 283/2014Regulation on guidelines for trans-European networks in the area of telecommunications infrastructure
Regulation 2016/679

Regulation on Data Protection

Regulation 1725/2018Regulation on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data
Commission recommendation 2008/594/ECCommission Recommendation on cross-border interoperability of electronic health records

eHealth Network (eHN) References

  • Interest: You want to know which are the main documents issued by eHN and applicable to eHDSI
  • Information Owner: eHN

Document Name (and link)


General guidelines

Describes the eHN generic guidelines, applicable for both the Patient Summary and ePrescription use cases (services)

Patient Summary Guideline (release 3) V06 (

PS guidelines R2 (deprecated)

Describes the eHN guidelines for the Patient Summary use case (service)

eP guidelines R2

Describes the eHN guidelines for the ePrescription/eDispensation use case (service)

eHDSI Governance ModelDescribes the Governance model for the eHealth Digital Service Infrastructure during the CEF funding

Describes an Organisational Framework guideline to support the governance, establishment and operation of National Contact Point for eHealth (NCPeH) towards the provision of Cross-Border eHealth Information Services (CBeHIS).

The Guidelines were updated in 2020.

Refined eHealth European Interoperability Framework

Presents a common refined framework for managing interoperability and standardization challenges in the eHealth domain in Europe

Official national declaration that NCPeH is ready to join the Cross-border eHealth Information Services providing the specific services, with indicating the anticipated date of the actual go live.
Agreement sets overarching legal principles and requirements.

The eHDSI Work Plan describes the key actions the Commission (DSI Owner and DSI Solution Provider) will do as regards the core service implementation and support to the National Contact Points for eHealth.

eHDSI Core Service Offering, Delivery and Deployment Plan

  • Interest: You want to get informed about the core/central services that eHDSI is offering and the deployment plans (per country and per use case/service)
  • Information Owner: eHDSI Solution Provider (Operations Manager)

eHDSI Change Management

  • Interest: You want a quick overview about eHDSI Change Management procedure and the change proposals (CP) registered for eHDSI
  • Information Owner: eHDSI Solution Provider (Change Manager)

eHDSI Core/Central Services in detail


Service Name

Main Artefacts

eHDSI Responsible

1Communication Service

eHDSI Website - CEF eHealth 2.0

eHDSI Owner
2Central Service DeskeHDSI Operations Framework (latest version - 1.0.1. W2 Production ready)eHDSI Solution Provider (Operations Manager)
3Collaboration ServiceCollaboration ServiceseHDSI Solution Provider (Operations Manager)
4Requirements ServiceeHDSI Requirements Catalogue - Business and Solution (Functional and Non-functional) RequirementseHDSI Solution Provider (eHDSI Business Analyst)
5Specifications ServiceeHDSI Solution Provider (eHDSI Architect)
6Configuration Service

eHDSI Solution Provider (eHDSI Architect)

7Terminology Service

eHDSI Solution Provider (eHDSI Architect)

8Test Service
  • Test Framework
  • Test Sessions Roadmap - eHDSI main test events:
    • TESTA & Central Services Connectivity
    • Preparatory Pre-Production-Testing (Prep-PPT)
    • Formal Pre-Production-Testing (Formal PPT)
    • Production Environment (Prod.Env.)
eHDSI Solution Provider (Operations Manager)
9Compliance Check Service (former Audit Service)

eHDSI Compliance Check types and events:

  • Initial Compliance Check (Purpose: Full Readiness Assessment)
  • Follow-up Compliance Check (Purpose: Action Plan Fulfillment Assessment )
  • Operational Compliance Check

eHDSI Owner (SANTE Unit B3)

10Monitoring Service

Monitoring Framework

eHDSI Solution Provider (Operations Manager)
11NCPeH Reference Implementation ServiceeHDSI Technical / OpenNCP COmmunityeHDSI Solution Provider (eHDSI Architect)

eHDSI Systems and Data Flow

Section on the diagram


The eHDSI starts with the Heath Care Professional of Country of Treatment (Country B, where the unplanned health care event occurred) asking for relevant health data of the patient, from patient's Country of Affiliation (Country A).

From technical point of view, the request goes from the NCPeH Gateway of Country B to the NCPeH Gateway of Country A. The requested information is retrieved from Country A National Infrastructure, sent back and presented to the Health Care Professional in Country B. On the diagram, this flow is represented with blue arrows (the request for information flow) and red arrows (the retrieved information flow).

Existing National Infrastructure

Country A will retrieve patient's health data from the National Infrastructure systems and aggregate this data into the Patient Summary and ePrescription documents.

An ePrescription means a medicinal prescription issued and transmitted electronically.

Patient Summary is an identifiable data set of essential and understandable health information needed to assure Health Care Coordination and the continuity of care.

The Member States are fully responsible to obtain and aggregate this data, as it is contained within their national systems. Also, the Member States are fully responsible to obtain the agreement of the patient for transferring and processing his/her personal data.

National Connector-AUsed as a bridge between National Infrastructure systems of Country A and the NCPeH Gateway. The Member States are fully responsible to implement this technical component.
National Connector-BUsed as a bridge between National Infrastructure systems (portal) of Country B and the NCPeH Gateway.
NCPeH Gateway – National Contact Point eHealth (National Infrastructure)

Using the Local Terminology Repository from the National Infrastructure, the Patient Summary and ePrescription are translated in English and transcoded (the health data is transformed from the national code system to the commonly agreed code system).

The Member States are fully responsible for exchanging and processing (translate and transcode) the Patient Summary and ePrescription documents. Therefore, the implementation, operation and maintenance of the NCPeH Gateway are under their responsibility and connect to their National Infrastructure.

eHDSI Solution Provider develops a reference implementation of the NCPeH Gateway. This is an open source implementation to be further used by the Member States.

Private Network provided by European Commission

The Network part is comprised by the TESTAng (TESTA new generation) private network and the TAP (TESTA Access Points) connectors. The TESTAng solution is established under the responsibility of DIGIT. The TESTA Access Points are installed in Member States premises and are managed under their responsibility. The Member States use TESTAng for two purposes:

  • To retrieve from the eHDSI Central Service (point 1f. below) the necessary configuration files for the proper operations of the NCPeH Gateway and Terminology services.
  • As a channel to transfer the ePrescription and Patient Summary in a secure way between the Member States.

This part of the network ensures encrypted secure transmission of ePrescription and the Patient Summaries. The TESTAng is only a technical mean for transmission and the data are not processed or stored.

eHDSI Central Services: Configuration Server and Central Terminology Server (CTS)
  • Configuration Server (CS): eHDSI Solution Provider (DG SANTE, Unit A4) is responsible for the deployment and maintenance of the Core Service (software development is performed by DG DIGIT). The CS is used by each NCPeH gateway to publish and store technical details, configuration information including the Domain Name System (DNS), Certificates, end points, International Patient Search Mask etc.
  • Central Terminology Server (CTS): eHDSI Solution Provider (DG SANTE, Unit A4) is responsible for the development, deployment and maintenance of this Core Service. The CTS is used to store code systems and the Member States translations/mappings of the medical terms.

eHDSI Systems and Data Flows

  • No labels


  1. Ioannis ASPROLOUPOS thank you for the like. 

    • Any suggestion of improvement? 
  2. Licinio KUSTRA MANO maybe the national connector box should be displayed to the "Country B" column as well because Country B needs to store eDispensation data to the national DB (via the national connector).

    1. Dear Ioannis ASPROLOUPOS, your comment was considered and the diagram updated. Thank you for your remark.