01Healthcare integration engines
Mirth Connect (NextGen)
A widely used healthcare integration engine for HL7, FHIR and DICOM, supplied by NextGen Healthcare.
Best for: Hospital and vendor interfaces.
Visit Mirth Connect (NextGen) →Healthcare Integration Engines
Engines and platforms for exchanging clinical and administrative data between healthcare systems: HL7 and FHIR integration engines, FHIR servers, cloud health data services and interoperability APIs.
27solutions
5Categories
6FAQs answered
02Healthcare integration engines
Rhapsody
Rhapsody's integration engine and interoperability platform, supporting HL7, FHIR and other protocols.
Best for: Large health systems.
Visit Rhapsody →03Healthcare integration engines
Corepoint
A healthcare integration engine, now part of Rhapsody, known for template-based interface building.
Best for: Interface teams that need quick setup.
Visit Corepoint →04Healthcare integration engines
InterSystems HealthShare
InterSystems' health information exchange and interoperability platform built on its IRIS technology.
Best for: Regional and national data exchange.
Visit InterSystems HealthShare →05Healthcare integration engines
InterSystems IRIS for Health
A data platform with built-in HL7 and FHIR interoperability, the successor to Ensemble.
Best for: Building health apps and interfaces.
Visit InterSystems IRIS for Health →06Healthcare integration engines
Iguana (iNTERFACEWARE)
An integration engine that uses a scripting approach to build and run healthcare interfaces.
Best for: Developer-oriented interfaces.
Visit Iguana (iNTERFACEWARE) →07Healthcare integration engines
Qvera Interface Engine
A healthcare integration engine for HL7, FHIR and other standards, with a web-based designer.
Best for: Small and mid-size organisations.
Visit Qvera Interface Engine →08Healthcare integration engines
Orion Health
A digital health company offering interoperability and health data platforms.
Best for: Population health and data exchange.
Visit Orion Health →09FHIR servers & platforms
Smile CDR
A FHIR-based clinical data repository and interoperability platform from Smile Digital Health.
Best for: Enterprise FHIR platforms.
Visit Smile CDR →10FHIR servers & platforms
HAPI FHIR
An open-source Java implementation of the HL7 FHIR standard, with a server and client libraries.
Best for: Open-source FHIR servers.
Visit HAPI FHIR →11FHIR servers & platforms
Firely
FHIR tools and servers from Firely, including the Firely Server and the .NET SDK.
Best for: FHIR on .NET.
Visit Firely →12FHIR servers & platforms
Medplum
An open-source, FHIR-based platform for building healthcare apps, with a hosted option.
Best for: Developer-led health apps.
Visit Medplum →13FHIR servers & platforms
Aidbox
A FHIR server and data platform from Health Samurai.
Best for: FHIR-first data platforms.
Visit Aidbox →14FHIR servers & platforms
LinuxForHealth FHIR Server
An open-source FHIR server, originally the IBM FHIR Server, now maintained by the LinuxForHealth community.
Best for: Self-hosted open-source FHIR.
Visit LinuxForHealth FHIR Server →15FHIR servers & platforms
Microsoft FHIR Server
Microsoft's open-source FHIR server, which underpins its Azure Health Data Services.
Best for: Azure-aligned FHIR deployments.
Visit Microsoft FHIR Server →16Cloud health data services
Azure Health Data Services
Microsoft's managed services for FHIR, DICOM and medical-device data in the cloud.
Best for: Microsoft-based health data.
Visit Azure Health Data Services →17Cloud health data services
AWS HealthLake
An AWS service for storing, transforming and analysing health data in FHIR format.
Best for: FHIR data lakes on AWS.
Visit AWS HealthLake →18Cloud health data services
Google Cloud Healthcare API
A Google Cloud service for storing and exchanging HL7v2, FHIR and DICOM data.
Best for: Healthcare data on Google Cloud.
Visit Google Cloud Healthcare API →19Interoperability APIs & networks
Redox
An interoperability platform that connects healthcare organisations and software vendors through one integration.
Best for: Vendors connecting to many EHRs.
Visit Redox →20Interoperability APIs & networks
Particle Health
An API platform for retrieving patient records from national health information networks.
Best for: Pulling patient records via APIs.
Visit Particle Health →21Interoperability APIs & networks
1upHealth
A FHIR API platform for healthcare data access and payer interoperability.
Best for: Payer and provider FHIR APIs.
Visit 1upHealth →22Interoperability APIs & networks
Health Gorilla
A health data network and API platform for clinical data exchange.
Best for: Exchange of clinical data.
Visit Health Gorilla →23Interoperability APIs & networks
Kno2
A platform for exchanging clinical documents and connecting to interoperability networks.
Best for: Document exchange.
Visit Kno2 →24Interoperability APIs & networks
ELLKAY
Interoperability and integration services, including an integration platform for healthcare data.
Best for: Managed integration services.
Visit ELLKAY →25Interoperability APIs & networks
Datavant
A data connectivity company providing tools to link and exchange health data while protecting privacy.
Best for: Privacy-preserving data linkage.
Visit Datavant →26Payer & administrative integration
Edifecs
Payer-focused interoperability and EDI software for claims, enrolment and FHIR APIs.
Best for: Payer data exchange.
Visit Edifecs →27Payer & administrative integration
Innovaccer
A healthcare data platform that connects and unifies data from many sources for care and payer use cases.
Best for: Unified health data for analytics.
Visit Innovaccer →Choosing the right approach
Match your requirement to a starting point, then compare vendors.
| Connect hospital systems with HL7 | A healthcare integration engine such as Rhapsody, Mirth or Corepoint |
|---|---|
| Build new apps with FHIR | A FHIR server, hosted or open source |
| Already on a major cloud | Its health data service: Azure, AWS or Google Cloud |
| Connect to many EHRs | An interoperability API platform such as Redox or Particle |
| Payer data exchange | Payer-focused interoperability and EDI software |
| Tight budget | Open-source options such as HAPI FHIR, Medplum or LinuxForHealth |
Related pages on PeterIndia.net
Neighbouring directories and hubs.
AI Healthcare RCM SolutionsAI for coding, denials and billing.Integration TechnologiesThe integration hub.ESB and Managed File TransferMessaging and file transfer.Process Integration SolutionsProcess hub.iPaaS and EAI PlatformsConnect applications.API Management Platforms and GatewaysManage APIs.B2B Integration PlatformsEDI and B2B.Data Integration, ETL and CDC ToolsMove and transform data.Middleware SoftwareMiddleware overview.Internet of Medical Things (IoMT)Connected devices feeding health data.Medical InformaticsMedical informatics links.
Frequently asked questions
Quick answers.
What is a healthcare integration engine?
It is middleware that receives, transforms, routes and monitors messages between healthcare systems such as electronic health records, labs and imaging, mainly using HL7 v2, FHIR and DICOM.
What is the difference between HL7 and FHIR?
HL7 v2 is the long-established message format used inside hospitals. FHIR is a newer standard based on web APIs and resources that suits modern apps and data exchange.
Do I still need an integration engine if I use FHIR?
Often yes. Many systems still send HL7 v2 and other formats, so an engine translates and routes between old and new interfaces and monitors delivery.
Engine, FHIR server or cloud service?
An engine moves and transforms messages between systems. A FHIR server stores and serves FHIR data through an API. Cloud services provide managed FHIR storage and APIs. Many deployments combine them.
What should I check when choosing?
Check protocol support, throughput, monitoring, security and compliance such as HIPAA, support for FHIR and terminology mapping, deployment options and the vendor's long-term support.
Is any of this open source?
Yes. HAPI FHIR, Medplum and the LinuxForHealth FHIR server are open source. Mirth Connect was open source for many years but newer versions are offered commercially, so check the current licence.
Descriptions summarise each vendor's or project's own positioning, checked on 5 October 2026. Product names and offerings change often, so confirm details on the linked site before deciding.