+1 619 822 1745 [email protected]

Rate your Engine’s feature set and ease of use

We asked participants to consider the following:

  1.   How does the engine handle different protocols (TCP / IP, SFTP / SOAP, Web Services, etc…)?
  2.   What level of compatibility does the engine offer with other software and hardware?
  3.   How complex / easy is it to duplicate, reuse, or copy interfaces from server to server with your engine?
  4.   How is interface version control and documentation?
  5.   Does the engine have predefined connectivity adaptors?
0% – Incomplete feature set and not user-friendly
100% – Full feature set and very user-friendly
  • Corepoint 96% 96%
  • Cloverleaf 88% 88%
  • Rhapsody 88% 88%
  • Ensemble 86% 86%
  • Mirth 80% 80%
Expand to read user comments
Corepoint
  • The Corepoint Integration Engine is rich with features that allow easy replication of data streams; powerful message transformation, filtering, and validation tools; and robust correlation mapping capabilities. All within a collaborative development environment, capable of scaling from single users to support large decentralized integration teams. It’s derivative model that allows inheritance of various message format translations for countless protocols, including HL7, XML, DICOM, NCPDP, X12, and FIHR to name a few. It has excellent connection monitoring, error and queue depth alerting, assured availability, and disaster recovery capabilities. Most importantly, it is a stable, reliable solution for what has become the most critical component of our interoperability infrastructure. Couple this tremendous product with a very knowledgeable and highly accessible support staff and now you have adopted a competitive advantage to better accommodate the many changes facing our industry.
  • Easy to program. If you get stuck, Corepoint help is quick to assist.
  • Rapid development, feature rich functionality.
Cloverleaf
  • The ability to use very advanced scripting with TCL makes this engine indispensable. Straight-forward database interactions, across a number of databases, would be ideal.
  • It has a full feature set, but there is a big learning curve for some of the modules.
  • One of the most important things is that we are able to completely isolate each customer and their throughput. Each customer gets their own processing and thus one customer does not affect another. Using “sites,” one customer cannot impact another. This is very important. Other engines claim they do it, but in reality they don’t. Cloverleaf’s site/process/connection structure is the best in the biz.
Rhapsody
  • The graphical/visual representation of interfaces and the ease of viewing data elements included or excluded make the work interesting and clear.
  • The mapping filter is very easy to use and meets 90% of our mapping requirements.
  • Strong graphical development environment. Supports both simple and complex interface paradigms using the same toolset. Need to continue to enhance the JavaScript development support.
Mirth
  • We really only have view-only access on the dashboard. But the features seem sufficient (though not dazzling) for our needs.
  • A bit technical to configure, need more graphical tools to implement a new connection.
  • No automated way to move interfaces between development, test, and production environments. Comparing differences between environments takes a external tool.
  • Not easy to create translation tables, unlike other engines.
Ensemble
  • The ability to reuse interfaces makes the engine really easy to use. The code control is lacking, but is improving with each release. The tools to tune the interfaces are not that great and make finding a problem difficult. Back compatibility is a plus and a minus. There is so much inefficient base code that is slow and needs to be updated, but it makes it easy to upgrade because the base code rarely changes.
  • If you cannot figure it out then their help desk will. Support is great, so when starting with a new feature support is able to answer your questions, if you have them.
  • Can’t live without the mirrored environment minimizing downtime.