Changing your Enterprise Application Integration (EAI) – Montpellier University Hospital

How the Montpellier University Hospital successfully made the switch

How was your experience with Enovacom?

We first met Enovacom 5 years ago to evaluate their interoperability platform to help us manage exchanging data with our partners, which includes the French blood organisation. We were then selected by MS Santé as a pilot site and we chose the ENOVACOM Secure Messaging solution. The goal was to be compatible with MS Santé but also to send emails securely without impacting or changing the existing email tool.

Why change your interoperability platform?

We had to replace our old EAI as it had become obsolete and was maintained by a worker who was retiring. Our goal was to have a newer, more modern interoperability platform that would help us meet our requirements: managing the rise in data exchange between different facilities and within our own establishment with specific adjustments for each recipient.

Moreover, our Pastel GAM software (Patient Administrative Management) from Mipih was installed with its own EAI, a second platform that needed managing. The idea is really to have one single interoperability solution to centralise all the data streams to make work easier to manage on a daily basis.

What we were looking for: to be able to create interfaces independently.

EAI

Can you give us 3 words to describe the Enovacom interoperability platform (previously Antares V2)?

Ergonomic

Simple

Extensive Possibilities

EAI

How was the project managed?

We received the solution on time and are were very satisfied and still are with the support Enovacom provided.

They advised us to set up naming protocols and gave us lots of tips and tricks.

Here are a few figures to summarise the project: 20 days after installation, training and support we were able to migrate and set up 60 interfaces independently in under 7 months.

What types of data were used in the project?

Many different types were used but the main categories were:

IMS (Information Management System) patient data, results and reports

Structure, product and supplier reference data

Economic and financial management data (expenses, revenue, stock management, accounting data)

Hospital invoicing information (procedures, sending patient ASPs, and private health insurance)

HR data (users, assignments, absences, variable payroll information)

Hospital Identity Form:

Name of structure: Montpellier University Hospital

Website: www.chu-montpellier.fr

Number of sites in the facility: 9

Total number of beds: 2274

Population of hospitals’ catchment area: 450,051 patients

What impact does setting up an interoperability platform have for you in a GHT environment today?

It is clear that when setting up a Local Hospital Group (GHT), having a reliable, simple, ergonomic and powerful interoperability platform should help us solve any data exchanging issues we may encounter..

Project Key Contact:

Name: Philippe POULAT

Job title and department: SIC Domain Manager – IT Systems Management

Project role: EAI project migration management

Project Figures

Number of people using the EAI software: between 3 and 5

Number of software programs applications interfaced: 40 applications with more to come

Number of messages exchanged within a few months: 1.5 million

Number of data streams: 127 just in the EAI

Average weekly number of patients managed: around 95,000 per week sent to over 5 partners

Information stream standards: HL7, ADT, IHE PAM, HPRIM, XML and many formats specific to the domains mentioned and therefore often proprietary

Register to our newsletter

Don't miss any news from Enovacom

You're now register !