Skip to content

InterSystems IRIS for Health

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

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.

Evidence Status

Confidence is high for vendor positioning. Current evidence comes from official InterSystems UK product and healthcare pages, so it is not independent proof of performance, implementation effort, licensing boundaries, or operational outcomes.

Current IRIS for Health documentation includes NHS Interoperability Toolkit material and the wiki separately tracks a GP Connect supplier-progress row for InterSystems IRIS for Health (Middleware) Send Document (Send) v2.0.1. These are useful standards-adjacent evidence points, but they should not be treated as product-wide NHS conformance, DSIC compliance, MESH/ITK3 onboarding, or customer deployment proof without product/version, capability, assurance, and deployment artefacts.

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.