1. Interop and health

Interoperability is defined as the ability of different or identical systems to communicate easily with each other. Two pieces of software are therefore interoperable, as long as they communicate with each other.

In health, a distinction is made betweenEAI (Enterprise Application Integration, in yellow) for flows within an institution andEDI (Electronic Data Interchange, in blue) for standardised flows going outside the institution.

Interop scheme

In EAI, the most common format is HL7 (Health Level 7 ). This format is based on the generation of specific files on the occasion of particular events in the life of the institution. Depending on the event, the structure and content of the file are adapted to transmit the maximum amount of useful information in an organised manner.


The HL7 is available in several versions:

  • Version 2.x (1987): "flat" file divided into segments and fields by separator characters defined in the file.
  • Version 3 <=> CDA (1997) : ajout d’une syntaxe XML. Les mêmes informations se retrouvent structurées et regroupées en balises.
  • Version 4 <=> FHIR (2014) : ajout d’une couche web/API pour faciliter l’intégration et l’utilisation des données.

HL7 therefore makes it possible to structure data exchange. In addition, organisations such as IHE(Integrating the Healthcare Enterprise) and Interop' Santé are drafting recommendations to standardise the interpretation of these data, in particular with profiles such as IHEPAM for identity management and extensions for national particularities.

2. Interop and exolis

The success of our solution is based on a strong integration with the existing HIS of the institutions. In this sense, we strive to respect interoperability standards and manage the main formats:

  • HL7 V2 (v2.3, v2.4, v2.5) :
    • ADT: patient identity, trusted person, stay, social security coverage
    • SIU: appointment, resources and appointment status
    • MDM: document transmission
    • ORU: transmission of documents
    • MFN: repository management
  • CDA
  • FHIR

Receiving most of the input information allows us to react automatically and thus avoid using human resources:

  • Automatic sending of an e-mail for account creation when an appointment is created in the HIS,
  • Automatic inclusion in a specific pathway according to the procedure code, the reason for stay, the doctor, the UF or the type of report in the files,
  • Shifting the scenario and questionnaire timeline if the intervention or appointment is shifted.

However, we supplement our offer with specific connections, via web-services or file import/export, if they are necessary. These connections can be the subject of additional developments on option. We can therefore communicate with all the solutions used within the establishments. We develop, in-house, ad hoc half-connectors allowing a connection with all tools.


We are now interconnected with more than 30 different applications: Patient File, Administrative Management, Diaries, Laboratory Management, Imaging Software, Oncology Software, but also caregiver communities.

Do not hesitate to contact us via interop@exolis.fr if you wish to have more details on the existing flows or to discuss a particular need.

3. Frequently asked questions

Integration with an institution's IS

Our tool is complementary to these software packages because it allows us to accompany the patient "outside the walls". As a result, we are interoperable with the software present in the establishment, which allows us to receive and transmit information to interface with the patients.

Yes, the exolis teams can set up as many inbound and outbound connectors as necessary. It is therefore possible to manage several appointment flows if the establishment has several diaries.

Flow management for a group of institutions

Within the framework of a grouping, we are able to connect our tool to the different local software in the establishments as well as to the SRI, in place if it is present.
Within the framework of pre-admission, here is an example of a possible workflow:


interop grouping

One of the functionalities of our tool is the ability to manage patients and pathways that are shared between several institutions. However, each group has its own particularities. I invite you to contact us at interop@exolis.fr to discuss this more specifically.


Connection by exolis

Half-connectors and interoperability do not usually generate additional costs on the desired modules. Everything is included in the licence at the start of the project.

We can receive standardised streams without any special features. It is therefore entirely possible to connect directly to the existing core via a Y connection in an EAI.