TrakCare Assistant
Revenue Cycle Management
Medication Management

Healthcare organizations are continually modernizing their technology ecosystems to support new interoperability standards, AI initiatives, cloud adoption, and digital transformation. As part of that process, many IT leaders are evaluating whether their current integration platform is positioned to meet future business requirements. Common considerations include:

Healthcare organizations depend on integration engines to keep clinical, operational, financial, and patient-facing workflows running. iNTERFACEWARE Iguana is known for providing technical teams with a flexible, code-driven approach to building interfaces across HL7, FHIR, APIs, databases, and other healthcare systems, and it has a loyal developer following.
But healthcare integration requirements are changing. Organizations must manage growing transaction volumes, expanding partner ecosystems, cloud and hybrid infrastructure, FHIR-based exchange, and increasing demand for governed data that can support analytics and AI.
At the same time, iNTERFACEWARE has published significant changes to its operating model, support process, and product direction. Organizations running Iguana in mission-critical settings should read that material directly and factor it into their long-term infrastructure planning. Specific, sourced references are provided throughout this document.
InterSystems Health Connect provides an enterprise-grade healthcare integration engine for mission-critical interoperability. Built on InterSystems IRIS, it enables organizations to support existing HL7 and legacy workflows while establishing a scalable path toward FHIR, APIs, cloud services, advanced data management, and AI-ready healthcare data.
Capability |
InterSystems Health Connect |
iNTERFACEWARE Iguana |
| High Availability and Resilience | Synchronous database mirroring with automatic fail-over is built into the platform, alongside asynchronous mirroring for reporting and analytics. Enterprise Monitor, Enterprise Message Bank, and Enterprise Message Viewer provide cross-production visibility. | iNTERFACEWARE advises against its own high-availability option. Its support page states the configuration "uses some risky Lua scripts that can make Iguana less reliable, not more," and is headed "'High Availability' Configuration: Please Don't Use It." |
| Development Model | Graphical production editor, business rule editor, and data transformation editor, with full programmatic access when required. Interface maps and visual message tracing support troubleshooting across the message lifecycle. | Code-first by design. iNTERFACEWARE states that "Iguana is designed for developers and requires some coding," using Lua. Git integration is provided for version control. |
| Healthcare Standards Coverage | HL7 v2, FHIR, C-CDA, X12, EDIFACT, ASTM, DICOM, and IHE profiles ship as productized components with schema tooling, document viewers, and pre-built transformations via the SDA clinical data format. | Published format support covers HL7, FHIR, CDA, CCD, X12, JSON, XML, EDI, TXT, and CSV. DICOM and IHE profiles do not appear in iNTERFACEWARE's published format list. |
| Support Model | InterSystems Worldwide Response Center: 24/7/365 coverage across more than 80 countries, advisers based in 15 countries, and a published commitment to engage with enquiries within 30 minutes. | Support is largely delivered through self-service documentation, online resources, and direct outreach channels rather than a dedicated global support organization. |
| Vendor Operating Model | Established global organization with regional field, cloud operations, and support teams, structured escalation paths, and standard commercial terms. | iNTERFACEWARE states it "today operates only on a cash flow basis" under a "No Employees" model, following a restructuring in which the founder describes releasing the entire staff and dismantling the Canadian operation. |
| Roadmap Continuity | Transparent product roadmaps, predictable release cycles, and a proven release train supported by comprehensive release notes, deprecation guidance, and documented upgrade paths, giving organizations confidence in long-term planning and platform continuity. | Customers have navigated multiple platform transitions and product direction changes over time. While innovation continues, organizations may face greater uncertainty around long-term product continuity, migration requirements, and future platform strategy. |
| Path Beyond the Interface Engine | Composable path to a broader healthcare data and AI platform. Organizations can extend Health Connect with InterSystems technologies including a FHIR repository, healthcare data management, analytics, API management, embedded Python, AI capabilities, and cloud-scale infrastructure, while also deploying components independently based on business needs. | Primarily focused on integration and message orchestration. Organizations seeking capabilities such as a FHIR repository, healthcare data platform, analytics, or AI-enabled solutions typically need to incorporate additional technologies, platforms, or custom-built components beyond the interface engine. |