Skip to content

North West London ICS

This page tracks the North West London Integrated Care System example from the official InterSystems UK evidence set.

Official InterSystems Claim

InterSystems says North West London ICS used HealthShare Health Connect Cloud as a cloud interoperability service connecting multiple acute trusts and a single EHR instance with internal and external systems. The same source states a population served of 2.1 million.

Product / Service

HealthShare Health Connect Cloud.

Evidence Status

Confidence is moderate. The InterSystems customer success story is now corroborated by an independent Digital Health report and an AWS Marketplace partner blog, both describing North West London ICS use of HealthShare Health Connect Cloud on AWS and including Imperial College Healthcare NHS Trust-side quotations.

An independent 6B Trust Integration Engine list also records several North West London trusts with InterSystems Healthshare Health Connect as their TIE as of February 2026, including Chelsea and Westminster NHS Foundation Trust, Imperial College Healthcare NHS Trust, and The Hillingdon Hospitals NHS Trust. The same 6B page warns that its list is a best-effort compilation from FOI logs and news and may be inaccurate, and it lists London North West University Healthcare NHS Trust as unknown.

North West London acute-trust recruitment evidence adds a narrower official technical signal. A Hillingdon Hospitals NHS Foundation Trust Trac advert says a Senior Systems Integration Specialist would design, develop, and maintain interfaces using the Intersystems Health Connect integration engine, liaise with suppliers, and manage migration of current interfaces to the Trust Integration Engine (TIE). A related North West London acute-trust job-description archive requires experience with Intersystems Health Connect and interface development using Cache ObjectScript, HL7, FHIR, and SQL.

This is still not the same as an official NHS/customer programme page or procurement record. The Digital Health article, AWS blog, 6B list, and Trac recruitment material provide external or acute-trust corroboration, not definitive customer-side validation of the current ICS-level live scope, cloud service, service levels, or outcomes.

The 2026-06-21 current-source pass checked the old and new North West London ICB web estates, member-trust search results, and public procurement search routes. It found the Hillingdon / North West London trust Health Connect technical context above, but no stronger public ICB, board, contract-award, or procurement source naming a North West London ICS Health Connect Cloud procurement or current operating model. The remaining work is therefore customer/procurement validation, not another vendor or trade-source pass.

Remaining Follow-up Evidence

  • North West London ICS or member trust publication confirming the implementation.
  • Procurement or contract award record for the relevant integration service.
  • Current operating-status evidence, including scope, connected systems, and service continuity.
  • Outcome evidence from the ICS, member trusts, or independent evaluation.