Integrating with Epic, a leading EHR in healthcare, can be complex. We simplify the process with the Iguana Integration Engine.
Start creating seamless connections to Epic Systems, regardless of interface type: HL7v2, HL7v3, FHIR, Web Service, X12 and more.
At iNTERFACEWARE, we understand the challenges of integrating with Epic.
With the Iguana Integration Engine has comprehensive support of all Epic interface types. We eliminate complexity and ensure that your systems are compatible. This enables smooth data exchange between your systems and Epic.
Don't dive right into the technical aspects of integrating with Epic. Consider the following crucial factors to effectively plan and execute the integration:
Determine the Integration Direction
Are you accessing patient information from Epic or sending it to Epic? Understanding the direction of integration will help shape the integration strategy.
Identify the Data Type
Different data formats often require specific transport protocols and have distinct endpoints. Clearly define the type of patient data (message format) you will be integrating to ensure seamless data exchange.
Obtain the Epic Implementation Guide
The implementation guide from Epic is a vital resource for successful integration as it provides essential technical specifications. It outlines the data format – understanding the data types and structure is essential for navigating messages and mappings.
It also provides the required transport protocols and security considerations. This outlines how you will exchange and encrypt data, and how you will authenticate. Lastly, you can obtain sample data to aid in building the interface.
The Epic implementation guide serves as your roadmap, guiding you through the integration process. You must know how to define the data types, structures, mappings and transport protocols. Then you’ll be able to configure and build the interfaces required to connect to Epic systems.
When connecting to Epic, there can be many options. These are highly dependent on your situation and the implementation guide for your specific use case. The Iguana integration engine supports various connection components, making it easier to integrate with Epic's EHR systems.
Iguana effortlessly handles Epic EMR integration and can support your integration, whatever your requirements are. Connect with an HL7 feed, batch files, custom APIs or database connections:
Message FeedTCP/IP (LLP) |
TCP/IP is one of Epic's most commonly used protocols. TCP/IP is widely-used for the transfer of a stream of HL7 messages via an LLP feed. The interface can function as a server, listening on a port for data from Epic. The interface can also function as a client, sending data from your desired source to Epic. Iguana simplifies the setup process by providing prebuilt LLP source and destination components that ensure quick and straightforward integration. |
|
Batch FilesSFTP |
SFTP enables you to connect to Epic when intermittently transfering individual files and batches of files. When connecting via SFTP, your interface can pull files from Epic’s SFTP server, or send files to that server. Iguana offers prebuilt File source and destination components that enable seamless SFTP connections with Epic. This component handles effortless file exchange from any local directory. |
|
HL7 FHIR APIsHTTPS (Web Services) |
As healthcare interoperability embraces HL7 FHIR and web services, HTTPS connections are increasingly vital when integrating with Epic. You may need to connect via an API when requesting FHIR resources or any data format like JSON or XML. For example, a patient portal that is a FHIR-based health app would require a FHIR API to connect with Epic. Iguana provides an HTTPS component for seamless Epic FHIR integration and API integration. Iguana has prebuilt modules for web service authentication and requests. Whether you're pulling data from Epic or sending data to Epic via APIs, Iguana simplifies the connection and allows you to precisely customize your API integration. |
|
DatabaseOCI/ODBC |
Iguana offers a convenient solution to access data from Epic's database. Our pre-built Database Connection module provides a reliable and simplified process. Connect to any database via OCI and ODBC. This module automatically handles database connections and re-connections, and improves performance by keeping the connection open between queries. Leverage the power of Iguana's Database Connection module to seamlessly connect to Epic's database. Efficiently retrieve the information you need. |
|
By using the Iguana integration engine to integrate with Epic, you will benefit from:
Don't let the complexity of integrating with Epic hold you back. Utilize the power of the Iguana integration engine to facilitate the creation of interfaces and seamlessly connect with Epic.
Integrating with Epic can be daunting but we are here to walk you through it:
Is iNTERFACEWARE a service-based integration provider?
No, we’re not a service that builds Epic integrations for you. iNTERFACEWARE provides Iguana, an integration engine that gives your team the tools to build, manage, and maintain your own interfaces.
Unlike service-based models where a third party handles the integration work, Iguana puts you in control. This gives you the flexibility to meet system-specific requirements, make real-time changes, and avoid delays or dependencies on external vendors.
Many organizations choose Iguana because it offers greater visibility, customization, and scalability — especially when working in complex or evolving environments.
Who typically uses Iguana for Epic 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 healthcare standards (like FHIR, HL7, etc.), our 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.
Do you offer out-of-the-box integration with Epic?
Not exactly, but that’s by design. Instead of rigid, pre-built adapters, Iguana provides a flexible, code-based framework that empowers your team to build the exact integration you need.
We offer a pre-built Epic FHIR Component and a comprehensive collection of other Component templates to accelerate your development, but every implementation can be customized to your specific Epic instance and use case.
Why don't you offer plug-and-play Epic integration?
Because plug-and-play rarely works in practice. Even with so-called "universal" Epic adapters, integration usually breaks down due to system-specific configurations, workflow differences, and evolving requirements.
Iguana gives you full access to the code, so you can adapt and control every part of your interface — now and in the future.
How does Iguana connect to Epic?
Iguana supports connections via FHIR APIs, HL7 (over LLP), SFTP, and database connections — all common methods used by Epic. Our Epic FHIR Component provides a pre-built template as a guiding framework, handling authentication and core API operations, so your team can build interfaces faster.
What Epic interfaces can Iguana support?
Iguana can support FHIR APIs, HL7 messages (via LLP), flat files (via SFTP), and database connections — the common methods Epic uses to exchange data. Whether you're dealing with patient demographics, orders and results, billing data, or custom workflows, Iguana provides the tools to support those integrations.
Do I need to write code to integrate with Epic using Iguana?
Yes, and that's a benefit. It's a developer-centric platform that gives you full control and visibility by letting you write your own code in Lua, a lightweight scripting language that's easy to learn. You won't be starting from scratch though - our pre-built Components (like the Epic FHIR template) do much of the heavy lifting. Plus, Iguana's Translator IDE includes features like autocomplete, inline documentation, and live debugging to make development faster and easier.
How does Iguana's Epic FHIR Adapter help?
Our Epic FHIR Adapter is a pre-built Iguana Component that handles the OAuth2 authentication and core FHIR API operations required to work with Epic. It significantly reduces the time and complexity involved in connecting to Epic’s backend services, while still giving you the flexibility to adapt it to your needs.
Can Iguana integrate with any Epic environment (e.g., hospital-specific instances)?
Yes. Each Epic environment may have its own configuration, endpoints, and access rules. Iguana's flexible architecture allows you to adjust your interface code to meet those specifics, making it ideal for real-world Epic implementations.
How does Iguana differ from other integration tools?
While many integration tools rely on visual workflows (like drag-and-drop) or managed platforms, Iguana takes a developer-first approach — giving you direct control over your integration logic and data flows.
There are no “black boxes”. With full visibility and access to the code, you can fully customize each interface and build reusable modules for consistency and scale.
Many organizations choose Iguana after outgrowing simpler tools or looking to reduce long-term maintenance costs by owning their integration stack.
Is Iguana only for Epic integration?
Not at all. While we provide tools and templates to make Epic integration easier, Iguana is a universal integration engine designed to connect with any system (EHRs, LIS, RIS, databases, cloud apps, and more), through common transport methods like APIs, HL7, SFTP, and ODBC.
What kind of support can I expect from iNTERFACEWARE?
You won't be left on your own. iNTERFACEWARE provides responsive email and phone support, in-depth technical documentation, and access to optional Professional Services for more hands-on help.
Whether you need guidance building your first interface, developing a proof of concept, or solving a complex integration challenge, our team is here to assist. Many of our customers cite the quality of our support as one of the main reasons they chose Iguana.
