/
Summary Care Record (SCR) V1.0.1

Summary Care Record (SCR) V1.0.1

28-09-2023

ID

S60

Version

1.0.1

Type

Interoperability Standard

Status

Retired

Effective Date

May 10, 2022 

Framework(s)

Introduction

The Summary Care Record (SCR) is an electronic record of important Patient information, created from GP medical records. It can be seen and used by authorised staff in other areas of the health and care system involved in the Patient's direct care.

From an interoperability perspective there are two aspects to the summary care record:

  1. The creation and updating of the summary care record

  2. Providing the ability for authorised staff to access the summary care record, for which there are a range of options

Both of these aspects are covered in the documentation below.

Additional information is available at NHS Digital's summary care record site

 

Requirements 

Applicable Suppliers

Requirement

Level

Applicable Suppliers

Requirement

Level

Suppliers of new services or applications (i.e. those which are NOT currently deployed into an operational environment with existing SCR compliance).

Implement and maintain the API inline with the latest specification version of SCR FHIR API.

MUST

Suppliers of services which ARE currently deployed into an operational environment, and have existing SCR compliance.

Implement the requirements detailed in or later e.g. SCR FHIR API

MUST

All suppliers are encouraged to work towards compliance with the latest version as above.

Compliance, Assurance and Testing

SCR FHIR API

For Suppliers of new services or applications, see the Summary Care Record(SCR) section on Onboarding Overview of the Digital Care Services Interoperability Standards and Requirements.

NHS Summary Care Record Service - 

For Suppliers of services which ARE currently deployed into an operational environment:

To gain access to SCR suppliers follow the Common Assurance Process (CAP). CAP is an end-to-end assurance process, which involves a tailored (CAP) approach being developed which states what deliverable and activities are conducted.

As part of the CAP suppliers will be asked to demonstrate adherence to the following specifications:

  • CAP Information Governance Compliance Requirements

  • External Interface Specification

  • NHS Messaging Implementation Manual

  • Personal Demographics Service Integration Requirements

  • Summary Care Record Integration Requirements (see details below)

These specifications contain a set of generic requirements applicable to all systems seeking compliance to a business domain. Compliance with these specifications is mandatory and established through the CAP.

For advice, access to the documentation, and support from the NHS Business Partners programme, please contact businesspartners@nhs.net or visit https://digital.nhs.uk/services/nhs-business-partners

The NPFIT-SCR-SCRDOCS-0038.01 NHS CFH SCR Clinical Message Validation Process v1.docx document provides guidance on the clinical safety validation processes for SCR messaging.

Documentation

SCR FHIR API

For Suppliers of new services or applications:

  • API Catalogue - Summary Care Record (SCR) FHIR API

  • GP software developer guide

  • Testing APIs

It is recommended to read GP software developer guide in conjunction with the API documentation.

NHS Summary Care Record Service - 

For Suppliers of services which ARE currently deployed into an operational environment.

Summary Care Record Creation

GP Summaries are created and sent to the Summary Care Record repository (on Spine) via messaging from GP systems which implement the Patient Information Maintenance - GP capability.

To create summary care records and provide them to the service, suppliers must implement the requirements detailed in.

Summary care messages contain XHTML information and generated messages must conform to the specification in NPFIT-SHR-MODL-SUMREC-0025 08 GP Summary Presentation Text Specification v3.1 (Approved).xlsx

Implementations must comply with the NPFIT-EP-DB-0007.05 Allergy_ADR_Intolerance v 1.5 Draft.doc for all representations of medication-related adverse clinical events.

Implementations must comply with the 

Message definitions are detailed in the Domain Message Specification (DMS) for Summary Care Record  

Further information useful for implementers of this interface such as Use Cases, Trigger Events and Sequence Diagrams may be found in the Spine Message Implementation Manual (MIM).  NB version 4.2 is the version used for the GP Summary Update message.

Also, see MIM 4.2.00 Known Issues.doc

Summary Care Record Viewing

SCR viewing must be implemented in line with the 

General requirements for SCR viewing (regardless of implementation mechanism) are set out in 

Guidance for implementing Role-Based Access Control for SCR viewing is found in 

Suppliers have a number of options for implementing summary care record viewing, as detailed below:

Option

Description

Documentation

Option

Description

Documentation

1 click

a simpler and less resource-intensive way to enable SCR viewing into local applications. This solution allows a user of an application to click and launch the SCRa in a separate window for a specific patient.

Spine mini services

Spine mini services (SMS) are a more lightweight way of developing read-only integration with some national Spine services. SMS Client systems allow SCR access with patient permission and for Emergency Reasons. SCR Viewing systems will be able “plug into” the SCR Spine Mini-Service functionality of the SMS Provider. The SMS Provider system provides various defined functions and services for SCR Viewing systems, e.g. the SMS Provider would retrieve GP Summaries and manage “Permission to View” on behalf of viewing systems (clients).

Full SCR integration

Integration of SCR information into the GP clinical system. 

A GP system retrieves GP Summaries from the Summary Care Record on Spine using the PSIS Query message and displays it via appropriate screens within the GP clinical system.

Summary Care Record DMS 5.8 

Message Implementation Manual (MIM 7.2) PSIS Query

(sections relevant to PSIS Query)

 

Dependencies

Summary Care Record FHIR API

For Suppliers of new services or applications:

  • Authentication and Access - using NHS Care Identity Service 2 API

NHS Summary Care Record Service - 

For Suppliers of services which ARE currently deployed into an operational environment:

Roadmap