Skip to content

HealthShare Unified Care Record

This page tracks HealthShare Unified Care Record from the official InterSystems UK healthcare product set.

Official InterSystems Positioning

InterSystems positions HealthShare Unified Care Record as a shared care-record platform that aggregates, normalises, and deduplicates decentralised data for workflows, analytics, FHIR applications, and AI use cases.

User Interface

Clinical Viewer patient search with demographic search fields, matching records and source identifiers.

Opening the longitudinal record. Clinical Viewer lets the user select a person and inspect contributing record identifiers before opening their record. This illustrates UCR's clinical access surface, rather than its underlying data store. Published in the InterSystems Clinical Viewer brochure; release and customer configuration are not stated. Select the image to open it at full size.

Role in the Portfolio

Unified Care Record is the longitudinal record component of the HealthShare family. It is the most directly relevant product page for shared-care-record, regional record-sharing, and longitudinal patient-record synthesis topics.

Clinical Viewer Relationship

Clinical Viewer is not the same thing as Unified Care Record. InterSystems documentation lists Clinical Viewer separately from Unified Care Record within HealthShare, while the UCR product page and resource material describe Clinical Viewer as the way users access the longitudinal HealthShare record through desktop, mobile, browser, or embedded workflows.

Access and Governance Boundary

The UCR resource material supports a stronger product-boundary reading than the product page alone. Unified Care Record is the longitudinal record and data-unification layer; Clinical Viewer is the direct-care presentation route; and local deployments still decide identity matching, SSO, consent, user provisioning, security controls, monitoring, debugging, and role-specific information access.

Current Operational Evidence

Public July 2026 notices add specific UCR consent, FHIR, SSO and upgrade checks through the HealthShare support-alert boundary, plus a UK NRL pointer-labelling case. They do not identify an affected or corrected customer estate.

The ODS autoload advisory describes excessive patient caching after MPI events, despite autoload being disabled, in its specified UCR versions. It identifies correction HSDD-2364 in 2026.1 and patches for older releases. Here ODS means the HealthShare data-store component; it must not be confused with NHS Organisation Data Service or treated as NHS ODS integration evidence (SRC-300, checked 2026-09-08).

Evidence Separation

The high-risk audit on InterSystems Standards Product Map treats Unified Care Record as a strong shared-care-record product capability, not a complete implementation proof. Keep these layers separate:

Evidence layer Supported reading Still needed
Product capability UCR aggregates, normalises, and deduplicates decentralised data for longitudinal-record, workflow, analytics, FHIR, and AI use cases. Customer architecture, data-source catalogue, licensing, tenancy, operating model, and live status.
PRSB CIS relevance HealthShare PRSB CIS conformance is relevant to UCR record-content questions. Certificate/scope detail, assessed sections, exclusions, component coverage, and local CIS section mapping.
Clinical Viewer access Clinical Viewer is the presentation/access route over the longitudinal HealthShare record. Role/view configuration, RBAC, SSO, audit, embedded workflow, specialty views, and version-specific behaviour.
DSIC / GP Connect adjacency UCR can be relevant to shared/integrated care and GP Connect consumption patterns. DSIC catalogue/supplier evidence, GP Connect assurance, national-service onboarding, supplier responsibility, safety, and governance artefacts.

Evidence Status

Confidence is high for vendor positioning. Birmingham / West Midlands sources provide stronger external evidence that InterSystems HealthShare architecture is used in a regional shared-care-record context, but this page should still distinguish generic product capability from local configuration and governance.

BSMHFT's FOI 052/2025 independently confirms the HealthShare supplier and three-area collaborative Shared Care Record contract through April 2029. It strengthens customer deployment evidence but does not specify the UCR product version, licence scope or configuration. The separate MERIT contract's continuity remains a distinct question.

Programme CORTISONE adds UK Defence healthcare relevance for HealthShare because the programme vision describes shared access to entitled health information, NHS interfaces, and an integrated healthcare information ecosystem, while InterSystems vendor evidence says HealthShare was selected for CORTISONE. This supports a programme-role reading, not a public CORTISONE-specific UCR configuration claim.

Follow-up Evidence

  • Public product documentation for record aggregation, identity matching, normalisation, consent, SSO, provisioning, monitoring, and access controls.
  • Customer-side shared-care-record governance and DPIA material.
  • Current live-status evidence for named UK deployments.
  • Outcome evidence for clinical workflow, analytics, or patient-record access.