InterSystems HealthShare and Iguana Integration Engine are both healthcare interoperability products, but they are not interchangeable. HealthShare is documented as a health informatics platform that creates a longitudinal, normalized patient record and supports strategic interoperability and analytics for action across a facility, region or nation [8]. Iguana is presented as a code-first integration engine for building, running and owning interfaces between EHRs, labs, payers and other systems [10]. A buyer deciding between them is therefore choosing between a governed shared-record platform and a developer-controlled integration toolkit. The comparison below separates vendor statements from unresolved questions and does not assign a winner.

Documented Workflow and Core Output

HealthShare's documented workflow centers on creating a Unified Care Record. InterSystems states that HealthShare aggregates data from care records, claims, devices and research participation into one consistent format, with normalization, deduplication and identity resolution [1][2]. The product data sheet describes a longitudinal health record that is updated in near real time and can feed clinical workflows, analytics, FHIR applications and machine learning [3]. The output is a patient-centric data model with consent management, not simply a set of routed messages.

Iguana's documented workflow is interface construction and operation. iNTERFACEWARE describes a Translator environment where developers parse inbound HL7, map fields, push messages to queues and write to databases or APIs using Lua [9]. The vendor states that Iguana functions as a FHIR client and can transform data between HL7 v2, CDA, X12, CSV and custom formats [10]. The output is a working integration owned by the customer's team, with no claim that Iguana itself maintains a longitudinal clinical record.

Organizational Setting and Customer Segment

InterSystems positions HealthShare for organizations responsible for health information sharing across a nation, region, community or single organization [1]. Documented examples include health information exchanges, health plans, providers and software developers [1][7]. The vendor's product terms describe HealthShare as supporting strategic interoperability and analytics for action within a single facility or across a local, regional or national healthcare system [8]. This suggests buyers that need a shared, governed record spanning multiple source systems and organizations.

iNTERFACEWARE describes Iguana as designed for developers and teams that write and maintain integrations [10][12]. The vendor's materials cite use by hospitals, EHR vendors, billing systems, HIEs and other healthcare systems, and state that Iguana is trusted by more than 800 customers globally [12]. The stated emphasis is on full ownership, custom scripting and deployment within existing infrastructure [9][10]. The segment is therefore organizations with integration engineering capacity that want control over data movement rather than a vendor-managed shared record.

A Suggested Evaluation Workflow

A delivery organization that already operates an EHR and needs to connect a lab system, a payer API and a legacy billing application could evaluate Iguana by building a small HL7-to-FHIR transformation in the Translator environment, then testing retries and monitoring against its own message volumes [9][10]. The same organization considering HealthShare would instead document whether it needs a deduplicated longitudinal record shared across affiliated clinics, with consent policies and near-real-time updates [3][5]. This suggested exercise is not a test protocol and does not establish product superiority; it is a way to make the documented workflow differences concrete before procurement. This suggested exercise is not a test protocol and does not establish product superiority; it is a way to make the documented workflow differences concrete before procurement.

Implementation Boundaries and Module Scope

HealthShare is a product family with defined solution and add-on products. InterSystems lists HealthShare Unified Care Record as the foundation, with HealthShare Care Community, Personal Community, Provider Directory, Health Insight and Health Connect as related products [2][8]. The terms state that HealthShare Solution products may not be used to build or run custom applications or be used outside their defined functional scope [8]. Some components have prerequisites: Personal Community and Health Insight require HealthShare Unified Care Record [8]. This creates a bounded, configurable platform rather than an open development environment.

Iguana's scope is the integration engine itself. iNTERFACEWARE supports two generations, Iguana 6 and IguanaX, and continues to support Chameleon [11]. The vendor describes pre-built components for HL7 servers and clients, file readers and writers, and database adapters, with native parsing for HL7, XML, X12 and JSON [9]. Iguana is positioned as system- and environment-agnostic, with deployment on premise, in cloud or hosted [9][12]. The vendor explicitly states that Iguana does not provide traditional plug-and-play EHR adapters, because site-specific EHR configurations make fixed adapters unreliable [9].

Technical Documentation and Standards Coverage

HealthShare documentation emphasizes standards-based data sharing and administration. InterSystems states that HealthShare supports FHIR R4 and STU3, HL7v2, X12 and multiple CDA formats, and can represent data as FHIR resources through a FHIR server [5]. The Management Portal is described as a centralized interface for user provisioning, SSO, consent policies, messaging configuration, monitoring and population-scale data management [3][5]. This documentation is oriented toward platform administrators and solution implementers managing a governed record.

Iguana documentation is developer-facing and code-centric. The vendor's FHIR page describes authentication with OAuth2, RESTful operations, FHIR version support and a FHIR Resource Creator module for constructing resources in Lua [10]. A FHIR Profiling Tool is described as helping ensure resources conform to an organization's implementation guide [10]. The main site lists product documentation, support and license resources, and emphasizes backward compatibility and gradual convergence between Iguana 6 and IguanaX [11]. The documentation focus is on building, testing and maintaining interfaces rather than administering a shared clinical data model.

Regulatory Positioning and Unresolved Questions

InterSystems markets Payer Services as addressing US regulatory requirements CMS-0057-F and CMS-9115-F, with FHIR R4 APIs implemented per recommended implementation guides including HL7 Da Vinci, PDex and CARIN [6]. This is a US-specific regulatory statement and should be kept separate from HealthShare's broader global marketing. The vendor also notes that referential matching through InterSystems EMPI is currently available for customers in the United States [8]. These statements describe documented product positioning, not independently verified compliance outcomes.

Several comparison questions remain unresolved in the supplied documentation. Neither vendor publishes pricing or license costs in these sources, though InterSystems describes subscription and paid-up license types [8]. The sources do not provide independent performance benchmarks or clinical outcome data for either product. Iguana's claim of 800-plus customers is a vendor statement without an audited denominator [12]. HealthShare's KLAS category leader references are vendor-cited and dated 2019 and 2020 [2]. Buyers should request current references and validate regulatory conformance for their specific jurisdiction and use case.