Skip to content

InterSystems IRIS for Health

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

User Interface

FHIR Explorer Build tab with a Patient address query, strict handling and query-builder controls.

Building FHIR queries. The FHIR Explorer combines a typed query with a form-based query builder. This example comes from the IRIS for Health 2026.2 documentation, checked 15 September 2026. Select the image to open it at full size.

Official InterSystems Positioning

InterSystems positions IRIS for Health as a cloud-first healthcare data and application platform for building information-rich, FHIR-based healthcare applications and managing healthcare data.

Role in the Portfolio

IRIS for Health is the developer and healthcare data platform layer. It sits underneath or adjacent to application and interoperability use cases that need healthcare data management, standards support, and application development capability.

Current Release Boundary

The official release notice dated 22 July 2026 makes IRIS for Health 2026.2 generally available as a Continuous Delivery release. The March 2026 announcement identifies 2026.1 as an Extended Maintenance release; these are different release streams, not evidence that every customer or cloud service has upgraded (SRC-293, checked 2026-09-08).

The 2026.2 release notes add FHIR Explorer for querying and testing InterSystems or third-party endpoints, configurable accepted OAuth audience values, changed handling of included search results and Binary reads, and optional bypass of structural validation for migration ingestion. These are product/version-specific mechanics; the bypass can admit malformed data and requires alternative integrity controls. They do not establish UK profile conformance or managed-service rollout.

The July 2026 public support alerts also make deployed build, patch, audit, access-control, and upgrade evidence material. Use the HealthShare support-alert boundary before relying on a generic security or interoperability claim.

Evidence Status

Confidence is high for vendor positioning and version-specific release documentation. These sources do not independently establish performance, implementation effort, customer licensing boundaries or operational outcomes.

Current IRIS for Health documentation includes NHS Interoperability Toolkit material. Separately, the June 2026 NHS supplier-table snapshot recorded InterSystems IRIS for Health (Middleware) Send Document (Send) v2.0.1; the September table omits that row, leaving current IRIS supplier status unconfirmed. Omission alone does not prove withdrawal. These evidence points do not establish product-wide NHS conformance, DSIC compliance, MESH/ITK3 onboarding, GP2GP record-transfer support or customer deployment.

Programme CORTISONE adds a separate UK Defence healthcare evidence thread: vendor evidence says MOD selected HealthShare and IRIS for Health for CORTISONE, and MOD performance files name InterSystems Corporation for Programme CORTISONE IP and EMPI measures. This supports programme-role evidence for IRIS for Health, but not exact live configuration or contract schedule.

Follow-up Evidence

  • Current technical documentation for FHIR, data modelling, APIs, deployment, and operations.
  • UK hosting, compliance, security, and support material.
  • Reference architectures showing how IRIS for Health relates to HealthShare, FHIR Services, and customer applications.
  • Independent implementation or customer evidence where IRIS for Health is the named platform.
  • Current NHS or standards-body conformance/onboarding evidence naming IRIS for Health product/version, standard/capability, message/profile scope, date, and status.