Skip to content

GP Connect Access Document Due Diligence

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

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

Why It Matters

Access Document retrieves unstructured documents held in a patient's GP practice record. It is separate from Access Record: HTML and Access Record: Structured because it handles document search and retrieval rather than record-view rendering or coded record sections.

NHS Implementation Controls

NHS evidence points to these checks:

  • Confirm the approved direct-care use case and the care setting requiring document retrieval.
  • Confirm the RESTful API route through Spine Secure Proxy, including registered GP lookup and provider endpoint discovery.
  • Confirm whether document references are expected to come from Access Record returns and how the consuming system retrieves the actual document separately.
  • Confirm provider and consumer supplier status, including any pilot or rollout limits, before treating Access Document as available in a deployment.
  • Confirm how documents will be displayed, stored, audited, and governed locally, especially when retrieved from the GP-held record into another care setting.

Evidence Status

Confidence is high for NHS capability purpose and architecture. Current availability and implementation status need supplier-progress and deployment-specific evidence.

Follow-up Evidence

  • Current supplier-progress status for Access Document.
  • Pilot outcome evidence from NCRS, ambulance, ICB, or GP practice deployments.
  • Current InterSystems documentation or customer evidence naming Access Document support.