GP Connect Capability Map
This page tracks the NHS GP Connect capability taxonomy.
Summary Map
| Capability | Purpose | Primary pattern |
|---|---|---|
| Access Record: HTML | View a patient's GP care record as an unstructured document. | RESTful API via Spine Secure Proxy. |
| Access Record: Structured | View coded, machine-readable sections of the GP record. | RESTful API via Spine Secure Proxy. |
| Access Document | Retrieve documents attached to the GP record. | RESTful API via Spine Secure Proxy. |
| Send Document | Send a document to a GP practice system. | Messaging via MESH. |
| Update Record | Update a GP record with structured data from a permitted workflow. | Messaging via MESH. |
| Patient Facing APIs | Enable approved consumer applications to support patient-facing record and prescription access. | RESTful API via NHS API platform. |
Evidence Status
Confidence is high for the capability taxonomy because it is supported by NHS England Digital GP Connect service, developer specification, product/API pages, and architecture pages. Capability availability and live use still vary by supplier, care setting, onboarding state, and approved use case.
Interpretation
GP Connect evidence is capability-specific. Access Record, Access Document, Send Document, Update Record, and Patient Facing APIs use different patterns, assurance routes, rollout states, and use-case constraints.
Update Record is especially easy to over-generalise. In the current NHS API catalogue evidence it is a community-pharmacy structured update integration over MESH/ITK3, not a generic open-ended write-back mechanism for all GP Connect consumers.
Related Pages
- GP Connect Deep Dive
- GP Connect Due Diligence
- GP Connect Roadmap and Future Updates
- GP Connect Architecture Patterns
- GP Connect InterSystems Supplier Progress
- NHS Connectivity and GP Connect
Capability Pages
- Access Record: HTML
- Access Record: Structured
- Access Document
- Send Document
- Update Record
- Patient Facing APIs
Remaining Follow-up Evidence
- Current product-specific support claims by capability.
- Supplier assurance records by capability where publicly available.
- Customer-side deployment examples that identify which GP Connect capability is live.
- Current GP Connect-specific InterSystems documentation mapping Health Connect or HealthShare to each GP Connect capability, especially Update Record and Send Document messaging routes.