Improve patient care and teamwork by making your data compatible across all your applications by working with the European leader in interoperability. Automate and optimise the flow of information within your IT system and make life easier for your staff. Create a single interoperability platform to help supervise and pool every flow of information within your organisation and/or group. Enhance your IT systems by relying on an interoperability solution that is efficient, scalable, sustainable and which specialises in healthcare.
Use a graphical interface to create a workflow between several applications quickly and easily without having to write a single line of code. Become more self-sufficient by creating your own interfaces based on healthcare standards.
Monitor every flow of data in real-time with a graphical interface. Anticipate malfunctions and corrective actions with alerts to possible risks. React quickly to any anomalies by visualising the information processing steps and potential error messages. Do not lose any data if something goes wrong – get your settings back in one click.
Simplify integrating applications within your organisation with our library of connectors. Integrate your applications into a diverse environment without having to worry about technical aspects.
Any question? A project?
Our experts are here for you
Enovacom’s interoperability platform is the heart of your information system. It improves the supervision and management of your data flows, while sending your data from your applications to your information system.
The operating principle of the Enovacom Integration Engine (EIE) is based on three components:
• Entry services: Modules in permanent listening or in regular polling, which makes it possible to import application data into the EIE.
• The scenarios that represent the heart of EIE processing. One scenario allows for a series of different actions. Some actions can be instructions (switch, while, etc.) that allow you to control the execution of a scenario. Each action in a scenario allows a specific task to be performed, such as translation actions, communication protocols, or control instructions.
• Output services that allow data to be exported from EIE to applications.
The EIE makes it possible to interface with the various applications of the information system, as well as with external instances, through a wide range of exchange protocols. This is referred to as an input service for retrieving files from the EIE, and an egress service for their storage.
Some services operate with regular polling. They use the following protocols:
– Directory monitoring
– Pop3 client
– IMAP client
– FTP or SFTP client
– PeSIT client)
Other services are constantly listening on the TCP/IP port. Here are the corresponding protocols:
– MLLP servers
– PeSIT server.
Lastly, the EIE offers complete management of Web Services.
Similar to input protocols, EIE has a wide choice of output protocols:
– Copy in: a directory receives messages to be sent from the Write deferred file activity.
– MLLP Client receives messages to be sent from the Deferred MLLP Client activity.
– FTP Client Put receives messages to be sent from the Deferred FTP Client activity.
– SFTP Put receives messages to be sent from the Deferred SFTP Client activity.
– PESIT client and server receive the messages to be sent or made available..
– SMTP/SMIME client receives messages to be sent from the deferred mail sending activity.
– AS2 client receives messages to be sent from the deferred AS2 client activity.
The EIE can also consult and populate an external database.
The EIE’s library includes all the exchange norms and standards in the healthcare world: HL7, IHE , FHIR, HPRIM, HPRIM Santé, PN13, LDAP connector, etc.
In the event that the output or input files of an application do not correspond to these standards (e.g. flat file), specific translation services could be integrated to allow the implementation of this flow.
To guarantee excellence in the implementation of health standards, Enovacom’s team regularly participate in Connectathons to compare the theoretical consequences of the implementation of new standards, or the evolution of existing standards, to the reality.
The EIE implements the transactions required by the IHE Technical Framework.
Library of formats taken into account in the EIE:
• HL7-HPRIM format
• Any format
• XML format
• Mime format
• Fixed length format
• CSV format
• PSL Afnor format
• HPRIM médecin format
• HPRIM santé v2.x format
• PN13 format (pharmacy exchange standards)
• CDA R2 format
• DICOM worklist
Enovacom and DICOM
The EIE natively manages the DICOM (Digital Imaging and Communications in Medicine) format. It allows processing of MWL (Modality Worklist) and MPPS (Modality Performed Procedure Step) requests. The EIE behaves as a server interrogated by the different modalities (X-ray machines, scanners, MRI, ultrasound machines, etc.) and sends back information on the patients in its database.
One scenario allows for a series of different actions. Some actions are processing activities (transformation, sending mail, etc.) and others are instructions (switch, while, etc.), which allow you to control the execution of a scenario.
The construction of a scenario is done graphically from the administration screen of the Enterprise Application Interface. The scenario is stored in a file described in BPML (Business Process Modelling Language) syntax.
The execution of a scenario is triggered by receiving a message from an input service, or from another scenario.
At the start of its execution, the scenario retrieves all the information from the input message and assigns the corresponding variables. It also memorizes the start date of treatment.
At the end of execution, the scenario either performs an update of the database, if it was called asynchronously, or returns the response to the caller if it was called synchronously.
In a scenario, all the main processing activities run in sequence, from the start activity to the last activity. The main processing is represented by the activity column located furthest to the left of the editing area.
Processing is interrupted if one of the activities generates an error. Errors can be handled by certain instructions, so that you can continue processing if necessary.
Some instructions allow you to define activity sets represented outside of the main processing, which will be executed under certain conditions, or a certain number of times depending on the instruction concerned. These instructions are Switch, ForEach, While, Until, and Sequence.
Return to normal in the event of unavailability of an IS application
The EIE is able to supervise the activities related to an application. That is, if an IS application is stopped, the EIE can detect it and notify the administrator with alerts.
When this application is put back into service, messages that have not been sent are automatically sent to this application in the order they arrived in the queue.
If no standard exists
If no standard exists, the EIE is able to transform the structured data of files by generating a style sheet or scripts based on detailed specifications.
Thus, the EIE can interpret a structured data file whose format does not correspond to a standard or a norm and transform it into another given format.
Style sheets can be created manually or using a graphical tool available from the GUI.
Mapping files are translation documents produced by our graphical mapper. This interface is used to list, add, download, or delete the mappings stored on the EIE.
With the EIE, the integration engine goes beyond being a black box at the centre of HIS applications. The solution makes it possible to proactively carry out the following operating actions:
Supervision of the solution: control of data spaces, growth rate, process, etc.
Whether for supervision, notifications or dashboards, the EIE can define the supervision environments specific to each type of user. The solution’s web-based approach makes it possible to give everyone, wherever they are, the necessary information for technical or business uses.
Monitoring and management of alerts can be configured simply and efficiently, engendering a proactive, rather than curative, approach.
The graphical and real-time interface allows active supervision of all the flows deployed. The operators or the users – depending on their respective rights – can intervene on the supervision interfaces to view the processing steps. Also, they can view the messages concerned and possibly request the reprocessing of one phase or another part of the processing.
The platform administrators can then delegate the business supervision of the interfaces directly to the administrative services or the care units concerned.
The EIE allows you to use its communication logic to process notifications or alert messages, so that sending Mail or SMS can be implemented simply.
The key points:
• Proactive supervision
• Access to supervision anywhere
• Distributed notifications
• Interactive interfaces
• Fast incident resolution through direct and concise access to information
Applications deliver a retun for institutional directors, and they sustain their IS investments.
CIOs have a unique, global supervision tool. They can integrate all types of applications into their IS and create specific business workflows.
The nursing staff avoid having to re-enter information. They can synchronize and access all information from all applications.
Our interoperability platform allows you to share flows with external partners, so that you can meet information exchange requirements. Administrative and financial flowsMedical flows with […]See more