Getting Started With Iguana's Pre-Built Components

The first time you open Iguana and click to create a new component, it can feel like there is a lot to choose from. LLP listeners, file readers, FHIR adapters, database mappers, custom translators, and more. For new users, this can seem like a big menu with no clear starting point.

What many people do not realize is that Iguana includes a set of pre built templates designed to make those early steps easier. These templates act like training wheels. They give you a working structure that already follows best practices, so you can focus on learning how data moves through Iguana instead of trying to build everything from scratch.

Here is a look at how those templates work and how to use them effectively.

The component creation dialog: your starting point

When you select Create Component inside Iguana, you are taken to a dialog that shows a list of categories:

• HL7

• Database

• FHIR

• File based workflows

• Protocol templates

• Custom translator components

Each category contains ready to use examples. These templates give you a basic structure for common integration patterns, including the component type, the wiring between modules, and the essential Lua scaffolding if needed.

If you are new to Iguana, these templates save learning time by showing you what a good starter component looks like.

Why templates matter for beginners

Pre built templates help in three practical ways:

They give you a working structure immediately

Instead of starting with an empty translator and a blank screen, you get something recognizable. For example, the HL7 Mapper template comes with:

• Sample code that reads HL7 input

• Parsing and annotation window connections

• A basic structure for mapping fields

• Comments that explain what the script is doing

This makes the translator less intimidating when you first open it.

They teach you established patterns

You do not need to guess how experienced Iguana users design their components. The templates already follow the separation between source, mapper, and destination. They show where to put transformation logic, where to add validation, and how to return output cleanly.

They speed up early success

Your goal as a new user is to get something working. Seeing real data parse correctly and flow through the annotation window helps you understand what Iguana is doing under the hood. Templates help you reach this point faster.

Highlight: pre built HL7 templates

HL7 remains one of the most common formats in healthcare integration. Iguana includes HL7 specific templates that help you:

• Parse incoming HL7 v2 messages

• View them in the annotation window

• Extract fields with autocompletion

• Produce structured output like JSON or XML

• Set up basic routing or filtering rules

For example, an HL7 ADT template may include Lua snippets like:

local h = hl7.parse{v = RawMessage}
local out = {}

out.PatientID = h.PID[3][1]:S()
out.FirstName = h.PID[5][1][2]:S()
out.LastName = h.PID[5][1][1]:S()

return json.serialize{data = out}

Beginners can modify these examples without needing to memorize HL7 segments or write a parser from scratch.

Database templates: ideal for clinics with SQL back ends

Many clinics store information in SQL databases. Iguana includes templates that show how to:

• Connect to a database

• Write safe connection parameters

• Run select queries

• Iterate through result sets

• Map database fields into your desired format

The template typically uses code such as:

local conn = db.connect{
   api = db.MY_SQL,
   name = DB_NAME,
   user = DB_USER,
   password = DB_PASS
}

local rs = conn:query('SELECT * FROM Patients')

This gives you a working baseline for reading and transforming data from internal systems.

FHIR templates: helpful for modern API based exchanges

If you work with FHIR resources, Iguana provides templates that simplify:

• Receiving or sending JSON FHIR payloads

• Validating fields

• Normalizing identifiers

• Creating outbound requests to FHIR servers

These templates help you avoid the common pitfalls of handling structured JSON manually.

Templates do not lock you in

One of the best things about Iguana is flexibility. Templates help you start faster, but they do not restrict you. You can:

• Add custom fields

• Replace mapping logic

• Add new components

• Insert validation steps

• Use Git to version and evolve the component

A template is simply a starting point. Once you are comfortable, you can turn it into a fully custom piece that fits your exact workflow.

A recommended process for new users

If you are just beginning with Iguana, here is a simple workflow that works well:

1. Choose the template that best matches your data source

2. Insert sample data into the translator

3. Use the annotation window to explore how the template works

4. Modify the mapping rules one step at a time

5. Test the output

6. Commit the changes to Git

7. Reuse the component in future projects

Following this path helps you see real results early and builds confidence quickly.

Pre built templates are your guide, not your destination

Templates were designed to help new Iguana users get to a working interface without feeling overwhelmed. They give you a structure, show you common patterns, and help you understand how data moves through the system. Once you learn the patterns, you can adapt them, extend them, or even use them as the foundation of a reusable component library.