Deliverables

Requirements

D6.1 – Software requirements and architecture specification of a S-EHR – V1

Fundamental technical result of InteropEHRate will be composed of two aspects. The first one will be a set of open specifications, implementable by any vendor or institution. The second technical result will be a reference implementation composed of reusable software components, which will implement the specifications and will be interoperable with any other implementation of the same specifications. This document focuses on the requirements and the reference implementation of one of the components; the Smart-EHR mobile app (S-EHR-A).

D2.1 – User Requirements for cross-border HR integration – V1

This report describes final users’ requirements of InteropEHRate platform, including the initial definition of clinical content for S-EHR, the description of three different reference scenarios where S-EHR is applied and the methodology applied to refine final users’ requirements according to the three different final user categories: patients and family caregivers, healthcare professionals, and clinical researchers. Refinements and evolution on the clinical definition of S-EHR content and reference scenarios descriptions will be reported in the forthcoming version of this deliverable.

D5.1 – Software requirements specification of an integrated EHR web app for HCP – V1

This deliverable assumes the elaboration of preliminary software requirements and the design of the integrated web app – Healthcare Professional Application (HCP app) used by healthcare professionals for creating and accessing health data of foreign patients, based on user requirements specified in Work Package 2 – Architecture for cross-border HR integration and continuous collaboration with the final users. Healthcare Professional Application will exploit the Device to Device and remote protocols defined in Work Package 4 HR Interoperability Protocols for implementing the following functionalities: (i) import/export data directly from/to the Smart-Electronic Health Record (S-EHR) mobile application on the smartphone, (ii) import/export data from/to S-EHR cloud and (iii) access integrated health records imported from Electronic Health Records (EHRs)/Electronic Medical Records (EMRs) of other healthcare providers.


EU interoperability protocols and open specifications 

D2.4 – InteropEHRate Architecture – V1

This report describes a novel architecture for citizen centred EHR interoperability and the structure of its reference implementation.
The InteropEHRate architecture specifies how different actors using applications offered by different vendors will be able to interoperate thanks to open (vendor indipendent) protocols and APIs.
This document also provides an introduction to the reference implementation, i.e. to the set of software components developed by the project to provide a concrete example of implementation of the open protocols and to support their usage.
A more detailed description of each specific protocol and software component will be described in referred forthcoming deliverables.

D3.3 – Specification of remote and D2D IDM mechanisms for HRs Interoperability – V1

This deliverable provides the first version of the specification of remote and D2D Identity Management (IDM) including authentication mechanisms in InteropEHRate. This document also provides a detailed technical background, which is a necessary step to move forward. The final and more detailed specification will be provided in the second forthcoming deliverable.

D3.7 – Specification of consent management and decentralized authorization mechanisms for HR Exchange – V1

This deliverable provides the first version of the specification of consent management and decentralized authorization mechanisms for health records in InteropEHRate. This document also provides a detailed technical background, which is a necessary step to move forward. The final and more detailed specification will be provided in the second forthcoming deliverable on March 2021.

InteropEHRate framework – Design

D2.4 – InteropEHRate Architecture – V1

This report describes a novel architecture for citizen-centred EHR interoperability and the structure of its reference implementation.
The InteropEHRate architecture specifies how different actors using applications offered by different vendors will be able to interoperate thanks to open (vendor-independent) protocols and APIs.
This document also provides an introduction to the reference implementation, i.e. to the set of software components developed by the project to provide a concrete example of implementation of the open protocols and to support their usage.
A more detailed description of each specific protocol and software component will be described in referred forthcoming deliverables.

D6.4 – Design of a S-EHR mobile app – V1

This deliverable is confidential (accessible only by the Consortium and EC). It is dedicated to the description of the architecture of the Andaman7 mobile application and the S-EHR protocol integration.

D4.1 – Specification of remote and D2D protocol and APIs for HR exchange – V1

This report describes the initial version of the open specification of the device-to-device (D2D) and the remote-to-device (R2D) protocols, defined (and to be experimented) in the context of the InteropEHRate project. These protocols will be used by software applications facilitating health data exchange between the citizens and the Healthcare professionals. The D2D protocol defines the technology, data structures and operations to be offered by the interacting applications, allowing the exchange of health data between the aforementioned stakeholders without the usage of the internet. On the other side, the R2D protocol defines the technology, operations and structure of data used for enabling the exchange of health data between an Electronic Health Record (EHR) system of a single organization, either a National EHR or to a S-EHR Cloud (a remote cloud system for the storage of  encrypted personal health data) and the citizen with the usage of the internet.

D3.9 – Design of libraries for HR security and privacy services – V1

This deliverable provides the first version of the design of security and privacy services, in particular, the components and the functional primitives regarding identity management and consent management. The content of this deliverable derived from the InteropEHRate deliverables D3.3 – Specification of remote and D2D IDM mechanisms for HRs Interoperability – V1 and D3.7 – Specification of consent management and decentralized authorization mechanisms for HR Exchange – V1 and depict the major features and principles of designing the security libraries addressing identity management, consent management and crypto primitives.

D5.4 – Design of an integrated EHR web app for HCP – V1

This deliverable presents the preliminary relevant aspects and findings concerning the design of the Healthcare Professional Application (HCP Web App) used by healthcare professionals for creating and accessing health data of foreign patients. The preponderance of its content is derived from the deliverable D5.1 – Software requirements specification of an integrated EHR web app for HCP – V1 and reflects, at this stage of project implementation, the most important initial design features addressing the import/export data directly from/to the S-EHR on the smartphone.

D5.7 – Design of the data integration platform – V1

This document describes the fundamental software components – together referred to as Data Integration Platform – that are responsible for the conversion and translation of Electronic Health Records across languages and across local and national healthcare standards.

D5.9 – Design data mapper and converter to FHIR – V1

This document describes the fundamental software components – together referred to as “data integration platform” – that are responsible for the conversion and translation of Electronic Health Records across languages and across local and national healthcare standards.


InteropEHRate framework – Software


Business analysis

Validation

Reports

D1.7 – Data Management Plan – V1

The goal of the InteropEHRate project is to provide secure cross-country interoperability of health records by means of a mobile and web-based Application (Device 2 Device and Web) without a central institution. In the course of the development of the various software applications and the corresponding administrative processes including the management of the project, data is produced and collected. This deliverable describes the FAIR management of these research data sets.

D9.1 – Dissemination Strategy and Action Plan

This deliverable provides the Dissemination Strategy and Action Plan developed for the purpose of the InteropEHRate project in order to raise awareness about the project’s ambitions, progress, and end-results. It describes the Dissemination Strategy and strategic objectives of communication and dissemination, the Dissemination Action Plan and expected achievements.
Project Branding is included in section 3.1 identifying the values of the project and its application to visual identity.

D2.10 – Development and Testing environment

The present document describes the integration activities that will be performed for the integration of the various software components of the InteropEHRate project. The document describes the integration roadmap that is followed, along with the development tools used. In addition, a summary of the integration activities that took place during the first year of the project is depicted.


Publications

Presentations (Event)

InteropEHRate project overview presentation

The InteropEHRate project is funded by the European Union for 42 months and is implemented by a unique consortium of experienced institutions and qualified experts. InteropEHRate partners represent healthcare solution providers, hospitals, universities and research centres, as well as European and local stakeholder associations.
Our key goal is to complement and integrate the current interoperability infrastructures with new technologies for health data exchange centered on the person, based on a bottom-up approach that does not require the coordination by a superior authority and that leaves more control of health data to the people.
The slideshow here linked gives an overview of the project’s aim, vision, and technical approach and is designed for the general public

InteropEHRate presentation at the HL7 Hellas meeting

On 25th September 2019, the project InteropEHRate was presented by Theodora Zacharia, scientific advisor of the Athens Doctors Association, partner of the InteropEHRate Consortium, at the HL7 Hellas meeting held in Athens, Greece. Technical and semantic interoperability aspects of InteropEHRate’s technical approach were described and discussed, against the backdrop of the three user case scenarios: device-to-device temporary sharing, emergency, and research access. Technical components include the Smart Electronic Health Record (S-EHR) mobile app and cloud, the healthcare providers web app, and the InteropEHRate Health and Research services.
This presentation – available at the link above – is published for the time being, only in the original language (greek).


Other publications

Towards an incremental approach to let citizens master the access to and the use of their health data via Interoperable EHRs

EHTEL members welcome the recent initiative of the European Commission towards a ‘Recommendation to establish a Format for a European Electronic Health Record (EHR) Exchange’. It aims to facilitate cross-border interoperability and secure access to electronic health records for seamless exchange and use of health data in the EU.

InteropEHRate project flyer – 1st version

InteropEHRate project flyer is a printable document designed to raise public awareness about the project goals, technical approach, and expected results. It conveys the key messages of InteropEHRate to a wide range of audiences encompassing from the health and technology sector to policy-makers and the general public. Although the main audience will be participants of technical and health sector related conferences, addressing multiple audiences requires an additional effort to express in lay language the various technical aspects of the project.