Mirth Customer Experiences & Testimonials

Thank you for a brilliant tool!

Thanks for all the hard work and the excellent contribution to the healthcare IT community.

The product is maturing and expanding every day keep up the good work. Thanks

Great job on an exceptional product.

I am certified in three Integration products and have worked extensively with four total. This is by far my favorite for its many capabilities and ease of use! Congrats! Great Product!

Love it! Permits me to get Patient Move raw data from my clinical system without bothering or dealing with the data czars that control access to “their” data.

Great support!!! Thanks to Michael and the support team.

We’ve got around 60 channels deployed and running at any given time. We process on the order of 9 million files per quarter. Mirth has allowed us to standardize our interfacing options, which helps not only with development, but with communication between us and prospective clients about what exactly it is they’re purchasing.

Radnet is a large outpatient imaging center operator. As such, we have a very large referral base. As everyone knows, the industry these days is around integrating the patient’s record between systems. To do this we looked at a lot of well known interface engine vendors on the market, and all of them had unrealistic pricing schemes by charging fees per interface. Since we have literally hundreds of interfaces, the total cost was ridiculous. Then we found Mirth which meets all of our required functionality for an interface engine, and the pricing cannot be beat.

We were able to successfully listen and process messages from a hospitals RPMS system into our backend systems with relative ease using Mirth. My background is working with Biztalk server and I have found mirth far easier to hit the ground running. I anticipate further projects in our organization using Mirth.

We use Mirth to get data into a syndromic surveillance system called RODS. Without Mirth, this would be a nearly impossible task for one person, who would have to write literally dozens of scripts to keep the data flowing and importing well. Using Mirth, I’m able to consolidate dozens of those data streams into just three or four channels that send it to our application listeners. Additionally, the relative ease of Mirth compared to writing raw HL7 scripts is magnificent, and allows me to train other personnel with few development skills for redundancy.

We have successfully implemented a number of systems using Mirth. Mirth has supplied us with flexibility and customizability that we just did not have before.

Only Mirth’s flexibility, price point and reliability is capable of working for us. Mirth has become the central HL7 hub that communicates all kind of RIS, PACS and reporting systems from our company and associated partners.

We are in the process of replace several standalone Java applications with Mirth Channels. The ability to utilize existing Java classes in the transform has made the process quite easy.

The first HL7 systems I worked with were at a laboratory testing company for results messages and we rolled our own solution for my project. While I actually enjoyed the programming, the experience, and feel proud of what we built, it took 3 times the man months we would have needed with Mirth. This tool really helps you build solutions quickly.

We operate a freestanding emergency room in Texas. Thanks to MIRTH we have tied software packages together from 7 vendors and implemented automated reporting for patient labels, daily census, billing data, and lab/imaging results. We can operate completely paperless and have an average patient door-to-door time of 84 minutes. The flexibility and insight MIRTH provides has been an invaluable asset for the center. We operate 24/7 365 and have had no significant issues keeping MIRTH up and online for our center.

After implementing our in house solution for HL7 data, we switched to Mirth because of the advantages of having a common platform and community.

We have investigated other products, companies, or solutions to drive us closer to our Meaningful use, and the Health info exchange initiatives. Mirth is a very robust, and cost effective, integration engine.

We have had many positive experiences to allow EMRs to communicate with our platform using Mirth Connect.

We are a few months from having the implementation of RadWhere done, we would not be able to contribute that story till then. We are also looking at using Mirth in other areas here. We store a copy of inbound orders (from EMR vendors) in a Mirth accessible database. Orders are then sent to Quest lab. When the results from Quest are delivered back through another Mirth channel, we use specific logic to match the result to an order so as to provide the EMR with their order specific, enhanced HL7.

We are a few months from having the implementation of RadWhere done, we would not be able to contribute that story till then. We are also looking at using Mirth in other areas here. We store a copy of inbound orders (from EMR vendors) in a Mirth accessible database. Orders are then sent to Quest lab. When the results from Quest are delivered back through another Mirth channel, we use specific logic to match the result to an order so as to provide the EMR with their order specific, enhanced HL7.

We used Mirth to automate the collection of CCDs from AllScripts Enterprise product and deposit them in our regional repository. We were able to do this even though the vendor stated they were months from having that functionality. The mirth tool set is getting better and better.

We started using Mirth Connect 1.7 and were immediately able to digest CCD document (with the help of the great Mirth support staff). We are now in beta with Mirth Match and Mirth Results.

We have selected Mirth as the result of a “Proof of concept” challenge between several providers. An e*gate solution had been in place before, and we were looking for a new service provider for the maintenance of the existing and the development of new processes. Competing products have been e*gate, a Microsoft product and Mirth. The e*gate provider quit the POC after reading the requirements. The MS provider showed up but was unable to show fully operational data flow as required. The Mirth provider fully implemented the requirements within the time slot available, showed even further development possibilities, we had enough time to make load tests (like : 1000 incoming messages simultaneously with 3 different destinations + transformations + filters) as well as failure test (what are the losses is network connection is interrupted). Needless to say that the decision for Mirth was very easy. In addition, the estimated manpower for full analysis and implementation was lower than estimated manpower for preliminary analysis for the MS product!

If you already have some interface experience and HL7 knowledge, even a complicated Mirth channel can be constructed very quickly. If you are new to interfaces, a basic channel is not hard to set up.

Mirth has enabled our practice to provide radiology interpretation services to many different practices and facilities that have a variety of RIS/HIS systems. it has even allowed in conjunction with AMICAS PACs to provide radiology interpretation services to facilities without a HIS/RIS. This has allowed us to become more efficient and allowed us to bring in business that might otherwise have been unobtainable.

Prior to deploying Mirth we used to manually type in all of our pathology test results that we received back from other laboratories, taking one person between 5-7 hours a week. Now we use Mirth to instead reformat received HL7 messages from other laboratories into a format acceptable to our Cache database. It has improved our turnaround times on releasing reports by up to 40%.Mirth is a very easy to use application and is 100% stable.

Mirth has reliably handled critical message interchange between our product and some of our partners for over a year now. Had we not decided to adopt Mirth, the time spent creating an in-house solution, not to mention the time spent gaining confidence with such a system, would have crippled us. With a 1000+ beds now serviced by our Mirth setup things are running as strong as ever.

Once you understand how Mirth function, it’s very easy to develop. Mirth is very flexible.

Mirth Connect has enabled us to fast track interfaces with our participation in HIE projects. Add another connector to a pre-existing channel…up and running…

Mirth has allowed our less technical team members to make significant contributions to our integration/interoperability projects freeing our traditional developers to focus on improving the applications user experience.

I started HL7 interfacing on an IDX ConnectR server. Developing interfaces on that platform was time consuming and labor intensive. I started playing with Mirth in my test environment and could not believe the difference. Time to create a channel and the amount of work required was so much less; I replaced as many IDX channels with it as I could in production and I am no longer implementing any new channels on the IDX platform. We process about 200,000 messages /day and Mirth is now handling 75% of that.

We were working on a custom solution for our feeds. We got nowhere in 5 months. I heard about Mirth and we were able to complete the project in less than a month. Now I turn to Mirth to see if it can help me in anyway before I move on to a custom solution.

I have 8+ experience implementing HL7 based interfaces with a mix of all possible Health Information Systems. Actually I had written my own interface engine (because that time there was no such excellent tool) and can definitely appreciate what Mirth has done. Using Mirth, I can churn up channels much quicker.

Mirth has greatly simplified our installations for interfacing with our product, and by allowing configuration changes to a channel without recompiling. I try to use Mirth to solve my design projects any chance I get.

Mirth has immensely contributed to allow our company to prepare and deploy channels for Results, Orders, ADT and ERA interface.

Mirth has made HL7 transformation easy and allowed rapid integration into our project.

We were under the gun to get an ADT message feed to our OB Tracevue system. The project manager for the OBTV roll out neglected to budget for an interface from the Meditech system (these can cost between 3000 and 10000 dollars). Instead of back pedaling on the budgetary numbers and asking for more money, we were able to implement Mirth, attach an existing ADT feed to it, add the OB Tracevue system as a destination. Worked like a charm and saved us alot of money.

The support was great in assisting with any issue we had.

We recently purchased a new Case Management system here at Johns Hopkins Medicine. Integration requirements for this project are varied and more complex than a typical integration effort. In addition to the standard HL7 messages requirements are additional archival patient health and final data needs. One of the challenges was to integrate data from our custom claims processing web application. Our current Interface Engine does not have the ability interface with web applications. Not a problem! I downloaded Mirth Connect and within hours had implemented and tested a file reader channel using the built in SMB protocol. This SMB to MLLP interface is just one of many solutions I am planning for Mirth connect here at the Hospital. Many Thanks!

Mirth has allowed us to achieve unbounded flexibility in routing messages in our infrastructure. Prior to Mirth we established point to point connections between hospitals and our RODS application. Now we put Mirth in the middle so that we have the extreme flexibility in transformation and routing. It has enabled us to do seamless migrations to new versions of our backend software.

The use of Mirth here has opened doors for everyone of our projects that we have not been able to complete in the past. Mirth has become a critical part of the success of our business. So much so that I have talked Hospitals and billing companies into using the Mirth product. Each customer that started using it is completely overwhelmed with the capabilities that Mirth provides.

Had great experiences with Mirth and its support people. I have commercial support that I used to help get me started with a couple of channels. I was able to take what I learned and develop into more complex interfaces. This product makes it so easy that coding projects I normally wouldn’t even think of tackling, I can now do with confidence.

We are in the process of moving to Mirth from Biztalk. Mirth itself is a superior product, eliminating the need for complex schemas and functiods that can be difficult to troubleshoot due to their compartmentalization. As a developer I find Mirth is “easy mode” for complex integration. The support provided by the Mirth team is second to none. Our primary reason for migrating off of Biztalk was the lack of support by our third party vendor. Mirth’s response to an urgent ticket I opened was 3 minutes, the other vendor averaged 5 hours.

We have developed a real-time interface between hospital’s registry system and Surescripts’ Rxhub system to query for drug fill history of ER patients. The system is in place and operational for more than 11 months now. The ER staff is very happy.

Mirth has been great to work with, both as a product, and as a company. We’ve crafted up several interfaces (groups of channels) to fit both custom and standard interface needs. I love that my group, using Mirth, is always the first to have their code completed, and we’re waiting on other groups to test.

This is by far the best product I have worked with to date. Each member of the Mirth team that I have worked with is extremely knowledgeable and easy to work with. I would recommend using Mirth and working with the Mirth team to any company.

I hope you realize how much we in the health industry appreciate Mirth. Keep up the good work!

Love the Mirth product. Support is great help. The software “just runs” and that is great for a busy IT department.

You guys rock!

I think the Mirth team does an excellent job. I have been happily using Mirth since version 1.4. If only I can convince my new boss to switch from Orion…I see a great future for Mirth in government work.

We started working with Mirth this January, after a 6 month selection process.

We have replaced our home-grown system. We spent several months on this but that was because of intensive testing. At the moment we are processing about 50K message a day and we are much more flexible in creating new communication channels.

We already had an in-house solution for creating / processing messages, but it was file-based. Mirth allowed us to very quickly deploy a live-messaging solution without hours and hours of development time, and it didn’t require us to redevelop our side. If we had to develop the LLP handling, logging, ACK’ing, etc. we’d still be developing it.

Too many successes to list and no time to type it all out. My goal is to get GE to drop that over bloated lousy software CCG based on Cloverleaf in Centricity CPS 9.0 and go with Mirth. Quickly, I author several programs in VB I replaced with Mirth so less time programming and more time completing a channel. Interfaces that we would have dreaded completing and I have no problems attacking with confidence. Lab interfaces were nightmares and are manageable now. Being a GE VAR we have many different clients with many different interfaces to PM and EMR and we can meet those needs better than any company now without the need for outside help. My favorite part of this is being able to suggest the removal of the slow overpriced interface coders that are hard to work with and replace them with Mirth on the other side.

To be honest I know nothing about HL7 and did not have a lot of time (I think I only had a few weeks or a month at most), but with Mirth it was more than enough and the clients were impressed with the results.

Time to deploy is fantastic and we have developed a solution for a customer that needed a research database and used Mirth as the sole integration engine for it. It helped this startup get past the huge initial cost of Cloverleaf or one of the other engines.

Since implementing Mirth VM in our environment we have 42 channels in production. I am impressed with Mirth’s ability to keep up with processing the thousands of messages we pass daily and we do have some channels with some complex filters and transformations. The support and development staff is very professional and very helpful. Whenever we are presented with a challenging situation I’m confident that they’ll do their best and work diligently in getting our issue(s) resolved.

Mirth, and Mirth Appliances have allowed our large radiology practice the ability to tackle numerous technically challenging interface projects. We are a leader in automating and integrating teleradiology reporting and workflow thanks to the Mirth product. In the rural areas our radiologists serve we have reduced the turn around time for patient results by days. In many cases we directly insert the radiology reports into remote EMR and RIS systems directly using channels we have built with Mirth.

Mirth has helped us overcome a lot of NextGen’s inherent hurdles and opened up many possibilities with a low overhead.

In a couple of months we developed, tested and deployed a HL7 interface between our EMR product and a PACS system. This interface eliminated duplication of data entry and streamlined order entry and reporting aspects of MRI, CT and Ultrasound investigations for a major client.

I’ve implemented one interface in my production environment using Mirth. I needed a simple way to pull data out of my clinical data repository and send it over TCP/IP LLP sockets to my enterprise interface engine. I had the interface developed and promoted in a day. It has been stable for over 1 year now. I’ve even configured it to send out alerts if there are any issues without much effort.

I have an EMR vendor that has a very specific non-standard HL7 format that they expect the results to be delivered in. Sun JCAPS is not able to do that easily and it’s been almost a year that my Integration dept has been working on getting that system to do what took me about 3 days of experimentation in Mirth to do.

Our business challenge that Mirth is solving is a narrative note interface between the local hospital and our EMR. Our current EMR allows for this type of interface but they are limited to one document type. With the Mirth engine I was able to expand this limited interface to now allow for sixteen plus document types. This will save about 35,000 documents from being faxed, printed and scanned into the system over a six month period. A low grade document scan has a storage cost of 30k. An imported document with no human interaction has a storage cost of 3k. Not to mention the ability to report discrete data on the interface message versus no discrete reporting on the image scan. Mirth is going to save time, storage, paper and not to mention lower our carbon footprint.

Clinical Systems Integration for a rural healthcare system. We are deploying an EHR and part of our architecture requires an ESB. Mirth was chosen because it not only works as a traditional integration engine with support for HL7, but it also will allow us to build a Service Oriented Architecture for our EHR. We currently have our HL7 messages for the EHR moving through Mirth, and are developing a document imaging query service which should be in production within a month.

We would like to look into Mirth as a replacement for our Rhapsody thus saving considerable money. We maintain our own servers however and are not likely to need hardware.

Mirth has provided a vital role for us. It has delivered such great service that all other options are looked at before I even consider a Mirth problem.

We have deployed three PICOs in one of our client hospitals and they are working flawlessly now. Two are in Cluster mode and one supports the testing and development environment.

The main benefit to our company is to allow us to move from one or two higher level developers doing all the HL7 work, to being able to use other people to install and tweak our HL7 work. It also made our IHE work last year, and this year, more flexible and streamlined than our previous methods.

Mirth makes our life easier by allowing us to be more flexible.

Mirth definitely has helped the organization in saving money by helping us create interfaces and share them in less amount of time.

If it wasn’t for Mirth, we would not have an interface engine.

Has enabled rapid adoption of HL7. Excellent product.

We installed Mirth successfully in numerous different environments. The flexibility of Mirth gives us the power to integrate our application into hospital environments without problems.

HL7 is the Great Hoax; all the vendors implement very limited and self-serving subsets. Because Mirth is so flexible, we can get data in via any available interface, whether it’s SOAP, direct to database, XML over HTTPS, whatever. Because the EMR vendors are often so uncooperative, having Mirth on our side to exploit any and every avenue to get data in is indispensable.

We looked at Iguana, Egate and Mirth. We kept Mirth running and it has worked fine.

We looked at Neotool and from a pricing standpoint Mirth won. Now that we have Mirth, the flexibility we have, we think would not be possible with any other product.

We like Mirth because of its flexibility and dependability.

We initially had an internally developed application written in Java and Perl that was very limited in functionality and we lost all internal development staff for it. Mirth has filled the need for additional functionality quickly.

We have looked at other applications. We are confident that Mirth will be very suitable for all our needs.

We are looking if Mirth is a replacement for our Cloverleaf system. Mirth has a lot of features that cloverleaf doesn’t have.

We chose Mirth to fill a gap between our legacy enterprise system (egate) and our new enterprise system (ensemble). It allowed us to do some integrations that were limitations in egate, while we got our hands around the learning curve for our new system.

We chose Mirth over Neotool.

We are upgrading our older Datagate to Mirth. We’d look at Sun’s offerings and the complexity is too high. Final decision was made based on our work with ICA – they recommended Mirth, so we will be using it. It’s also a simpler package and appears up to the task of replacing Dgate, and future problems as well.

Our organization is using Neotool but it was not ideal for my project. I needed to extract data from our SQL Server 05 and send it as HL7 messages to Cerner. Mirth was simple and intuitive. It was the perfect solution and we ended up using it to extract messages from our Cerner system to our SQL Server database.

Previous Interfaceware customer. Like what Mirth offers around ease of use and extensibility.

Using Mirth to migrate from Interfaceware’s Chameleon software tool.

Selected over egate/jcaps.

We found you all, called you, talked, and we liked you, and could work out a price to fit our needs, and your solution can grow as we do. Your solution allowed us to successfully and in a very short amount of time integrate our solution with a large EMR company. It allowed us to fulfill a contract with a large hospital system enabling them to use our product through the EMR system.

I do not consider proprietary solutions. Your only competitor was OHF and you have left that behind in the dust. You have been central in dealing with a legacy database, and a practice management vendor that wants to charge for any change to the database.

Definitely reduced cost and development time.

Mirth saved us from having to pay one of our vendors ~ $140,000 for interface changes to accommodate a new pharmacy application, plus it enabled us to totally convert 14 hospitals from a legacy pharmacy app to a more modern one in less than 6 months.

We looked to Iguana and OPENLink Siemens. We choose Mirth.

We had many different integration engines (internally developed), often one different system for every pair of applications. Now, with Mirth, we tend to centralize most of messaging systems in our organization.

Feature rich and simple to use.

Have quovadx/cloverleaf. Been having issues- time for upgrade – expensive connections. Added Mirth as an experiment, now have live production ADT in place with several others in various stages.

We looked at the proprietary products on the market and found that Mirth and your PICO and Enterprise solutions exceed the capabilities of these competitor’s products independent of price. We are also excited about testing your Virtual Devices as we expand our own use of virtual servers.

Our Mirth team was able to successfully integrate our HIS (Informix), ancillary results management system (Java/Oracle) and LIS (TD/Oracle). We continue to find ways on how Mirth can solve other challenges in our integration efforts.

Well, The Mirth team was able to save my company a tremendous amount of money in interface costs when we went live with the NextGen EHR. We only had to purchase one Patient Demographic interface for each or our external systems due to Mirth

We have many success stories with Mirth, most of them about our ability to deliver a finished interface to specifications faster than any of the dozens of vendors we work with expect. For a small community hospital, our interface capabilities and flexibility exceed that of much larger organizations with greater resources. Specifically, a vendor once told me that deploying a new engine and developing the interfaces that we did with Mirth to exchange data with their applications would have taken months, instead of the days it took us.

I looked at NeoTools and Mirth. I chose Mirth.

In my 10 years of working with interfaces, this is one of the best products I have worked with and it dazzles my co-workers when we set up some test scenarios and they see how easy it is to use.

As a company dedicated to safety in healthcare, Mirth has made a significant impact to gather real-time actionable data that is used to save lives.