Skip to content

InterSystems GP Connect Evidence Boundary

This page tracks what the wiki can and cannot currently say about InterSystems and GP Connect.

Supported InterSystems Touchpoints

InterSystems has two recorded GP Connect touchpoints in this wiki:

  • Health Connect: a 2019 InterSystems UK news item said NHS FHIR-profile components made available to NHS customers included GP Connect and Transfer of Care support, and that Health Connect supported the FHIR version used by those initiatives at that time.
  • HealthShare: a 2025 InterSystems UK news item said PRSB validation of HealthShare 2024.1 included support for GP Connect, FHIR, HL7 v2, DICOM, and IHE profiles.

PRSB separately confirms InterSystems Healthshare as conformant to Core Information Standard Version 2 at Level 2 until 17.06.2028, which strengthens the PRSB conformance part of the HealthShare claim. It does not, by itself, prove every GP Connect implementation detail for a particular deployment.

NHS Supplier-Progress Evidence

The page edited 3 September 2026 was checked structurally on 8 September. It retains the source-spelled InterSytems Healthshare structured-consumer row with Medications v1.2.6, Allergies v1.2.6, Immunisations v1.5.0, and Uncategorised v1.5.0; its other structured cells, including Access document, are blank.

The June snapshot recorded InterSystems IRIS For Health (Middleware) with Send Document (Send) v2.0.1, but that row is absent in September. Preserve the historical evidence and treat current IRIS status as unconfirmed; a missing row does not prove withdrawal or discontinued support.

GP Connect InterSystems Supplier Progress carries the precise boundary, including the source typo InterSytems, blank cells that should not be over-read, and the 2026-06-21 evidence request pack for turning the NHS rows into supplier/product/deployment evidence requests.

Evidence Boundary

Current InterSystems-specific GP Connect evidence is stronger than the original vendor-only set because the current NHS table supports specific HealthShare cells and the June capture preserves a historical IRIS signal. Current Health Connect Cloud documentation supports the broader healthcare-standards integration boundary, but it does not convert the dated GP Connect statement into current GP Connect conformance evidence. The remaining boundary is implementation: match the NHS rows to current InterSystems GP Connect documentation, assurance artefacts, and deployment proof before using them for procurement-grade claims.

Current NHS API pages strengthen the service-side context: Access Record Structured and Send Document remain current NHS surfaces, and Send Document is explicitly a production messaging pattern using MESH, ITK3, HL7 FHIR STU3 payloads, and workflow ID GPFED_CONSULT_REPORT. That helps interpret the NHS supplier-progress row, but it remains NHS service evidence rather than InterSystems product-conformance evidence unless linked to an InterSystems row or customer deployment.

GP Connect should also remain an NHS England evidence category in this wiki. Use NHS Connectivity and GP Connect when comparing Scotland, Wales, and Northern Ireland so that devolved-nation digital-health, LIMS, procurement, and record-sharing evidence is not collapsed into GP Connect terminology.

Remaining Follow-up Evidence

  • Current GP Connect-specific Health Connect documentation.
  • Current HealthShare documentation showing how GP Connect support is configured and assured.
  • Supplier, standards-owner, or customer-approved response to the GP Connect evidence request pack on the supplier-progress page.
  • Customer-side deployment evidence showing which GP Connect capabilities are live in a specific InterSystems-backed programme.
  • Recheck the NHS supplier-progress page after any edit later than 3 September 2026.