Context and objectives
The initial context: diverse technical solutions where monitoring health data is not possible
To manage communications between the different applications used by laboratories and clients (doctors, hospitals, or external service providers), the UNILABS group had utilised several EAI-type software applications as well as several ‘custom’ scripts. The initial aim was to automate the sending of data flows i.e. analysis requests, reports and financial information.
The drawbacks of the “old environment”:
There is no way to supervise or monitor the data exchange
It is unsure how long the solutions will last as the interfaces have been created separately
There is no event feature and no HL7 connector available
Three solutions we had were unable to communicate with each other
Support is often needed due to the amount of errors
It is costly to maintain the platforms complex technical architecture
The integration tool used was therefore reconsidered as it was essential that we could effectively manage the data flow.
Project aim: to organise health-oriented data flows effectively
The aim of undertaking a new project was to enhance our capabilities in exchanging, sharing and monitoring information with the chosen and very unique – Enovacom interoperability platform. Key driver: ensuring patient information is shared effectively and helping healthcare professionals to make more informed decisions on a daily basis, improving patient-care.
3 different cities are involved in this new project with each city managing their own information flow – Zurich, Geneva and Ticino.
Providing and implementing the new interoperability platform should enable UNILABS Switzerland to achieve the following objectives:
Consolidation of interfaces into a single tool
Installing a new, industrial, ready-to-use ESB architecture
Improving interface supervision (monitoring and incident alerting)
Easy to use platform with the tools to resolve problems fast
Quick and easy to integrate new interfaces (a new interface means sending biological test results to a new recipient)
Unilabs Switzerland: now interoperability enabled
The first project meeting took place in August 2016. The aim was to set out the schedule, the teams involved and their relevant roles, and the project’s technical outline.
An 8 step project
The project to connect over 100 different software applications was divided up into several steps. Certain interfaces needed to be created first in order to make way for others.
Test phases varied in length depending on the interface with a general average of 1 month before being validated for production.
The project in numbers
100 software applications to connect
154 interfaces to create
1 unique interoperability platform to install