IGUANA INTEGRATION ENGINE

Build and own your FHIR integrations with Iguana

Connect EHRs and healthcare systems using FHIR APIs with a developer ready engine. Iguana connects to any FHIR server while giving you full control over how data is requested, transformed, and delivered.

  • Iguana functions as a FHIR client
  • FHIR R4, JSON, XML, HL7 v2
  • Epic, Oracle (Cerner), eCW, Athenahealth, and more
Request a Demo
Connect any System with Iguana Capterra, G2, and KLAS rated

Iguana for FHIR API integration

A developer first engine that lets you build, run, and scale FHIR integrations without vendor lock in.

Connect to any FHIR server
Securely retrieve, post, and update FHIR resources through external API endpoints.
FHIR-ready and code-driven
Parse and transform FHIR JSON, XML, and HL7 v2 with Iguana's code-based development environment.
Secure and reliable
Protect every exchange with strong authentication, encryption, and trusted performance.
Designed for developers
Give technical teams full control to code, customize, and manage their integrations.

FHIR integration with EHRs, Labs, etc.

Iguana powers mission critical FHIR integrations for providers, labs, and vendors to connect to any healthcare system:

Customer Testimonial

“FHIR gave us a standard, but each environment still had its own nuances, from authentication to resource requirements...

Iguana let us adapt without adding complexity, handle edge cases, and keep everything maintainable. Iguana is now the foundation of our FHIR integrations.

How Iguana Stands Apart

Different integration needs call for different solutions.

Iguana is optimal for organizations that need to tailor complex workflows, scale with confidence, and maintain full ownership over their infrastructure.

vs. Drag & Drop Tools
vs. Managed Services
Interfaces
Code-first, dev-owned
For teams who write & maintain integrations
Visual, no/low-code
Built for speed, not scripting
Fully outsourced
Vendor built and maintained interfaces
Flexibility
Fully customizable
Custom scripting logic, complex workflows
Limited by templates
Adapters for select systems only
Dependent on vendor
Custom work requires vendor support
Control
You own everything
Build, deploy, and update on your terms
Abstracted layer
Limited visibility into logic or processing
Vendor-managed
Changes require tickets or support cycles
Deployment
Cloud, on-prem, or hybrid
Build, deploy, and update on your terms
Often Cloud-based
Potentially limited deployment options
Vendor-hosted only
No deployment considerations required
Best Fit For
Full control and scalability
Ideal for complex or growing environments
Simple integration needs
Works well for basic point-to-point cases
Non-technical teams
Best when outsourcing is a strategic choice
Some teams prefer no-code or managed options, and that's okay.
But if flexibility, visibility, and long-term ownership matter to you, let's talk.

Why Every FHIR Integration Is Different

Important

FHIR integrations aren't as plug-and-play as they seem

On paper, FHIR promises standardized APIs for healthcare data exchange. In practice, every FHIR implementation is different — from authentication and security requirements to implementation guides, extensions, and performance constraints. Those differences can introduce real complexity when you're trying to build reliable, production-grade interfaces.

How Iguana Works With FHIR

Vendors, providers, and payers all implement FHIR slightly differently. Successful integrations need to respect those differences instead of assuming every FHIR server behaves the same.

Common FHIR integration challenges
  • Implementation guides and profiles differ by organization, each with unique required elements and constraints.
  • Authentication and security models (OAuth2, SMART-on-FHIR, scopes, tokens) can be complex to implement, and vary between FHIR servers.
  • Custom extensions, value sets, and resource relationships change from one environment to another.
  • Operational constraints like rate limits, pagination, and maintenance windows impact how you design integrations.
How Iguana addresses these challenges
  • Iguana’s code-based engine lets you support any system requirements or custom FHIR resource logic without template constraints.
  • Pre-built FHIR adaptors help to abstract OAuth2 authentication and token lifecycles, jumpstarting your FHIR integration.
  • Support for extensions and custom mappings allows you to normalize or transform data for each target system.
  • Built-in functions for REST API calls, and scripting help you manage retries, throttling, batching, and monitoring for production workloads.
How Iguana Works With FHIR

1. Ingest Data

Iguana can ingest any data format, such as HL7v2, and transform the data to appropriate FHIR Resources based on the FHIR specification.

2. Authenticate

Iguana can authenticate with the FHIR Server, supporting industry standards like OAuth2.0.

3. RESTful API Interactions

Iguana can perform different operations against the FHIR Server (ex. GET, PUT, POST, DELETE) to send and receive FHIR resources.

4. FHIR Version Support

Iguana can support any version of the FHIR Standard (STU3, R4, etc.), ensuring compliance with the evolving standard.

Future-proof your integrations with FHIR-based interfaces.

Speak With an Expert Today

Trusted by 800+ Healthcare Providers & Vendors

From hospitals to health tech companies, organizations worldwide choose Iguana for its unmatched flexibility, reliability, and expert support.

Testimonials via Capterra and G2
Very Versatile Integration Engine
"The availability of various inputs and outputs gives Iguana limitless possibilities for implementing integrations between third-party systems and local databases."
Artur L.
Easy Set Up, Reliable, Outstanding Support
"What I like most is the flexibility in creating and updating custom interface channels. Great support, very reliable, and easy to troubleshoot."
Ron C.
Iguana Is Unmatched
"In one word: flexibility. We work with HL7, EDI, FHIR, APIs, CSVs, etc. There is very little we have run into that we could not accomplish with Iguana."
Chris A.
Clean Look, Intuitive Functionality
"Iguana is powerful in its simplicity. It enables seamless data integration between our EMR and pharmacies, labs, clearinghouses, and more."
George O.
Iguana is Easy to Use and Manage
"We process over 20 million HL7 messages daily across 2,500+ channels. Iguana has been stable, reliable, and high-performing for over a decade."
Josh M.
Reusable Integrations, Configurable Endpoints
"We reuse integration code with endpoints like HTTPS, LLP, SFTP, and files. We can deploy integrations to multiple agencies with simple configuration changes."
Michael G.

Ready to Experience Iguana for Yourself?

Contact Us Today

Is Iguana Right for You?

Great Fit If You...
Have in-house development or integration staff
Build custom integrations with healthcare systems
Want control over data formats and workflows
Prioritize reliability and control in integrations
Need a platform that scales with your architecture
Might Not Be a Fit If You...
Need a no-code or drag-and-drop tool
Just need a basic one-off connection
Don't want to manage or maintain integrations
Prefer a fully hands-off managed service
Just need a short-term or simple solution
See a fit? Let's connect and explore what Iguana can do for you.
CONTACT US

Ready to Explore Iguana?

Tell us your integration goals, and we'll show you how Iguana can help you build the solutions you need.

Talk to a FHIR Integration Expert

We'll help you explore how Iguana fits your integration environment — and what a modern FHIR strategy could look like.

FAQ

Does Iguana support FHIR?

Yes. Iguana fully supports FHIR — both the FHIR data model (resources like Patient, Observation, Encounter, etc.) and the FHIR RESTful API standard. With Iguana, you can ingest, transform, and route FHIR resources just like any other data format, and integrate them into your broader healthcare ecosystem.

Can Iguana act as a FHIR client?

Absolutely. Iguana can function as a FHIR client to retrieve or submit resources to FHIR servers, such as the Epic FHIR API. This makes it ideal for pulling data from external systems or synchronizing data across FHIR-enabled services. However, Iguana is not a FHIR server — it doesn’t expose a FHIR API for external systems to query directly.

Can Iguana translate FHIR to and from other healthcare data formats?

Yes. Iguana is purpose-built for data format transformation. You can parse and generate FHIR resources in JSON or XML, and convert them to/from formats like HL7 v2, CDA, X12, CSV, or even custom data formats. This flexibility can be crucial for bridging modern FHIR APIs with legacy systems.

What tools does Iguana offer to help connect with FHIR APIs like Epic’s?

One of the most popular FHIR components included with Iguana is the Epic FHIR Adapter. It provides a ready-to-use framework for authenticating with Epic’s FHIR API using OAuth 2.0 and JWT, and makes it easy to perform common interactions like create, read, search, and other extended operations.

The adapter handles token management securely and comes with sample scripts for creating and querying Patient resources, so developers can quickly get started without needing to build the authentication and API logic from scratch.

Because it's fully customizable, teams can adapt it to fit their specific Epic workflows while still maintaining full control within the Iguana Translator environment.

Can Iguana help with building or validating FHIR resources?

Yes. Iguana includes a FHIR Resource Creator module that makes it easier to construct standards-compliant FHIR resources in Lua, whether you’re generating them from scratch or transforming data from another format like HL7 v2.

For validation and profiling, the FHIR Profiling Tool helps ensure that the FHIR resources you’re working with conform to your organization’s implementation guide or required structure.

Does Iguana come with pre-built FHIR adapters or "plug-and-play" integrations?

Iguana isn’t a plug-and-play platform in the traditional sense — it’s designed for teams that want full control over their integrations. However, Iguana does come with reusable components that significantly reduce development time for common FHIR workflows. These aren’t black-box connectors, but rather well-documented modules your team can adapt and extend as needed.

Will my team need to write code to work with FHIR in Iguana?

Yes. Iguana uses Lua scripting in its Translator environment to build and manage FHIR integrations — including authentication workflows, API calls, and FHIR resource transformations. While the platform takes care of boilerplate tasks like HTTP requests and JSON parsing, your team will still write and maintain scripts to define the logic of each interface. This code-based model gives you full flexibility to work with any FHIR resource, endpoint, or data mapping scenario — without the limitations of plug-and-play tools.

If FHIR integration in Iguana requires code, will we be on our own?

Not at all. While Iguana gives you the flexibility to script custom FHIR integrations, it also provides the tools and support to make development efficient and approachable. You’ll have access to pre-built components (like our Epic FHIR Adapter, FHIR Profiling Tool, and FHIR Resource Creator), shared code libraries, and intelligent development features such as autocompletion, real-time debugging, and live output previews. And if you need help, our expert support team is always available whenever you need guidance.

Does iNTERFACEWARE provide managed FHIR integration services?

No, iNTERFACEWARE does not provide a managed integration service. We offer Iguana, a self-hosted integration engine that puts your team in full control. You develop, deploy, and maintain your integrations internally, using Iguana's platform and tools. This model gives you long-term flexibility, eliminates vendor lock-in, and ensures that integration capabilities grow alongside your organization's needs.

Who typically uses Iguana for FHIR integration?

Iguana is designed for teams that want to build and manage their own integrations — typically healthcare software vendors, hospital IT departments, and developers.

To use Iguana effectively, you’ll need access to a developer or technical team. It’s a code-based platform, so programming is required. If you’re new to FHIR, we offer coding templates and tools can help you get started. But if you don’t have technical resources in-house or through a partner, Iguana likely won’t be the right fit.

What kind of support can I expect from iNTERFACEWARE?

You can expect responsive and knowledgeable support from a team that understands FHIR integration. We provide email and phone support, detailed documentation, and training resources to help your team succeed. For more hands-on help, our professional services team is available to assist with specific projects or ongoing needs.

Whether you're exchanging data through FHIR APIs, working with FHIR resources, (or other formats and protocols), we're here to help guide you through the process. Many of our customers cite the quality of our support as one of the main reasons they chose Iguana.

The all-in-one integration platform by iNTERFACEWARE.
G2 - Healthcare Integration Engines
Rated 4.5/5
4.5/5 on G2
Capterra - Integration Software
Rated 4.8/5
4.8/5 on Capterra
KLAS - Integration Engines
KLAS Rated*
93.6/100
*Average performance score from 2017-2022 in the 'Best of KLAS' report
iNTERFACEWARE Inc.
© iNTERFACEWARE Inc.
Privacy | Terms of Service | MSA
General Inquiries
iNTERFACEWARE Inc.
2 Bloor Street East, Suite 3500
Toronto, Ontario   M4W 1A8   Canada
contact@interfaceware.com
1-888-824-6785
Follow Us: