Skip to content

GP Connect Deep Dive

GP Connect is an NHS service and API/messaging integration context. It is not an InterSystems product. The InterSystems relevance is that Health Connect and HealthShare are positioned as integration/shared-record platforms that may need to consume, expose, or route GP Connect capabilities in NHS settings.

This page is now the overview for the GP Connect evidence set. Use the subpages for detailed capability, architecture, due-diligence, and InterSystems-specific evidence boundaries.

For the wider NHS England digital primary-care procurement, capability, standards, assurance, and migration context, use NHS England Digital Primary Care. GP Connect is one standards/service family within that DSIC/NHS England environment, not a synonym for DSIC.

What GP Connect Is

See GP Connect Service Context for the NHS service definition, direct-care scope, and onboarding constraints.

Capability Map

See GP Connect Capability Map for the summary taxonomy, then use the dedicated capability pages for Access Record: HTML, Access Record: Structured, Access Document, Send Document, Update Record, and Patient Facing APIs.

Due Diligence

See GP Connect Due Diligence for implementation and assurance checks that mirror the capability-map order: Access Record: HTML, Access Record: Structured, Access Document, Send Document, Update Record, and Patient Facing APIs.

Architecture

See GP Connect Architecture Patterns for SSP, MESH, and NHS API Platform patterns.

Roadmap and Future Updates

See GP Connect Roadmap and Future Updates for contemporary NHS evidence on GP Connect supplier progress, Update Record releases and pharmacy-service constraints, NCRS Access Document pilots, NHS App patient-facing API direction, and the wider Single Patient Record / Connecting Care Records context.

InterSystems Relevance

See InterSystems GP Connect Evidence Boundary for the difference between NHS GP Connect evidence, InterSystems vendor claims, PRSB conformance evidence, current NHS supplier-progress evidence, current Health Connect Cloud standards evidence, and live implementation proof. Use GP Connect InterSystems Supplier Progress for the current NHS rows naming IRIS for Health (Middleware) and HealthShare, including the parsed Send Document (Send) v2.0.1 and Access Record: Structured HealthShare cell mapping.

UK Nations Context

See NHS Connectivity and GP Connect for the cross-UK boundary. The current evidence supports GP Connect as an NHS England service context. Scotland, Wales, and Northern Ireland are interpreted through their own digital-health, record-sharing, FHIR, portal, LIMS, procurement, and integration programmes in the current evidence set.

Use GP Connect and Spine Equivalents by Nation for the devolved-nation comparison. It compares GP Connect and Spine by function rather than treating Scotland, Wales, or Northern Ireland as if they used the NHS England service stack.

GP Connect Pages

Evidence Still Needed

  • Current InterSystems technical documentation for Health Connect GP Connect components; current Health Connect Cloud documentation supports general standards/integration capability but not a current GP Connect conformance claim.
  • Current HealthShare documentation showing how GP Connect support is configured and assured.
  • Current NHS roadmap updates for Update Record, Access Document, and Patient Facing APIs, separated from InterSystems implementation claims.
  • Customer-side deployment evidence showing which GP Connect products are live in a specific InterSystems-backed programme.
  • Local clinical-safety, data-sharing, and onboarding artefacts for any named implementation.
  • Product documentation and assurance evidence that connects the parsed NHS InterSystems supplier-progress rows to a supported implementation pattern.