Iguana Webinar: Interface Design Best Practices

Originally presented on February 24th, 2021

By Marcus Walters, Solutions Consultant

Interface Design Best Practices

Overview: 'Interface Design Best Practices'

Our first live webinar of the new year focused on Interface Design Best Practices presented by our very own Solutions Consultant, Marcus Walters. This webinar covered the fundamentals of interface design, as well as ways to implement clarity, efficiency, and flexibility into your own interfaces.

Some of the core topics covered included designing patterns in Iguana, securing credential data at rest with Lua, as well as storing and recalling configurations across multiple Iguana instances.

Note: This live webinar was originally presented on February 24th, 2021.

Webinar Resources

Download the complete set of webinar slides and the associated assignment files here:


Questions & Answers

We are moving to AWS, one of the items that is in discussion is sending data to an iguana receiver in one datacenter to forward to the AWS (iguana instance) thoughts on this? This is all to prevent interruption of customer service and IP endpoints.

Using Iguana to send data to one hosted in the cloud would be a great solution in the short term. The reason why is because the underlying infrastructure is using a cloud hybrid approach. Hybrid cloud is essentially the combination of two or more infrastructures, each with their own set of rules that govern how data is processed. Depending on various factors like speed, network configurations, and future scale outs, dynamic routing of Iguana data should take into consideration all of these factors first before it could be utilized as a long term solution.

For instance, if the AWS instance is held in a data center across the country or even in another state, that could add a delay that may affect data if the throughput is high.

Could you define a variable in the config file that is a value extracted from the HL7 that can be used within lua files to, for example pass into a DB query?

To do this, you must:

  1. Create the config.lua script and variable declarations, and then requiring it in the main.lua script.
  2. Parse the incoming message via the HL7.parse{} API
  3. Assign the variable in the config.lua script a value from the parsed HL7 message.

At this point, the variable can be used freely in the scope it was defined in, and can be passed into a DB query. 

Get notified of upcoming webinars and more: