Open resources for Developers

This resource section compiles the open-source executables, components and libraries of the different specifications developed by the InteropEHRate project. They are made available to the open-source community of developers via GitLab and Drive.

InteropEHRate implementation guides

InteropEHRate open-source executables

Smart Electronic Health Record (S-EHR) Mobile app

Healthcare provider (HCP) app

InteropEHRate components and libraries

Reference Implementation of Services and Applications:

InteropEHRate Health Services (IHS): The IHS component aims to be a single access point for all the InteropEHRate translation, conversion, and information extraction services. It is implemented as an API layer supporting the different requests received by the InteropEHRate HCP Application and by the R2D library, for automatic translation, extraction, and conversion of health data. For more details regarding conversion, translation and information extraction features, the reader can refer to the relative GitLab projects.

Translation Service: The InteropEHRate Translation Service is included within the IHS project. It is responsible for the automatic translation of health data initially provided as input, represented using local natural languages (such as Italian or French), and then converted in output into English, as the main international language, or into another local language if it is required (for example for data to be displayed within a hospital in a different country).

Conversion Service: The InteropEHRate Conversion Service is included within the IHS project. It is responsible for the automatic conversion of health data initially provided as input, represented using local data standards (such as CDA or SUMEHR), and then converted in output into FHIR international data standards.

FHIR Export: This component is integrated within the IHS and it is responsible for the creation of FHIR resources depending on different kind of query allowed. The FHIR Export service can produce FHIR Bundles both homogeneous (including a list of resources having the same type) and heterogenous (including a set of resources of different types, representing for example a Patient Summary record).

Pseudo-Identity generator: A service for the creation of pseudo-identities that will be used for the pseudonymization of health data to be sent to the Reference Research Centre for research purposes.

IRS Server Research Data Sharing: A node of the Research Network (a server) that stores published research studies and provides a central access point to S-EHR Apps for retrieving the descriptions of research studies.

S-EHR Cloud: A reference implementation of the optional service that can be enabled by a citizen through the S-EHR Mobile App, whose purpose is to give the citizen the ability to safely store their health data in the Cloud.

HCP App: The example standalone HCP app provided by the InteropEHRate framework that may also be integrated with a legacy EHR.

Health Record Index: An EU-hosted service assisting HCPs in accessing the citizen’s health data stored in a S-EHR Cloud during emergency situations.

Server R2D Access HR Exchange: A reference implementation library of the R2D Access protocol used to receive and serve S-EHR requests from the Internet.

S-EHR Application libraries:

Mobile Health Record Index library: The library that communicates with the Health Record Index from the S-EHR App in order to insert or update the S-EHR Cloud information of a citizen.

Mobile R2D Backup: The reference implementation library of the R2D Backup protocol that allows citizens to communicate with a S-EHR Cloud provider and back up their health data.

Anonymization and Aggregation Library: The privacy library on the S-EHR App side used for the anonymization / pseudonymization of health data prior to its upload on a Reference Research Centre.

Mobile D2D HR Exchange: The reference implementation library of D2D protocol for the exchange of health data on Bluetooth on the S-EHR app side.

Mobile D2D Security Management: A reference implementation of the security management that is necessary for the secure exchange of health data over the D2D protocol.

Mobile R2D Security Management: A reference implementation of the security management that is necessary for the secure exchange of health data over the R2D Access and R2D Emergency protocols.

Mobile R2D HR Management: A reference implementation of the R2D Access protocol for the exchange of health data on the Internet.

HCP app libraries:

Terminal Health Record Index library: The library that allows the communication between the Health Record Index service and an HCP app in order to obtain the S-EHR Cloud information of a citizen in need during an emergency situation.

Terminal R2D Emergency library: A reference implementation library of the R2D Emergency protocol that allows authorized HCPs to communicate with a S-EHR Cloud provider and gain access to the health data of
a citizen during an emergency situation.

Terminal D2D HR Exchange: A reference implementation library of D2D protocol for the exchange of health data on Bluetooth on the HCP app side.

Terminal D2D Security Management: A library that implements the security requirements that are necessary in order to ensure the secure exchange of health data over the D2D protocol.

R2D Access server libraries:

R2D Server Security Management: The Security Management Library of the R2D Server implements the main security functionalities required by the R2D Access, R2D Backup and R2D Emergency protocols.