Introducing
The HL7® Interface Engine Built for Today’s Healthcare Cloud
We connect you to the networks and platforms that unlock your healthcare data
“
Our customers rely on us for current and accurate patient information at the point of care and we rely on QIE to provide the interoperability and communication between numerous data sources and systems. Easy to use, QIE requires just a single full-time employee to manage more than 300 interfaces.”
Merin Joseph
EVP & CIO – WESTMED Practice Partners
“
One of the best things about Qvera's HL7 interface engine is that we’re able to take data out of our Epic EHR and do what we need to with it. That really makes all the difference ensuring our providers have the data they need in order to provide the highest quality care to our patients.”
Alicia Soccomando
Business Analyst Lead – QuadMed
Case Studies
New Case Study
QuadMed: Epic EHR interoperability made easy with the help of QIE
Revere Health: Adoption of QIE results in lower costs & improved care
AllianceChicago: QIE helps identify & reduce child lead exposure risk
Oregon Clinic: Bi-directional Epic integration alleviates physician burden
QIE Sandbox
Want to kick the tires first? Take QIE for a test drive now!
The QIE Online Sandbox is a cloud-hosted deployment of Qvera's award-winning HL7 Interface Engine (QIE). Each sandbox is pre-configured with examples that demonstrate how easy it is to solve real-world interoperability challenges with QIE.
Build Interfaces in Minutes, not Hours
Node Path Lookup Dialog – Easily populate node path values using sample messages and a point-and-click user interface
Powerful Node-Path Syntax for Querying Message Data
Instead of writing for-loops and if-statements, get right to the data you need with QIE’s simple, yet powerful, node path syntax for identifying, navigating, and modifying message nodes and sections. Node path syntaxes are available for all data formats, including the following:
HL7 - HPath Examples
message.getNode('PID-5.2')
Returns component 2 of field 5 of the PID segment (Patient First Name)
message.getNode('OBR[@4.1=XR003]-2')
Returns field OBR-2 where the value in OBR-4.1 is equal to ‘XR003’
message.getNode('ORC[group=!ORC]')
Returns the ORC group of segments – adds all segments found to the group until another ORC segment is encountered
XML - XPath Examples
message.getNode('/List/Patient[3]')
Returns the 3rd patient object from a list of patients
message.getNode('/List/Patient[@id=123]')
Returns the patient with the id attribute is equal to ‘123’
message.getNode('/List/Patient[@id=123]/name')
Returns the patient name object where the patient id attribute is equal to ‘123’
JSON - JPath Examples
message.getNode('/Patient/FirstName')
Returns the FirstName field in the Patient object
message.getNode('/Results/[Identifier=’LOI-1968-7′]')
Returns the Result object where the identifier field is equal to ‘LOI-1968-7’
message.getNode('/Results/[Identifier=’LOI-1968-7′]/ObservationValue')
Returns the ObservationValue of the Result object where the identifier field is equal to ‘LOI-1968-7’
DICOM - DPath Examples
message.getNode('/0002,0002')
Returns the Media Storage SOP Class UID from the DICOM message
message.getNode('/0008,0008/[2]')
Returns the 2nd value instance of the Image Type field from the DICOM message
message.getNode('/18,6011/[18,601c=1024]/18,6026')
Returns the Physical Units X Direction (0018,6026) sub-field of the Sequence Of Ultrasound Regions field (0018,6011) where the Region Location Max X 1 (0018,601c) sub-field is equals to ‘1024’
Visual Channel Editor for Rapid Interface Development
Source Nodes: Each channel is created with a single source node which can be configured for receiving data from virtually any source: File, FTP, HTTP, Network Share, Socket, Custom Script, etc.
Mapping Nodes: Mapping nodes are used to perform data manipulations. QIE includes a mapping function wizard for common manipulations to be configured without the need for custom scripts.
Condition Nodes: Condition nodes control how messages are routed through the channel. If the condition is met, the message follows the ‘success’ path. Otherwise, it follows the ‘fail’ path.
Destination Nodes: Destination nodes are used to send messages to downstream systems. QIE supports virtually any connection type: File, FTP, HTTP, Network Share, Socket, etc.
QIE Visual Channel Editor – Quickly map data flow through the interface using QIE’s wire-frame, drag-and-drop visual editor
Step-by-Step Testing with an Integrated Test Environment
QIE’s fully integrated testing framework, simplifies the process of testing proposed configurations and changes, making it easy to see exactly how the changes will effect the interface.
- Step messages through proposed changes, one function at a time, before committing them to production
- Easily view the message state before and after each executed step
- The active channel node is highlighted as the test message is stepped through the interface, showing exactly where it is during each step of the testing process
- Configure multiple sample messages to represent all expected message variations
- Easily create sample messages from actual messages processed by the channel
Infinitely Scalable, Highly Available and Built for Today’s Healthcare Cloud
The diagrams below show just a few of the scalability and high availability options that are possible with QIE*
* The QIE HL7 interface engine configurations shown above can be implemented either on premises or in a cloud hosted environment
QIE Product Information
Product Overview
HL7 FHIR
DICOM
Scalability & HA
Learn More about the HL7 Interface Engine
General Overview of Features and Functionality →
| Cloud Computing | Enterprise | Standard | ||||||
|---|---|---|---|---|---|---|---|---|
| QIE Container Support - Ability to deploy QIE as a light weight Docker container | ||||||||
| Container Orchestration - Provision, deploy & scale containers using Docker Swarm or Kubernetes Engine | ||||||||
| Docker Hub - QIE container images published by Qvera and available in Docker Hub | ||||||||
| Cloud Hosting | Enterprise | Standard | ||||||
|
Amazon AWS - Published Solutions
- Virtual machine images with OS, QIE and back-end database pre-configured for single click deploy
- Container images pre-configured for QIE distributed cluster deployments (coming soon)
|
||||||||
|
Google Cloud - Published Solutions
- Virtual machine images with OS, QIE and back-end database pre-configured for single click deploy
- Container images pre-configured for QIE distributed cluster deployments (coming soon)
|
||||||||
|
Microsoft Azure - Published Solutions
- Virtual machine images with OS, QIE and back-end database pre-configured for single click deploy (coming soon)
- Container images pre-configured for QIE distributed cluster deployments (coming soon)
|
||||||||
| Enterprise Scalability and High Availability | Enterprise | Standard | ||||||
| QIE Distributed Cluster - Multiple QIE instances running simultaneously in a distributed cluster configuration against a single QIE database. Provides HA redundancy and QIE scalability. | ||||||||
| QIE HA Primary/Backup - One primary QIE instance with one or more backup (standby) QIE instances which automatically take over message processing if the primary instance fails. | ||||||||
| Back-End Database Scalability and High Availability | Enterprise | Standard | ||||||
| Enterprise DBMS Support - Use MariaDB, MySQL or Microsoft SQL Server as the back-end QIE database | ||||||||
| DBMS in Distributed Cluster - Multiple DBMS instances running simultaneously in a distributed cluster | ||||||||
| DBMS in HA Primary/Backup - One primary DBMS instance with one or more backup DBMS instances | ||||||||
| Rapid Interface Development | Enterprise | Standard | ||||||
| Visual Channel Editor - Quick wire-frame interface development using a graphical interface editor | ||||||||
Advanced Node Path Syntax - QIE's simple, yet powerful, node path syntax for identifying, navigating,
and modifying message nodes and sections - available for every data format:
|
||||||||
|
Advanced JavaScript Editor - A JavaScript editor with advanced features that make coding in QIE easy
Code Wizard - Easy access to all built-in QIE defined functions
Code Completion - Intelligent code completion speeds up the process of scripting in QIE
Syntax Validation - Real time syntax validation highlights coding errors as scripts are written
|
||||||||
|
Task Automation Utilities - Utilities that automate and simplify common time-consuming tasks
Node Path Lookup Dialog - Populate node path values using a point-&-click sample message dialog
RegEx Validation Dialog - Easily validate the syntax of regular expressions
Standard Functions Dialog - Add common data mapping functions without any coding required
Smart Message Editors - Stylized message editors highlight fields based on type. Editors support node-path search. For example, searching for 'PID-2' in HL7 selects the Patient ID
|
||||||||
| Shared Variables & Caches - Store elements in system variables or channel caches for shared usage | ||||||||
| Channel Change History - Track and revert configuration changes with built in version control | ||||||||
| Organize Channels by Zone - Group, manage and control access to channels using Zones | ||||||||
| Encrypt & Secure Interface Configurations - Secure your intellectual property and prevent interface tampering by publishing your interface configurations for distribution as encrypted secure packages | ||||||||
| Fully Integrated Testing Framework | Enterprise | Standard | ||||||
| Step-by-Step Testing - Step messages through proposed changes, one function at a time, before committing them to production. Easily view the message state before and after each executed step. | ||||||||
| Visual Follow Test Messages - The active channel node is highlighted as the test message is stepped through the interface, showing exactly where it is during each step of the testing process. | ||||||||
| Configure Multiple Sample Message - Configure multiple sample messages to represent all expected message variations. Easily create sample messages from actual messages processed by the channel. | ||||||||
| Monitoring, Error Management, and Alerting | Enterprise | Standard | ||||||
| Channel Status Dashboards - Monitor channel status/health using the global and zone status dashboards | ||||||||
|
Automated Email Alerts - Configure users to receive role based email alerts by channel/zone
Erred Messages - Send alerts for erred messages
Consecutive Errors - Send alerts after 'x' consecutive send/receive errors
Channel Inactivity - Send inactivity alerts based on a schedule of expected activity
Large Queue Backlog - Send alerts when queue backlogs exceed defined thresholds
|
||||||||
|
Channel Auto Error Recovery - Configure channels to automatically recover from erred states
Stop After Consecutive Errors - Configure channel to stop after 'x' consecutive errors
Restart Auto-stopped Channel - Auto-restart a channel stopped in an error state after 'x' seconds
|
||||||||
|
Channel Auto Error Recovery - Configure channels to automatically recover from erred states
Stop After Consecutive Errors - Configure channel to stop after 'x' consecutive errors
Restart Auto-stopped Channel - Auto-restart a channel stopped in an error state after 'x' seconds
|
||||||||
|
Error Management Automation - Automate and streamline the process of managing erred messages
Scripted Error Management - Automate the process of managing errors with scheduled scripts
Managing Errors as Batches - View and manage errors in batches using the Distinct Errors Dialog
|
||||||||
Error Management Forms - Build error resolution workflows using error management forms |
||||||||
| Data Formats and Standards | Enterprise | Standard | ||||||
| Industry Standard Data Formats - HL7® (v2 & v3), FHIR®, CDA®, DICOM, X12, ASTM and more... | ||||||||
| General Data Formats - JSON, XML, CSV, DB Query, Plain Text, Fixed Width, Binary and EDIFACT | ||||||||
| Communication Protocols | Enterprise | Standard | ||||||
| Industry Standard Protocols - HL7 LLP, FHIR RESTful API, SAML, OAuth, Secure LLP Socket and more... | ||||||||
| IHE Communication Protocols - XDR/XDS, XCA/XCPD, PIX/PDQ, DSUB and more... | ||||||||
| Web Service Communication Protocols - HTTP/S, SOAP, REST (both URL & Content Encoding) | ||||||||
| Other Communication Protocols - File, Network Share, FTP, FTPS, SFTP, DB Query, Custom Scripting | ||||||||
| Digital Certificate Management - Easily import, generate and manage private keys, self-signed certificates and certificate signing requests (CSR). Automated email notifications and alerts for expiring certificates. | ||||||||
| HL7 Interface Engine Extensibility | Enterprise | Standard | ||||||
| Import External Java Libraries - Dynamically load and use any external Java library for use within QIE | ||||||||
| Published Functions - Import or create custom JavaScript functions that can be used in channel scripts | ||||||||
| Third-Party Status Monitoring - IMonitor QIE channel status with third-party tools & QIE's monitoring API | ||||||||
| Security | Enterprise | Standard | ||||||
| Comprehensive Role-Based User Security - Limit access based on user role. Enforce strong passwords and password expiration. Set auto lock/logout thresholds. Track user activity with audit logging. | ||||||||
| Database Encryption - All sensitive data is automatically encrypted (passwords, message data, etc.) | ||||||||
| Secure Access to Admin Console - Ability to secure access to the QIE Admin Console using HTTPS | ||||||||
| Support and Training | Enterprise | Standard | ||||||
| QIE Auto-Update - Schedule automatic download and install of new QIE releases | ||||||||
| Training & Certification - Access to tutorials, a comprehensive knowledge base, and certification courses | ||||||||
| Phone & Email Support - Get support from a Qvera engineer by phone, remote screen share and email | Limited | |||||||
| After Hours Emergency Support - 24x7 emergency production support | ||||||||
| QIE Product Offerings | Enterprise | Standard | ||||||
| Licensing & Pricing - Flexible retail licensing options for QIE Enterprise start as low as $199 per month. Wholesale licensing and pricing options are available for approved OEM and Reseller partners. | Perpetual or Subscription | Free | ||||||
| Channel Limit - Maximum number of running channels (interfaces) allowed | No Limit | 2 | ||||||
| Message Throughput Limits | ||||||||
Unthrottled message limit - Messages processed in real time as soon as they are received |
No Limit | 2,500 msg/wk | ||||||
+ Throttled message limit - After unthrottled limit reached, processing is throttled to 1 message per min |
n/a | + 10,000 msg/wk | ||||||
= Total message throughput - Unthrottled message limit + Throttled message limit |
No Limit | = 12,500 msg/wk |
FHIR Features and Functionality →
| Support for the HL7 FHIR Standard | Enterprise | Standard |
|---|---|---|
| Support for all FHIR Versions - Seamless transition and support for all versions of the FHIR specification - DSTU 2, STU 3, R4, R5, etc. | ||
| Support for all FHIR Extensions - Easily support all FHIR extensions, including those defined in the various FHIR implementation guides | ||
| Support for all FHIR Operations - Ability to call/execute all defined RESTful API operation including those supported by terminology servers (looking up or translating code sets) | ||
| Support for all FHIR Formats - Manage FHIR resources as either JSON or XML. Use QIE’s native FHIR conversion utilities to easily convert FHIR resources from JSON to XML and vice versa. | ||
| Support for all FHIR RESTful APIs - Full support for REST based web service calls, including support for all REST based HTTP methods used by the FHIR API - GET, POST, PUT, DELETE, PATCH and HEAD | ||
| Translating Between FHIR and Other Data Formats | Enterprise | Standard |
| Convert FHIR ‹–› HL7 - Easily convert FHIR resources (from both JSON and XML formats) to HL7 v2 messages and vice versa using QIE’s advanced node path syntax and support for templates | ||
| Convert FHIR ‹–› CDA - Easily convert FHIR resources (from both JSON and XML formats) to CDA documents and vice versa using QIE’s advanced node path syntax and support for templates | ||
| Advanced Node Path Syntax - QIE’s simple, yet powerful, node path syntax for identifying, navigating, and modifying message nodes and sections - available for every data format | ||
| Adding SMART on FHIR Capabilities to an Application or EHR Platform | Enterprise | Standard |
| Configure QIE as a SMART App Server - Utilizing QIE’s support for OAuth 2.0, QIE can be configured to act as a SMART App Server that can authenticate a SMART Application with an EHR Authorization Server following the launch sequences outlined in the SMART App Launch Framework | ||
| Configure QIE as a SMART Authorization Server - Utilizing QIE’s support for OAuth 2.0, QIE can be configured to act as a SMART Authorization Server that can handle SMART Application authorization requests following the launch sequences outlined in the SMART App Launch Framework | ||
| Configure QIE as a SMART enabled FHIR Server - Utilizing QIE’s support for OAuth 2.0, JSON, XML and QIE’s built in FHIR conversion utilities, QIE can be configured to act as a SMART enabled FHIR Server for any EHR platform. | ||
| QIE Product Features that support HL7 FHIR | Enterprise | Standard |
| Built-in JSON & XML FHIR Conversion Utilities - With QIE’s built in FHIR conversion utilities, FHIR resources can easily be converted between both JSON and XML formats supported by the standard | ||
| HTTP Endpoint Configuration - A QIE channel can be configured to listen for inbound HTTP requests and respond with appropriate HTTP content, response codes and custom HTTP header values | ||
| Digital Certificate Management - Easily import, generate and manage private keys, self-signed certificates and certificate signing requests (CSR). Automated email notifications and alerts for expiring certificates. | ||
| Integrated OAuth 2.0 Support - QIE web service connection can easily be configured to automatically handle the process of requesting, storing and renewing OAuth 2.0 bearer tokens |
DICOM Features and Functionality →
| DICOM Network Communications | Enterprise | Standard |
|---|---|---|
| DICOM Connections - DICOM connections can be configured in QIE to connect to any PACS, RIS or device | ||
| DICOM Channel Listeners - A QIE channel can be configured to listen for inbound DICOM requests, and respond with appropriate responses. Listeners can be bound to one or more DICOM connections. | ||
| DICOM Services - DICOM listeners and connections can be configured to support the appropriate DICOM services or presentation contexts. QIE supports all defined presentation contexts. | ||
| DICOM TLS Communications - QIE supports securing DICOM connections using TLS security, including support for limiting trusted certificates and support for client authentication | ||
| DICOM Messaging Services | Enterprise | Standard |
|
Composite DICOM Message Services (DIMSE-C) - QIE supports all DIMSE-C services
C-FIND - Used to locate a particular DICOM object
C-GET - Used to request a DICOM object from a system or device that has it
C-STORE - Used to transmit a DICOM object across an interface to another system for storage
C-MOVE - Used when one device wants to send a DICOM object to another
C-ECHO - Used to verify that a DICOM connection is functioning - analogous to a ‘Ping’
| ||
|
Normalized DICOM Message Services (DIMSE-N) - QIE supports all DIMSE-N services
N-GET - Used to retrieve information
N-SET - Used to request that information be modified
N-ACTION - Used to request that a particular action be performed
N-CREATE - Used to request that a DICOM object plus services be created
N-DELETE - Used to request that a DICOM object plus services be deleted
N-EVENT-REPORT - Used to notify users of a service about an event regarding a DICOM object
| ||
| DICOM Message Format | Enterprise | Standard |
DICOM Message Type - Native support for the DICOM binary format including the ability to query for information using the message.getNode('') function and the ability to modify information using the message.setNode('') function without having to convert the DICOM object to an XML or JSON format |
||
DICOM Node Path Syntax (DPath) - QIE’s simple, yet powerful, node path syntax for identifying, navigating, and modifying DICOM data elements. For example, calling message.getNode('‘/0000,0100’') returns the Command Field element from the DICOM object. |
||
| DICOM Node Path Lookup Dialog - Easily populate node path values using sample DICOM messages and a point-&-click user interface, so you always know exactly what data is going to be returned or modified | ||
| DICOM Format Conversion Utilities | Enterprise | Standard |
| Convert to DICOM from XML or JSON - Convert an XML or JSON formatted representation of a DICOM object to a native binary DICOM object | ||
| Convert from DICOM to XML or JSON - Convert a native binary DICOM object to an XML or JSON formatted representation of the DICOM object | ||
| Convert from DICOM to JPEG - Easily render the image data in a native binary DICOM object as a JPEG image for use in other message formats or use cases | ||
| Preview DICOM Images - Easily preview DICOM object image data using the QIE console | ||
| DICOM Helper Functions | Enterprise | Standard |
| DICOM Dictionary Lookup Dialog - Easily find the right DICOM Tag, SOP Class UID or Transfer Syntax UID using QIE’s built-in DICOM Code lookup dialog | ||
|
Auto-Create Request & Response Objects - Functions to create common DICOM requests & responses
Create C-FIND Request - A function to create a C-FIND request object
Create C-GET Request - A function to create a C-GET request object
Create C-STORE Request - A function to create a C-STORE request object
Create C-MOVE Request - A function to create a C-MOVE request object
Create C-ECHO Request - A function to create a C-ECHO request object
Create DICOM Request - A function to create a generic DICOM request object
Create DICOM Response - A function to create a response to an associated DICOM request object
|
Cloud Computing, Scalability and High Availability →
| Amazon AWS | Enterprise | Standard |
|---|---|---|
| Published Virtual Machine Images - Virtual machine images available in the Amazon AWS Marketplace with OS, QIE and back-end database pre-configured for single click deploy | ||
| Published Container Images - Container images available in the Amazon AWS Marketplace pre-configured for QIE distributed cluster deployments (coming soon) | ||
| Google Cloud | Enterprise | Standard |
| Published Virtual Machine Images - Virtual machine images available in the Amazon AWS Marketplace with OS, QIE and back-end database pre-configured for single click deploy | ||
| Published Container Images - Container images available in the Amazon AWS Marketplace pre-configured for QIE distributed cluster deployments (coming soon) | ||
| Native Support for the Cloud Healthcare API - Easily configure a connection to the Google Cloud Healthcare API, by simply importing the JSON Key File which automatically configures the web service connection, including OAuth security. Access any of the supported data stores (FHIR®, HL7v2®, DICOM) | ||
| Microsoft Azure | Enterprise | Standard |
| Published Virtual Machine Images - Virtual machine images available in the Amazon AWS Marketplace with OS, QIE and back-end database pre-configured for single click deploy (coming soon) | ||
| Published Container Images - Container images available in the Amazon AWS Marketplace pre-configured for QIE distributed cluster deployments (coming soon) | ||
| Enterprise Scalability | Enterprise | Standard |
| QIE Container Support - Ability to deploy QIE as a light weight Docker container | ||
| Container Orchestration - Provision, deploy & scale containers using Docker Swarm or Kubernetes | ||
| Docker Hub - QIE container images published by Qvera and available in Docker Hub (coming soon) | ||
| QIE Distributed Cluster - Multiple QIE containers running simultaneously in a distributed cluster configuration against a single QIE database. Optional RabbitMQ message queuing service also available. | ||
| Enterprise High Availability and Fault Tolerance | Enterprise | Standard |
| QIE in HA Primary/Backup Configuration - One primary QIE instance with one or more backup (standby) QIE instances which automatically take over message processing if the primary instance fails | ||
| Multiple Load Balanced QIE Instances - Multiple QIE Servers running simultaneously in a cluster configuration against a single QIE database, which is also configured in an cluster or HA configuration | ||
| DB in HA Primary/Backup Configuration - OOne primary DB instance with one or more backup DB instances | ||
| DB in Distributed Cluster - OMultiple DB containers running simultaneously in a distributed cluster |
* The QIE HL7 interface engine configurations shown above can be implemented either on premises or in a cloud hosted environment
Partners, Platforms and Programs
Partners & Platforms
OEM Partner Program
Reseller Program
FHIR Starter Kit
Latest News
Now Available – QIE 4.0 is Built for the CloudFebruary 24, 2020 - 12:00 pm
Fueled by Di Vinci Project, FHIR quickly spreading to Payor-Provider Communication – and That’s a Good Thing!December 1, 2019 - 12:00 pm
QIE Level 1 Certification is now OnlineAugust 2, 2019 - 10:47 am
Announcing the release of Qvera Interface Engine (QIE) version 3.0.46June 5, 2019 - 8:00 am