QSS Technosoft builds, migrates and runs interfaces on iNTERFACEWARE’s Iguana integration engine for hospitals, labs, healthtech companies and payers: HL7 v2, FHIR, X12 and API channels, Iguana X and Iguana 6 deployments, migration from Mirth Connect, and 24/7 managed operations.
100+ healthcare projects | 16+ years in healthcare | HIPAA · HITECH · NCPDP SCRIPT
HL7 v2 • FHIR R4X12 · NCPDPInterface standards
100+Healthcare projectsProven healthcare expertise
CMMILevel 3ISO 27001 · ISO 9001
16+ yearsIn healthcareUS-headquartered in Bloomington, MNTrusted Partners
Iguana is the interface engine teams choose when speed of development matters, and it is now the most common commercial destination for organizations leaving Mirth Connect after the 2025 license change.
Because we run Mirth Connect, Open Integration Engine and Rhapsody as well, we can tell you when Iguana solutions are the right move and when they aren’t.
CHALLENGES INTEGRATION TEAMS FACE
Interface projects rarely fail on the engine. They fail on the vendor’s dialect of HL7, on the migration nobody validated, on the channel one person understands, and on the alert nobody receives at 3 a.m. Here is where we see integration teams get stuck, and how our Iguana solutions are built to get them unstuck.
Problem
How we solve itAssessment of your channels, a costed comparison of Iguana against licensing NextGen or moving to a fork, then channel-by-channel re-implementation in the Translator with parallel validation.
A supported engine, no feeds dropped.ProblemHow we solve itMessage profiling and mapping per partner in the Translator, tested against real sample messages before go-live, with a reusable component library.
Feeds that parse the first time and keep parsing.ProblemHow we solve itIguana’s Translator plus our channel templates: most point-to-point interfaces go from spec to tested channel in days.
Integrations on the timeline the business asked for.ProblemHow we solve itIguana’s dashboard and logging extended with alerting, automated retry and a monitoring model your team can read, plus an on-call rota that covers nights.
Problems caught before the ward does.ProblemHow we solve itFHIR channels and v2-to-FHIR transformation inside Iguana, so legacy feeds and modern APIs meet in one layer.
Modern APIs without replacing what works.ProblemHow we solve itDedicated Iguana engineers ramped in weeks, documentation of every channel, and managed operations if you’d rather not run it at all.
Continuity that doesn’t depend on one person.
Facing similar challenges?Tell us which engine you run today, and we’ll show you whether Iguana is the right move.Talk to Our US Team →OUR SERVICES
Six kinds of Iguana work, one team. Whether you are standing up Iguana for the first time, upgrading from Iguana 6 to Iguana X, migrating from Mirth Connect or looking for someone to run the channels you already have, the same engineers handle all six, alongside the other HL7 FHIR integration tools healthcare teams rely on.
Iguana interface and channel development
The core of Iguana healthcare integration: channels written in the Translator that receive, transform and route messages between the systems a hospital runs, built to a documented standard your own team can maintain.
Message formatsHL7 v2 (ADT, ORM/OMG, ORU, SIU, MDM, DFT), FHIR R4, C-CDA, X12, NCPDP, DICOM, JSON, XML and CSV.
Translator scriptsReusable modules and a component library.
ConnectorsLLP/MLLP, TCP/IP, HTTP(S), SFTP/FTP(S), database, file and web-service (REST/SOAP).
Tested firstEvery channel tested against real sample messages before it reaches production.
DaysFrom spec to tested channel
9Message formats handled
7Connector typesEHR, lab, imaging, pharmacy and payer integration
The connections that make the engine useful: channels to and from the systems on either side, on the standards each partner uses.
EHR platformsEpic, Oracle Health (Cerner), Meditech, Allscripts (Veradigm), athenahealth, OpenEMR and Tebra.Clinical partnersLIS and reference labs, RIS/PACS, pharmacy and e-prescribing (NCPDP), EMPI.Payers and public healthX12 270/271 and 837/835 clearinghouse feeds and public-health reporting.ExchangesHIE, Carequality, CommonWell and TEFCA connectivity via the engine.7EHR platforms20+EHR/EMR/HIS integrations delivered4Exchange networksIguana X deployment and Iguana 6 upgrades
Standing up the current generation of the engine, or moving an existing Iguana 6 estate to it, with the component-based architecture and Git-based deployment Iguana X introduced.
New deploymentIguana X installation, licensing support and environment design on Windows, Linux or containers.Iguana 6 to XChannel conversion and parallel validation.Reuse and controlComponents reused across channels and environments; version control on every channel.ResilienceHigh availability, backup and disaster recovery.2Versions run in parallel during upgrade3Platforms: Windows, Linux, containers100%Channels under version controlMigration from Mirth Connect and other engines
Moving your interfaces to Iguana without dropping a feed, whether you are leaving Mirth after the license change or consolidating from Cloverleaf, Rhapsody or a custom integration layer.
InventoryChannel inventory and dependency mapping on the source engine.Honest rebuildRe-implementation in the Translator; Iguana is not a Mirth import, so we scope it as a rebuild.Safe cut-overParallel run with message-level comparison, phased cut-over by feed and a rollback plan.Hand-overDocumentation so the new engine is not a new single point of failure.4Source engines migrated from2Engines run in parallel before cut-over0Feeds droppedFHIR, API and cloud-hosted Iguana
Modern exchange through the same engine: FHIR channels, REST APIs, and Iguana deployed where you need it.
FHIR R4 channelsFHIR listeners and senders; HL7 v2 to FHIR and C-CDA to FHIR transformation.Web servicesREST/SOAP channels for apps, portals and third-party services.HostingAWS, Azure or Google Cloud, on-premise or hybrid; containerized Iguana with CI/CD.Hybrid gatewaysSecure cloud gateways for hybrid estates during and after migration.2Formats transformed to FHIR3Cloud platforms supported3Deployment options: cloud, on-premise, hybridManaged Iguana operations and 24/7 support
The interfaces you already have, monitored, supported and kept current, whether we built them or not.
MonitoringChannel monitoring, alerting, queue management and automated retry.UpkeepVersion upgrades, certificate renewals and security patching.PerformanceTuning, capacity planning and license-tier advice.Help desk24/7 help desk with named interface analysts and agreed response times.24/7Help desk coverage3Upkeep areas covered3Performance areas tunedAn interface engine is judged on what happens after the demo: the channel that still parses when the lab changes its ORU, the migration that loses no message, the upgrade that doesn’t take the feeds down, the 3 a.m. alert that reaches someone who can fix it. QSS runs Iguana as a practice, not a skill on a CV, beside Mirth Connect and Rhapsody practices, which is why our recommendation is about your channels rather than our preference.
Named Iguana engineers and interface analysts, a reusable Translator component library, and 20+ EHR, EMR and HIS integrations delivered through the engine.
Learn more →
Mirth Connect, Open Integration Engine and Rhapsody in production alongside Iguana, so the engine choice and the migration plan come from someone who has done both directions. Iguana is one of several HL7 FHIR integration tools healthcare organizations compare, and we place it where it fits.
Learn more →
The Translator makes fast development possible; our channel standards and documentation make it maintainable after we leave.
Learn more →
Monitoring, alerting, retry and 24/7 support as a managed service, so the feeds keep flowing after go-live and through the next upgrade.
Learn more →
HIPAA, HITECH, Cures Act API rules, 42 CFR Part 2 consent handling, TLS on every channel and ATNA-style audit.
Learn more →
Fixed-scope channel sets, dedicated Iguana teams or managed operations, under CMMI Level 3 and ISO 27001, with 4.9/5 on Clutch.
Learn more →The building blocks we draw on most often. Select the ones that matter and we’ll map them to your channels in the discovery call.
ADT, ORM, ORU, SIU, MDM, DFT and custom message types
Mapping, validation and routing logic tested on real messages
Reusable modules shared across channels and environments
Inbound and outbound HL7 over the standard transports
FHIR listeners, senders and resource transformation
Bridge legacy feeds into FHIR resources
LIS and reference-lab interfaces with per-client conformance
Durable queues and automated re-send on failure
Channel status, throughput and error visibility
Iguana 6 to Iguana X conversion with parallel validation
Re-implementation with message-level comparison
TLS, certificate management, RBAC, audit and patching
Batch and polling connectors for legacy sources
Web-service channels for APIs and apps
Summary documents for transitions of care
Eligibility, claims and remittance transactions
E-prescribing connectivity
Imaging metadata and study-notification feeds
Vitals from monitors and wearables into the record
Email, SMS and ticket integration on channel events
Clustered engines, failover and disaster recovery
Git-based channel versioning (Iguana X) and change control
Partner simulation and validation before go-live
AWS, Azure, Google Cloud, Docker and Kubernetes
Epic, Oracle Health, Meditech and master patient index feeds
HOSPITALS & HEALTH SYSTEMS
Every system on one integration layer
Smooth integration between EHRs, LIS, RIS and other critical systems across hospital networks.
Learn More →
EHR Integration
Network-wide Feeds
Critical SystemsCLINICAL LABORATORIES
Fast, secure lab data exchange
LIS integration and standardized messaging in HL7 and FHIR for fast, secure lab data exchange.
Learn More →LIS IntegrationOrder ResultsStandard MessagingRADIOLOGY & IMAGING CENTERS
Results that reach the referring physician
Reliable, real-time communication between PACS/RIS systems and referring physicians.
Learn More →PACS IntegrationReferrer CommunicationReal-time DataHEALTHTECH COMPANIES
Interoperability built into your product
Custom Iguana interfaces that speed up product development and interoperability for SaaS platforms.
Learn More →Faster LaunchProduct InteroperabilityChannel LibraryPHARMACEUTICAL & LIFE SCIENCES
Integration built for trials and reporting
High-performance integration for clinical trials and regulatory data exchange at scale.
Learn More →Trial DataRegulatory ExchangeHigh VolumeTELEMEDICINE PLATFORMS
Virtual care connected to the record
Bridge telehealth software with EHRs and health data systems through flexible, future-proof integrations.
Learn More →EHR ConnectivityVirtual VisitsFlexible IntegrationINSURANCE & PAYERS
Claims and data exchange, automated
Automated claims processing, data exchange and compliance across HL7, FHIR and X12.
Learn More →Claims AutomationX12 ExchangeCompliance SupportSituations We See Most in 2026
Switching
Upgrading
Deploying
Healthtech
Senior
Registries
OperationsReal results. Real impact. Empowering better care through technology.
We integrated Iguana to power a cloud-based document storage solution for senior living communities, enabling digital uploads, e-signatures and secure document sharing without physical paperwork.
Tech Used
Iguana · HL7 · REST APIs · AWS · MongoDB · Angular
Results
We used Iguana to synchronize personal health records across mobile and desktop devices, with real-time access to medical data, care provider communication and doctor search for a complete patient wellness experience.
Tech Used
Iguana · FHIR · React Native · Firebase · Node.js
Results
Iguana integration enabled data exchange between hospitals, pharmacies and senior care providers, digitizing patient workflows and giving real-time access to clinical tools across the senior care ecosystem.
Tech Used
Iguana · HL7 · PostgreSQL · .NET Core · React.js
Results
We use AI where it saves an analyst hours and catches problems earlier, and keep a person in control of every mapping that touches patient data.
Channel Data
Vendor specs, messages,
traffic, local codes
AI Engine
Draft, detect,
compare, map
Analyst Review
Human oversight
+ audit trail
Action
Faster, safer
channels
Translator script draftsDraft channels from vendor specs in hours, not days
Anomaly & drift detectionCatch malformed messages and code changes within minutes
Migration verificationCompare every message between Mirth and Iguana overnight
Terminology mappingMap local codes to SNOMED CT, LOINC and RxNormAn interface engine carries every message a hospital exchanges. We design every Iguana environment to the regulations that apply, and can show you how, control by control.
TLS 1.2+ on every LLP, HTTPS and API channel; mutual TLS where partners support it; certificate lifecycle management.
Role-based access to the Iguana dashboard, channel-level permissions, MFA at the platform edge, and no shared accounts.
Message logs, channel change history and administrative logs retained for OCR audits; Git-based versioning on Iguana X.
42 CFR Part 2 and opt-in/opt-out rules enforced in routing logic; sensitive-data segmentation where required.
HIPAA-eligible environments on AWS, Azure or Google Cloud with BAAs in place; on-premise where you require it; backups and tested disaster recovery.
FHIR channels built to ONC specifications and USCDI data classes where the engine fronts patient-access APIs.
Iguana kept on a supported release with a documented upgrade cadence, so the engine never becomes the unpatched system.
Third-party vulnerability assessments and penetration tests tracked to closure; conformance and load testing before every partner go-live.
Best when you have a defined list of feeds, an Iguana X upgrade or a migration with a date. Fixed price, milestone-based delivery.
Best when integration is continuous. Named Iguana engineers and interface analysts who work as an extension of your team.
Best when you want the channels you already have monitored, supported and kept current, with build capacity on call.
The engines, versions and HL7 FHIR integration tools healthcare IT teams run alongside Iguana, grouped so you can find your own.
Iguana versionsIguana X (component-based, Git-integrated) · Iguana 6 (legacy, still widely deployed)
Other engines we runMirth Connect (3.x–4.6) · Open Integration Engine · BridgeLink · Rhapsody · Infor Cloverleaf
StandardsHL7 v2.x · FHIR R4 · C-CDA · X12 · NCPDP SCRIPT · DICOM · IHE · Direct · USCDI
Connectors & transportsLLP/MLLP · TCP/IP · HTTP/HTTPS · SFTP/FTP(S) · File · SQL Server · PostgreSQL · MySQL · Oracle · MongoDB · REST/SOAP web services · SMTP
Scripting & toolingIguana Translator (Lua) · JSON/XML libraries · Git · Iguana X components · Docker images · Terraform
Application stackNode.js · Python · Java · .NET/C# · React · Angular · React Native · Flutter
HostingAWS · Microsoft Azure · Google Cloud · On-premise · Kubernetes
Testing & monitoringIguana dashboard and logs · HL7 Inspector · 7Edit · Postman · Custom message simulators · Grafana/Prometheus · Alerting integrationsEvery Iguana environment is scoped to its channels and partners, but buyers deserve a straight answer. These are typical engineering ranges based on our delivery history and current market rates.
One or a few Iguana channels to a single partner
2–4 weeks
$5,500–$15,000
Typical investment
A new Iguana X environment, an Iguana 6 upgrade, or Mirth and other channels re-implemented on Iguana
6–12 weeks
$25,000–$60,000
Typical investment
Multi-system channels, FHIR, national-network connectivity and 12 months of managed operations
4–8 months, phased
$70,000–$150,000+
Typical investment
Figures are engineering ranges; iNTERFACEWARE license fees are separate and quoted from the vendor’s current price list. You leave the discovery call with a range specific to your project.
Talk to a healthcare interoperability architect about your systems, your partners and where you are with your current engine, and leave the call with an interface map, an Iguana recommendation and a cost range.
ExpertGuidance
TailoredRecommendations
Clear Cost& TimelineAnswers about Iguana healthcare integration: standards, Iguana X and Iguana 6, Mirth Connect migration, security, timelines and costs.
The Iguana Integration Engine, from iNTERFACEWARE, is a healthcare integration platform that streamlines data exchange between systems such as EHRs, LIS, RIS, PACS and third-party applications. It supports HL7, FHIR, X12, DICOM and other messaging standards, and its Translator lets developers build and test interfaces against real messages in hours. With scripting flexibility, live debugging, version control and a scalable architecture, Iguana helps healthcare organizations achieve interoperability faster and at lower integration cost.
Since NextGen made Mirth Connect commercial-only with version 4.6 in March 2025, Iguana has become the most common commercial destination for teams leaving Mirth. It fits organizations that value fast channel development, vendor support and per-server licensing. It is not an import: Mirth channels are re-implemented in the Translator, so we scope it as a rebuild with parallel validation. The alternatives are licensing NextGen Mirth Connect or moving to an open-source fork; because we run all of them, our assessment compares the three for your channels and budget.
Iguana X is iNTERFACEWARE’s current generation of the engine, built around reusable components and Git-based deployment. Upgrading makes sense when you want component reuse across many channels, modern version control and a supported release; we convert channels, run both versions in parallel and cut over feed by feed.
It depends on what you value. Iguana solutions offer vendor support, fast Translator-based development and a clear upgrade path, at a license cost. Open Integration Engine and BridgeLink preserve the open-source model and your existing Mirth channels import directly, but support comes from the community and from partners like us. They are the HL7 FHIR integration tools healthcare teams weigh most often against each other, and we give you the three-year cost and risk comparison for your environment in the discovery call.
HL7 v2 and v3, FHIR, X12 (EDI transactions), CDA/C-CDA, DICOM, NCPDP, and custom JSON, XML and CSV formats.
Yes. iNTERFACEWARE rates the engine at over 3,600 messages per second, making it suitable for large healthcare networks and high-traffic data environments on modest hardware.
Iguana provides enterprise-grade security features, including role-based access control, SSL/TLS encryption and audit logging, and we configure and operate it to meet HIPAA, HITECH, GDPR and other regulations; the compliance section above describes each control.
Faster interface development (interfaces built in days rather than months), a low hardware footprint, built-in scripting and testing that reduce reliance on external vendors, and reliable uptime and error handling that reduce disruption. Licensing is per server rather than per interface, which matters as channel counts grow. Our services add reusable components and managed operations that lower the cost of each new interface.
Yes. Iguana is cloud-compatible and can integrate both on-premise and cloud-based EHRs, billing systems, patient portals and third-party APIs, enabling hybrid or full-cloud interoperability.
Yes. QSS Technosoft tailors Iguana integration services to your operational goals, data structures and compliance requirements.
Fully. Iguana’s Translator uses Lua scripting for custom data transformation, routing logic, error handling and more, with live testing against real messages.
Hospitals, clinics, imaging centers, labs, telehealth companies, healthtech startups and insurance providers all benefit from Iguana’s ability to unify systems and support reliable data exchange.
Yes. Iguana is optimized for real-time processing, so systems communicate on time and accurately, which is critical in clinical and operational workflows.
A single channel or interface set takes 2 to 4 weeks; a new deployment, an Iguana X upgrade or a migration from another engine 6 to 12 weeks; an enterprise program is phased over 4 to 8 months. See the cost and timeline section above.
Yes. Iguana works with both modern and legacy systems, with tools to transform outdated data formats and protocols into standardized messaging such as HL7 or FHIR.
Iguana is developer-friendly, but scripting knowledge (especially Lua) helps. We provide training and documentation, and our managed service covers organizations that would rather not run it themselves.
Full lifecycle support: monitoring, troubleshooting, performance tuning, upgrades and scaling assistance, as a managed service if you prefer.
Extensive healthcare interoperability experience; a dedicated Iguana practice beside Mirth Connect and Rhapsody practices, so our advice is not tied to one engine; experience with Iguana X upgrades and Mirth-to-Iguana migrations; and end-to-end monitoring and 24/7 support.
The engine is Iguana, made by iNTERFACEWARE Inc.; "igauana" is a common misspelling in searches. Whichever spelling brought you here, this page covers Iguana healthcare integration: building, upgrading, migrating to and running the engine.
Yes. We start with a channel inventory and documentation pass, then monitoring and alerting, then a supported-version plan. Most take-overs begin as managed operations and add build capacity as needed.
Engineering typically ranges from $5,500 to $15,000 for a single channel set, $25,000 to $60,000 for a deployment, Iguana X upgrade or engine migration, and $70,000 to $150,000 or more for an enterprise program with managed operations. iNTERFACEWARE license fees are separate.
Yes. We build Iguana channels to and from Epic, Oracle Health (Cerner), Meditech, Allscripts (Veradigm), athenahealth, OpenEMR and Tebra, using HL7 v2, FHIR R4 and each vendor’s supported interfaces.
