Written by Technical Team | Last updated 23.01.2026 | 10 minute read
The NHS in England has been progressively enhancing interoperability across its healthcare systems to ensure seamless sharing of patient information. A pivotal component of this initiative is the GP Connect API, which facilitates authorised health and social care professionals in accessing and managing patient data held within General Practitioner (GP) systems. For developers and technical teams aiming to integrate with GP Connect, a comprehensive understanding of its architecture, capabilities, governance requirements, and implementation nuances is essential to delivering safe, scalable, and compliant solutions.
GP Connect is designed to bridge the information gap between disparate healthcare systems by providing standardised APIs that enable real-time access to GP-held patient records in EMIS and SystmOne. This standardisation ensures that clinicians, regardless of their organisational affiliation or care setting, can retrieve and, in certain scenarios, update patient information to support direct care delivery.
The GP Connect programme is fundamentally focused on improving patient outcomes by making relevant clinical information available at the point of care. This reduces reliance on manual processes such as phone calls, paper-based record transfers, or delayed document sharing, all of which can introduce inefficiencies and clinical risk.
The API suite encompasses various functionalities, including:
Access Record HTML: Offers a read-only HTML view of a patient’s GP record, allowing clinicians to quickly review comprehensive patient information in a familiar, human-readable format. This is particularly valuable in urgent and emergency care settings where speed and clarity are critical.
Access Record Structured: Provides structured, coded data retrieval from GP records using FHIR resources. This enables deeper integration into consuming clinical systems and supports advanced use cases such as decision support, population health analysis, and clinical auditing.
Access Document: Enables retrieval of documents attached to a patient’s GP record, such as referral letters, care plans, investigation results, or discharge summaries, ensuring continuity of information across care transitions.
Appointment Management: Allows for the booking, amendment, and cancellation of GP appointments across different systems, supporting cross-organisational workflows and improving patient access to primary care services.
Update Record: Permits authorised systems, particularly in community pharmacy and urgent care settings, to send structured updates to a patient’s GP record. This ensures that clinically relevant interactions are captured centrally and are visible to the patient’s registered GP.
Each of these capabilities is underpinned by specific API specifications, which are detailed in the GP Connect specifications for developers: https://digital.nhs.uk/services/gp-connect/develop-gp-connect-services/specifications-for-developers
The GP Connect APIs are built upon the Fast Healthcare Interoperability Resources (FHIR) standard, ensuring a consistent and modern approach to healthcare data exchange. The use of FHIR not only promotes interoperability but also aligns GP Connect with broader national and international healthcare IT strategies, making it easier for vendors to adopt and extend their solutions over time.
Key architectural components include:
RESTful API Design: Utilising standard HTTP methods (GET, POST, PUT, DELETE), the APIs provide predictable and uniform interfaces for interacting with GP systems. This simplifies development, testing, and maintenance for consuming applications.
FHIR Profiling: GP Connect defines constrained FHIR profiles tailored to NHS use cases. These profiles specify mandatory fields, value sets, and cardinalities to ensure consistent interpretation of data across systems.
Transport Layer Security (TLS): All data exchanges are secured using TLS/HTTPS, ensuring the confidentiality and integrity of patient information during transmission and meeting NHS cyber security requirements.
Spine Integration: GP Connect operates in conjunction with the NHS Spine, the central infrastructure that supports national NHS services. Spine routing ensures that API requests are directed to the correct GP system based on patient registration details, reducing complexity for consuming systems.
Authentication and Authorisation: Access to GP Connect APIs relies on robust identity and access management, including smartcards, role-based access control, and system-level authentication, ensuring that only authorised users and systems can access patient data.
For a deeper dive into the technical standards, message headers, error handling, and conformance expectations, developers should refer to the General API guidance: https://digital.nhs.uk/services/gp-connect/develop-gp-connect-services/development/general-api-guidance.
Key takeaway for GP Connect integration: Successfully integrating with the GP Connect API is not just a technical exercise in FHIR and RESTful APIs. It requires early alignment with NHS information governance, clinical safety standards (DCB0129/DCB0160), and Spine connectivity to ensure safe, compliant, and scalable access to GP patient records across England’s healthcare ecosystem.
A critical aspect of GP Connect integration is understanding the clinical data models and coding systems used within GP records. Structured data returned via GP Connect often uses standard terminologies such as SNOMED CT for clinical concepts, dm+d for medications, and HL7 value sets where appropriate.
Consuming systems must be capable of interpreting these codes accurately to avoid misrepresentation of clinical information. This is particularly important for systems that present data directly to clinicians or perform automated processing such as alerts, rules, or analytics. Developers should ensure that clinical terminology services or mappings are in place where local code systems differ.
In addition, attention must be paid to the contextual meaning of data elements, such as problem status, episode of care, or medication intent, as these can influence clinical decision-making.
Integrating with GP Connect requires careful planning and adherence to several prerequisites:
Network Access: Systems must have connectivity to the Health and Social Care Network (HSCN) to interact with GP Connect services in live environments. Development and test environments may have alternative access arrangements.
Personal Demographics Service (PDS) Compliance: To accurately identify and match patients, systems should be capable of performing PDS lookups, either directly or via third-party services. This ensures correct NHS number resolution and patient identity matching.
Information Governance: Organisations must comply with the GP Connect Direct Care API Information Governance Model. This includes ensuring that access is for direct care purposes, that users have legitimate relationships with patients, and that access is auditable.
Clinical Safety: A Clinical Safety Officer (CSO) should oversee the integration process. The system must comply with clinical risk management standards such as DCB0129 for manufacturers and, where applicable, DCB0160 for deploying organisations.
User Experience and Workflow Design: Beyond technical integration, it is essential to design workflows that present GP Connect data in a clear, clinically meaningful way. Poor UX can negate the benefits of interoperability and introduce safety risks.
Before embarking on development, it is advisable to engage with the GP Connect programme team to discuss specific use cases and confirm eligibility. Early engagement helps align expectations, identify potential constraints, and streamline onboarding and assurance activities.
Robust testing is a cornerstone of successful integration and is mandatory for assurance approval. The GP Connect programme provides several resources to facilitate this:
In addition to functional testing, organisations should conduct performance testing, resilience testing, and user acceptance testing to ensure that integrations behave reliably under real-world conditions.
To integrate with GP Connect, organisations must follow a structured onboarding and assurance process:
Throughout this process, the GP Connect team provides guidance, documentation, and support to help organisations navigate assurance efficiently.
Integrating with GP Connect offers a wide range of strategic, clinical, and operational benefits:
Enhanced Clinical Decision-Making: Timely access to comprehensive GP records supports safer, more informed clinical decisions, particularly in urgent, out-of-hours, and cross-organisational care settings.
Improved Care Coordination: Seamless information sharing reduces fragmentation, supports integrated care pathways, and improves communication between primary, secondary, and community care providers.
Operational Efficiency: Automated access to records and appointments reduces administrative workload, duplication of data entry, and reliance on manual processes.
Data Quality and Continuity: Structured updates ensure that key clinical interactions are recorded centrally, improving longitudinal patient records.
Patient Empowerment: Upcoming and evolving patient-facing capabilities aim to give individuals greater visibility of their health information, supporting transparency, trust, and self-management.
GP Connect is a foundational component of the NHS’s wider interoperability strategy. As Integrated Care Systems (ICSs) mature and digital transformation accelerates, GP Connect is expected to play an increasingly important role in enabling joined-up care, population health management, and innovation across the health and care ecosystem.
Ongoing enhancements may include expanded write capabilities, broader system coverage, and alignment with emerging national platforms and standards. For developers and digital leaders, investing in GP Connect integration is not only a technical decision but a strategic one that positions organisations to meet future interoperability and care delivery demands.
GP Connect is transforming healthcare interoperability in the NHS by providing secure, standardised access to patient records held in EMIS and SystmOne. By adopting these APIs, healthcare providers and system suppliers can improve care coordination, reduce administrative overhead, enhance clinical safety, and ultimately deliver better outcomes for patients. A thorough understanding of the technical, clinical, and governance aspects of GP Connect is essential for any organisation seeking to successfully integrate and maximise its value.
What support tools and testing environments are available to developers integrating with GP Connect?
GP Connect provides a suite of developer tools such as the API demonstrator and provider test suites, which let developers simulate interactions, inspect FHIR request/response payloads, and validate conformance before moving into live assurance stages. These tools help accelerate development and reduce implementation risks.
Can GP Connect be used to create patient-facing digital services?
Yes — GP Connect includes Patient Facing APIs that enable patients to view parts of their GP record and manage permissions via apps (e.g., NHS App). These patient-centric APIs are designed for secure, consumer-oriented views while still conforming to clinical safety and governance requirements.
What is the role of the Personal Demographics Service (PDS) in GP Connect integrations?
The PDS is used to accurately identify and match patients across systems by retrieving NHS numbers and demographic details, ensuring that API calls route to the correct GP record. Integrating with PDS is essential before performing GP Connect queries.
Does GP Connect allow retrieval of historical documents like discharge summaries?
Yes — the Access Document capability lets consuming systems retrieve unstructured clinical documents (such as referral or discharge summaries) stored in the patient’s GP record, improving continuity of care across settings.
Are there limitations on the kinds of clinical data GP Connect Structured APIs return?
Structured APIs support key clinical data like medications, allergies, immunisations, consultations, problems, and investigations. They do not currently include extended demographics, templates, or flags/alerts — and are continually evolving as suppliers mature their implementations.
Is your team looking for help with GP Connect integration? Click the button below.
Get in touch