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 serves approved direct care and the bounded medical-examiner use case through approved systems; see GP Connect Service Context for purpose and onboarding restrictions. 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 supplier-progress page edited 3 September 2026 retains the HealthShare structured-consumer cells but omits the IRIS middleware Send Document row recorded in June. The supplier-progress precision page preserves both dated observations and the unchanged blank-cell boundaries.

The service page edited 1 September 2026 closes new-developer GP Connect onboarding for Send Document, Update Record and Appointment Management, while allowing existing consumer suppliers to onboard end users. Apply that operational boundary alongside effective DSIC standards and API specifications.

Current service status continues to list Medicus Patient Facing APIs as live and Access Document as FoT ready, although the supplier table labels Medicus Access Document development. This national status evidence and the DPIA's new-market-entrant reference do not establish a 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

The service-facing source below, captured in June, returned 404 on the 8 September 2026 recheck. Its named supplier/service scope is historical. The current API catalogue still describes community-pharmacy production use, subject to the newer service onboarding boundary.

Update Record should still be treated as controlled structured write-back, not generic write-back. The historical NHS GP Connect: Update Record page says the capability has been technically and clinically assured between community pharmacy and general practice, and limits the named assured 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 effective DSIC S102 v1.0.3 standard is now listed across GP IT Futures, Tech Innovation, Community Pharmacy Clinical Services, and Digital Primary Care, with mandatory sender and receiver requirements and ITK3/MESH/PDS or Spine Mini Services dependencies. Treat that as a broader catalogue-standard surface, not evidence that non-pharmacy workflows, DMICP/CORTISONE, or an InterSystems implementation are approved.

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 NCRS roadmap, reviewed in July and edited 23 July 2026, now reports GP Connect Access Document pilots with two ambulance services and GP practices across selected ICBs during April–June 2026. This advances the earlier planned-pilot evidence; it does not establish universal availability, named InterSystems implementation, or evaluated outcomes. July–September priorities include performance/security/scalability improvements, role-based views and usability.

The NCRS service page, edited 24 August 2026, still limits GP Connect information to pilot users. Pair this availability boundary with the reported pilots before claiming a capability is available in a deployment.

Patient-Facing Direction

The NHS App roadmap, edited 22 July 2026, retains GP Connect patient-facing API work for linked profiles. Record-access priorities include finding appointment-note information, improving the documents screen and exploring combined test results. Downloading or sharing GP record content remains work planned next, not a delivered feature established by the roadmap.

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 Transparency defines data items; the service-facing June snapshot is historical and its URL returned 404 on 8 September 2026.
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