Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
FHIR is characterized as a 'RESTful' framework, aligning with the general industry interpretation of REST. However, it predominantly adheres to Level 2 of the REST Maturity Model within its core specification, while achieving full Level 3 compliance is feasible through the adoption of extensions. Being a standard, FHIR relies on the uniformity of resource structures and interfaces, which some may argue conflicts with REST principles; nonetheless, this standardization is crucial for maintaining consistent interoperability among various systems. Each "resource type" is associated with a defined set of interactions, allowing for the precise management of resources. Applications that assert their compliance with this framework refer to themselves as "RESTful FHIR," emphasizing their adherence to these standards. Furthermore, within this RESTful design, transactions are executed directly on the server resource via HTTP request and response, reinforcing the framework's integrity and functionality. This structured approach not only enhances interoperability but also streamlines the development of applications that utilize FHIR.
Description
The Qvera Interface Engine (QIE) is a healthcare integration engine from Qvera, which has worked in healthcare interoperability since 2008. It receives, routes and transforms messages between clinical, imaging and administrative systems for hospitals, health systems, imaging centers, and software vendors who embed QIE in their own products.
A single engine covers HL7 v2 and v3, FHIR, DICOM including native DIMSE, X12, NCPDP, ASTM, CDA and IHE profiles, over MLLP, REST, SFTP, file, database, message queue and SMB network share transports. Imaging and clinical interfaces do not need separate tools.
Three design choices set it apart. Interfaces are scripted in JavaScript, with a built-in Code Wizard, rather than in a proprietary language. The datastore is your own choice of MSSQL, MySQL or MariaDB, so there is no proprietary datastore to adopt. And the Remote Management Hub monitors and controls QIE instances deployed inside separate customer networks from one console.
Deployment is on-premise, in containers, or in your own cloud. More than 1,000 sites run QIE in production today, carrying more than 25,000 interfaces and processing more than 50 million messages a day. SOC 2 Type 2 attested.
API Access
Has API
API Access
Has API
Integrations
AdvancedMD
Amazon Web Services (AWS)
Arintra
CaseManager DX
Docker
EHNOTE
EndoManager Imaging
Google Cloud Platform
Greenway Health
Health Studio
Integrations
AdvancedMD
Amazon Web Services (AWS)
Arintra
CaseManager DX
Docker
EHNOTE
EndoManager Imaging
Google Cloud Platform
Greenway Health
Health Studio
Pricing Details
No price information available.
Free Trial
Free Version
Pricing Details
Starting at $9,980.00 / year
QIE is licensed three ways. A per-channel subscription starts at $9,980 per year for a two-channel block and scales in blocks from 2 to 100+ channels, with volume pricing as the block size grows. An Enterprise license covers unlimited channels and is priced by instance and HA node. An OEM/embedded license is billed on usage in arrears plus a partner fee. All three carry a one-year initial term and continue quarter-to-quarter after it.
Free Trial
Free Version
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Vendor Details
Company Name
HL7
Founded
1987
Country
United States
Website
www.hl7.org/fhir/http.html
Vendor Details
Company Name
Qvera
Founded
2008
Country
Kaysville, UT, United States
Website
www.qvera.com/hl7-interface-engine/