This is a demonstration of the eiConsole for Healthcare’s Map to HL7 Message Template feature. In the course of this demonstration, we’ll show you just how easy it is to use a sample HL7 message, for instance from an implementation guide, to create a new mapping from a custom format.
Here we are in the eiConsole’s main grid.
We’ll create a new transformation for this mapping. The first thing we need to do is build the map itself. We’ll do this in the Data Mapper.
Our Source format will be a custom XML file, so we’ll choose the XML format reader…
… and load our custom XML.
The Data Mapper will load the structure that we can then view.
Now, we’ll use our sample HL7 message using the HL7 V2.x format reader to create a template to map to.
We’ll choose the HL7 version, in this case, 2.4, elect to use Friendly Names, and check to use a sample file.
We’ll choose the sample HL7 message, click open, and Read Format.
A slice of the HL7 vocabulary corresponding to the sample message provided will appear in the Target format tree.
Now, we’ll want to create a mapping. To do this, under the Formats menu, we’ll choose to Add Target Sample Data As Template.
A number of green nodes corresponding to the segments, fields, and components used in the sample message will automatically appear in the mapping panel.
By default, these fields will contain the values from the sample file. However, we now want to map dynamic information from our Source data into some of these fields. For instance, let’s map the Patient Name. We’ll delete the hardcoded values….
…. and replace them using drag & drop with values from our Source XML.
We can also manipulate this data during the mapping. For instance, let’s map the date of birth. You’ll see that the message format expects yyyyMMdd with no punctuation.
However, in the Source, the format is MM-dd-yyyy. Again, delete the hardcoded value, drag and drop the value from the Source.
But this time we’ll use one of the functions from the pallet above to do the date manipulation. Choose the Date/Time Formatting tool…
…and drag it onto the field requiring the formatting.
Enter in the Source pattern, which is MM-dd-yyyy and the desired output, yyyyMMdd, and click OK.
As we do this, XSLT is being generated for our mapping.
We can then test in the Testing view of the Data Mapper.
Here we can see values from the Source mapped into our HL7 XML template. Similarly, we can see the date of birth with the formatting rules placed in the date and time of birth field.
Once we have completed our mapping to the template, we save it and return to the main eiConsole screen.
To convert our output to delimited HL7, we’ll choose the HL7 V2.X transformer.
Again select the expected version…
…and check the friendly name option.
Save your work and test in the eiConsole’s Testing Mode. To test this transformation we’ll start at the first stage and end after the mapping onto HL7 V2.X.
Choose the From File for the Source. Click the Execute Test button.
Choose your custom XML file and click Open.
Checkmarks will appear as each stage completes.
Here we can see our custom XML format with Sally Underweather born 09-19-1980.
Here we can see that data after being mapped onto the HL7 message template. Again, you can see Sally Underweather. This time her name in the PID Name component and the date of birth as well.
Finally, the HL7 Transformation Module converted that into a delimited HL7 Compliant format.
So, it’s just that easy. You can take a sample HL7 message from any implementation guide or vendor system, load it as a Target template, drag and drop your source data onto it, and you’re done. You’ve created a transformation to a custom defined HL7 message template.