What experience does CHIC Unisante have with software publisher Enovacom?
André Apack: When I arrived in 2014, I found that we had several different solutions to handle exchanging healthcare data: The Enovacom interoperability platform only managed the organisation’s external exchanges, while two other Enterprise Application Integration (EAI) solutions handled some of the internal data streams. I wanted to standardise this so that just one EAI would cover all the data streams. The aim was to simplify managing sensitive data exchanges & data streams between healthcare providers. Therefore, we issued a call for tender to make three publishers compete with one another over functionality, connectors and cost. I personally knew the Enovacom EAI and how well it worked which is why I let my collaborators assess the different offers.
And you chose the ENOVACOM Suite V2?
A.A.: That is right. This application had the best balance between technical quality and cost as it had everything we wanted. Ever since, it has managed all of these external data streams:
- To and from the CPAM (Primary Health Insurance Office) for B2 data;
- Treasury Department particularly for PESV2;
- The overall budget;
- RPU (accident and emergency patient summary);
- ARS (Regional Health Agency), etc.
We also use it as the interface for internal data streams: transporting laboratory results, patient identity and other functionalities which we will continue to work on over time.
The added value of this tool is that it lets us modify certain data streams before they become available further down the line. “The ENOVACOM Suite V2 interoperability platform manages the patient identity database used by all four establishments”.
Can you tell us more about the added value?
A.A.: One example is raw data from the laboratory that we filter to make it perfectly adapted to the application it is sent to. Another example is the identity streams of healthcare professionals in our organisation which are sent to the GCS (Health Cooperation Group) E-Health directory in Lorraine. This is where we assign software access rights based on workers profiles. Today, we use the ENOVACOM Suite V2 EAI for all four of CHIC facilities which allows us to manage the patient identity database and transfer patients to business applications in a standardised way.
It is important to highlight that all of the CHIC facilities’ application servers are very centralised.
“Setting up the EAI only took a few weeks”, André Apack.
How long did it take to set up the Enovacom Suite V2 EAI?
A.A: Setting up the main part of the project started in the summer of 2014 and only took a few weeks. The Enovacom engineers then came on site to transfer the previous data streams and train the IT management to use EAI how we needed i.e. creating our own data streams and running things how we wanted. They were extremely involved and their methodology was very well-structured so we did not have any surprises about the services or the time spent putting them into action from what they had outlined in their quote. Even after they left our offices, the Enovacom team was there with us throughout the whole process to help answer our questions and assist us if we encountered any problems while creating data streams.
How would you assess the project a year and a half on?
A.A: We have only good things to say. Our internal and external data exchanges are now much smoother as ENOVACOM Suite V2 allows us to monitor and alter the interfaces as and when we need to. We’re having no problem continuing to evolve the interfaces as part of the PES V2 project. We are satisfied with the solution and working with the teams.