GP Connect and Spine Equivalents by Nation
This page compares GP Connect-like and Spine-like national services across England, Scotland, Wales, and Northern Ireland.
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, GP Connect, 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 sources, Wales WGPR/WCP/WCCG/NDR/WDS/NHS Wales App sources, and Northern Ireland NIECR/encompass/EpicCare Link/HCN/DIS/ePharmacy sources.
Before promoting this comparison into a dedicated devolved-nations evidence-domain page, recheck the Source and Evidence Domain Map promotion trigger. Keep this page as the parent service-equivalence route unless future work repeatedly needs the parent comparison, all three country connectivity pages, all three InterSystems-by-nation pages, and the canonical evidence registers for the same cross-nation question.
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. That shared structure does not make Scotland, Wales, or Northern Ireland DSIC- or DUAA-compliant. It means each nation needs its own evidence pack for the local legal, professional, service, and operational route.
| 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? | DSIC, GP Connect, Spine-connected services, DUAA section 121 / Schedule 15, NHS Standards Directory, DCB0129/DCB0160, NHS England records-management code, CQC candour, and local DSA/DPIA apply only where the England route is in scope. |
| 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 import DSIC or DUAA labels. |
| 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 import DSIC or DUAA labels. |
| 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 import DSIC or DUAA labels. |
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 is the only row where DSIC and DUAA section 121 / Schedule 15 terminology belongs in the current evidence set. 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. | DSIC and DUAA are England-only in this wiki. They still require named-standard, supplier-role, safety, IG, and deployment evidence. |
| 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. | Do not describe Scottish routes as DSIC-compliant or DUAA section 121 / Schedule 15-compliant without direct nation-specific evidence. |
| 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. | Do not import NHS England DSIC/GP Connect/DUAA labels into Wales unless a Welsh source explicitly adopts them. |
| Northern Ireland | Mediate Health and Care Number, Digital Identity Service, 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; GP Connect, Spine, DSIC, and DUAA section 121 / Schedule 15 are not current NI labels in this evidence set. |
Comparison Map
| Function | England | Scotland | Wales | Northern Ireland |
|---|---|---|---|---|
| GP record / GP summary access for care | GP Connect Access Record, Access Document, and Summary Care Record. | 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-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 digital identity-service work; NHAIS / Caché licensing remains a separate GP-registration application fact. |
| Prescribing / medicines | Electronic Prescription Service. | Acute Medication Service and wider ePharmacy routes. | Primary Care Electronic Prescription Service and Shared Medicines Record are listed in DHCW digital clinical tools. | 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 digital front-door direction plus local portal work; not a GP Connect route in current evidence. | 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, 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, National Data Resource / Care Data Repository, Welsh Clinical Portal, WDS/PDS relationship, WCCG, and NHS Wales App. | 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. |
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. |
| Electronic prescription exchange | Scotland ePharmacy/pharmacy-services context; Wales PC EPS and Shared Medicines Record; Northern Ireland ePharmacy programme. | Equivalent high-level function, not identical supplier, message model, or legal framework. |
| National platform / integration layer | Scotland NDP; Wales NDR/CDR and DHCW national services; Northern Ireland encompass / Epic plus Rhapsody context. | These are not NHS England Spine services in the current evidence set. |
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 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.