Skip to content

Information Space

The InterSystems healthcare knowledge space currently spans these confirmed domains:

  1. Healthcare data/application platforms: IRIS for Health and FHIR Services, now split into independent product pages with current FHIR Server, managed-service, OAuth/security, supported-operation, Network Connect, Cloud Services Portal, and cloud-hosted-service boundaries where public docs exist.
  2. FHIR and transformation technical depth: InterSystems FHIR Server, FHIR packages/profiles, Bulk FHIR Coordinator, OMOP, and SDA/CDA transformation now have independent evidence pages.
  3. Connected-care and interoperability suites: HealthShare, Unified Care Record, Clinical Viewer, Health Connect, Health Insight, EMPI, Personal Community, Provider Directory, Care Community, and HealthShare AI Assistant now have clearer component boundaries and independent pages where evidence exists; HealthShare 2026.1 detail is account-gated and AI Assistant has public sample artefacts but not full governance evidence.
  4. Clinical and laboratory systems: TrakCare, IntelliCare and TrakCare Lab Enterprise, now split into independent product pages; international TrakCare PHC/community-health evidence is tracked separately so Gateway Health, Victoria, Chile APS, Northern Territory, DHAMAN, and Qatar boundaries do not collapse into generic country-presence claims.
  5. UK NHS digital connectivity and interoperability evidence, with adjacent public-sector healthcare context: EPR, connected care, interoperability, and regional/national deployment examples, including Birmingham and West Midlands references plus dedicated Scotland, Wales, and Northern Ireland pages. Scotland now has InterSystems Edinburgh office, Public Health Scotland TrakCare Patient Management System, and NHS Shetland TrakCare ED / Ensemble evidence; Wales has all-Wales LIMS 2.0 / TrakCare Lab Enterprise board and procurement evidence; Northern Ireland has narrow Caché / NHAIS licensing evidence kept separate from encompass / Epic / Rhapsody context. The evidence grades remain mixed across vendor-only, customer-side, FOI, NHS/local-programme, DPIA, official national strategy, procurement, and external corroboration sources.
  6. Standards and interoperability context: HL7 FHIR, HL7 v2/v3, GP Connect, Spine, PDS, SCR, EPS, e-RS, DICOM, IHE profiles, APIs, cloud-based data exchange, Network Connect, UK NHS ITK accreditation claims, Data (Use and Access) Act 2025 statutory context, NHS Standards Directory / DHSC standards-direction mapping, PRSB standards-family synthesis, PRSB Core Information Standard conformance, HL7 UK OIDs, GP Connect capability definitions, capability-specific due-diligence pages, SSP/MESH/API-platform patterns, dated NHS supplier-progress evidence with a current HealthShare structured-consumer row and historical IRIS Send Document row, and a cross-UK boundary separating England GP Connect from shared national infrastructure such as Welsh EPS use of Spine. The Standards Directory map now separates recognised standards surfaces from InterSystems conformance evidence across FHIR/UK Core, GP Connect, MESH, PDS/events, terminology, medicines, clinical safety, transfer-of-care, shared-record/life-stage content, imaging, and diagnostics. DUAA is kept as a statutory data/IT standards layer: Royal Assent on 19 June 2025, staged commencement, and an England health/adult social care information-standard provision that can reach IT and IT-service providers without itself proving supplier conformance. Devolved equivalents are now compared functionally through Scotland ECS/KIS/CHI/NDP/SCI/ePharmacy/MyCare.scot, Wales WGPR/WCP/WCCG/NDR/WDS/NHS Wales App, and Northern Ireland NIECR/encompass/EpicCare Link/HCN/DIS/ePharmacy.
  7. NHS England Digital Primary Care context: the new parent section groups DSIC, GP Connect, GP foundation capabilities, standards/national-service dependencies, procurement/migration, Buying Catalogue, Tech Innovation, and Digital Primary Care replacement-framework context. The DSIC capability-to-standard crosswalk maps GP software/service components to national-service checks, then maps those to HealthShare, Health Connect, IRIS for Health, FHIR Server, and related InterSystems components with an explicit boundary that HealthShare is not currently proven as a full DSIC GP foundation system.
  8. UK Defence healthcare context: Programme CORTISONE is now tracked separately as NHS-adjacent Defence Medical Services evidence. It covers DMS/DPHC/DMedC scope, entitled children/family boundaries, post-service NHS-care boundaries, HealthShare / IRIS for Health CORTISONE evidence, FY25-30 Contracts Finder OCDS licence-award evidence, the January 2026 TPP EHR contract announcement, PRSB relevance, and the current absence of public evidence for non-healthcare UK Defence InterSystems use.

The September 2026 review adds current service-delivery boundaries to this map: initial national MyCare.scot availability, phased Welsh LIMS deployment, Welsh EPS reuse of Spine/PDS, a named Welsh CDR feed, and Acacia inquiry findings that constrain claims of completed primary-care rollout (SRC-328 to SRC-335).

The broader 9 September review adds product-role and FHIR comparisons and a plain explanation of the standards layers. Keep product capabilities, service models, national interfaces and measured customer outcomes distinct.

Each page should identify whether it uses primary evidence, official guidance, operational inference, commentary, or unknown-provenance material. Cross-domain gaps belong in Evidence Validation Queue.

The growing source/evidence set now has a domain access layer: Source and Evidence Domain Map and NHS England Digital Primary Care Evidence Domain.