Skip to content

HealthShare Provider Directory

This page tracks HealthShare Provider Directory within the HealthShare family.

Supported Positioning

InterSystems positions Provider Directory as a master data management solution for provider data. The product page says it collects, consolidates, deduplicates, validates, searches, and publishes provider information, using a linkage engine and business rules to create master records for providers and provider organisations.

Role in the HealthShare Suite

Provider Directory is part of the HealthShare product taxonomy in current InterSystems documentation and product navigation. It should be analysed as provider-data management, not as patient identity, clinical viewing, or a shared-care-record datastore.

Evidence Status

Confidence is high for vendor positioning and listed features. Deployment evidence is still needed for data sources, authoritative-provider-data policy, governance, update/push patterns, hosting model, ODS/SDS mapping, local synchronisation, audit, and UK-specific provider identifiers.

NHS England Directory Boundary

For a DSIC-aligned England deployment, Provider Directory should be tested against national organisation and directory services rather than treated as a generic local directory:

  • ODS manages organisation identifiers and reference data for health and social care; NHS developer guidance says ODS codes support organisation lookup, GP-practice lookup, validation of codes in messages/reports, and GP Connect data-sharing boundaries.
  • ODS API guidance supports searching organisations, retrieving details for an ODS code, relationships, succession, and modified-organisation lists for local synchronisation. Current ODS news also highlights 2026 migration/data-quality changes around dynamic geography and the FHIR R4 API.
  • SDS remains relevant for Spine-connected message addressing and endpoint lookup, while ODS is the safer source family for provider/organisation codes and reference data in this identity-directory pass.

The resulting position is bounded: Provider Directory is a plausible HealthShare provider master-data component, but an England assurance claim still needs product/version evidence, ODS/SDS mapping, data-source authority, synchronisation design, directory stewardship, audit, local role model, safety ownership where workflow is affected, and customer deployment artefacts.

Follow-up Evidence

  • Current Provider Directory technical and data-governance documentation, including synchronisation and audit behaviour.
  • Evidence for ODS/SDS mapping, local authoritative-source choices, provider-data stewardship, and role-model ownership.
  • Customer or procurement evidence where Provider Directory is explicitly named.