No more typing reviews! Try our Samantha, our new voice AI agent.

Hillstone Networks Hillstone CloudEdge Virtual-Firewall vs Mirth Connect Health Check comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Hillstone Networks Hillston...
Ranking in AWS Marketplace
460th
Average Rating
10.0
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Mirth Connect Health Check
Ranking in AWS Marketplace
28th
Average Rating
7.8
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Centralized security has protected hybrid workloads and provides deep visibility into cloud traffic
Cloud-native automation and IaC: Terraform support, auto-scaling templates, and API maturity lag behind Palo Alto VM-Series and FortiGate-VM. Dynamically scaling in public cloud requires more manual effort. Third-party integrations and ecosystem: fewer native connectors with SIEM/SOAR platforms, CSPM, and third-party tools compared to market leaders. Documentation and training material: technical documentation and community resources (forums, tutorials, KB) are more limited, which lengthens the learning curve for new teams. SASE/SSE capabilities: the integrated SASE/ZTNA offering is less mature compared to the convergence already provided by Fortinet or Palo Alto. Centralized multi-instance management: managing large fleets of virtual appliances could be smoother; centralized management (HSM) works, but some users would like more granularity and automation.
reviewer2902977 - PeerSpot reviewer
Senior Software Engineer at a manufacturing company with 10,001+ employees
Streamlines clinical data exchange and has improved HL7 to FHIR transformation and monitoring
The best features Mirth Connect Health Check offers are that it provides a graphical way to create channels, source connectors, destination connectors, filters, and transformers without the need for extensive coding. The dashboard messages browser allows me to track message status, receiving, send, error, and troubleshooting issues quickly. It supports HL7, XML, JSON, and TCP/IP and HTTPS, RESTful APIs, and databases. Out of all those features, I find myself appreciating the troubleshooting issues, error identification, the API, and multiple protocols the most. The message browser logs, test messages, and connection testing make troubleshooting easier than many custom integration solutions. It also provides JavaScript and custom libraries that can be integrated for advanced use cases. In our organization, we are mostly using patient care devices, services, and order APIs. So mostly, EMR data, we are integrating with Mirth Connect Health Check as an HL7 integration. For the outbound, we are sending using RabbitMQ to device applications. Since using Mirth Connect Health Check, I have noticed that it has definitely reduced a lot of time as an HL7 or healthcare data integration. Different data formats require compliance and other aspects, but if I go with some other native language, it takes more time to build an application. Mirth Connect Health Check is very easy to use.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable aspect is the combination of traditional firewall functionality with cloud deployment flexibility."
"CloudEdge has helped us apply consistent security controls to our AWS workloads with our on-premises workloads."
"Hillstone CloudEdge Virtual Firewall provides advanced security for cloud and virtualized environments through next-generation firewall (NGFW) capabilities, including application visibility and control, intrusion prevention (IPS), antivirus protection, VPN services, threat intelligence, and advanced attack defense mechanisms."
"On balance, Hillstone CloudEdge is a solid and highly competitive solution within the virtual NGFW firewall segment."
"Having all the data in a single application helped my team by saving time and improving accuracy."
"Since using Mirth Connect Health Check, I have noticed that it has definitely reduced a lot of time as an HL7 or healthcare data integration."
"Mirth Connect Health Check has positively impacted my organization by speeding up deployment time in my previous jobs."
"Mirth Connect Health Check has positively impacted my organization by allowing our interoperability master, who knows how the message should be drafted and sent but is not a technical person, to use this tool easily."
"Mirth Connect Health Check has positively impacted my organization by making integration seamless and being developer-friendly."
 

Cons

"The setup cost is more expensive with similar features."
"Additional automation resources for AWS would also be helpful."
"Cloud-native automation and IaC: Terraform support, auto-scaling templates, and API maturity lag behind Palo Alto VM-Series and FortiGate-VM."
"Mirth Connect Health Check's scalability is pretty good for small to medium hospitals, but for bigger installations, we had issues talking about millions of messages per day, and that's why we ended up coding our own solution."
"I believe Mirth Connect Health Check could be improved as the interface should be slightly better."
"The weakness part is that the UI is somewhat outdated, making it difficult to manage with large environments, and it requires JavaScript knowledge for advanced development."
"One main challenge I faced was because I was using a 32-bit application, and the amount of data that we were collecting was significant since it was our country's biggest laboratory, processing thousands of samples every day."
"Mirth Connect Health Check can be improved mainly in the JavaScript coding section, where it does not give me good access to the variables and the inside of class codes so that I can customize things on my own, which depends on the behavior of Mirth using the reference of their open-source Java code."
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Construction Company
37%
Healthcare Company
11%
Comms Service Provider
11%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What needs improvement with Hillstone Networks Hillstone CloudEdge Virtual-Firewall?
Additional automation resources for AWS would also be helpful. More comprehensive CloudFormation or Terraform examples, deployment templates, and guidance for high-availability architectures could ...
What is your primary use case for Hillstone Networks Hillstone CloudEdge Virtual-Firewall?
We deploy Hillstone CloudEdge Virtual-Firewall in AWS to protect workloads hosted inside our VPC. We use it to inspect north-south traffic, enforce access-control policies, secure communication bet...
What needs improvement with Mirth Connect Health Check?
An improvement point I see for Mirth Connect Health Check is a heavier version in terms of memory. I chose eight out of ten because it is not a web application.
What is your primary use case for Mirth Connect Health Check?
My main use case for Mirth Connect Health Check is to gather data for my healthcare client. We used to gather data from the clinical instruments in Mirth Connect and then translate that data throug...
What advice do you have for others considering Mirth Connect Health Check?
I would advise others looking into using Mirth Connect Health Check to look for its capability in handling data. If that suffices your requirements, definitely go ahead, and also check for a web-ba...
 

Overview

Find out what your peers are saying about Hillstone Networks Hillstone CloudEdge Virtual-Firewall vs. Mirth Connect Health Check and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.