Log out?

eiConsole for Healthcare – HL7 Demo

eiConsole for Healthcare – HL7 Demo

In this demonstration, you will see some of the unique capabilities of the eiConsole for Healthcare. In this example, HL7 formatted lab results will be received, along with a corresponding image, to report. These two data sources will be combined into a single transaction in a standards-based XML format. Open the video & follow the documentation below to continue.

We’ll begin by opening up the Receive-HL7 Results Route, or interface, from the Route File Management window.


hl7-demo-01-13-16-r2

This brings us to the Main Route Grid that depicts the flow of data between our Source System (a Lab System) and our Target System (an External Insurance Company).


We begin with the Listener, which is configured to poll a directory for an HL7 input file.


Once such a file is found, we move on to the Processors. The Processors then look at the name of the inbound file and attempt to find a corresponding image to report with the pdf extension. That image report is added to the transaction and converted into a BASE64 encoded format.


hl7-demo-04-13-16-r2

We then move on to the Source Transformation which will take the HL7 data and convert it into a generic XML representation. We do this by using the eiConsole’s HL7 Transformer (HAPI). The HL7 is parsed, converted into XML and then grouped into a logical XML representation.


In the Routing stage, we route the data along to our single Target System.


hl7-demo-06-13-16-r2

The Target System includes a Target Transformation to convert our generic XML representation of the HL7 into the insurance-specific XML format – in this case, an ACORD TxLife 1122 XML transaction.


Data transformations in the eiConsole are handled using the Data Mapper. All of your logical mapping is done here (between your Source format) – in this case, our HL7 data represented as a tree on the left and our Target format is an ACORD TXLife XML transaction represented as a tree to the right.


Logical mapping rules are created through dragging and dropping onto the structure in the middle with green nodes representing XML elements in our result and blue nodes representing values mapped into those fields.


hl7-demo-09-13-16-r2

For instance, here we can see patient information mapped into the person FirstName, MiddleName and LastName tags.


hl7-demo-10-13-16-r2

We also see a yellow Mapper underneath BirthDate that demonstrates how the eiConsole’s Data Mapper can be used to perform data manipulation during the mapping process. Here, we are formatting the date of birth value coming in from our HL7 into an XML date format using our date formatting tool from the pallet below.


hl7-demo-11-13-16-r2

As this mapping was created, XSLT was generated under the covers.


hl7-demo-13-13-16-r2

Within the Data Mapper, is also where we pull in the HL7 image, already converted into a Base64 encoded representation and we place it into our main XML transaction as an AttachmentData element.


hl7-demo-14-13-16-r2

Once the data has been converted into our outbound ACORD 1122 XML transaction, we move on to the Transport stage. In this stage we’ve configured a Directory drop to simply place the XML transaction in a specified directory. However, any number of Transport types are possible. And, more typically, we’ll be doing something like an HTTP Post to a Web Service.

Now that we’ve viewed the configuration of these stages, let’s move along to watching it in action. To do that, we’ll switch to Testing Mode of the eiConsole.


Here we’ll see all the stages we just talked about represented as question marks. We can choose to start our test at any stage and end it at any stage.


Now, when we click the Execute Test button, the Listener will fire up and begin polling the specified directory for data.


hl7-demo-18-13-16-r2

As it finds an HL7 formatted file,  it will pick it and the corresponding image up. As each stage completes, the question marks will turn into green check marks indicating success.

Now, we can take a look at how the data appeared at each step in the process. Here we can see our initial HL7 lab result input.


We then picked up the corresponding PDF image.


That PDF image was converted into a single BASE64 encoded stream.


Then, in the Source Transformation, we converted the HL7 input into XML.


The HL7 XML representation is then routed to our one Target…

where it is mapped onto an industry specific XML standard format – in this case, an ACORD TXLife transaction.


Within this transaction, you can see the imbedded image created from the PDF.


You can also see the mapping of a number of lab test results.


Finally, this file was dropped in a directory for further processing.

And that’s all there is to it. It’s just that simple to use the eiConsole for Health – to manipulate HL7 data and to convert it into virtually any other file format.

    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