Skip to content

Shared care and GP Connect

Core Information Standard

The Core Information Standard is an active common content model for shared-care records. NHS England says shared-care records should conform, while also explaining that the potential information set is non-prescriptive and that local use cases, information governance and role/circumstance views determine what is included. The directory page does not expose an ISN or section 250 authority. Treat it as a high-value interoperability ceiling, not a universal statutory dataset. SRC-014

GP Connect Access Record Structured

GP Connect provides a FHIR-based route to structured GP record information for direct-care contexts across primary, secondary, urgent and community settings. The directory shows no GP Connect ISN, so it is not a universal section 250 mandate. Separately, GP contract changes required in-scope practices from 1 October 2025 to enable read-only GP Connect Access Record for other NHS direct-care providers and private healthcare providers where explicit patient permission is obtained and they provide direct care. Current product guidance prohibits beyond-care use except the stated medical-examiner use case. Clinical safety, identity, authorisation, patient choice, purpose filtering and dependent standards remain separate. SRC-015 SRC-038 SRC-039

DAPB4101 pathology transition

DAPB4101 v1.0.0 is a current section-250 standard for structured pathology reports sent from laboratories to the requesting GP organisation for direct care. In the initial scope, LIMS or middleware creates and sends pathology-specific UK Core FHIR R4 reports with prescribed SNOMED CT content; GP systems receive and ingest them. It is not a general secondary-care, shared-record or research-sharing mandate.

The formal ISN still says full conformance was due on 30 April 2025. NHS England’s later implementation page, edited 10 July 2026, says a live first-of-type FHIR/SNOMED pilot is under way, testing and assurance are intended to finish by April 2027, supplier roadmaps and national rollout follow, and SNOMED PBCL will continue during gradual PaLM adoption. It also says the full-conformance date will be extended but gives no replacement. Therefore record the official-source conflict: April 2027 is a pilot milestone, not a new conformance deadline, and national implementation is not complete. SRC-028

For a real implementation, confirm the current FHIR implementation guide and API version, SNOMED CT UK edition, specialty and message scope, PaLM/PBCL mapping, EDIFACT coexistence and cutover, acknowledgement/error handling, and end-to-end DCB0129/DCB0160 safety evidence. DAPB4101 v1.0 initially covers biochemistry, haematology, immunology, transfusion medicine and microbiology; NHS002/NHS004 screening flows are excluded, and coded result values, interpretations, units and specimens are not all mandated. Conformance to the reporting standard does not authorise onward NHS App, SPR, AI, planning or research use.

Safe implementation

  • map each view or API interaction to a documented care use case;
  • filter by role, relationship, purpose and current context;
  • distinguish source absence, “not asked,” negation and data-quality uncertainty;
  • maintain provenance, timestamps, code-system versions and correction pathways;
  • test sensitive information, third-party content, access override and audit review;
  • maintain DCB0129 manufacturer and DCB0160 deployment safety evidence;
  • prevent direct-care access from silently feeding beyond-care analytics.

The minimum-to-maximum requirement model, direct-care sharing route, NHS standards applicability register, and clinical safety and security controls govern the implementation.