• Create the Channel
• Tutorial Instructions
• Complete Sample Code
• More Information

In this article we will copy an HL7 message to an XML document. For simplicity we will only map a few fields, but as you will see extra fields can easily be added. We placed the mapping code in Filter component, which is (usually) the most logical place for mapping code.

You can use exactly the same method to copy data between any of the different types of node trees.

These are the steps:

1. Parse the message into a source HL7 node tree structure
2. Create a XML table node tree for the target message
3. Map the data from the source node tree to the target node tree

We recommend that you type in the code for each step, but we also include complete Sample Code if you prefer to paste it in and follow along.

Create the Channel [top]

1. Create a Channel with the the following settings:
   • Source = LLP Listener
   • Destination = To Translator
   • Channel name = Mapping HL7 to XML
2. Activate the Filter Component: Click the Filter tab and check Use Filter.
3. Click the Add Channel button to create the channel.
   Ignore the red warning messages, see resolving the milestone configuration error.
4. Open the Translator by clicking the Edit Script link at the bottom of the Filter tab.
5. Download and import the Mapping_HL7_to_XML_Filter.zip project file.
   This file contains a skeleton project and six sample HL7 messages.
6. Iguana will load the project and data into the Translator, your screen should look like this:
   

Tutorial Instructions [top]

1. Pass the message data to the script.
   • Iguana automatically passes the message data to the main() function
   • The message can be accessed using the Data parameter
   • No action is needed
2. Parse the message into a convenient read-only “node tree” structure.
   Add the following line of code to your script:
   
3. Compare the text message and the parsed message.
   Click on the Data parameter (red text) and the ADT message icon:
   
   The messages should look something like this (we clicked on the PID segment to expand it):
   
4. Create the XML outgoing message.
   Add the following line of code to your script:
   
5. Map the HL7 node PID>Patient Identifier to the XML patient attribute id.
   Enter this line of mapping code, auto-completion will help you to find the fields:
   
6. Map the HL7 node PID>LastName to the XML patient element last-name.
   Note: We need to use the node:setInner() function to set an XML element.
   Add the following line of code:
   
7. Complete the patient mapping.
   Add these two lines of code:
   
8. Compare the incoming and outgoing messages.
   Add a trace() command and click on the Msg (ADT)and Out (Document) annotations to view them:
   
   As you can see the mapping worked correctly, the patient data was mapped from the incoming to the outgoing message.
   
9. Push the outgoing message into the Iguana queue.
   Add the following code to your script:
   
   Note: This is not part of the mapping process, but it is needed to forward the message to the Destination Component.

Complete Sample Code [top]

Here is the completed mapping code that you can cut and paste into your script:

local XML_TEMPLATE = [[
<?xml version="1.0"?>
<patients>
  <patient id="">
    <first-name></first-name>
    <last-name></last-name>
    <social-security-no></social-security-no>
  </patient>
</patients>
]]

function main(Data)
   -- (1) Parse the HL7 message
   local Msg = hl7.parse{vmd = 'example/demo.vmd', data = Data}

   -- (2) parse the XML template
   local Out = xml.parse(XML_TEMPLATE)
   
   -- (3) Map (part of) the message
   Out.patients.patient.id = Msg.PID[3][1][1]
   Out.patients.patient["first-name"]:setInner(Msg.PID[5][1][2]:nodeValue())
   Out.patients.patient["last-name"]:setInner(Msg.PID[5][1][1][1]:nodeValue())
   Out.patients.patient["social-security-no"]:setInner(Msg.PID[19]:nodeValue())
   
   -- (3) Push the outgoing message into the Iguana queue
   queue.push(Out)
end

More Information [top]

• See our other interface tutorials in this section
• See our general tutorials section
• See our code samples section