eiConsole for Healthcare – Map From HL7 Message Template (Demo)
This is a demonstration of the eiConsole for Healthcare – Mapping from HL7 Message Template. Using the eiConsole for Healthcare, it’s easy to map from any HL7 message to any other data format. Let’s show you how.
Simply create a new route.
We’ll create a new Source Transformation. We’ll call this Map-From-HL7-Message.
First, we need to translate the HL7 message into XML using the HL7 2.X transformer.
We’ll select our desired HL7 version, 2.4.
And select the Use Friendly Names.
Here we need to load our Source and Target formats. Our Source Format will be loaded with the HL7 V2.X format reader.
Again, we’ll choose HL7 2.4 and to Use Friendly Names. We’ll also check the Use Sample File. We’ll load a sample Lab Results message, click Open, and Read Format.
The structure of our Source HL7 message will appear on the left-hand side of the screen.
Now, we’ll load in our desired Target format which will be a custom XML structure. We’ll use the XML format reader and select the CustomLabResults.xml sample file, and click Read Format.
Now, to map from one to the other, we’ll drag-and-drop the XCSData element onto the “stylesheet”, and select all of the elements from the Target and drag-and-drop them onto XCSData in the center:
The structure of our Target data will appear in the center panel.
Now, make sure the Enable or disable Apply Templates for Complex Types button is deactivated. To map values from the HL7 message, we’ll simply navigate to the appropriate segment, field or component, then drag & drop. We’ll map the Last Name, First Name, and Date of Birth for demonstration purposes.
If we need to do any further manipulation of the data, the pallet of structures above the mapping can be used to accommodate that. For instance, if we want to map the inbound date format onto an XML date format, we can use the Date/Time Formatter tool.
We drop it on the Date_Time_of_Birth field, enter in the HL7 date format and our desired output format and click OK.
We can continue in this fashion until all of the various fields are mapped. We then save our mapping.
And return to the eiConsole. We can now test the mapping in the eiConsole’s Testing Mode.
We configure the test and click on the Execute Test button.
Select the sample file, click Open.
And as each stage completes the question mark will turn into a checkmark.
Now we can view the results. Here was our input HL7 message.
This is the result of the transformation to XML.
And finally, the mapping onto the custom format where we see the three fields that we had mapped in the Mapper populated with the values from the HL7 feed.
So it’s just that easy. We use the HL7 Transformation Module to convert the HL7 message into XML, we perform a mapping using drag & drop in the Data Mapper, and then we test in the Test Mode. In minutes we’ve built a transformation from any HL7 message to another format.