GP Connect and Spine Equivalents by Nation
The expanded UK Core Services Matrix distinguishes actual cross-nation reuse from analogous functions. New evidence confirms Welsh NHS login and PCRM reuse, NI BSO supplying Welsh FPPS, and Scottish NHSCR demographic/movement exchanges. These do not prove shared full-GP-record APIs or wholesale DSIC adoption.
This page compares GP Connect-like and Spine-like national services across England, Scotland, Wales, and Northern Ireland. Start with the UK Healthcare Connectivity Landscape for the broader map of networks, identity, records, referrals and diagnostics; this page retains the functional comparison and adapter model.
For service names at a glance, use the UK Core Services Matrix. It compares national services and identifies provider or health-board delivery where appropriate; this page retains the broader integration, legal and adapter analysis.
Main Reading
There is no clean one-to-one GP Connect equivalent outside England in the current evidence set. The safer comparison is functional:
- GP-record or GP-summary access for direct care.
- Messaging, referral, and document exchange between care settings.
- National patient identity and demographic lookup.
- Electronic prescribing and medicines exchange.
- Patient-facing record access.
- National platform or backbone services.
England packages many of these routes through Spine, Spine-connected services, SCR, GP Connect, the National Document Repository, and related NHS England Digital services. Scotland, Wales, and Northern Ireland use different national platforms, portals, identifiers, and programme boundaries, so the current evidence supports functional comparison rather than labelling those devolved routes as GP Connect.
The devolved comparison uses Scotland ECS/KIS/CHI/NDP/SCI/ePharmacy/MyCare.scot and GP record-transfer sources, Wales WGPR/WCP/WCCG/GP2GP/NDR/WDS/NHS Wales App sources, and Northern Ireland NIECR/encompass/EpicCare Link/HCN/DIS/ePharmacy plus GP IT Modernisation / GP2GP sources.
The national-service boundary is not a blanket exclusion of shared infrastructure. NHS England's Spine page, updated 24 August 2026, explicitly covers England, Wales and the Isle of Man; DHCW documents Welsh EPS prescription exchange through Spine and pharmacy nominations in PDS. This does not establish Welsh GP Connect use or extend England DSIC procurement requirements.
Use NHS National Record and Data Platforms for the SCR / NDR / SPR / FDP distinction. In this wiki, NDR must be source-qualified because NHS England National Document Repository, NHS England national data repository wording, and Wales National Data Resource are different evidence routes.
The 15 September 2026 whole-UK review met the traversal threshold for a master overview, an England service drill-down and a diagnostics drill-down. Existing country pages and this comparison remain canonical for their detailed functions. The recorded structure decision adds no duplicate evidence-domain register.
Legal Record Alignment Across Nations
Use the UK healthcare-recording legal alignment model as the common record-handling structure across all four administrations: creation, maintenance, amendment, confidentiality, data protection, electronic communications, provider governance, candour, records management, provenance, audit, clinical safety, and standards. Each nation needs its own evidence pack for the local legal, professional, service, and operational route. DUAA section 121 / Schedule 15 concerns England health and adult-social-care information standards; the Act also changes UK-wide data-protection law. Neither layer supplies a product-compliance badge.
| Administration | Common legal-record alignment question | Nation-specific proof boundary |
|---|---|---|
| England | Does the route satisfy UK GDPR/DPA, PECR where relevant, confidentiality/Caldicott, section 251 if needed, professional record duties, provider governance, records management, clinical safety, provenance, and named information standards? | Assess DSIC, GP Connect, named Spine services, the DUAA section 121 / Schedule 15 health and adult-social-care information-standard regime, NHS Standards Directory, DCB0129/DCB0160, NHS England records-management code, CQC candour, and local DSA/DPIA against the route in scope. Spine also serves Wales; check service-specific boundaries. |
| Scotland | Does the route satisfy the same record-creation and maintenance disciplines for Scottish services, identifiers, boards, portals, and national platforms? | Use Scottish records-management code, Scottish candour law/guidance, CHI/ECS/KIS/NDP/SCI/ePharmacy/MyCare.scot evidence, NHS board approvals, local IG, clinical-safety, and deployment artefacts; do not extend England DSIC or the section 121 / Schedule 15 health-standard regime to this route. Assess UK-wide data-protection changes separately. |
| Wales | Does the route satisfy the same record-creation and maintenance disciplines for Welsh services, identifiers, portals, and national digital platforms? | Use Welsh records-management code, Welsh duty-of-candour framework, WDS/WGPR/WCP/WCCG/NDR/NHS Wales App evidence, DHCW or health-board approvals, Welsh IG, safety, and deployment artefacts; do not extend England DSIC or the section 121 / Schedule 15 health-standard regime to this route. Assess UK-wide data-protection changes separately. |
| Northern Ireland | Does the route satisfy the same record-creation and maintenance disciplines for HSC services, identifiers, portals, encompass, and regional record access? | Use Northern Ireland records-management code, HSC governance, Health and Care Number/DIS/encompass/EpicCare Link/My Care/ePharmacy evidence, local safety and IG artefacts, and deployment proof; do not extend England DSIC or the section 121 / Schedule 15 health-standard regime to this route. Assess UK-wide data-protection changes separately. |
Health Connect / HealthShare Adapter Logic
For the Executive Summary architecture, the reusable pattern is common but the compliance language is not. Health Connect is the proposed mediation and adapter layer; HealthShare is the proposed shared-care, viewer, EMPI, provider-directory, or analytics layer where commissioned. England DSIC and the DUAA section 121 / Schedule 15 health and adult-social-care information-standard regime are specific to the England route in this comparison. UK-wide data-protection changes remain relevant across all four administrations. Scotland, Wales, and Northern Ireland require their own national-service, information-governance, clinical-safety, and customer deployment proof.
| Administration | Health Connect adapter logic | HealthShare target logic | Label boundary |
|---|---|---|---|
| England | Mediate GP Connect, MESH, ITK3, PDS, ODS/SDS, FHIR/UK Core, local trust, regional, or hospital routes where the workflow requires them. | Support shared-care record, clinical viewer, EMPI, provider directory, analytics, or patient-facing functions where the deployment scope proves them. | England DSIC and the section 121 / Schedule 15 health-standard regime require named-standard, supplier-role, safety, IG, and deployment evidence; UK-wide data-protection duties are a separate layer. |
| Scotland | Mediate CHI, ECS/KIS, National Digital Platform, SCI Gateway, ePharmacy, MyCare.scot, board, or local routes only where a Scottish source or contract supports the route. | Support shared-record/viewer or identity/directory functions only where NHS Scotland or board deployment evidence names the HealthShare role. | England DSIC and the section 121 / Schedule 15 health-standard regime do not establish Scottish route compliance. Apply Scottish service requirements and UK-wide data-protection duties. |
| Wales | Mediate Welsh Demographic Service, Welsh GP Record, Welsh Clinical Portal, Welsh Clinical Communications Gateway, National Data Resource / Care Data Repository, NHS Wales App, or local routes where specified. | Support shared-care/viewer functions only where Welsh deployment evidence names the HealthShare component and role. | Welsh Spine reuse does not establish GP Connect use or England DSIC/section 121 / Schedule 15 applicability. Apply Welsh service requirements and UK-wide data-protection duties. |
| Northern Ireland | Mediate Health and Care Number, NIDIS, encompass/EpicCare Link, My Care, ePharmacy, local HSC, or legacy GP-registration routes only where contracted and evidenced. | Do not infer HealthShare from Caché / NHAIS licensing, encompass, EpicCare Link, My Care, or Rhapsody boundary evidence. | Treat Northern Ireland as a separate HSC architecture. This evidence set does not establish NI GP Connect/Spine use or England DSIC/section 121 / Schedule 15 applicability; UK-wide data-protection duties still apply. |
Comparison Map
| Function | England | Scotland | Wales | Northern Ireland |
|---|---|---|---|---|
| Network connectivity | HSCN and service-specific internet access. | SWAN and its national/external network gateways. | PSBA public-sector network. | HSC Wide Area Network. Network access is separate from clinical-service permission in all four routes; see the landscape. |
| Diagnostic results and images | Legacy EDIFACT/MESH, pathology FHIR pilot and NIR beta. | PACS, SCI Store and pathway-specific NDP/SCI Gateway routes. | LIMS/WCP/WRRS and separately phased RISP. | CoreLIMS and NIPACS+, linked to wider clinical access. See diagnostic exchange for status and suppliers. |
| GP record / GP summary access for care | GP Connect Access Record and Access Document; the Summary Care Record viewed through NCRS or another approved system. | Emergency Care Summary and Key Information Summary, both derived from GP-practice data for defined care contexts. | Welsh GP Record through Welsh Clinical Portal / national clinical tools. | Northern Ireland Electronic Care Record and, now, encompass / EpicCare Link for professional access to regional record data; GP practice remains outside current encompass scope. |
| GP practice record transfer when a patient moves practice | GP2GP; see GP2GP Record Transfer. | Electronic transfer of GP health records to the new GP practice where records are electronic and the move is within Scotland; cross-UK moves currently use printed-record handling in public patient guidance. | DHCW primary-care services list GP2GP for electronic transfer between Welsh practices. | GP IT Modernisation material identifies GP2GP as an electronic transfer route for patient notes / records between practices or clinical systems. |
| GP-to-other-care messaging and referrals | GP Connect Send Document / Update Record, MESH, and NHS e-Referral Service. | SCI Gateway for electronic clinical communications and referrals between primary and secondary care. | Welsh Clinical Communications Gateway and Welsh Clinical Portal routes; GP2GP is listed in DHCW primary-care services. | encompass / EpicCare Link for professional access; ePharmacy and local HSC routes rather than GP Connect. |
| National patient identity / demographics | NHS Number and Personal Demographics Service on Spine. | Community Health Index (CHI), modernised as national NHS Scotland infrastructure. | Welsh Demographic Service connected to PDS; NHS Wales also uses national demographic and clinical data infrastructure. | Health and Care Number plus live NIDIS Phase 1 demographics; NHAIS registration replacement is a separate Phase 2, with screening continuity separately evidenced. |
| Prescribing / medicines | Electronic Prescription Service. | Acute Medication Service and wider ePharmacy routes. | Welsh EPS uses NHS Spine and PDS; Shared Medicines Record is a separate programme. | BSO / Department of Health ePharmacy programme for electronic prescribing and medicines services. |
| Patient-facing access | NHS App and NHS login ecosystem, with GP Connect patient-facing APIs in the wider NHS England direction. | MyCare.scot national web rollout from April 2026 and mobile app from June, with staged features; not GP Connect. | NHS Wales App. | My Care portal for information in encompass; GP records and GP-arranged tests are explicitly excluded. |
| National platform / backbone | Spine plus PDS, SCR, National Document Repository, EPS, e-RS, SDS, GP Connect, MESH, and API-platform routes. | National Digital Platform plus CHI, ECS/KIS, SCI Gateway, and ePharmacy; not a single Spine clone. | DHCW national services, NDR/CDR, WCP, WCCG, NHS Wales App, WDS/PDS, and NHS Spine for EPS. | encompass / Epic platform, EpicCare Link, My Care, Health and Care Number / digital identity-service work, NHAIS for GP registrations, and ePharmacy programme. |
Four-Nation Adapter Proof Table
Use this table for the Executive Summary question when Health Connect / HealthShare is proposed as a common mediation and shared-care architecture across the four UK health administrations. The table is a proof checklist, not evidence that the adapters already exist in a named deployment.
| Administration | Adapter target | InterSystems architecture role | Proof needed before using the claim |
|---|---|---|---|
| England | DSIC, GP Connect, Spine services, PDS, ODS/SDS, MESH, ITK3, EPS, e-RS, NHS App / NHS login, NCRS, and NRL context. | Health Connect mediates national-service and local-system interfaces; HealthShare may act as shared-care record, clinical viewer, EMPI, provider directory, analytics, or patient-facing layer where commissioned. | DSIC catalogue/capability scope, GP Connect supplier/onboarding evidence, SSP/HSCN/RBAC/JWT/TLS MA, MESH mailbox, ITK3 payload validation, PDS/ODS/SDS onboarding, NDSA/DSA, DPIA, DCB0129/DCB0160, and customer deployment artefacts. |
| Scotland | CHI, ECS/KIS, National Digital Platform, SCI Gateway, ePharmacy, MyCare.scot, and board or local integration routes. | Health Connect could mediate Scottish national or local interfaces if contracted; HealthShare could support shared-record/viewer functions only where commissioned. | NHS Scotland or board interface specifications, CHI and relevant service onboarding, board approvals, data-sharing and controller model, safety case, operational runbook, and customer deployment proof. |
| Wales | Welsh Demographic Service / PDS relationship, Welsh GP Record, Welsh Clinical Portal, Welsh Clinical Communications Gateway, National Data Resource / Care Data Repository, NHS Wales App, and local NHS Wales routes. | Health Connect could mediate Welsh national or local interfaces; HealthShare could support shared-care or viewer functions only where a Welsh deployment exists. | DHCW or health-board interface specifications, onboarding approvals, identifier and demographics model, WCP/WGPR/WCCG/NDR route evidence, Welsh information-governance pack, clinical-safety case, and deployment proof. |
| Northern Ireland | Health and Care Number, Digital Identity Service, encompass, EpicCare Link, My Care, ePharmacy, local HSC routes, and legacy NHAIS / GP-registration context. | Health Connect could mediate HSC interfaces only if contracted; HealthShare should not be inferred from current Caché / NHAIS licensing or encompass evidence. | HSC or BSO interface contracts, HCN/DIS onboarding, encompass/EpicCare Link integration approval where relevant, My Care boundary confirmation, data-sharing and safety artefacts, operations evidence, and explicit InterSystems product/customer proof. |
Urgent-Care Adapter Boundary
The urgent-care matrix adds five functions to the national comparison. Model assessment, service discovery, referral delivery, receiving-service acceptance, appointment ownership and GP notification separately; not every pathway books a slot. A transport acknowledgement must not be presented as clinical acceptance or a confirmed appointment. This is an implementation synthesis, not evidence that an InterSystems adapter already exists.
England uses role-specific NHS 111 reporting, UEC DoS, BaRS and GP Connect routes. Scotland requires NHS 24/board/FNC contracts; Wales requires its 111/health-board handoff and booking arrangements; NI requires the relevant Phone First/OOH/Trust route. Check the patient identifier, referral purpose, information model, endpoint authority, supported operation, acknowledgement/failure handling, local service availability and accountable receiving team for the selected route. Do not infer these from a public directory, a FHIR label or a shared supplier.
The PRSB 111 model offers content reuse, and England/Wales border routing establishes a care pathway. Neither supplies a common UK-wide operational contract. Detailed evidence belongs in the linked country pages; unresolved interface and rollout questions remain in the validation queue.
Spine-Like Interpretation
"Spine equivalent" is used here as a functional comparison, not as a product or service name. The clearest crosswalk is:
| Spine function | Closest devolved equivalents | Boundary |
|---|---|---|
| National patient identifier and demographic service | Scotland CHI; Wales WDS / PDS relationship; Northern Ireland Health and Care Number / digital identity-service work. | Identifier equivalence does not imply the same API, governance, or access model. |
| Summary record for urgent/direct care | Scotland ECS/KIS; Wales Welsh GP Record / WCP; Northern Ireland NIECR and encompass / EpicCare Link context. | These are not GP Connect Access Record unless official evidence says so. |
| Referral and document exchange | Scotland SCI Gateway; Wales WCCG / WCP; Northern Ireland encompass workflows and local HSC services. | GP Connect Send Document and Update Record are England-specific in this evidence set. |
| GP-practice record transfer | Scotland GP2GP / NSS patient-record transfer; Wales GP2GP in DHCW primary-care services; Northern Ireland GP2GP in GP IT Modernisation. | GP2GP should be treated as record transfer when a patient changes practice, not as GP Connect, shared-care-record access, or InterSystems implementation proof. |
| Electronic prescription exchange | Scotland ePharmacy/pharmacy-services context; Wales PC EPS and Shared Medicines Record; Northern Ireland ePharmacy programme. | Check each route: Wales EPS reuses NHS Spine; Scotland and Northern Ireland retain their own evidenced programmes. |
| National platform / integration layer | Scotland NDP; Wales NDR/CDR and DHCW national services; Northern Ireland encompass / Epic plus Rhapsody context. | These platforms are not substitutes for every Spine service; Wales separately uses Spine for EPS and the WDS/PDS relationship. |
Do not read "NDR" as a cross-UK platform name. In England, current public sources support National Document Repository and separate national data-repository language for commissioning flows; in Wales, NDR means National Data Resource / Care Data Repository context.
Product Boundary
This comparison is about national NHS/HSC digital services, not InterSystems product capability. InterSystems evidence for Scotland, Wales, and Northern Ireland remains on the country pages. In particular, Northern Ireland Caché / NHAIS licensing is not evidence of InterSystems powering encompass, GP2GP, or a GP Connect-equivalent service.
For Scotland, TrakCare Patient Management System (PMS) and TrakCare ED are source or local system labels for TrakCare in specific settings. Public Health Scotland uses the PMS label in a secondary-care data-quality context; NHS Shetland names TrakCare ED as its Intersystems-supplied Accident & Emergency patient-management system. Those labels support a Scotland TrakCare reading, not a separate national connectivity service or standalone product taxonomy.