Video Key Moments
Data Mapping to an HL7 Message Template in eiConsole
In this demo, you will see how to take a sample HL7 v2 message from an implementation guide or vendor spec, load it as a target template, and then map custom source data into that HL7 structure using PilotFish’s Data Mapper. The workflow is designed to reduce HL7 setup time, improve mapping accuracy and make transformations easier to test and maintain.
[Try the Free 90-day Trial] [Talk to an Expert]
30-second summary
- Build a new transformation by loading a custom XML source format and an HL7 v2 target template
- Map dynamic values into the template with drag & drop rules, plus formatters for common fixes like dates
- Validate your output in testing mode, including a clear before and after view of mapped data
- Convert the mapped HL7 XML template output into delimited HL7 for downstream systems
What You Will See in this Demo
Create a new source transformation
You start in eiConsole by adding a source and target, then launching the PilotFish Data Mapper to build the transformation.
Read Your Custom Source Format
The Source side uses a custom XML file. The XML format reader loads the structure so you can map from real fields, not guesswork.
Load an HL7 v2 sample as a Target Template
On the Target side, you load an HL7 2.x sample message, optionally using friendly names, so the target tree is easier to navigate during mapping. The mapper retrieves the relevant slice of the HL7 vocabulary based on the sample you provide.
Build Mappings Fast with Template-aware Nodes
When you add the Target sample data as a template, the data mapper automatically creates template nodes for the segments, fields and components present in the message. This gives you a clean starting point.
Map Real Values and Fix Formats During the Map
You map fields like patient name, then apply tools such as the date and time formatter to convert values like MM/DD/YYYY into YYYYMMDD to match HL7 expectations.
See the Generated XSLT and Test Inline
As you map, the engine generates XSLT for the transformation. You can test and review the mapped HL7 XML template output directly in the mapper testing view.
Convert Template Output into Delimited HL7 and Run an End-to-end Test
After saving the mapping, you return to eiConsole and run the HL7 2.x transformer to produce a standards-compliant delimited HL7 message. In testing mode, you execute a sample run and verify the pass status and output.
Why HL7 Message Templates Help Teams Ship Faster
- Start from a known-good message pulled from a guide or vendor example
- Reduce mapping omissions by using template nodes that reflect what the message actually contains
- Handle real-world inconsistencies with built-in formatters during transformation, not in post-processing
- Move from mapping to runnable HL7 output using the same eiConsole workflow and testing mode
Production Fit: From Mapping to Deployed Interfaces
The same transformation you build here can be used inside larger interface routes that combine Listeners, Transports and Processors. It can then be deployed for unattended execution with operational monitoring. PilotFish also works great in Docker containers.
Security, Observability, Compliance
- Support secure Transport patterns for HL7 and related healthcare integrations
- Operational visibility for message tracking, drilldowns and alerts when routes run unattended
- Clear separation between build, test and deploy to support governed change control
FAQ
Yes. This demo shows how to use a sample HL7 message as a target template, then map custom data into that template’s structure.
No. The mapping is built visually and the transformation logic is generated as XSLT behind the scenes. Toggle between XSLT and visual mapping.
Yes. After mapping to the HL7 template output, the HL7 2.x transformer converts it to delimited HL7.
Check out our FAQ pages for more.
Data Mapping to an HL7 Message in the eiConsole for Healthcare
This is a demonstration of the eiConsole for Healthcare mapping to HL7 message template feature. In the course of this demonstration, I will 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.
Create a New Source Transformation
Here we are in the eiConsole. We’ll add a source and add a target.
Next, 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 PilotFish Data Mapper. Our source format will be a custom XML file. We use the XML format reader to read that file in. Simply hit “read format”, that will pull in the structure of our custom XML file on the left-hand side.
We’ll use a sample HL7 file for our target side. First, we’ll select the HL7 2.x format reader – we’ll choose to use “friendly names” in a sample file. Choose “read format”. A slice of the HL7 vocabulary corresponding to the sample message provided will appear in the target format tree.
Create a Mapping
Now we’ll want to create a mapping. To do this under the format menu, I’ll choose to add my target sample data as a template. A number of green nodes corresponding to the segments fields and components used in the sample message will automatically appear in my mapping panel. By default, these fields would contain the values from my sample file. However, I now want to map dynamic information from my source data into some of these fields.
For instance, let’s map the patient name. I’ll simply drag & drop from my source side onto the mapping. I can also manipulate this data during the mapping. For instance, let’s map the date of birth. We’ll see that my message format expects a different date than I am expecting on the target side. I can use tools like the date/time formatter to manipulate the mapping. Simply drag & drop this formatter onto the mapping. A pop-up box will appear. In this situation, my source data date of birth is coming in as MM/DD/YYYY and I want to change that to YYYYMMDD. I’ll simply enter the input pattern here and on the output pattern I will define what I expect the day to change to. That will now manipulate that data in the way that I expect.
As I do this, XSLT is being generated for the mapping that I can test in the testing view of the data mapper. Here we can see values from my source mapped into my HL7 XML template. Similarly, we can see the date of birth with the formatting rules placed in the date and time of birth field.
Convert Output into Delimited HL7
Once I’ve completed my mapping to the template, I save it and return to the main eiConsole screen to convert my output into delimited HL7. Here I’ll choose the HL7 2.x transformer. Again, I’ll choose my version and select the “friendly names” option. I can save my work and testing in the eiConsole’s testing mode to test my transformation.
Next, I’ll set the parameters from my test and load in a sample file. Once I hit “execute test” you’ll see all the question marks turn to green checks. Here we can see our custom XML format with Sally Underweather born on September 19, 1980, our original date format. And here we can see the data after being mapped under the HL7 message template. 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 loaded as a target template drag & drop your source data onto it and you’re done. You’ve created a transformation to a custom defined HL7 message template.
If you’re curious about the software features, free trial, or even a demo – we’re ready to answer any and all questions. Please call us at 813 864 8662 or click the button.
X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas.