Qvera Interface Engine (QIE)
Qvera | 24.2.1.16442bWindows, Windows Server 2019 Base Version 1803 - 64-bit Amazon Machine Image (AMI)
Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Robust functionality, dependable and stable
What do you like best about the product?
Love the user interface, stability of the product and the amazing support Qvera provides.
What do you dislike about the product?
It would be extremely helpful to be able to open more than one window at a time.
What problems is the product solving and how is that benefiting you?
Integration between disparate systems.
- Leave a Comment |
- Mark review as helpful
Qvera Interface Engine review
What do you like best about the product?
The Qvera Interface Engine tool is very flexible in providing Oneida with ultimate solution for the numerious interfaces we have. If the assigned tech doesn't the answer he has other resources to pull from. Each of them work great has a team to help each other out.
What do you dislike about the product?
Currently there has not been anything I dislike about QIE.
What problems is the product solving and how is that benefiting you?
Some of the errors are hard to understand why the error occured. With the assistance of tech support they assistance helping me correct the error
QIE has been a huge help to Virginia Womens Center
What do you like best about the product?
customer support at Qvera is extremely helpful in customizations of the interface. As somone who understand javascript very well; that is a huge help. Also like the diversity of options for interfaces and database connections and ease of use.
What do you dislike about the product?
there isnt' anything I can think of that I dislike about QIE.
What problems is the product solving and how is that benefiting you?
Real-time patient demographic and scheduling information coming in from our EHR through QIE is sent to several different HL7 interfaces for ancillary applications, as well as a DICOM worklist and several SQL database connections. We store all of the incoming HL7 data in a database that provides real-time information to our intranet, where we've built applications to track patient sign-ins and encounter status in real-time, as well as a number of report-based applications that utilize the data.
Qvera is awesome
What do you like best about the product?
I like the flexibility that I have with creating interfaces to simplify jobs internally. Connecting with external vendors has never been an issue. Installing Qvera is simple and straightforward. I use the Qvera interface where ever I can fit it in with our workflows.
Qvera's customer support has been one of the best interactions I've had with any company I've worked with. Their knowledable team and KB is extensive and usually can solve any problems the same day. They are very responsive to any tickets that I've put in.
Qvera's customer support has been one of the best interactions I've had with any company I've worked with. Their knowledable team and KB is extensive and usually can solve any problems the same day. They are very responsive to any tickets that I've put in.
What do you dislike about the product?
Using QIE over Mirth does incur a cost. But I do feel the support and the functionality outweigh any benefits of using Mirth over QIE.
What problems is the product solving and how is that benefiting you?
We're using to QIE to create interoperability between healthcare facilities. Being able to easily share documents has been a game changer for our practice. QIE also helps us with our PACs and auto importing reports such as MRI Reports into our EMR.
Qvera for innovation
What do you like best about the product?
It is so nice to be able to intervene with common errors to cut down on intervention calls. It seems like it is so fast to implement and integrates with everything we want it to. We are converting all of our mirth interfaces to take care of error resolution and it has helped tremendiously on a daily basis. Customer Support is amazing. They are fast, friendly, knowledgeable and work so great as a team. Qie and the Supporting team are amazing!
What do you dislike about the product?
I have not found a dislike yet. With my creative, talented staff and that of Qvera, we have been able to do everything we wanted so far.
What problems is the product solving and how is that benefiting you?
It has helped in minimizing immunization issues being sent to state registry incorrectly and send alerts for user errors to be able to be corrected and resent.
Eliminate ADT and DTF interface issues and improved availability by services not going down. It has aided in the virtual visits for group scheduling in our Behavioral Health area.
Eliminate ADT and DTF interface issues and improved availability by services not going down. It has aided in the virtual visits for group scheduling in our Behavioral Health area.
Excellent Interface Engine
What do you like best about the product?
QVera is very user friendly, and easy to learn. We have been able to create very efficient workflows using QVera. Any time we run into an issue or aren't sure how to do something, their support is responsive, fast and able to solve problems.
What do you dislike about the product?
I don't dislike anything about the software. It is fairly priced, easy to use and support is very knowledgeable.
What problems is the product solving and how is that benefiting you?
We import members from employer clients, send and receive lab results, and run queries to deliver to external reporting sources, including the local health department and immunization registries.
I heart Qvera!
What do you like best about the product?
There are so many features about QIE that are helpful to me:
1. The install of QIE software is quick and easy for a not so techncial person like myself
2. The look/feel of the GUI is very intuitive - at a glance you can tell what interfaces are running, start/stop the interface,
3. QIE offers "inactivity alerts'" that trigger email alerts based on customizable time frames and days of the week. These alerts can be different for each interface
4. When building an interface, the "flowchart" visual of the interface build is wonderful!
5.I use the Global/System Variable often - specifically the tables. I can write logic that points to the values in the table like a list. So when a new value is added, I can simply add the entry to the table without having to change the interface logic.
6.The export/import feature makes it simple to copy interfaces from the TEST environment to the Production environment! Even has the option to NOT overwrite the endpoints.
7. QIE supports all the interfaces we have needed to build - interfaces with HL7 transacitons and EDI data. And we have a webservice interface in Qvera as well.
8. This should be #1 - Qvera technical support is AMAZING! On occassions where I needed assistance with getting the desired outcome with programming, the tech support staff was quick to respond and so knowledgable!
1. The install of QIE software is quick and easy for a not so techncial person like myself
2. The look/feel of the GUI is very intuitive - at a glance you can tell what interfaces are running, start/stop the interface,
3. QIE offers "inactivity alerts'" that trigger email alerts based on customizable time frames and days of the week. These alerts can be different for each interface
4. When building an interface, the "flowchart" visual of the interface build is wonderful!
5.I use the Global/System Variable often - specifically the tables. I can write logic that points to the values in the table like a list. So when a new value is added, I can simply add the entry to the table without having to change the interface logic.
6.The export/import feature makes it simple to copy interfaces from the TEST environment to the Production environment! Even has the option to NOT overwrite the endpoints.
7. QIE supports all the interfaces we have needed to build - interfaces with HL7 transacitons and EDI data. And we have a webservice interface in Qvera as well.
8. This should be #1 - Qvera technical support is AMAZING! On occassions where I needed assistance with getting the desired outcome with programming, the tech support staff was quick to respond and so knowledgable!
What do you dislike about the product?
To date, I haven't found anything that I dislike about Qvera. And we have been using QIE for 2 years now.
What problems is the product solving and how is that benefiting you?
My company develops softare for hospitals/long term care facilities. QIE has made the development of our interfaces with our clients much easier and therefore faster builds. When the client has a request for change to their interface, the work effort time to make such changes is less too. Installing QIE on our client's with their own servers is quick and easy too. QIE is an extemely reliable interface engine. All these things make for a better implemantion process for our client - plus an after go-live reliable interface.
QIE makes business flows easier
What do you like best about the product?
QIE makes moving information, business processes possible. It's fairly simple to build interfaces the business asks for. If there is something you can't figure out, something you can't do, something you wonder can you do? all you need to do is call support, they always bend over backwards to assist and help us get exactly what we need accomplished.
What do you dislike about the product?
I don't find anything not helpful about QIE, if I had a thought to make things better, having training videos available to teach some specific items, or be able to direct you down a certain path to build what you are needing.
What problems is the product solving and how is that benefiting you?
QIE provides us the ability to move, transform and edit data based on specific business needed criteria. We are always able to build what the business is asking us to do usually with minimal effort and ease, if we get stuck, Qvera support is stellar!
Best support team I have ever worked with
What do you like best about the product?
The Qvera engine is very powerful and has all sorts of functionality. Other tools on the market tend to lean heavily either towards low/no-code or full code. I picked Qvera because it had the ease of use for HL7 analysts combined with ability to code completely custom integrations for software developers.
As great as the tool is though, the absolute best part of the product is the support I receive. The team that answers the phone (amost always live answer) is fully capable of building interfaces, writing code, etc. I have never had such a good support experience with other companies. I have built some very non-standard, complex interfaces in the 10 years I have been using their product. I have run into challenges on niche integrations (ex: Hybrid DICOM, HL7/API) where support will actually pull in the software developer that wrote that part of the program to help troubleshoot or provide advice. I am not talking about weeks later either, it is usually within 30m of calling.
As great as the tool is though, the absolute best part of the product is the support I receive. The team that answers the phone (amost always live answer) is fully capable of building interfaces, writing code, etc. I have never had such a good support experience with other companies. I have built some very non-standard, complex interfaces in the 10 years I have been using their product. I have run into challenges on niche integrations (ex: Hybrid DICOM, HL7/API) where support will actually pull in the software developer that wrote that part of the program to help troubleshoot or provide advice. I am not talking about weeks later either, it is usually within 30m of calling.
What do you dislike about the product?
The main frustration would be related to their use of RHINO for JavaScript code within Java. Because you can write code using both languages in the same code section, it is often difficult to troubleshoot issues related to conversion between the two languages.
What problems is the product solving and how is that benefiting you?
We use Qvera to integrate all internal HL7 interfaces. Additionally we have several interfaces using DICOM and API resources. We process tens of millons of messages every month through the engine.
A True QIE Ambassador!
What do you like best about the product?
Ease of use, fexibility, customizability. We use QIE for a vast amount of workflows far beyond the typical HL7 interfaces.
What do you dislike about the product?
The biggest thing I would love to see that is not present is the ability to step through custom scripts inside a mapping node.
What problems is the product solving and how is that benefiting you?
Are company uses QIE in the typical HL7 space but my primary role involves interacting with EHRs utilizing their APIs to solve a far broader set of needs.
showing 1 - 10