Skip to content

HealthShare EMPI

This page tracks InterSystems EMPI within the HealthShare family.

Supported Positioning

InterSystems positions EMPI as an enterprise master person index for identity resolution. The product page says it can pair with Unified Care Record to merge multi-source data into a longitudinal record or operate as a standalone enterprise or agency-wide solution.

User Interface

EMPI Patient Search displaying demographic filters and four matching example records with MPI identifiers and ranks.

Identity search. Demographic filters return matching example records, MPI identifiers and ranks. This screen comes from an InterSystems employee tutorial dated 17 April 2023, which explicitly uses randomly generated HL7 messages. The exact release is not stated; this is a historical tutorial, not NHS PDS implementation evidence. Select the image to open it at full size.

Role in the HealthShare Suite

EMPI is part of the HealthShare product taxonomy in current InterSystems documentation and product navigation. In wiki analysis, it is the identity-resolution / person-index component, not the whole Unified Care Record or Clinical Viewer.

Evidence Status

Confidence is high for vendor positioning and taxonomy. Deployment-specific matching rules, stewardship workflow, demographic data sources, PDS coupling/synchronisation, merge/unmerge controls, audit behaviour, clinical-safety ownership, and local governance need product documentation or implementation evidence.

The public July 2026 support notices introduce a version-specific SSO check relevant to EMPI. Use the HealthShare support-alert boundary with the deployed build and correction evidence; this adds no PDS implementation proof (SRC-295, checked 2026-09-08).

NHS England Identity Boundary

For a DSIC-aligned England deployment, EMPI relevance is not enough by itself. NHS England PDS evidence makes the national identity dependency more concrete:

  • PDS is the national master patient-demographics database and includes the NHS number, registered GP, nominated pharmacy, and core demographics.
  • PDS FHIR technical conformance creates safety and stewardship requirements around local-copy synchronisation, sensitive patient records, superseded NHS numbers, invalidated patient records, warning users, referring cases to the local back office, and de-coupling invalid local records from PDS until corrected.
  • NHS PDS integrated-products evidence currently found in this pass names Intersystems HealthConnect 2020.1 for North West Anglia NHS Foundation Trust, application-restricted, approved 2021-08-25. It does not name HealthShare EMPI or prove EMPI PDS integration.

The resulting position is stronger but narrower: EMPI is the plausible HealthShare identity-resolution component, while PDS/NHS-number use remains a national-service implementation claim requiring product/version, onboarding, local matching/stewardship, synchronisation, back-office, audit, clinical-safety, and customer deployment evidence.

Programme CORTISONE is the strongest UK Defence healthcare context for EMPI relevance. The CORTISONE vision describes an Enterprise Master Patient Index as the master demographic source for Defence Medical Services, and MOD performance files name InterSystems Corporation against Programme CORTISONE IP and EMPI measures. Public sources still do not expose the detailed matching configuration or stewardship workflow.

Follow-up Evidence

  • Current EMPI technical documentation for matching, stewardship, merge/unmerge, audit, and PDS/NHS-number handling.
  • Product/version and national-service onboarding evidence if EMPI is claimed to use PDS or PDS FHIR.
  • Customer deployment evidence showing configured identity-resolution scope, local back-office workflow, DCB0129/DCB0160 ownership, and data-sharing/DPIA treatment.