InterSystems Health Connect™ Cloud

What do you like best about the product?

Very flexible. ETL and DTL is very easy. everything can be done like just drag and drop methods. Integrations are powerful. A very good Low code no code concept. For what the health connect provides as features??? It is worth it.

What do you dislike about the product?

Understanding ObjectScript isn’t something everyone has, especially when you need to write a small piece of custom code. The documentation is very good overall, but it can be a bit difficult to navigate and to find the right section when you need it.

What problems is the product solving and how is that benefiting you?

Data transformation and performance upscaling are key for me. In healthcare, you don’t want any delays at integration touchpoints, and Health Connect provides faster, better DTLs than other engines in the market.

What do you like best about the product?

Because InterSystems Health Connect sits on top of InterSystems IRIS, it has access to the full suite of interoperability tools and the full performance of IRIS, which has been honed to scale horizontally and vertically. Integration, especially with health care data, is easy with Health Connect and its built in dictionaries, schemas, and tooling.

InterSystems is actively upgrading the user experience as well, replacing a dated Zen front end with a modern Angular UI. This will allow them to continue to refine their user interface in a modern technology with many additional tools available to them.

If you're an InterSystems customer, their best in class WRC will respond to any issue you have and provide support that, frankly, goes way beyond any other services I've used.

What do you dislike about the product?

Health Connect doesn't allow you to program in ObjectScript and build classes, which I view as a key part of scalable interoperability.

What problems is the product solving and how is that benefiting you?

Health Connect is a healthcare based enterprise service bus. It sits shoulder-to-shoulder with other engines like Cloverleaf and Rhapsody. It's simple to build if you aren't a programmer, but the XML backend makes it easy to code at scale if needed.

What do you like best about the product?

What I like most about InterSystems Health Connect is how practical it is in real-world use. It makes connecting different healthcare systems much less complicated than you’d expect, even when they use different formats or standards. Once everything is set up, it runs reliably in the background, which is really important in healthcare where you can’t afford delays or errors.

What do you dislike about the product?

What I dislike is that the learning curve can be quite steep, especially if you’re new to the platform or don’t have prior experience with similar integration tools. Some parts of the interface feel a bit outdated and not as intuitive as they could be, which can slow you down at the beginning.

What problems is the product solving and how is that benefiting you?

For me, the biggest benefit is that it centralizes and simplifies that whole process. Instead of building and maintaining separate connections between each system, everything goes through one platform, which saves a lot of time and reduces errors.

What do you like best about the product?

What stands out most to me about InterSystems Health Connect is its ability to unify fragmented healthcare systems into a single, interoperable ecosystem. Healthcare data is often siloed across EHRs, labs, imaging systems, and third-party applications, and Health Connect’s strength lies in seamlessly integrating these using standards like HL7, FHIR, and APIs.

I particularly appreciate its real-time data exchange capabilities. In a clinical context, timely access to accurate patient data can directly influence outcomes, so having a platform that ensures low-latency, reliable interoperability is extremely valuable.

Another aspect I like is its scalability and flexibility. It supports both legacy systems and modern cloud-based architectures, which is critical because healthcare organisations rarely have the luxury of starting from scratch. Health Connect acts as a bridge between old and new technologies.

Finally, from an AI and data perspective, I see strong potential in how integrated data can be leveraged for analytics, predictive modelling, and decision support. Clean, connected data is the foundation for meaningful AI in healthcare, and platforms like Health Connect make that possible.

What do you dislike about the product?

One limitation is that Health Connect can have a steep learning curve, especially for developers new to InterSystems technologies, and customization or integration work may require specialized expertise.

What problems is the product solving and how is that benefiting you?

InterSystems Health Connect solves the problem of fragmented healthcare data by enabling seamless integration between different systems like EHRs, labs, and imaging platforms. This improves data accessibility and real-time information flow.

For me, it’s beneficial because it provides a reliable foundation for building AI-driven healthcare solutions, such as wound analysis systems, where clean, connected, and timely data is essential for accurate insights and better decision-making.

What do you like best about the product?

I love InterSystems Health Connect for its effective ability to connect different systems easily and efficiently, especially in environments that require continuous data exchange. It is characterized by its high stability and ability to handle large amounts of data without issues, and it supports standards such as HL7 and FHIR, making integration seamless and flexible. Additionally, it provides a good balance between strong performance and flexibility in implementing integration processes, and it has a good capability to monitor data flow effectively, which facilitates maintenance and technical support. Moreover, the system has good flexibility in building and modifying integration processes according to business needs and is considered reliable in complex work environments.

What do you dislike about the product?

One of the aspects I see that can be improved in InterSystems Health Connect is ease of use, as the interface may be relatively complex for new users and requires time to get accustomed to. Additionally, the initial setup and configuration process can be lengthy and requires good technical expertise, especially in large environments or when implementing complex integrations. Furthermore, the documentation could be clearer and include more practical examples to facilitate understanding and application. Sometimes, also, some customization processes require additional steps or more time, which may affect the speed of execution.

What problems is the product solving and how is that benefiting you?

InterSystems Health Connect helps me connect different health systems, improve data integration, and facilitate access to it. It reduces errors by minimizing manual input and speeds up data transfer for better decision-making. It reduces complexity in system management and improves the efficiency and quality of data.

What do you like best about the product?

I like the drag and drop functionality and that there are buttons for a lot of things. I also like the learning materials on learning.intersystems.

What do you dislike about the product?

The UI looks a bit old and UX is hard to navigate at times. For example there are places that are missing a "Continue"/"Go back" button which I would appreciate.

What problems is the product solving and how is that benefiting you?

Message transformation.

What do you like best about the product?

What I like most about InterSystems Health Connect is its reliability and flexibility when handling complex healthcare integrations. Its powerful message transformation and routing capabilities make working with standards like HL7 and FHIR much more manageable. The ability to customize and extend integrations using its tooling is a big advantage. I appreciate the robust monitoring and debugging tools, which make it easier to quickly identify and resolve issues. The high performance and stability, especially when processing large volumes of messages in real time, are impressive. It allows us to onboard new systems and interfaces without significant rework, thanks to its scalability. Its centralized integration management simplifies what would otherwise be a very complex environment. Overall, it provides a dependable and efficient platform for managing healthcare integrations, significantly reducing operational overhead compared to more fragmented approaches.

What do you dislike about the product?

While InterSystems Health Connect is a powerful and reliable platform, there are a few areas that could be improved. One challenge is the learning curve, especially for new users who are not familiar with its architecture or underlying technologies. Getting fully comfortable with development and configuration can take time. The user interface could also be more modern and intuitive. While it is functional, certain tasks—especially around navigation and configuration—can feel less streamlined compared to newer integration platforms. Additionally, documentation can sometimes be dense or fragmented, making it harder to quickly find specific implementation guidance. Debugging complex issues, while supported by good tools, can still require deep expertise in some cases. Initial setup and configuration can be resource-intensive depending on the environment. Overall, these are not deal-breakers, but improving usability, onboarding, and documentation would make the platform even more efficient and accessible, especially for new users.

What problems is the product solving and how is that benefiting you?

InterSystems Health Connect simplifies complex system interoperability and data consistency issues. It centralizes integration, reduces redundancy, enhances reliability, automates message processing, and ensures scalable, seamless information flow across healthcare systems.

What do you like best about the product?

I've been impressed with InterSystems Health Connect with regards to the intuitiveness of UI/UX, while still maintaining an accessible back end and available customization. Health Connect allows for large scale interface integrations with a focus on performance and scalability.

What do you dislike about the product?

The price of Health Connect can be a large hurdle for smaller networks, though this is offset by great ROI when it comes to institutions requiring many integrations and scalability. It can be difficult at time to find the right support resources, but once you do, the support is fantastic.

What problems is the product solving and how is that benefiting you?

Health Connect solves the issue of connecting many disparate EHRs, each with their own custom formatting, at scale. Prior to transitioning to InterSystems Health Connect at my prior position, the number of interfaces/messages quickly became too much for the system to handle, requiring system downtime, new interfaces took much longer (5x) to implement, and maintenance time was drastically reduced (10x) with much better managed support.

What do you like best about the product?

I appreciate InterSystems Health Connect's ability to convert data between different formats and ensure patient data is always accessible. I find its reliability and speed critical for maintaining efficient patient care. I also like the amazing customer support, and the initial setup was pretty straightforward.

What do you dislike about the product?

I think the complexity of its interface could be made simpler. Sometimes it could be a challenge, especially when you don't have the personnel. We are short-staffed, so when the person in charge is not available, operations have to stall as they wait for the person who knows the system well. If it could be made in a language that could be understood by a regular employee it could be better.

What problems is the product solving and how is that benefiting you?

I use InterSystems Health Connect to convert data formats and ensure constant access to patient data. It solves system fragmentation issues and reduces downtime.

What do you like best about the product?

I like the simplicity and cleanliness of the UI in InterSystems Health Connect. Compared to Epic, which I find very cluttered and annoying, the user interface of InterSystems Health Connect is easier to use. The initial setup of InterSystems Health Connect was easy.

What do you dislike about the product?

I do not like the options for sign in

What problems is the product solving and how is that benefiting you?

I use InterSystems Health Connect to solve issues with accessing out-of-state patients’ stress test records, making it easier to view their files in EPIC.