Skip to content

GP Connect Roadmap and Future Updates

This page tracks contemporary official NHS signals about GP Connect roadmap, rollout, and future-facing capability changes. It is intentionally separate from the capability pages because roadmap evidence cuts across GP Connect, NCRS, NHS App, Shared Care Records, and the emerging Single Patient Record context.

Current Position

GP Connect remains a direct-care service used through approved clinical or care systems, not a standalone user login or general record-sharing platform. NHS England Digital's live GP Connect pages continue to separate the service into capability families such as Access Record, Access Document, Send Document, Update Record, and Patient Facing APIs.

The strongest current supplier evidence is the NHS England Digital GP Connect supplier progress page. It says GP Connect capabilities must be built into both GP patient record systems and consumer systems, and that GP system supplier capabilities become commissionable subject to development, assurance, testing, and First of Type deployment. As of the page edited on 5 June 2026, TPP SystmOne and Optum EMIS Web are listed as full-rollout approved across Access Record: HTML, Appointment Management, Send Document receive, and Update Record on the GP patient record system side; the same page also tracks consumer-side capability by supplier and clinical system. The 2026-06-19 structural parse maps InterSystems IRIS for Health (Middleware) to Send Document (Send) v2.0.1, and maps the source-spelled InterSytems Healthshare row to Access Record: Structured Medications v1.2.6, Allergies v1.2.6, Immunisations v1.5.0, and Uncategorised v1.5.0, with other HealthShare structured cells blank.

The current GP Connect service page, last edited 15 June 2026, adds service-status context that matters for Medicus: Patient Facing APIs are live with Medicus, Access Document is FoT ready for Medicus, several Access Record: Structured sections are FoT ready for Medicus, and GP Connect use remains through approved systems with onboarding and assurance. The GP Connect DPIA also names Medicus as a new NHS market entrant for GPs. This is national GP Connect context, not proof of any named local HealthShare integration.

The GP Connect deployment and utilisation page is useful as a baseline rather than a future roadmap. Its April 2025 snapshot shows broad Access Record: HTML practice enablement, lower but substantial Access Record: Structured enablement, and a combined Update Record / Send Document message count. Use it to understand maturity and scale, while using the supplier-progress and specification pages for current capability status.

Update Record Direction

Update Record should still be treated as controlled pharmacy-to-GP structured write-back, not generic write-back. The service-facing NHS GP Connect: Update Record page says the capability has been technically and clinically assured between community pharmacy and general practice, and limits its use to Pharmacy First, Blood Pressure Check, and Pharmacy Contraception services. It also identifies EMIS and TPP as the general practice clinical system suppliers and Cegedim Healthcare Solutions, EMIS Pinnacle, Positive Solutions, and Sonar Informatics as the community pharmacy suppliers assured for this use at the time of the page.

The current GP Connect specifications for developers directory lists a GP Connect Update Record release dated 8 May 2026 with release notes for 1.2.1-public-beta and artefacts including an API test suite and implementation guide. The GP Connect transparency appendix, also edited in May 2026, maps Update Record data items to pharmacy consultation information, patient information, medicines, presenting complaint, observations, service information, and consent/visibility constraints. Together, these sources make Update Record a live roadmap item for pharmacy-service workflow breadth, supplier assurance, and GP workflow filing rather than an open general-purpose record mutation API.

Access Document and NCRS

The clearest near-term GP Connect roadmap signal outside the core GP Connect pages is the National Care Records Service roadmap. NHS England Digital says NCRS completed technical delivery of GP Connect integration in late 2025 to support a planned 2026 pilot, then identifies January to March 2026 work including GP Connect Access Document pilots with two ambulance services and GP practices in selected ICBs, expansion of GP clinical information through additional GP Connect integrations, and increased interoperability with local Shared Care Records.

The NCRS service page aligns with that roadmap. It lists GP Connect data among NCRS information sources, says GP Connect information is available to pilot users only, and lists upcoming pilots for access to clinical documents from care settings where those documents are held by a patient's registered GP practice.

Patient-Facing Direction

Patient Facing APIs are linked to the NHS App roadmap. The NHS App roadmap says the team is supporting GP systems and GP surgeries to adopt GP Connect patient-facing APIs, is working on better discovery and interpretation of GP health-record information, and is working next on making it easier for users to find specific information and download or share GP record content. It also mentions linked profiles for users whose GP systems use GP Connect patient-facing APIs.

For the wiki, this means patient-facing GP Connect evidence should stay separate from clinician-facing Access Record evidence. The future-facing signal is NHS App adoption and user experience around GP record access, not InterSystems product support by itself.

Wider Strategic Direction

The wider NHS direction is toward connected records, shared care records, and the Single Patient Record, but these are not the same thing as GP Connect. NHS England's Single Patient Record page says the programme expects people to start viewing SPR data through the NHS App from 2028, with 2026 to 2028 work involving legislation, supplier/public/professional engagement, and prototypes for priority scenarios. NHS England's Digitising the Frontline page separately says Connecting Care Records work during 2025 and 2026 is using interoperability tools such as the National Record Locator to improve access to shared care records across England.

These are strategic context sources. They increase the importance of GP Connect, patient-facing APIs, NRL, and Shared Care Record interoperability evidence, but they do not prove that any GP Connect capability is available in a named InterSystems deployment.

Evidence Watchlist

Watch item Why it matters
GP Connect supplier progress Tracks provider and consumer capability by supplier, status, and specification version.
GP Connect service and GP Connect DPIA Tracks current service status, onboarding/NDSA context, and national Medicus DPIA context.
GP Connect deployment and utilisation Provides a point-in-time usage and practice-enablement baseline.
GP Connect specifications for developers Tracks current release versions, artefacts, and archived releases.
Update Record service page and transparency appendix Defines the pharmacy services, assured suppliers, data items, and constraints.
NCRS roadmap and service page Shows GP Connect Access Document pilot direction and Shared Care Record interoperability signals.
NHS App roadmap Shows patient-facing GP Connect API adoption and future GP health-record user journeys.
Single Patient Record and Connecting Care Records Provides wider national strategic context, not GP Connect implementation proof.

Interpretation

The current roadmap picture is not a single GP Connect roadmap page. It is a set of official NHS signals:

  1. supplier assurance and specification releases for GP Connect itself;
  2. controlled Update Record expansion through pharmacy service workflows;
  3. Access Document pilots and GP clinical-information expansion through NCRS;
  4. patient-facing API adoption through NHS App health-record and linked-profile work;
  5. broader strategic pressure from Shared Care Record, NRL, and Single Patient Record programmes.

These NHS roadmap sources define NHS-side capability direction, but they do not prove InterSystems implementation. Product or deployment claims require InterSystems documentation, NHS supplier-progress rows, local implementation records, or customer evidence. For current InterSystems row precision, use GP Connect InterSystems Supplier Progress.

Follow-up Evidence