Last updated: Dec 04, 2018 17:01
- Interest: You want to get informed about the eHDSI Governance model and the responsible bodies within eHDSI
- Information Owner: eHealth Network (eHN)
eHDSI Governance Body
|eHealth Network (eHN)||eHealth Policy Owner|
|eHealth Policy Secretariat||European Commission - DG SANTE (B3)|
|eHDSI Owner and Co-Owner||European 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)|
|eHDSI Solution Provider||European Commission - SANTE (A4), DIGIT (A3, B4)|
Main Legal References
- Interest: You want to know more about the Legal framework applicable to the eHDSI landscape
- Information Owner: eHDSI Owner
Cross-border Healthcare Directive
|Implementing Directive 2012/52/EU||Directive on the recognition of medical prescriptions issued in another Member State|
|Regulation 1316/2013||Regulation establishing the Connecting Europe Facility|
|CEF Telecom guidelines Regulation 283/2014||Regulation on guidelines for trans-European networks in the area of telecommunications infrastructure|
Regulation on Data Protection
|Regulation 45/2001||Regulation on Data Protection for Community institutions and bodies|
|Commission recommendation 2008/594/EC||Commission 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)
Describes the eHN generic guidelines, applicable for both the Patient Summary and ePrescription use cases (services)
|PS guidelines R2|
Describes the eHN guidelines for the Patient Summary use case (service)
Describes the eHN guidelines for the ePrescription/eDispensation use case (service)
|eHDSI Governance Model||Describes the Governance model for the eHealth Digital Service Infrastructure during the CEF funding|
|Guidelines on an Organisational Framework for eHealth NCP||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)|
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 Core/Central Services in detail
eHDSI Website - CEF eHealth 2.0
|2||Central Service Desk||eHDSI Operations Framework (latest version - 1.0.1. W2 Production ready)||eHDSI Solution Provider (Operations Manager)|
|3||Collaboration Service||Collaboration Services||eHDSI Solution Provider (Operations Manager)|
|4||Requirements Service||eHDSI Requirements Catalogue - Business and Solution (Functional and Non-functional) Requirements||eHDSI Solution Provider (eHDSI Business Analyst)|
|5||Specifications Service||eHDSI Solution Provider (eHDSI Architect)|
eHDSI Solution Provider (eHDSI Architect)
eHDSI Solution Provider (eHDSI Architect)
|8||Test Service||eHDSI Solution Provider (Operations Manager)|
|9||Audit Service||eHDSI Solution Provider (eHDSI Information Security and Quality Manager)|
|10||Monitoring Service||eHDSI Solution Provider (Operations Manager)|
|11||NCPeH Reference Implementation Service||eHDSI Technical / OpenNCP COmmunity||eHDSI 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.
A 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||Used as a bridge between National Infrastructure systems and the NCPeH Gateway. The Member States are fully responsible to implement this technical component.|
|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.
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:
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)|