Log out?

eiConsole for Healthcare – Differencing Engine (Demo)

This is a demonstration of the eiConsole for Healthcare Differencing Engine. The vast majority of healthcare information systems and devices support the HL7 data standards. However, the fact that two pieces of software implement HL7 does not imply plug and play interoperability. Even vendors offering support for the same HL7 messages will use different versions, which include divergent content and introduce custom extensions. The eiConsole for Healthcare’s Differencing Engine makes mapping between different HL7 messages easy.

icon_sample-dataORU-LabResults-V1
icon_sample-dataORU-LabResults-V2

Here, we see 2 examples of an ORU message – LabResults in HL7 V2.4. They’re very similar with many of the segments mapping from one to one. However, we can see that the second version here includes an ABC custom segment as well as an OBX segment as different from the first. Let’s see how this would be accommodated in the eiConsole for Healthcare.


differencing-engine-01-13-16-r2

differencing-engine-02-13-16-r2To generate a mapping between two versions of HL7, we’ll use the Data Mapper. Within this transformation tool, we’ll need to load our Source and Target samples. We’ll accomplish that with the HL7 V2.X format builder…


Where we’ll select the HL7 version of each and load the sample file. We’ll load the first version as our Source…


And we’ll load the second implementation as our Target.


By expanding the hierarchical view of the message, we can see that they look very similar but they are not the same.


Next, to invoke the Differencing Engine – we click this icon, which will generate a mapping between the Source and the Target.


With one click of the button, a map is automatically created. All common fields are automatically mapped to one another.


differencing-engine-08-13-16-r2

For instance, we can look at the MSH segment where each of the fields is mapped to the corresponding field from the MSH segment from the Source.


differencing-engine-09-13-16-r2

However, if we scroll down to the bottom of the mapping we see the ABC segment. This is present only in the Target and not in the Source. So, there are no blue nodes mapped into these green nodes.


differencing-engine-10-13-16-r2

Instead, we have constant text values taken from the Target sample. In order to tweak this mapping to be complete, the end user may choose to replace some of these constant values with other values from the source or an external data source. It’s just that easy. You load in a sample of the Source, a sample of the Target, invoke the Differencing Engine and a map   – which is 95% complete is created automatically, on the fly, in front of your eyes.

    to post comments

    This is a unique website which will require a more modern browser to work! Please upgrade today!

    Thanks!

    Our editors are notified.

    Close