The Qvera Interface Engine (QIE) is a strong fit for Rhapsody and Corepoint teams that want one license to cover the whole product: the full capabilities of the engine, with production, test and developer licenses included, high availability included on every licensing model, and DICOM networking in the same engine as HL7 and FHIR. Rhapsody’s JavaScript filters port to QIE’s JavaScript scripts, Corepoint builds are recreated in QIE’s channel editor, and Qvera engineers are available to assist with the move. QIE is in production today at more than 600 sites, running more than 25,000 interfaces and processing more than 50 million messages a day.
Six things Rhapsody and Corepoint teams ask about when they evaluate an alternative:
Yes. Rhapsody and Corepoint configurations map onto QIE’s channel model, and Qvera engineers are available to assist your team with moving the interfaces, one at a time, so messages keep flowing while each one is checked.
A Rhapsody or Corepoint team has three choices:
Rhapsody and Corepoint cells come from Rhapsody’s own product pages, brochures, trust center and AWS Marketplace listings, reviewed on 8 October 2026. Rhapsody’s product documentation is behind a customer login, so “not published” means nothing was found in its public material, not that the feature is proven absent.
| Building interfaces | QIE | Rhapsody Integration Engine | Corepoint Integration Engine |
|---|---|---|---|
| How an interface is built | Channel editor: receiver, mapping, condition and destination nodes | Rhapsody IDE, a Windows application: routes built from communication points and filters, drag and drop | Menu-driven graphical builds, “no-code-required” in Rhapsody’s words |
| Scripting language | JavaScript, which can call Java libraries | JavaScript filter; custom components in Java (Rhapsody Development Kit) | None required, per Rhapsody |
| Testing with sample messages | ✓ step-by-step testing with sample messages | ✓ built-in testing of transformations with multiple scenarios; filter-testing APIs for continuous integration | ✓ test-as-you-develop, with a test message manager |
| AI assistant in the product | ✓ AI Companion, with every license | ✓ Rhapsody Axon, “no separate product to purchase or install” | ✓ Rhapsody Axon |
| Standards | QIE | Rhapsody Integration Engine | Corepoint Integration Engine |
| HL7 v2 | ✓ | ✓ | ✓ |
| HL7 v3 and CDA | ✓ | ✓ | ✓ |
| FHIR | ✓ as a client and producer, JSON and XML, OAuth 2.0 | ✓ conversion between FHIR XML and JSON, mapping to other standards | ✓ listed |
| X12 and NCPDP | ✓ | ✓ | ✓ |
| DICOM networking (store, query, retrieve, verification, worklist) | ✓ in the engine | DICOM listed as a message format; filters convert DICOM to XML; image routing is a separate product, Image Director | DICOM listed; the DICOM Gear extension turns DICOM headers into HL7 orders; image routing is the separate Image Director |
| DICOM header de-identification | ✓ | not published for the engine | not published for the engine |
| Running the engine | QIE | Rhapsody Integration Engine | Corepoint Integration Engine |
| Database the engine needs | Microsoft SQL Server, MySQL or MariaDB | not published | Microsoft SQL Server (ONC disclosure) |
| Windows, Linux, macOS | ✓ | Engine: Windows, Linux, AIX. Rhapsody IDE: Windows only | Windows |
| Vendor-published container image | ✓ Docker Hub and AWS ECR | not published | not published |
| Kubernetes, including Azure Kubernetes Service | ✓ | not published | not published |
| AWS Elastic Container Service | ✓ install guide | not published | not published |
| Your own cloud account (AWS, Azure, Google Cloud) | ✓ | ✓ “self-host in your own AWS, Azure, or GCP environment”, in Rhapsody’s words | “on your infrastructure”, in Rhapsody’s words; a cloud account is not specified |
| Vendor-run hosting | ✓ Qvera hosts and runs the QIE instance, and builds and runs your interfaces (Integration Services level 04, under a master services agreement) | ✓ Rhapsody as a Service: Rhapsody hosts and runs the engine; you build in the IDE. Envoy: Rhapsody builds and runs the integrations | ✓ Corepoint as a Service; managed services |
| High availability | ✓ two or more nodes share one database, automatic failover; included on every licensing model | “can be configured for availability”, in Rhapsody’s words (brochure); how, and how it is licensed, not published | Assured Availability (A2): failover to a backup server; listed by Rhapsody under the engine’s extensions (brochure) |
| Many sites from one console | ✓ Remote Management Hub (RMH): sites connect outward, no inbound firewall rule or VPN per site | Rhapsody Dashboard, “an at-a-glance view of all your Rhapsody environments” | Connection Central views; Mobile Monitor app |
| Configuration history | ✓ every change, compare and restore | “version control” on Rhapsody’s comparison pages; the mechanism is not published | not published |
| Security & support | QIE | Rhapsody Integration Engine | Corepoint Integration Engine |
| Security attestations | SOC 2 Type 2 | SOC 2 Type II, ISO 27001:2022 and HITRUST e1, as listed on its trust center | as Rhapsody |
| Support | 24/7 for system-down emergencies; phone support (8am to 5pm Mountain), email, customer portal and knowledge base | 24×7 by phone, portal and email, in Rhapsody’s words; response targets and tiers not published (support page) | as Rhapsody, with its own support line |
| Licensing | QIE | Rhapsody Integration Engine | Corepoint Integration Engine |
| Model | Channel-based, Enterprise or OEM; production, test and developer licenses included; see pricing below | Licensed by communication points; no price list published. On AWS Marketplace: Rhapsody as a Service, $50,000 for 12 months, one production license with up to 5 communication points | Licensed by communication points; no price list published. On AWS Marketplace: Corepoint as a Service, $60,000 for 12 months, one production license with up to 5 communication points |
Yes, in one engine. Anything QIE does for HL7 v2 it also does for HL7 v3, FHIR, DICOM including native DIMSE and DICOMweb, X12, ASTM, CDA and IHE profiles, over MLLP, REST, SFTP, file, database, message queue and network share. The Qvera DICOM Router is that same engine configured for imaging.
It runs on Windows or Linux, in Docker or Kubernetes from images Qvera maintains, or on AWS ECS: on-premise, in containers, or in your own AWS, Azure or Google Cloud account, against Microsoft SQL Server, MySQL or MariaDB. Running engines at more than one site, or inside networks you do not control, is what the Remote Management Hub (RMH) is for.
The Qvera Interface Engine · The Qvera DICOM Router · Remote Management Hub
Whichever engines are on your shortlist, ask every vendor, Qvera included, to show the move using one of your own Rhapsody routes or Corepoint connections. Ask what carries over, what is rebuilt, how the result is tested, and what the complete cost is once support, high availability, test and development environments, file transfer and multi-site management are included.
See how QIE compares with Iguana 6 and IguanaX, and how Iguana teams move their Lua interfaces.
Qvera offers Channel-based, Enterprise, and OEM licensing models. Channel-based licensing starts at $9,980 per year for 2 channels. View Qvera Licensing and Pricing.
QIE is in production at more than 600 sites, running more than 25,000 interfaces and processing more than 50 million messages a day. Qvera has built healthcare interface engine software since 2008 and is SOC 2 Type 2 attested.
How this comparison is sourced: Qvera publishes this page and sells QIE. What this page says about QIE comes from Qvera’s own product documentation and production deployments; about Rhapsody Integration Engine and Corepoint Integration Engine, from Rhapsody’s own product pages, brochures, trust center and AWS Marketplace listings. All competitor information was last reviewed on 8 October 2026. Vendors change their products, so check their current documentation before relying on any single claim. Found something out of date? Tell us and we will correct it.
