Skip to content

HealthShare

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

For source routing across HealthShare components, standards relevance, deployment evidence, AI Assistant boundaries, and DSIC adjacency, use the HealthShare Components Evidence Domain. It is a navigation layer over Sources and Evidence Matrix, not a substitute for source IDs.

Official InterSystems Positioning

InterSystems positions HealthShare as an advanced interoperability platform and connected-care suite for capturing information, sharing it meaningfully, supporting understanding, and driving action across organisations and communities.

Role in the Portfolio

HealthShare is the connected-care and interoperability family. Current InterSystems documentation and product navigation identify HealthShare 2026.1 products including Care Community, Clinical Viewer, Health Insight, InterSystems EMPI, Personal Community, Provider Directory, and Unified Care Record; separate product pages also position Health Connect as a HealthShare-related integration engine. The detailed HealthShare 2026.1 documentation index is public, but much of the underlying documentation requires WRC login.

Component Split

Component Role in this wiki
HealthShare Unified Care Record Longitudinal shared-record and data-unification proposition.
HealthShare Clinical Viewer Clinical presentation layer for browser, mobile, and embedded access to HealthShare/UCR information, with historical H&W ICWR DPIA deployment-context evidence.
HealthShare EMPI Enterprise master person index / identity-resolution component.
HealthShare Provider Directory Provider master-data management component.
HealthShare Health Insight Analytics companion to UCR for population, clinical, business, and workflow insight.
HealthShare Personal Community EHR-neutral patient digital-front-door product connected to HealthShare and EHR product navigation.
HealthShare Care Community FHIR-enabled care-management and care-plan workflow component that complements UCR, with accessible Personal Community integration evidence for patient-contribution care plans and a vendor-published Lincolnshire NHS care-plan signal.
HealthShare AI Assistant Generative-AI assistant capability operating within Clinical Viewer and the Navigation Application, with public sample deployment files but account-gated detailed documentation.
Health Connect Integration engine / managed service related to the HealthShare product family.

Evidence Status

Confidence is high for vendor positioning and component taxonomy. HealthShare has additional UK evidence in this wiki through Birmingham / West Midlands validation, PRSB Core Information Standard conformance, NHS supplier-progress evidence, Programme CORTISONE evidence, published DPIAs, FOI records, and customer-side EPR/shared-care-record sources, but configured capabilities, local data flows, and operational outcomes still vary by deployment.

Anchor Audit Notes

The current HealthShare anchor model remains component-based. HealthShare should be read as a product family and connected-care architecture, not as a single deployable feature or a full GP foundation clinical system. Component, customer, and assurance claims need separate evidence:

  • Unified Care Record and Clinical Viewer support shared-record and direct-care viewing patterns; Clinical Viewer access, SSO/RBAC/audit, AI Assistant adjacency, and deployment assurance need the separate high-risk audit on the standards product map.
  • EMPI and Provider Directory support identity and provider-data functions. The 2026-06-21 PDS/ODS pass strengthens the NHS England dependency boundary: PDS FHIR creates concrete NHS-number, synchronisation, invalid/superseded-record, local back-office, and safety requirements; ODS creates organisation-code, relationship, succession, validation, and local-synchronisation requirements. It found official PDS integrated-products evidence for Intersystems HealthConnect 2020.1, not direct EMPI or Provider Directory implementation proof.
  • Health Insight supports analytics use cases.
  • Personal Community and Care Community support patient-facing and care-management patterns where licensed and configured; Care Community now has accessible Personal Community integration-mechanics evidence, but not independent deployment assurance.
  • Health Connect supports integration, routing, transformation, and operations patterns adjacent to HealthShare.
  • HealthShare AI Assistant is a current product capability with public launch/sample evidence, but UK clinical-safety and governance proof remains open.
  • DUAA adds a statutory standards/data-governance layer for England health/adult social care IT and IT-service providers, but does not change the HealthShare product taxonomy or prove any HealthShare deployment compliant.

This anchor check leaves the main unresolved model gap in the Evidence Validation Queue: which HealthShare components are licensed, configured, safety-assessed, integrated, and live in a named customer or DSIC-relevant deployment.

Remaining Follow-up Evidence

  • Public HealthShare technical architecture and component product documentation beyond the account-gated HealthShare 2026.1 index.
  • Public module-level implementation documentation for Health Insight, EMPI, Personal Community, Provider Directory, and AI Assistant. For EMPI / Provider Directory, prioritise PDS FHIR onboarding, ODS/SDS mapping, local synchronisation, stewardship, audit, and safety-ownership evidence. Direct Care Community configuration remains useful only if Lincolnshire or another customer-confirmation requirement is opened.
  • Implementation-specific evidence showing configured components, data flows, and governance.
  • Independent outcome evidence for connected-care deployments.
  • Supplier, customer, or catalogue evidence proving the exact role split when HealthShare is part of a DSIC-relevant architecture.