Skip to content

Standards and Interoperability

This page is the overview for standards and interoperability evidence in the wiki.

Use Standards and Interoperability Evidence Domain as the source/evidence routing layer for standards surfaces, supplier-role boundaries, and implementation-proof questions. This page remains the human-readable synthesis overview.

Evidence Set

Evidence area Current conclusion Detail page
InterSystems product standards positioning Official product pages and selected technical docs position IRIS for Health, FHIR Services, Health Connect, HealthShare Unified Care Record, and HealthShare Clinical Viewer around FHIR, HL7, DICOM, IHE, API, data-normalisation, managed infrastructure, shared-record content, clinical presentation/access, FHIR Server, profiles/packages, OAuth/security, Network Connect, Health Connect Cloud, Cloud Services Portal deployment settings, BFC, OMOP, SDA/CDA transformation, AI Assistant / Navigation Application adjacency, and IRIS for Health ITK-documentation themes. The high-risk row audits now cover Health Connect, IRIS for Health, FHIR Services, HealthShare Unified Care Record, HealthShare Clinical Viewer, and HealthShare / PRSB CIS. InterSystems Standards Product Map
NHS England / DHSC standards direction and directory map NHS England continues to describe information standards as legal requirements for consistent capture, governance, sharing, and digital exchange of health and care data. DAPB/DAB governance, mandatory information-standard compliance, the NHS Standards Directory, and current standards collections remain the stronger evidence of ongoing standards stance. The directory now has a dedicated relevance map for FHIR/UK Core, GP Connect, MESH, PDS/events, terminology, medicines, clinical safety, transfer-of-care, shared-record, life-stage, imaging, and diagnostics entries, plus a GP Connect / MESH / ITK3 child page for the densest dependency chain. NHS Standards Directory and DHSC Standards Direction
Data (Use and Access) Act 2025 DUAA received Royal Assent on 19 June 2025 and is being commenced in stages. ICO guidance now says all DUAA data-protection provisions are in force as of 19 June 2026. For this wiki, the key health point remains that DUAA clarifies that health and adult social care information standards in England can include IT and IT services, and can apply to providers of IT, IT services, or information-processing services used or intended for health/adult social care in or in relation to England. DUAA does not itself prove any InterSystems conformance or DSIC catalogue status. Data (Use and Access) Act 2025
UK healthcare recording legal and professional position The UK position on healthcare records is layered across UK GDPR, Data Protection Act 2018, PECR, common law confidentiality, Caldicott, NHS Act 2006 section 251, professional standards, provider governance, candour, nation-specific records-management codes, public records, access-route separation, NHS information standards, terminology, clinical safety, provenance, and Health and Care Act 2022 / DUAA England information-standard changes. This proves the assurance model and required evidence categories, not compliance by any named product or deployment. UK Healthcare Recording Legal and Professional Position
Healthcare record source layers Repeated source-layer labels now have a canonical routing map so acronyms and shorthand such as GMC, NMC, HCPC, GPhC, CQC, NICE, PRSB, provider governance, professional duties, DSA/DPIA, records-management code, DCB0129/DCB0160 clinical safety, and public-records routes resolve to source-layer pages or sections. Healthcare Record Source Layers
NHS ITK accreditation claim InterSystems makes a UK NHS Interoperability Toolkit accreditation claim, current IRIS for Health docs repeat the historical ITK accreditation context, and the NHS ITK conformance-process and conformance-catalogue routes exist, but the 2026-06-20 current-source recheck did not find a current public non-vendor row naming InterSystems. The NHS Solution Assurance compliance catalogue explicitly excludes ITK Accreditation. NHS ITK Accreditation
GP Connect GP Connect is an NHS service/API integration context, not an InterSystems product. It now has capability pages and mirrored due-diligence pages, current NHS API/status context, structurally parsed NHS supplier-progress evidence mapping IRIS for Health (Middleware) to Send Document (Send) and HealthShare to specific Access Record: Structured sections, and an evidence request pack for turning those NHS rows into product/version, validation-scope, exclusion, component-coverage, adjacent-standard, and deployment-artefact requests when they are used for assurance. GP Connect Deep Dive
DSIC / NHS England digital primary care DSIC is the England-only digital primary-care procurement, capability, standards, assurance, migration, and Buying Catalogue environment. It maps GP foundation capabilities to national services and standards such as PDS, NHAIS, GP2GP, SCR, GP Connect, GPAD, GPES, MESH/MNS, eMED3, Yellow Card, EPS, e-RS, NHS login, ITK, NDO, and NEMS. NHS England Digital Primary Care
Cross-UK NHS connectivity GP Connect and Spine are NHS England evidence in the current source set. Scotland, Wales, and Northern Ireland need nation-specific functional comparison based on their own summary-record, messaging, identifier, prescribing, portal, and national-platform routes. GP Connect and Spine Equivalents by Nation
PRSB standards PRSB is a health and care record-content standards body. Its standards are relevant to shared care records, transfer of care, person-authored information, care plans, pharmacy, child health, maternity, end-of-life care, pathway content, provenance, and supplier conformance. The operating model needs a caveat because PRSB says the NHS England CISS contract ended in December 2025 while NHS England moves standards development/maintenance into a new model. PRSB Standards
PRSB Core Information Standard PRSB independently lists InterSystems Healthshare as Core Information Standard Version 2, Level 2 conformant, valid until 17.06.2028. CIS Version 3.0 is in review/final approval and should not replace the current published Version 2 evidence point until released. PRSB Core Information Standard (PRSB CIS)
Programme CORTISONE / UK Defence healthcare MOD CORTISONE evidence is standards-relevant because the programme vision describes open standards, NHS interfaces across the four UK nations, an Integration Platform, and EMPI. InterSystems evidence now supports a HealthShare / IRIS for Health CORTISONE role plus a Contracts Finder OCDS FY25-30 licence-award summary, but public CORTISONE-specific PRSB conformance and full technical architecture evidence remain open. Programme CORTISONE / UK Defence Healthcare
HL7 UK OIDs HL7 UK lists InterSystems-related West Midlands OIDs, which support identifier existence but not current operational status. HL7 UK InterSystems OIDs

Working Interpretation

InterSystems' UK healthcare proposition is strongly interoperability-led. The official website connects the product portfolio to healthcare standards, record aggregation, FHIR infrastructure, integration engines, API-based data exchange, GP Connect, and NHS/public-sector connected-care needs.

Evidence should stay separated by type:

  • Product-positioning evidence from InterSystems pages.
  • External standards evidence from NHS England Digital, DHSC, PRSB, or HL7 UK.
  • Customer or programme evidence that proves configured implementation, live use, or operational status.

The current public reading is not that NHS England has stopped caring about standards. It is that PRSB's NHS England-funded CISS role ended in December 2025, while NHS England/DHSC continue national information-standard governance through DAPB/DAB, the NHS Standards Directory, mandatory standards compliance, and the proposed Health Bill transfer of digital and data functions into the Secretary of State / restructured DHSC model.

The Standards Directory is now mapped separately because it contains several standards families that affect this wiki beyond PRSB: GP Connect APIs, UK Core/FHIR, MESH/ITK3, PDS/events, GP2GP/NHAIS, terminology/medicines, DCB0129/DCB0160 clinical safety, transfer-of-care, shared-record/life-stage content, DICOM, and pathology. Directory presence is standards-surface evidence; it still needs product, conformance, supplier-progress, or customer evidence before becoming an InterSystems implementation claim. GP Connect / MESH / ITK3 now has a child page because the role split across GP foundation system, consumer, document sender, middleware, viewer, and patient-facing component is too dense for the parent map.

DUAA adds a statutory supplier-facing pressure point to the standards model. Section 121 / Schedule 15 does not replace the NHS Standards Directory, DSIC, GP Connect onboarding, PRSB conformance, or clinical-safety evidence, but it strengthens the question of whether a named information standard applies to the IT supplier or IT service provider, not only to the care organisation using the system. ICO topic guidance now replaces factsheet-only treatment where available; the main subject-access guide is updated, while Right of Access in brief, SARs Q&A, research, automated decision-making/profiling, and IDTA/Addendum updates remain tracked until final guidance is published.

The healthcare-recording legal and professional synthesis adds the wider assurance frame around the standards pages. UK GDPR, DPA 2018, PECR, common law confidentiality, Caldicott, NHS Act 2006 section 251, professional record-keeping, provider governance, candour, records-management codes, public-records/access-route separation, SNOMED CT, PRSB/provenance, DCB0129/DCB0160, Health and Care Act 2022, and DUAA should be handled as separate layers. For InterSystems analysis, the key consequence is that Health Connect / HealthShare technical suitability must be paired with deployment artefacts: legal basis, confidentiality route, PECR controls where applicable, record amendment/export/search procedures, access-control/provenance/audit design, records-management retention, clinical safety, information-standard applicability, and supplier RACI (SRC-241 to SRC-260).

Follow-up Validation

  • Use the NHS ITK evidence request template to seek current accreditation, conformance, or certificate records naming InterSystems; do not use Solution Assurance compliance-catalogue rows as ITK proof.
  • Add accessible official InterSystems technical documentation for remaining IRIS for Health and HealthShare interoperability features not covered by the new product-depth pages or account-gated HealthShare 2026.1 documentation.
  • Keep Programme CORTISONE / UK Defence healthcare contained unless a new primary source appears or the user explicitly reopens it; do not use it as the default validation path.
  • Validate supplier-specific GP Connect progress records against product documentation, assurance artefacts, and named customer deployments.
  • Use the GP Connect InterSystems Supplier Progress request pack when supplier-progress rows are being used as assurance evidence rather than only source-register evidence.
  • Validate HealthShare, Health Connect, IRIS for Health, and FHIR Services implementation details against current InterSystems technical documentation.
  • Keep product capability claims separate from configured implementation patterns in customer deployments.

Standards Pages