HealthShare Components Evidence Domain
This domain page groups HealthShare component, connected-care architecture, standards, deployment-boundary, and DSIC-adjacent evidence. It is a working slice of Sources and Evidence Matrix, not a replacement for either canonical register.
Domain Boundary
HealthShare Components includes InterSystems HealthShare, HealthShare Unified Care Record, Clinical Viewer, EMPI, Provider Directory, Health Insight, Personal Community, Care Community, HealthShare AI Assistant, and Health Connect where it is used as a HealthShare-adjacent integration engine.
It excludes:
- Generic InterSystems product portfolio claims unless they clarify the HealthShare family boundary.
- DSIC or GP Connect compliance unless the evidence names a HealthShare, Health Connect, IRIS for Health, or partner role.
- Customer deployment outcomes unless the source is customer-side, procurement-side, DPIA, FOI, or other implementation evidence.
- Scotland, Wales, Northern Ireland, UK Defence, or international examples unless the source names HealthShare or a relevant component in that setting.
Source Clusters
| Cluster | What they support |
|---|---|
| HealthShare product and component taxonomy | HealthShare connected-care positioning, Unified Care Record, Clinical Viewer, EMPI, Provider Directory, Health Insight, Personal Community, Care Community, AI Assistant, Care Community patient-contribution integration mechanics, Lincolnshire Care Community vendor signal, and the account-gated 2026.1 documentation boundary. |
| Health Connect and interoperability mechanics | Health Connect as a HealthShare-related integration engine, standards support, transformations, Health Connect Cloud, Network Connect, cloud deployment, and monitoring/operations positioning. |
| Standards and conformance evidence | PRSB Core Information Standard conformance for HealthShare, standards governance, OIDs, NHS Standards Directory relevance, GP Connect and ITK context, and the distinction between standards presence and named implementation proof. |
| UK deployment and programme context | Birmingham / West Midlands shared-care-record evidence, Clinical Viewer DPIA context, National Record Locator references, current Medicus integration signal, official national Medicus GP Connect context, Programme CORTISONE HealthShare / IRIS evidence, and procurement/customer-side boundaries. |
| AI Assistant and runtime-service boundary | HealthShare AI Assistant launch positioning, sample deployment artefacts, AI Model Services product-term boundary, and the remaining UK governance/safety evidence gap. |
| DSIC, GP Connect, and national identity/directory adjacency | HealthShare or adjacent InterSystems component relevance to DSIC shared-care, viewer, identity, provider directory, integration, FHIR, GP Connect consumer/middleware patterns, PDS, ODS/SDS, DSCR/GP Connect support context, and national Medicus GP Connect context without proving full GP foundation compliance or a local West Midlands route. |
Evidence Claims
| Claim | Evidence status | Canonical detail |
|---|---|---|
| HealthShare is the connected-care and interoperability family in the current InterSystems portfolio. | High for vendor positioning. | HealthShare |
| The HealthShare family splits into multiple components with different implementation roles. | High for taxonomy; deployment-specific licensing and configuration remain open. | HealthShare, Evidence Matrix |
| HealthShare Unified Care Record and Clinical Viewer support shared longitudinal-record and direct-care viewing patterns. | High for product positioning; customer configuration, SSO/RBAC/audit, AI-adjacent governance, and deployment status vary. | HealthShare Unified Care Record, HealthShare Clinical Viewer, InterSystems Standards Product Map |
| EMPI, Provider Directory, Health Insight, Personal Community, Care Community, AI Assistant, and Health Connect are adjacent components, not interchangeable labels. Care Community now has accessible integration-mechanics evidence through Personal Community patient-contribution documentation. EMPI / Provider Directory now have stronger NHS national-service dependency evidence through PDS/ODS, but implementation proof remains component-specific. | High for component boundary; high for Care Community / Personal Community integration mechanics; high for PDS/ODS dependency boundary; implementation proof remains component-specific. | HealthShare, HealthShare Care Community, DSIC HealthShare Compliance Map |
| HealthShare has evidence relevant to DSIC-aligned integrated-care architecture. | High for component relevance; boundary for full DSIC GP foundation compliance. | DSIC HealthShare Compliance Map |
| HealthShare alone is a complete DSIC GP foundation clinical system. | Not proven. | Evidence Validation Queue |
| HealthShare AI Assistant has public launch, sample, and product-term evidence, but not enough public UK clinical-safety and governance evidence. | Moderate-high for vendor positioning; vendor/boundary for deployment governance. | HealthShare AI Assistant |
Component Assurance Snapshot
| Component area | Current support | Assurance boundary |
|---|---|---|
| Shared longitudinal record and viewing | UCR and Clinical Viewer have product positioning, PRSB relevance, and high-risk audits separating content/viewing from deployment proof. | Need customer architecture, SSO/RBAC/audit, clinical safety, data-sharing, live status, and role/view configuration. |
| Identity and directory | EMPI and Provider Directory have product positioning for patient/person identity and provider master data. PDS/ODS evidence now defines national identity/directory dependencies, and PDS integrated-products evidence names Intersystems HealthConnect 2020.1 but not EMPI or Provider Directory. |
Need product/version evidence, PDS FHIR onboarding, ODS/SDS mapping, matching/stewardship, directory governance, synchronisation, audit, clinical-safety ownership, and customer deployment evidence. |
| Analytics and secondary use | Health Insight and IRIS/FHIR/OMOP-related evidence support analytics relevance. | Need measure definitions, refresh patterns, data-quality controls, lawful basis, approvals, pseudonymisation, and customer deployment evidence. |
| Patient-facing and care-management | Personal Community and Care Community have product positioning; Care Community now has Personal Community integration evidence and a vendor-published Lincolnshire signal. | Leave Care Community complete for now; do not continue unless Lincolnshire/customer confirmation becomes a specific requirement. |
| Integration and standards plumbing | Health Connect, IRIS for Health, FHIR Services, and HealthShare standards evidence support plausible integration roles. | Need named standard, profile, onboarding, conformance, customer architecture, and service-management evidence before implementation assurance. |
| AI-adjacent presentation | AI Assistant has launch/sample/product-term evidence and Clinical Viewer adjacency. | Need UK availability, model/prompt governance, clinical safety, RBAC/audit, runtime terms, and deployment artefacts. |
Open Evidence Work
- Accessible HealthShare 2026.1 component documentation beyond the public account-gated documentation index. Direct Care Community technical documentation should not be the default next target unless Lincolnshire/customer confirmation becomes a specific requirement.
- Customer-specific component licensing, configuration, data-flow, role-based access control, single sign-on, audit, Clinical Viewer / Navigation Application governance, and clinical-safety evidence.
- EMPI / Provider Directory implementation evidence for PDS FHIR onboarding, NHS-number handling, ODS/SDS mapping, synchronisation, local back-office workflow, stewardship, audit, and safety ownership.
- UK deployment evidence for HealthShare AI Assistant, including model, prompt, runtime-service, audit, RBAC, and clinical-safety controls.
- Direct mapping of HealthShare / Health Connect / IRIS roles to GP Connect, PDS, MESH, ITK3, NHS login, EPS, e-RS, GP2GP, and other DSIC national services where claimed.
- Customer-side evidence for the West Midlands Medicus / HealthShare route, because official NHS national Medicus status does not prove local HealthShare onboarding or assurance.
- Deployment artefacts for any HealthShare-backed DSIC solution: supplier/capability listing, architecture, DPIA, data-sharing agreement, clinical-safety case, onboarding, certificates, migration, training, and go-live evidence.