We use IRIS for integration with labs and the implementation with all labs and our central clinic has been quick and easy. Using HL7 very easy and calls APIs and Database without create big transformations. Using IRIS as repository of data of patients, making a RESP API with only 3 clicks and deploy it in production without stop any process.... We saved a lot of time and money.

This is the best all-in-one for interoperability application that I've used ever. It is easy to use, easy to learn and is supported by a big community that can help me.

IRIS requires a qualified person for its administration, there is a lot of configurations, levels, permissions, etc.. It's not easy configure security with a out-standard configuration.

Overall InterSystems Iris for Health has been an incredible interoperability tool. It has shortened development time and smoothed the path to production for our team. It has great support and resources to back it so that it is keeping pace with the advancements of our modern world. It is truly an an amazing interoperability tool and I have had nothing but great experiences both with the tool and the company.

The InterSystems Iris UI is incredibly intuitive and they offer several out of the box features that are quite impressive. InterSystems IRIS for Health has built in capabilities for HL7 data handling and premade data transforming functions to get you working quickly. It also allows for incredible customization so that you can adjust those out-of-the-box features to meet the needs of your organization, vendors or use case quickly and effectively. On top of all of this the access to documentation, learning materials, and the InterSystems Community of Developers makes InterSystems Iris one of the best Interoperability tools I have had the chance to work with simply because the answers are at your fingertips. And if you cannot find an answer in the documentation or forums then connect with the InterSystems Worldwide Resource Center and they will get you in touch with area experts so that there is no problem out of reach.

It would be nice to see source control as part of the out of the box features that comes with InterSystems Iris, though there are well documented and proven methods to get this implemented. The base code is in ObjectScript so you will need to learn and familiarize yourself with this language before you can dive into custom functions and classes. There is a lot of documentation and courses available to set you on the right path for ObjectScript development and you do not need to know ObjectScript on day 1 to begin developing with InterSystems Iris.

Support is very good, as soon as you have an issue you can open a discussion in a small but growing community, or contact support that will help you as a peer developer if needed.

Having an inmense amount of features integrated with the solution, from web interface, to interfaces with different kind of technologies, to database.

Having that vast catalog of features comes with a cost (literally and figurative) integration makes harder, although InterSystems is working to simplify it.

I am happy with the product in daily BAU in my Role.

Intersystems IRIS is good product and easy to learn and implement the interfaces in healthcare domain.The huge documentation gives a clear idea about product and each and every component. This is helpful for new developers to use the IRIS for their BAU.

As I am a developer in healthcare domain few features are missing and it is directly not supporting in the IRIS. Example RTF file conversion, there is no direct components to handle it and we need to rely on third party software to implement the interfaces.

My overall experience was good as the query performance increased, and the time required for managing the database fell greatly in these two odd months, from when we began.

The speed of performance of IRIS is too good and fast. We were able to get around 2500% increase in query performance after our switch, which is too good. Also the process of migration and scaling due to heavy lifting is also easier.

We hit several barriers in implementing as it is still quite new and had to use some workarounds as there wasn't much clarity in the documentation