Skip to content

GP Connect Access Record Structured Due Diligence

This page tracks due-diligence requirements for GP Connect Access Record Structured.

Use GP Connect Access Record: Structured Capability for the capability definition. This page is the implementation and assurance checklist.

Why It Matters

Access Record Structured is the most relevant GP Connect area for structured interoperability analysis because it exposes coded, machine-readable sections of the GP record through a FHIR API pattern.

NHS Implementation Controls

NHS England Digital records several implementation controls and dependencies:

  • Network access is through HSCN, with internet access not currently available on the API page at time of access.
  • API access is controlled through Spine Secure Proxy, including authentication, authorisation, audit, data-sharing checks, and transaction logging.
  • Consuming systems need local RBAC and must send a JWT containing user, role, system, and organisation details; SSP also checks whether the consumer is authorised to communicate with the provider.
  • Communications use TLS MA across both consumer-to-proxy and proxy-to-provider legs.
  • Assurance includes clinical testing and technical testing, with onboarding started by submitting a use case where prerequisites and product fit exist.

Evidence Status

Confidence is high for NHS API requirements. This page describes NHS requirements, not whether a specific InterSystems deployment is assured or live.

Interpretation

Any InterSystems-specific Access Record Structured claim should be separated into:

  1. NHS service/API requirements, supported by NHS England Digital pages.
  2. Vendor product capability claims, currently supported only by InterSystems Health Connect and HealthShare statements.
  3. Live implementation or conformance evidence, which still requires current product documentation, supplier assurance evidence, or customer deployment proof.

Follow-up Evidence

  • Current InterSystems technical documentation for Access Record Structured support.
  • NHS GP Connect supplier assurance or progress records naming InterSystems products, if public.
  • Local clinical-safety, data-sharing, and onboarding artefacts for any named deployment.