The Qvera Interface Engine (QIE) is a strong fit for Iguana teams that want high availability included on every licensing model, full DICOM networking alongside HL7 and FHIR, and a built-in AI Companion. The AI Companion converts your Lua scripts to QIE scripts, and Qvera engineers are available to assist with the move. If you want to keep writing Lua, or to run an engine that needs no database, QIE is not the right answer. QIE is in production today at more than 600 sites, running more than 25,000 interfaces and processing more than 50 million messages a day.
Six things Iguana teams ask about when they evaluate an alternative:
Yes. The AI Companion converts your Iguana Lua scripts into QIE scripts, and Qvera engineers are available to assist your team with moving the interfaces, one at a time, so messages keep flowing while each one is checked.
“Our biggest concern going in was how much of our existing Iguana work would have to be redone. It was a much smaller lift than we thought. Our existing Lua code already defined what each interface needed to do, and the AI Companion handled the bulk of translating that into QIE scripts. Every interface is now running in production, with effectively no downtime.”
Josh Atchley, Senior Manager, Platform & Infrastructure, Nexus Health Systems
An Iguana team has three choices:
Iguana cells come from iNTERFACEWARE’s own documentation, license agreement and downloads page, reviewed on 27 September 2026. “Not found” means nothing was found in that documentation, not that the feature is proven absent.
| Building interfaces | QIE | Iguana 6 | IguanaX |
|---|---|---|---|
| Scripting language | JavaScript, which can call Java libraries | Lua, in the Translator | Lua, in Translator 2.0 |
| How an interface is organized | Channels of receiver, mapping, condition and destination nodes | Channels: source, filter, destination | Components, each a Lua program in its own Git repository |
| Live view of sample messages while you script | ✓ step-by-step testing with sample messages | ✓ Translator annotations | ✓ Translator 2.0 |
| AI assistant in the product | ✓ AI Companion, with every license | not found; described by iNTERFACEWARE as a future plan | not found; described by iNTERFACEWARE as a future plan |
| Standards | QIE | Iguana 6 | IguanaX |
| HL7 v2 | ✓ | ✓ | ✓ |
| HL7 v3 | ✓ | not found | not found |
| FHIR | ✓ as a client and producer, JSON and XML, OAuth 2.0 | REST calls in Lua; example FHIR server channel | REST calls in Lua; Epic, Cerner and ModMed adapter templates |
| CDA | ✓ | builds documents | builds documents; “not designed to parse” them |
| X12 | ✓ | ✓ | ✓ |
| DICOM networking (store, query, retrieve, verification, worklist) | ✓ | not found; a DICOM file plugin that iNTERFACEWARE plans to remove | not found; no DICOM documentation |
| DICOM header de-identification | ✓ | not found | not found |
| Running the engine | QIE | Iguana 6 | IguanaX |
| Database the engine needs | Microsoft SQL Server, MySQL or MariaDB | none; message logs are built in | none; SQLite built in |
| Windows, Linux, macOS | ✓ | ✓ | ✓ |
| Vendor-published container image | ✓ Docker Hub and AWS ECR | not found | sample Dockerfile; no published image |
| License permits your own cloud account | ✓ | ✓ (agreement §4) | ✓ (agreement §4) |
| High availability | ✓ two or more nodes share one database, automatic failover; included on every licensing model | outside load balancer; handles server failures, not channel failures | documented designs behind your own load balancer; queue recovery needs shared storage |
| Many sites from one console | ✓ Remote Management Hub (RMH): sites connect outward, no inbound firewall rule or VPN per site | Global Dashboard, which connects to each remote server | not found |
| Configuration history | ✓ every change, compare and restore | built-in Git repository | Git repository per component |
| Security and support | QIE | Iguana 6 | IguanaX |
| SOC 2 Type 2 attested vendor | ✓ | not found | not found |
| Support | Phone, email, customer portal and knowledge base; 8am to 5pm Mountain; 24/7 for system-down emergencies | Ticket email and after-hours numbers, for direct paid-up customers; no hours published (support page) | as Iguana 6 |
| Licensing | QIE | Iguana 6 | IguanaX |
| Model | Channel-based, Enterprise or OEM; see pricing below | Annual subscription, counted by channels; no prices published | Annual subscription, counted by components; no prices published |
Yes, in one engine. Anything QIE does for HL7 v2 it also does for HL7 v3, FHIR, DICOM including native DIMSE and DICOMweb, X12, ASTM, CDA and IHE profiles, over MLLP, REST, SFTP, file, database, message queue and network share. The Qvera DICOM Router is that same engine configured for imaging.
It runs on Windows or Linux, in Docker or Kubernetes from images Qvera maintains, or on AWS ECS: on-premise, in containers, or in your own AWS, Azure or Google Cloud account, against Microsoft SQL Server, MySQL or MariaDB. Running engines at more than one site, or inside networks you do not control, is what the Remote Management Hub (RMH) is for.
The Qvera Interface Engine · The Qvera DICOM Router · Remote Management Hub
Iguana and QIE are not the only healthcare integration engines. Depending on an organization’s requirements and existing technology relationships, a shortlist may also include Mirth Connect and its community forks, Rhapsody Integration, Corepoint, InterSystems Health Connect, Infor Cloverleaf and PilotFish. These are established products with real customers, and any of them may be right for a particular organization.
If another engine is on your shortlist, ask every vendor, Qvera included, to show the move using one of your own Iguana interfaces. Ask what carries over, what is rebuilt, how the result is tested, and what the complete cost is once support, high availability, test environments and multi-site management are included.
Qvera offers Channel-based, Enterprise, and OEM licensing models. Channel-based licensing starts at $9,980 per year for 2 channels. View Qvera Licensing and Pricing.
QIE is in production at more than 600 sites, running more than 25,000 interfaces and processing more than 50 million messages a day. Qvera has built healthcare interface engine software since 2008 and is SOC 2 Type 2 attested.
Nexus Health Systems moved every interface from iNTERFACEWARE Iguana to QIE without rewriting them or interrupting message flow, using the AI Companion.
Read the case study →How this comparison is sourced: Qvera publishes this page and sells QIE. What this page says about QIE comes from Qvera’s own product documentation and production deployments; about Iguana 6 and IguanaX, from iNTERFACEWARE’s own documentation, license agreement and downloads page. All competitor information was last reviewed on 27 September 2026. Vendors change their products, so check their current documentation before relying on any single claim. Found something out of date? Tell us and we will correct it.
