Skip to content

NHS Connectivity and GP Connect

This page describes how NHS connectivity and GP Connect evidence relates to InterSystems products and the four UK health systems.

The current evidence set supports GP Connect as an NHS England service context. Scotland, Wales, and Northern Ireland have their own digital-health, record-sharing, FHIR, portal, and integration evidence, so the comparison outside England is functional rather than a GP Connect label match.

Use GP Connect and Spine Equivalents by Nation for the service-by-service comparison of GP Connect-like and Spine-like functions outside England.

Use NHS England Digital Primary Care for the wider NHS England digital primary-care procurement, capability, standards, assurance, migration, and HealthShare compliance context. GP Connect is one service/API family within that wider England-specific environment.

Evidence Boundary

Question Current answer
Is GP Connect a UK-wide NHS standard? No public evidence in this pass supports treating GP Connect as UK-wide. The current evidence set supports it as an NHS England service/API and messaging context.
Can InterSystems product standards positioning be treated as GP Connect assurance? No. Health Connect, HealthShare, IRIS for Health, and FHIR Services are relevant integration products, but standards positioning is not the same as NHS GP Connect supplier assurance or a live local deployment.
What is the strongest current InterSystems GP Connect evidence? NHS supplier-progress material names and maps InterSystems rows: IRIS for Health (Middleware) maps to Send Document (Send) v2.0.1, and source-spelled InterSytems Healthshare maps to Access Record: Structured Medications, Allergies, Immunisations, and Uncategorised cells. Official NHS service/DPIA evidence separately strengthens national Medicus context but is not InterSystems implementation proof.
What should be compared outside England? Compare by function: GP-record summary access, clinical messaging/referrals, demographics/identity, prescribing, patient portals, and national platform services.
Is DSIC a UK-wide NHS standard? No current evidence supports that. DSIC is tracked as an NHS England digital primary-care operating/procurement/capability/standards environment.

NHS England

NHS England is the only part of the UK evidence set where the wiki currently has direct GP Connect evidence.

Capability route Direction InterSystems relevance Boundary
Access Record: HTML, Access Record: Structured, and Access Document From GP patient-record provider systems to approved consumer systems through the Spine Secure Proxy / Spine pattern. A shared-care record, hospital EPR, social-care system, NHS 111 system, or other point-of-care product can be a GP Connect consumer if it is approved and onboarded. The parsed HealthShare row supports specific Access Record: Structured sections: Medications, Allergies, Immunisations, and Uncategorised. Access Record Structured supports coded read access and document discovery/retrieval, not patient-facing views, secondary-use reporting, or write-back. The parsed HealthShare row does not prove local onboarding, Access document support, or a customer deployment.
Send Document From another care setting into the registered GP practice, using MESH. The NHS supplier-progress page maps InterSystems IRIS For Health (Middleware) to Send Document (Send) v2.0.1. The IRIS row is not evidence of Access Record, Appointment Management, or Update Record support. Send Document currently sends encounter documents such as consultation summaries; it is not a general GP record write-back channel.
Update Record From community pharmacy into GP practice workflow, using MESH / ITK3 / FHIR STU3 for approved services. No current InterSystems-specific Update Record support is proven in this wiki. NHS England frames current Update Record use around Pharmacy First, Blood Pressure Check, and Pharmacy Contraception services, with named GP and community-pharmacy suppliers. The current evidence supports a defined pharmacy-to-GP workflow, not a generic write API.
Patient Facing APIs Patient-facing access through approved consumer and provider routes, currently tied to NHS App direction in this evidence set. NHS service/DPIA evidence says Patient Facing APIs are live with Medicus and names Medicus in the new-market-entrant context. No current InterSystems-specific Patient Facing API support is proven in this wiki. Patient-facing access is separate from clinical consumer access, with a different route, onboarding model, and roadmap context. Medicus national status does not prove a West Midlands HealthShare route.

For England, the practical InterSystems interpretation is:

Scotland

Scotland should be analysed as its own NHS Scotland digital-health and interoperability context, not as an extension of NHS England GP Connect.

The functional Scotland comparison is tracked on Scotland Connectivity Equivalents. The closest GP Connect-like routes are Emergency Care Summary, Key Information Summary, and SCI Gateway; the closest Spine-like functions are CHI, the National Digital Platform, ePharmacy / AMS, and related national services.

The current Scottish Government evidence focuses on citizen access/control of health and care data, safe digital foundations for staff to record, access, and share information, and a multi-year move toward common standards and interoperability across a fragmented health and social care data landscape.

InterSystems-specific Scotland evidence is mostly TrakCare-centred and is now tracked on InterSystems in Scotland:

  • Public Health Scotland says all NHS Boards except Dumfries & Galloway and Western Isles had implemented a version of TrakCare Patient Management System (PMS), and NHS Shetland names Intersystems-supplied TrakCare ED, an Accident & Emergency patient-management system, and Ensemble with live contract dates and integrations.
  • InterSystems' historical NHS Scotland case study says TrakCare was implemented across Scottish health boards and that NHS National Services Scotland chose InterSystems Ensemble as a national integration platform.
  • Current or more recent vendor sources cover NHS Ayrshire & Arran hosted TrakCare as a Service and NHS Forth Valley TrakCare deployment context.

The PMS and ED labels are source or local system naming for TrakCare in specific settings, not separate products or evidence of a GP Connect route.

This supports a Scotland reading of InterSystems as an EHR/PAS and integration-platform supplier in public NHS contexts. It does not prove a GP Connect capability, an NHS England GP Connect route, or current board-by-board connectivity status.

Wales

Wales should be analysed through Digital Health and Care Wales and NHS Wales services, not through GP Connect unless Welsh evidence is later found.

The functional Wales comparison is tracked on Wales Connectivity Equivalents. The closest GP Connect-like routes are Welsh GP Record, Welsh Clinical Portal, Welsh Clinical Communications Gateway, GP2GP, and the NHS Wales App; the closest Spine-like functions include the Welsh Demographic Service / PDS relationship, National Data Resource / Care Data Repository, WCP, WCCG, and Welsh prescribing / medicines routes.

The current Wales evidence supports four distinct themes, with InterSystems-specific evidence now tracked on InterSystems in Wales:

  • DHCW has a National Data Resource / FHIR standards context.
  • DHCW primary-care services include GP2GP and Welsh Clinical Communications Gateway connections between GPs and hospitals.
  • NHS Wales board material says the all-Wales LIMS 2.0 path involved a new contract with InterSystems to upgrade WLIMS1 / TrakCare Lab 2016 to TrakCare Lab Enterprise and migrate Wales LIMS infrastructure to an InterSystems-hosted private cloud.
  • Sell2Wales formally records the DHCW LIMS services award to InterSystems Corporation, while DHCW and InterSystems material establish chronology and vendor-stated all-Wales TrakCare Lab Enterprise scope.

This supports a Wales reading of InterSystems as a national pathology/LIMS supplier and of Wales as having its own FHIR and GP/hospital connectivity routes. It does not support describing NHS Wales connectivity as GP Connect, and it does not prove that TrakCare Lab Enterprise provides GP Connect capabilities.

Northern Ireland

Northern Ireland should be analysed through Health and Social Care Northern Ireland and the encompass programme, not through GP Connect unless Northern Ireland evidence is later found.

The functional Northern Ireland comparison is tracked on Northern Ireland Connectivity Equivalents. The closest GP Connect-like routes are NIECR, encompass, EpicCare Link, My Care, and ePharmacy; the closest Spine-like functions are Health and Care Number, Digital Identity Service, NHAIS, encompass / EpicCare Link, and ePharmacy.

The current official evidence says encompass has created a single digital care record for citizens receiving health and social care across Northern Ireland's five HSC Trusts. Department of Health Northern Ireland confirms encompass is now live across all Trust areas and says HSCNI partnered with Epic to build it. Professional access for GPs and other health professionals is through EpicCare Link, which provides read-only access to encompass and some limited functionality such as requesting imaging tests.

The primary-care boundary is explicit: general practice and Primary Care are currently not within the scope of encompass, although GP-led teams can access encompass through EpicCare Link. The public My Care portal also excludes primary-care records, GP records, and GP-arranged test results.

The one direct InterSystems Northern Ireland source found in this pass is a Find a Tender notice for InterSystems Caché licences used by NHAIS applications for GP registrations, tracked on InterSystems in Northern Ireland. Rhapsody vendor material is useful boundary context for the integration layer around encompass, but it is not official HSCNI evidence unless separately confirmed.

This supports a Northern Ireland reading of secondary-care and HSC record access through encompass / EpicCare Link, plus a separate InterSystems Caché / NHAIS licensing fact. It does not support a Northern Ireland TrakCare, HealthShare, Health Connect, or GP Connect claim.

Cross-UK Interpretation

Product family What it can support in analysis What not to infer
Health Connect / IRIS for Health Integration-engine, middleware, standards, MESH, API, FHIR, and healthcare-message routing analysis where product documentation and local deployment evidence align. Current GP Connect assurance, a specific NHS route, or live use without supplier-progress or customer evidence.
HealthShare / Unified Care Record / Clinical Viewer Shared-care-record, longitudinal-record, and clinical-viewer analysis, including possible GP Connect consumer patterns in England where proven. Capability-by-capability GP Connect support or local configured data flows without table, product, or deployment evidence.
TrakCare / TrakCare Lab EHR/PAS/LIMS use in named NHS settings, especially Scotland and Wales where the current evidence is TrakCare-centred. GP Connect support or UK-wide primary-care connectivity by default.
FHIR Services / FHIR Server Generic FHIR repository, managed FHIR infrastructure, OAuth/security, profile/package, and API infrastructure analysis. NHS GP Connect profile conformance, onboarding, or live national-service integration unless separately evidenced.

Follow-up Evidence

  • Recheck the NHS GP Connect supplier-progress and service-status pages after future edits for InterSystems, HealthShare, IRIS for Health, Medicus, and patient-facing API changes.
  • Find current public InterSystems documentation that maps Health Connect, IRIS for Health, or HealthShare directly to current GP Connect implementation guides.
  • Add NHS Scotland / NSS / board-side current evidence for TrakCare and Ensemble connectivity status, especially any board-level Integrated Care Record or national integration-platform evidence beyond the NHS Shetland FOI response.
  • Add DHCW source material for Wales FHIR implementation, GP2GP, Welsh Clinical Communications Gateway, Welsh Clinical Portal, Care Data Repository, and how LIMS 2.0 feeds clinical records after deployment.
  • Recheck Northern Ireland for any future GP-primary-care inclusion in encompass and for any InterSystems evidence beyond NHAIS Caché licensing.