Skip to content

GP Connect Access Record HTML Due Diligence

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

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

Why It Matters

Access Record: HTML is a read-only clinical record view. It can be embedded into a consuming electronic patient record, but it is not structured data extraction and it is not write-back.

NHS Implementation Controls

NHS evidence points to these checks:

  • Confirm the use case is approved direct care and the consuming system is allowed to access GP Connect in that care setting.
  • Confirm the Access Record: HTML flow through Spine Secure Proxy, including patient identification through NHS number, registered GP lookup, endpoint discovery, and provider response through SSP.
  • Confirm whether the required provider GP systems are enabled for Access Record: HTML in current supplier-progress material.
  • Confirm how the consuming system displays HTML sections or headings, including date filtering where relevant, without treating the returned content as coded structured data.
  • Confirm local audit, RBAC, clinical-safety, and information-governance arrangements for users viewing GP record information.

Evidence Status

Confidence is high for NHS capability definition and architecture. This page does not prove InterSystems support or live deployment in any named programme.

Follow-up Evidence

  • Current supplier-progress status for required provider and consumer systems.
  • Current InterSystems documentation showing any Access Record: HTML consumption, display, or routing support.
  • Customer-side evidence for local Access Record: HTML deployment.