At the end of this course each person should be capable of installing, setting and up and administrating an Iguana server and using all it's major capabilities with the Translator.  While we use specific examples to teach the Translator, the course does teach core principles to apply the Translator to a wide variety of problems.

Day 1

Introduction to HL7 and installing Iguana 5.5

1. Introductions.
2. HL7 overview.
3. Introduce the Wiki and explain how to best use this helpful resource.
4. Installation of Iguana 5.5.
   • Getting a license and how to get one in an emergency.

Iguana Overview

1. Introduce Iguana 5.5.
2. Open Dashboard.
3. Build an Inbound Channel.
   • LLP --> Channel (Queue).
4. Test the channel using the built-in tools.
5. Finding your data within the logs.
   • Iguana uses a full text search index which means by default one searches for exact words.
     • How to use '!' to disable this if linear search is needed.
   • Look at the log views - hex, segment etc.
   • Filtering logs by specific time.
   • Exporting.
6. Other Iguana Settings.

Translator

1. Core Principles.
2. Create an Outbound Channel.
   • Channel (Queue) --> LLP.
3. Configure the Translator filter component.
   • We import a simple script from a zip file to demonstrate.
   • It will only show a couple of functions to discuss core principles.
   • Import sample data from text file.
4. Main IDE features.
   1. Show how we can vary the sample data.
      • Explain we use the sample data for development and testing.
      • That it can be pulled from logs and edited directly.
   2. Show the data coming into main and coming out as mapped table data.
   3. Walk through the script.
      • Demonstrate code navigation.
      • Show pop out dialogs and how they are synced with the data.
   4. Explain annotations and auto-completion.
      • Introduce key concept that the code is actually executed within the IDE environment.

Day 2

HL7 to HL7 Interface

1. Start with our Outbound Channel --> LLP channel.
2. Configure the Filter component with our own mapping.
3. Save the first milestone.
   • Add a comment line and save this milestone.
   • Explore the differences window.
   • Explain that source code control is a fundamental part of the Translator environment.
     • Everything must be committed before it can be run in production.
     • We use the opensource BSD licensed Fossil source control under the hood.
     • Everything is versioned.
4. Go to the channel screen.
   • See reference to milestone.
   • Explain choice between most recent and a specific milestone.
   • Start the channel.
   • Show the use of the HL7 simulator and HL7 Listener to feed data through the channel.
   • We should have the example set up so we get at least one error.
5. Resetting the Queue.
6. Building a Z Segment module.
   • Load in a string.split function to break apart a field that has two parts to it.
7. Trouble shooting an error.
   • Find error in logs.
   • Export error to Translator.
8. Filtering out unrecognized messages.
   • Correct the Error.
   • Save Milestone.
   • Restart the channel.
9. Understanding the Message schema file (vmd).
   • 'Get' the 'transform.vmd' file.
10. Utilizing the Diff module to compare Message translation.
11. An easy way to deal with dates - fuzzy date time parser.
12. Do the classic Clean Phone routine.
    • Strip non numerical characters from a phone number which has spaces and brackets using gsub.  
    • Use # operator to get the length of the string.
    • Then use string.sub to break the string into pieces.
    • Use concatenation .. operator to add them together.
    • Cover the important concept of methods and node extension routines.
      • i.e. make a cleanPhone() method like.
      • Patient.HomePhone = PID[10]:cleanPhone().
13. Introduce important concept of a Shared Module that can be used across many projects.
14. Building a cross reference table in your translation.
15. Inserting segments into your outbound message.
16. This is useful work flow to show customers on how they can import the error into the Translator.
    • Correct the error.
    • Save a new milestone.
    • Restart the channel.
    • See the transaction correctly handled.
    • Show the transaction history on the message.
17. Raising an Alert.
    • Create an Alert in the settings.
    • Build script to determine Alert trigger.
    • Reset the Queue and view log.
18. Stop the channel.
    • Show how we can reposition the queue to the very start.
    • Start the channel and reprocess all the transactions.
    • Show using the resubmission screen to re-process one transaction.
    • Show how altering the message in real time alters the outcome.

This is a very hands on lab section with the trainer demonstrating the exercises while people try them out.

Introduction to Lua 

1. Working with String.
2. Declaring variables.
3. Loops.
4. Demonstrate using the capitalize function.  (WHITE --> White).
5. Parsing a text file.
6. Connecting to an Ftp server.

This is a very hands on lab section with the trainer demonstrating the exercises while people try them out.

It's important to understand that the Translator is an open extensible environment.

Day 3

HL7 to Database

1. Set up LLP --> To Translator channel and ignore the classic To/From Database components.
2. Configure the LLP listener component listening port.
3. Export Sample Data from logs.
4. Configure the Translator component.
   • We load basic modules from a zip file.
   • It will only map ADT messages.
   • i.e. PID segment data into one patient table.
5. Create database.
   • Use Translator to execute statements on database.
6. Create Tables.
   • Use built in feature to show how to create tables.
7. Build our mapping.
   • Putting in the conn:merge{} statement.
   • Explore the live=true/false flag.
   • Commit the milestone.
8. Save the first milestone.
9. Start the channel and use the HL7 Simulator to feed data through the channel.
   • Set the debug setting to High.
10. Explore how the data gets into the database.
    • View in logs to see update and insert statements.
    • Open tables.vmd to show connection between vmd file and Iguana.

Error Handling

This is where we cover the:

1. Use of the "retry" module.
2. pcall and error.

The example channel will already have the retry module incorporated with it.  This part of the course will explain how it works and visibly demonstrate it in action with stopping and starting a MySQL database.

Mapping Next of Kin

In this part of the tutorial covers adding a new table - Kin.

1. A closer look at the conn:merge{} function.
   • Download the tables.vmd file from the example and look at the table definitions.
   • See how the key column attribute alters the behaviour of conn:merge{}.
2. Add one more "Kin" table to our mapping.
   • Use the Import tables from database wizard.
   • Add the table definition to the single message defined in the tables.vmd file.
   • Save the vmd file.
   • Upload it to Iguana GUI.
   • Use the diff window to see how the vmd XML changed.
3. Create a new mapping function for one next of kin.
   • Start with mapping the first next of kin using a function.
   • Cover the idea of handling a foreign key.
   • Now how do we deal with repeated segments?
   • Introduce for loop.
   • Show how the Iguana GUI annotations work when a function is called more than once.
4. Save the milestone.
   • Examine changes again.
   • Run the channel.
   • Confirm the data is being submitted.

And stop.  At this point the class will do the same exercise. 

From Database Interface

1. Set up Translator --> To LLP channel.
2. Configure the Source script.
3. Cover Seeding.
   • Run channel.
   • View the data that was sent.
4. Create the Filter Channel.
   • Create script to form message.
5. Handling NULL data from database.

At this point course attendees will have already seen the use of our database objects for querying.  The key concept to teach is the concept of 'seeding'.  i.e. where we make a very small amount of logic in the from channel to obtain IDs.

Also covered is how to deal with NULL data coming from the database.

Question and Answers with Iguana Developers

This session will include the opportunity to talk to members of the core Iguana development team. It's an opportunity to ask in depth questions about any technical questions you have about Iguana and the Translator.

System Administration

1. Cover backing up and restoring an Iguana server.
2. Exporting/Importing channels.
3. Manual installation.
4. Global dashboard.
5. Round off showing the remaining areas of the settings window.
   • Environmental variables.
   • Finding database DLLs.
6. High availability.

Optional Modules

From this point the course covers extra exercises that course attendees can complete on their own with assistance. Because the course is small customers often bring problems that relate to their actual work in this section.

Simple Webservice Example

A very simple web service which maps codes from one set to another.  Idea of centralizing such code mappings.  Demonstrates mapping XML and JSON - i.e. with a GET/POST parameter to say which format to return. Covers the web services configuration part of settings and authentication.

Simple CDA Example

Show mapping of data from a CDA document into a database.

Custom Acknowledgments

Cover application acknowledgments and query-response example.