Skip to content

HealthShare Clinical Viewer

This page tracks HealthShare Clinical Viewer from official InterSystems HealthShare material.

Classification

Clinical Viewer is a HealthShare clinical presentation component, not another name for Health Connect or the whole Unified Care Record. InterSystems documentation lists Clinical Viewer and Unified Care Record as separate included HealthShare products/components. Unified Care Record product material then positions Clinical Viewer as the user-facing route for viewing the longitudinal patient/member record.

Official InterSystems Positioning

InterSystems says HealthShare Clinical Viewer delivers a longitudinal representation of the patient/member record on desktop and mobile, giving clinicians, care managers, care coordinators, case managers, and other team members access to information beyond what may be available in the EMR.

The HealthShare Unified Care Record resource page adds more detail: Clinical Viewer makes HealthShare data available through a browser or embedded workflow tools, presents information in a summary format with click-through detail, supports specialty configuration, and includes vital-signs graphing for configurable views.

The same resource material also makes Clinical Viewer a useful boundary page for access and presentation questions: browser access, embedded workflow access, summary-to-detail navigation, specialty configuration, dynamic vital-sign views, and patient-report style output belong here unless a source specifically places them in another HealthShare component.

Relationship to Unified Care Record

Unified Care Record is the longitudinal-record and data-unification proposition. Clinical Viewer is the presentation layer/application that exposes HealthShare/UCR information to users. It is therefore part of the HealthShare/UCR proposition, but it should have its own space when discussing user experience, embedding, SSO, configuration, specialty views, or clinical application behaviour.

Clinical Viewer and Navigation Application

InterSystems' November 2025 HealthShare AI Assistant launch release adds a newer workflow boundary: the AI Assistant is described as operating within HealthShare Clinical Viewer and the Navigation Application, with conversational questions, patient summaries, pre-built and custom prompts, source traceability, configurable data profiles, role-based access controls, and audit tracking.

This supports a dedicated Clinical Viewer / Navigation Application subsection, but it should be read carefully. The release is vendor-published and does not yet provide independent deployment, clinical-safety, model, prompt, or UK availability evidence. It also does not redefine Clinical Viewer as the AI Assistant; rather, it places a newer assistant capability into the Clinical Viewer / Navigation Application workflow surface.

UK Deployment Clue

The Herefordshire and Worcestershire Integrated Care and Wellbeing Record DPIA gives a historical UK data-flow example: it describes InterSystems HealthShare use in a shared regional record instance and says aggregated, matched data would be displayed in Clinical Viewer. This is useful deployment-context evidence, but it is a 2021 DPIA rather than proof of current Clinical Viewer live status or configuration.

Evidence Separation

Use the high-risk row audit on InterSystems Standards Product Map when Clinical Viewer is being used as assurance or implementation proof. Keep these layers separate:

Evidence layer What current evidence supports What still needs separate proof
Presentation route Clinical Viewer is the HealthShare / Unified Care Record presentation and access surface for browser, mobile, or embedded workflows. Current product build, licensed modules, specialty templates, local workflow configuration, and customer rollout.
Access controls Product material and AI Assistant launch evidence make access, configurable data profiles, RBAC, and audit relevant to the Clinical Viewer / Navigation Application surface. Identity provider, SSO pattern, user provisioning, role/view model, break-glass or emergency-access policy if applicable, audit retention, and access-review process.
AI Assistant adjacency AI Assistant operates within Clinical Viewer and Navigation Application workflows according to vendor launch material, with public sample and product-term boundary evidence. UK availability, customer enablement, model/runtime provider, prompt governance, clinical-safety controls, data-flow terms, and deployment approval.
Deployment context H&W ICWR DPIA gives historical deployment-context evidence that aggregated, matched data would be displayed in Clinical Viewer. Current go-live status, current DSA/DPIA, final contract or service schedule, supplier RACI, DCB0129/DCB0160, operational support, and incident model.

Evidence Status

Confidence is high for vendor taxonomy and Clinical Viewer positioning, moderate-high for vendor AI Assistant launch positioning, and moderate-high for historical DPIA evidence that Clinical Viewer appears in at least one UK shared-care-record data-flow design. Current HealthShare 2026.1 documentation exists but is account-gated; public evidence still does not fully resolve licensing boundary, deployment topology, SSO/RBAC/audit configuration, specialty templates, Navigation Application behaviour, AI Assistant runtime governance, clinical-safety artefacts, current live status, or customer-specific usage.

Remaining Follow-up Evidence

  • Public Clinical Viewer product documentation and configuration guides beyond the account-gated HealthShare documentation index.
  • SSO, RBAC, audit, role/view, and embedded-workflow documentation for HealthShare clinical applications.
  • Navigation Application and AI Assistant documentation, including RBAC, audit, prompt, and clinical-safety controls.
  • Evidence distinguishing Clinical Viewer v1/v2 or version-specific features where relevant.
  • Customer-side examples showing how Clinical Viewer is deployed within shared-care-record programmes, including DSA/DPIA, DCB0129/DCB0160, supplier RACI, and current live-status evidence.