Skip to content

Health Connect

This page tracks Health Connect from the official InterSystems UK healthcare product set.

Official InterSystems Positioning

InterSystems positions Health Connect as a healthcare integration engine for high-volume transaction support, process management, monitoring, and secure data exchange. Its current product page emphasises the managed cloud offering.

User Interface

Health Connect Visual Trace showing sample messages passing between an inbound service, a business process and an outbound operation.

Message tracing. This administrator view follows related messages through an integration production. The screen uses sample messages and comes from the Health Connect 2026.2 documentation, checked 15 September 2026. Select the image to open it at full size.

Deployment Choices

The official fact sheet also documents self-managed deployment on premises or in a private or public cloud. Health Connect therefore names the integration product; the deployment model determines who operates it. Its practical tools include message transformation, failed-message handling and resend, message tracing, and monitoring (SRC-348, checked 2026-09-09).

Standards Positioning

InterSystems says Health Connect supports HL7 v2, HL7 FHIR, DICOM, IHE profiles, APIs, cloud-based data exchange, and current health standards. A 2019 InterSystems UK statement also said NHS FHIR-profile components made available to NHS customers included support for GP Connect and Transfer of Care.

Health Connect Cloud documentation describes the cloud service as a low-maintenance healthcare integration engine supporting common standards including FHIR, HL7 v2/v3, IHE profiles, CDA/C-CDA, DICOM, and X12. InterSystems Network Connect documentation separately describes secure cloud-service connectivity using VPN or private-circuit patterns.

Cloud Services Portal documentation adds managed-service mechanics that apply to InterSystems cloud deployments, including subscription, billing, cloud provider, region, tenant, deployment size, high availability, and service-level settings. The UK cloud-hosted services overview adds vendor-stated managed-service controls such as monitoring, isolated VPCs, a stated SLA, encryption, optional backups, and disaster-recovery positioning.

Role in the Portfolio

Health Connect supplies integration between applications within the HealthShare-related product space. HealthShare connected-care record products and FHIR Services managed infrastructure have separate roles.

Clinical Viewer Boundary

Clinical Viewer is not part of Health Connect in the current product reading. Health Connect covers integration-engine functions, while Clinical Viewer is a HealthShare clinical presentation component associated with longitudinal-record access and the Unified Care Record proposition.

Current Release Boundary

InterSystems announced Health Connect 2026.2 general availability on 22 July 2026 as a Continuous Delivery release; 2026.1 is the separate Extended Maintenance release. This establishes a software release boundary, not the version running in a named Health Connect Cloud tenant (SRC-293, checked 2026-09-08).

Public July 2026 alerts affect selected Health Connect FHIR and upgrade paths. The HealthShare support-alert boundary records the source scope; customer-specific build, configuration, correction and regression-test evidence remains necessary.

Evidence Status

Confidence is high for current vendor positioning, Health Connect Cloud standards-positioning documentation, and InterSystems cloud-service deployment mechanics. Confidence is moderate for dated GP Connect support claims. The 2019 GP Connect statement and generic standards support should be validated against current Health Connect documentation, NHS supplier assurance material, standards-body rows, onboarding artefacts, and customer deployment evidence before use in current implementation analysis. The 2026-06-20 standards-product-map audit found no current NHS or standards-body row in this pass that names Health Connect as currently ITK-conformant, GP Connect-assured, MESH-onboarded, or ITK3-conformant. The GP2GP pass likewise found no public evidence that Health Connect is GP2GP-assured or deployed for GP2GP record transfer.

Remaining Follow-up Evidence

  • Customer-specific managed-service hosting, monitoring, operations, support, and service-level documentation.
  • NHS GP Connect, GP2GP, Transfer of Care, and other UK interoperability assurance evidence beyond the dated 2019 statement.
  • Customer-side evidence for Health Connect Cloud deployments.
  • Current NHS or standards-body conformance/onboarding evidence naming Health Connect product/version, standard/capability, message/profile scope, date, and status.