Iguana Integration Engine is marketed by iNTERFACEWARE as a developer-oriented integration platform for healthcare data exchange. Vendor materials describe a code-first environment built around the Lua-based Translator IDE, with components for receiving, transforming, and routing messages across clinical, administrative, and financial systems. The product is positioned for organizations that want to build and maintain their own interfaces rather than rely on preconfigured adapters or outsourced managed services. [1][2][4][5]
Development Model and Core Environment
Iguana is presented as a full-code development environment rather than a no-code or drag-and-drop tool. Vendor FAQ content states that coding is required and that the product is built for technical teams who want control over how data moves between systems. The Translator is described as a patented development environment that includes real-time, test-driven development, autocomplete, real-time testing, and pre-built components intended to accelerate interface construction. [4][5][6]
The platform uses Lua for scripting. Source examples show functions that parse inbound HL7 with a schema, filter messages by type, map fields, push data to queues, connect to databases, and generate acknowledgments. These examples illustrate the code-level workflow but do not constitute formal product documentation or an exhaustive feature list. [1][4]
Data Formats, Protocols, and Connectivity
Vendor materials state that Iguana can receive, transform, and route standard or custom data formats. Listed formats include HL7, FHIR, CDA, CCD, X12, NCPDP, EDI, XML, JSON, delimited text, and proprietary formats. Transport methods cited in marketing content include LLP, FTP, SFTP, FTPS, HTTP, HTTPS, TCP/IP, database connections, file systems, and web services using SOAP or RESTful approaches. [1][4][8]
Pre-built components are described for common connection patterns, including an HL7 server receiving messages over LLP, an HL7 client sending over LLP, file readers and writers, and a database adapter template. Vendor content emphasizes that these are building blocks rather than plug-and-play EHR connections, with organizations expected to adapt them to site-specific configurations. [1][7]
A Hypothetical ADT-to-FHIR Interface
A technical team could hypothetically use Iguana to build an interface that receives ADT messages over LLP, parses them with an HL7 schema, maps patient demographic fields into FHIR Patient resources, authenticates to a FHIR server using OAuth2, and posts the resources via REST. This demonstration would exercise documented components and capabilities, but no specific outcome, performance level, or production readiness is claimed.
FHIR and HL7 Workflows
For FHIR, vendor materials describe Iguana functioning as a FHIR client that can authenticate with FHIR servers using standards such as OAuth2.0 and perform RESTful operations including GET, PUT, POST, and DELETE. The vendor states that Iguana can support multiple FHIR versions, including STU3 and R4, and can translate FHIR resources in JSON or XML to and from HL7 v2, CDA, X12, CSV, or custom formats. [2][4]
For HL7, marketing content describes parsing messages into structured data using built-in schemas, mapping fields between HL7 versions, handling custom Z-segments, and managing ACK/NACK workflows. Vendor FAQ answers state that Iguana includes pre-built components such as HL7 Map and HL7 to HL7 Map for normalizing and transforming messages, and that it includes built-in support for LLP connection management, acknowledgment handling, and error logging. [6][8]
Deployment, Monitoring, and Administration
Vendor materials state that Iguana can run on-premise, in the cloud, or in hybrid configurations, and that it is designed to work within existing IT infrastructure without requiring additional costly infrastructure. A centralized dashboard is described as an overview of service and interface status metrics, with access to tools and features across the platform. [1][4]
Administrative capabilities cited in vendor content include granular roles and permissions, per-interface logging, message activity logs, email and SMS notifications, built-in source control with GIT support, and public APIs for external systems to interact with Iguana for monitoring, troubleshooting, reporting, and analytics. High availability architecture is described as continuity of information exchange during unplanned downtime. [4]
Organizational Fit and Implementation Boundaries
Vendor comparison tables position Iguana against drag-and-drop tools and managed services. The product is described as code-first and developer-owned, with full customization and control, versus template-limited visual tools or vendor-managed outsourced interfaces. Deployment options are listed as cloud, on-premise, or hybrid for Iguana, compared with often cloud-based or vendor-hosted alternatives. [2][5][6]
iNTERFACEWARE states that it does not provide managed integration services. FAQ content explains that customers develop, deploy, and maintain integrations internally using Iguana's platform and tools. The vendor also states that Iguana does not provide traditional plug-and-play EHR adapters, citing site-to-site variation in EHR implementations as the reason for a code-level development approach. [1][5][8]