Skip to content

PRSB Core Information Standard (PRSB CIS)

This page tracks the Core Information Standard evidence for InterSystems HealthShare. Use PRSB Standards for the wider PRSB standards-family map.

Current Standard

The PRSB Core Information Standard (CIS) defines common health and care information for shared care records across sites, organisations, and care settings. PRSB states that NHS England specifies CIS as the standard that shared care records should conform to. The current published public release tracked in this wiki is CIS Version 2.01.

PRSB also states that CIS Version 3.0 is in review and final approval, with publication dates to follow. Treat CIS Version 2.01 / Version 2 conformance as the current published evidence point until the PRSB or NHS England standards route publishes the next release.

The NHS Standards Directory adds a useful boundary around CIS: it treats the Core Information Standard as a recognised shared-record content standard, while noting that CIS is not by itself a physical data model, a role-based access-control model, a presentation standard, a deduplication method, or a complete shared-care-record implementation definition. April 2026 updates also changed selected sex and gender items, so CIS should be checked against the NHS Directory as well as PRSB pages when implementation detail matters.

InterSystems Conformance

PRSB lists InterSystems Healthshare as Core Information Standard Version 2, Level 2 conformant, valid until 17.06.2028.

InterSystems separately states that HealthShare 2024.1 achieved PRSB Core Information Standard Level 2 conformance and that PRSB validation included platform support for GP Connect, FHIR, HL7 v2, DICOM, and IHE profiles.

Supported Conclusion

The strongest supported conclusion is that InterSystems Healthshare has PRSB-listed Core Information Standard Version 2, Level 2 conformance. This strengthens the standards evidence for HealthShare shared-care-record positioning and is directly relevant to HealthShare Unified Care Record and HealthShare Clinical Viewer.

Evidence Boundary

PRSB CIS conformance does not prove that every HealthShare deployment exposes every CIS section, every local role view, every GP Connect flow, or every technical standard named in vendor positioning. Local configuration, procurement scope, onboarding, clinical safety, data-sharing, role-based access, and information-governance controls still determine live implementation.

Keep these evidence layers separate:

  1. PRSB conformance listing.
  2. InterSystems HealthShare certification announcement.
  3. Product documentation for configured standards support.
  4. Customer implementation evidence.

The high-risk audit on InterSystems Standards Product Map treats the PRSB CIS row as strong conformance evidence with a narrow scope: it supports InterSystems Healthshare CIS Version 2 Level 2 conformance, but it does not by itself prove every HealthShare component, every GP Connect/FHIR/HL7/DICOM/IHE route, DSIC compliance, or local safety/governance readiness.

Product Applicability

Product or capability How CIS may apply Current evidence status
HealthShare Unified Care Record Direct shared-care-record content fit. Supported by PRSB Healthshare conformance and HealthShare UCR positioning.
HealthShare Clinical Viewer Direct-care presentation layer over shared-care-record information. Relevant but not independently PRSB-listed as a separate product in this pass.
HealthShare EMPI and Provider Directory Supporting identity and provider context around shared records. Supporting infrastructure, not standalone CIS conformance evidence.
IRIS for Health, FHIR Services, and Health Connect Technical enablement for data, FHIR, API, document, or integration flows that may carry CIS-aligned content. Applicability only unless a product or customer source maps the implementation to CIS.

PRSB Assurance Scope

Use the canonical reusable pattern on Standards and Interoperability Evidence Domain only if the PRSB listing is being used as assurance evidence. This page keeps the PRSB-specific scope instead of repeating the generic request table.

Assurance question PRSB-specific evidence needed
Is the listing current and correctly named? PRSB certificate or register reference, issuing body, product name spelling, conformance level, product version or build, issue date, expiry date, renewal status, and any withdrawal or supersession note.
What was assessed? Validation summary covering CIS version, sections or capabilities assessed, Level 2 interpretation, test method, validation criteria, evidence-pack index, assessment date, exclusions, and caveats.
Which HealthShare components are covered? Whether HealthShare Unified Care Record, Clinical Viewer, EMPI, Provider Directory, Health Connect, IRIS for Health, FHIR Services, or another named component was assessed directly, indirectly, or only as supporting infrastructure.
Which adjacent standards or deployment claims remain separate? Separately evidenced GP Connect, FHIR, HL7 v2, DICOM, IHE, MESH, ITK, ITK3, DCB0129, DCB0160, DSIC, DSA/DPIA, role/view, RBAC/SSO/audit, go-live, and operational-owner artefacts where those claims are relied on.

Follow-up Evidence

  • Current HealthShare technical documentation for the conformance scope.
  • PRSB certificate or detailed validation scope if publicly available.
  • Customer-side evidence showing how PRSB-conformant information is implemented in named shared-care-record deployments.