What the source record establishes
Interfaceware's Iguana is a healthcare integration engine for building, transforming, routing, and monitoring interfaces and APIs across clinical and business systems.
The maintained taxonomy connects that documented market position to C-CDA Document Exchange. This page keeps the claim at the level supported by the source: Interfaceware Iguana presents an offering relevant to this work. It does not silently convert a product description into an observed result, a conformity finding, or a universal recommendation.
Current fit signal: Integration teams seeking a configurable engine with strong scripting control should evaluate Iguana's current protocol, deployment, and support scope.
What C-CDA document exchange means in this market
C-CDA Document Exchange should be evaluated as an operating chain rather than a feature label. The chain begins with a named business condition and governed input, passes through configured logic and accountable review, produces an output or action, handles exceptions, and preserves enough evidence for another person to reconstruct the decision later.
Information access, blocking, and workflow use
Risk that organizations cannot deliver electronic health information in an authorized, timely, usable manner—or mistake technical delivery for satisfaction of access, exchange, use, clinical, or operational responsibilities.
Boundary: The publication does not decide whether a practice is information blocking or whether a particular access request must be fulfilled in a stated manner.
Semantic integrity and terminology
Risk that data move successfully but lose or distort meaning because codes, units, value sets, local terms, context, negation, status, and version provenance are incomplete or transformed incorrectly.
Boundary: A terminology map is evidence for a transformation, not an independent clinical decision or guarantee that the receiving workflow interprets the result correctly.
Data quality, completeness, and provenance
Risk that exchanged information lacks source, time, status, authorship, context, completeness, or transformation history, preventing the receiving organization from evaluating whether and how to use it.
Boundary: A source can document data availability or mapping; it does not prove clinical completeness, correctness, or use in the receiving workflow.
Activities that may sit inside the review
- request intake
- actor and EHI scope
- manner of fulfillment
- fees and licensing
- exceptions
- patient access
Who owns the decision
A capability can be technically available while operating ownership remains fragmented. The evaluation should name the person accountable for policy or business interpretation, the person responsible for configuration and data, the reviewer with authority to resolve exceptions, the approver of release or action, and the owner of monitoring and retirement.
Related domain records commonly place responsibility with health information management, compliance and legal, patient access, interoperability operations, clinical informatics. The local operating model may assign those roles differently, but it should not leave them implicit.
Interfaceware Iguana should be asked to distinguish what the product decides, what it recommends, what it merely displays, and what remains an organizational judgment. A generic “human in the loop” statement is inadequate unless the human has time, context, evidence, and authority.
Evidence package to request from Interfaceware Iguana
- The exact product and package proposed, with a dated list of native, integrated, partner, service, and customer-owned components.
- A representative input set, its authoritative source, permitted use, quality checks, and version history.
- The configured workflow from intake through review, exception, approval, action, retention, and export.
- A normal result and at least two difficult exceptions, including one caused by missing or contradictory evidence.
- Role and access definitions for configuration, review, approval, override, monitoring, and administration.
- An implementation map naming integrations, migrations, customer work, provider work, services, test environments, and release gates.
- A retained decision record showing source, logic or model version, user action, timestamps, disposition, and downstream effect.
- A measurement plan with baseline, observation period, population, error threshold, exclusions, and stop condition.
Demonstration script
- Which exact Interfaceware Iguana product, edition, module, service, and geography support C-CDA document exchange?
- What source data, content, rules, and integrations does Interfaceware Iguana require before the workflow can begin?
- Where does human judgment enter, and which person can approve, reject, override, or stop the C-CDA document exchange workflow?
- How does the proposed configuration handle missing data, conflicting evidence, changed rules, and an expired or revoked approval?
- What record preserves inputs, transformations, user actions, exceptions, outputs, timestamps, and downstream consequences?
- Which parts are native, partner-delivered, service-delivered, or left to the customer?
- What can be exported at implementation, audit, renewal, migration, and exit?
- Which observation would falsify the current fit hypothesis for Interfaceware Iguana?
- Which actor, data, requester, and requested manner are in scope?
- How are requests tracked from receipt through delivery or exception?
- What technical and policy alternatives are available?
- How is the receiving party able to interpret and use the information?
Use the same scenario with every finalist. Let the provider explain differences in architecture, but keep the business condition, required evidence, exception, and expected decision record constant. That makes the evaluation comparable without pretending that unlike products should receive one synthetic score.
Failure modes and boundary conditions
- automatic legal conclusions
- all delays labeled information blocking
- API availability treated as actual use
- one universal normalized model
- clinical correctness inferred from a mapped code
- silent replacement of historical terminology
Customer-built channels and scripts create implementation-specific behavior. Public product descriptions do not establish the quality, maintainability, security, or conformance of a particular interface estate.
A buyer should also distinguish absence of public evidence from evidence of absence. If Interfaceware Iguana has not publicly documented a required detail, the correct status is “not established in this review” until a current, attributable source or direct observation resolves it.
Authority and standards context
The Direct Standard Version 1.3
Direct remains a durable push-exchange path for referrals, transitions, notifications, and document delivery. Buyers should distinguish messaging capability, address discovery, trust participation, workflow integration, and delivery evidence.
Interpretation boundary: A Direct address or HISP connection does not establish that the recipient will reconcile the information, that the document is complete, or that the disclosure is authorized.
This mapping identifies a workflow that may help organize evidence. It does not state that Interfaceware Iguana conforms to, complies with, or is certified against the authority.
USCDI v6
USCDI version determines the content baseline around which profiles, certification, mapping, and exchange programs are designed. Buyers should demand a version-aware roadmap and evidence for missing or newly added elements.
Interpretation boundary: USCDI identifies data classes and elements; it does not by itself specify one transport, guarantee data availability, or establish clinical completeness.
This mapping identifies a workflow that may help organize evidence. It does not state that Interfaceware Iguana conforms to, complies with, or is certified against the authority.
QTF v2.1
Organizations should distinguish QHIN-level technical duties from the services a QHIN exposes to Participants and the separate interfaces a participant uses internally.
Interpretation boundary: A QTF reference does not establish that a non-QHIN product is certified or that a participant's downstream workflow conforms.
This mapping identifies a workflow that may help organize evidence. It does not state that Interfaceware Iguana conforms to, complies with, or is certified against the authority.
Comparable records to inspect
The following organizations also have current official positioning mapped to C-CDA document exchange. Inclusion is a research pathway, not a shortlist or claim of equivalence.
- Infor Cloverleaf — Enterprise Interoperability And Integration Platform with documented positioning relevant to C-CDA Document Exchange
- InterSystems HealthShare — Enterprise Interoperability And Integration Platform with documented positioning relevant to C-CDA Document Exchange
- NextGen Mirth Connect — Enterprise Interoperability And Integration Platform with documented positioning relevant to C-CDA Document Exchange
- Qvera — Enterprise Interoperability And Integration Platform with documented positioning relevant to C-CDA Document Exchange
- Redox — Enterprise Interoperability And Integration Platform with documented positioning relevant to C-CDA Document Exchange
- Rhapsody — Enterprise Interoperability And Integration Platform with documented positioning relevant to C-CDA Document Exchange
Official authority sources
The following primary authority pages support the standards context used in this record. They define an evaluation boundary; they do not endorse Interfaceware Iguana or establish product conformity.
The Direct Standard Version 1.3
Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.
USCDI v6
Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.
QTF v2.1
Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.
Conditional conclusion
Interfaceware Iguana belongs in deeper evaluation for C-CDA document exchange when its documented enterprise interoperability and integration platform operating model matches the buyer's real workflow, the proposed package contains the required components, and a representative test produces reviewable evidence through normal and exception paths. The conclusion should be reversed or narrowed when the product boundary, source data, authority mapping, integration burden, human decision rights, exportability, or measured result does not meet the stated approval conditions.