Skip to content

eConsult / UK NHS Triage

This page tracks the eConsult example from the official InterSystems UK evidence set.

Official InterSystems Claim

InterSystems says eConsult selected InterSystems IRIS for Health to support data interoperability and integration across eConsult platforms in an NHS triage context. Current InterSystems partner material also says eConsult, now part of Huma, chose InterSystems Health Connect Cloud (HCC) to simplify NHS integration and accelerate delivery.

Product / Service

InterSystems IRIS for Health historically; current InterSystems evidence also names Health Connect Cloud (HCC) as an eConsult / Huma integration route.

Customer and Marketplace Validation

eConsult Health's own 2021 press release says it selected InterSystems IRIS for Health to support NHS interoperability and expansion of eConsult and eTriage. That is customer-side evidence for the supplier-selection claim, though it remains historic and is not proof of current architecture without a newer source.

The GOV.UK Digital Marketplace G-Cloud 14 listing validates the eTriage service context: eTriage is listed by eConsult Health for NHS emergency departments, urgent treatment centres, and minor injury units, with integration to customer clinical systems, ECDS coding, PDS/PAS integration, tablet-based use, and public-cloud delivery. The listing does not name InterSystems, so it supports the eTriage NHS context rather than the InterSystems component.

The 2026-06-21 current-source pass found current InterSystems vendor/partner evidence and public Digital Front Door signals. InterSystems' HCC partner PDF says eConsult, part of Huma, chose HCC for NHS integration and that InterSystems delivers, hosts, and operates the platform. InterSystems' SHC24 partners page lists eConsult Health - a HUMA Company and says the platform now offers digital triage in 14 NHS Emergency Departments.

Adjacent public signals strengthen the current-service reading without closing the formal architecture gap. HSJ Partnership Awards 2025 lists InterSystems & eConsult as finalists for a digital triage platform for NHS urgent and emergency care settings with InterSystems IRIS for Health. Public eConsult leadership posts describe a King's College Hospital NHS Foundation Trust Digital Front Door / eTriage deployment, Epic and Adastra routing, and InterSystems UKI involvement. Public procurement notices record a London North West University Healthcare NHS Trust award to eConsult Health Limited for an NHS London Emergency Department Digital Front Door solution across five emergency departments; that procurement evidence names eConsult but not InterSystems.

Evidence Status

Confidence is now moderate-high for the historic customer-side selection of InterSystems by eConsult, high for the current marketplace/procurement description of eTriage service scope, and moderate for current InterSystems role evidence. The current role evidence is stronger than the 2026-06-18 state because InterSystems now names eConsult / Huma in HCC partner material and public Digital Front Door material names InterSystems & eConsult in an NHS urgent and emergency care setting.

The confidence boundary remains important. The current evidence still does not provide a Huma, NHS, customer-approved, or technical architecture pack confirming product versions, component responsibilities, clinical-safety ownership, DCB0129/DCB0160 artefacts, interface specifications, service levels, or live site-by-site scope. eConsult now sits in the Huma Workspace / Huma Cloud context in acquisition material, so live-architecture claims should be limited to the named IRIS for Health / HCC public evidence until Huma, NHS, or customer documentation confirms the deployed component architecture.

Remaining Follow-up Evidence

  • Huma, eConsult, NHS, or customer publication confirming the current InterSystems component role, product version, and deployment scope.
  • NHS or customer material describing Digital Front Door / eTriage integration architecture where InterSystems, Epic, Adastra, HCC, IRIS for Health, and any integration partner roles are named.
  • Product or platform documentation showing whether the current architecture uses IRIS for Health, Health Connect Cloud, both, or separate deployment profiles.
  • Evidence separating triage-workflow outcomes from underlying platform claims.