Versions Compared

Old Version 8

changes.mady.by.user Devishree Nath (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Robyn Brooke (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated term "Framework(s)" to "Contracting Vehicle(s)"
Page Properties

ID

S60

Version

1

2.0.0

Type

Interoperability toc

Standard

Status

Effective

Effective Date

Insert excerptDay One Effective DateDay One Effective Datenopaneltrue

 

Contracting Vehicle(s)

Table of Contents
minLevel1
maxLevel3
outlinefalse
styledisc
typelist
printabletrue

Introduction

The Summary Care Record (SCR) is an

electronic record

Electronic Record of important Patient

information

Information, created from GP medical records. It can be seen and

used

used by authorised

staff

Health or Care Professionals in other areas of the

health

Health and

care system

Care System involved in the Patient's direct care.

From an interoperability perspective there are two aspects to the

summary care record

Summary Care Record:

  1. The creation and updating of the

summary care record

  1. Summary Care Record

  2. Providing the ability for

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

  1. authorised Health or Care Professionals to access the Summary Care Record

Both of these aspects are covered in the documentation below.

Additional information is available

at NHS Digital's summary care record site

Compliance, Assurance and Testing

To gain access to SCR suppliers

on the Authority's Summary Care Records (SCR) site.

Requirements 

Applicable Suppliers

ID

Requirement

Level

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

SCR01

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

Status
colourRed
titleMUST

SCR02

Implement and maintain the SCR FHIR API inline with the GP Summary Requirements Refactored latest specification version.

View file
nameGP Summary Requirements Refactored for SCR FHIR API.docx

Status
colourRed
titleMUST

SCR03

Implement and maintain the SCR FHIR API inline with the GP Summary Presentation Text Specification Refactored latest specification version.

View file
nameGP Summary Presentation Text Specification Refactored for SCR FHIR API.xlsx

Status
colourRed
titleMUST

SCR04

Implement and maintain the SCR FHIR API inline with the SCR Viewing Requirements Refactored latest specification version.

View file
nameSCR Viewing Requirements Refactored for SCR FHIR API.docx

Status
colourRed
titleMUST

SCR05

Implement and maintain the SCR FHIR API inline with the Technical Specification for GP Summary XHTML latest specification version.

View file
nameSCR FHIR API Technical Specification for the GP Summary XHTML.docx

Status
colourRed
titleMUST

SCR06

Implement and maintain the requirements detailed in the COVID-19 SCR Additional Information Requirements latest specification version.

View file
nameCOVID-19 SCR Additional Information requirements.docx

Status
colourRed
titleMUST

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

SCR07

Implement the requirements detailed in the GP Summary Requirements v5.8.3 or later e.g. SCR FHIR API 

View file
nameGP Summary Requirements v5.8.3.docx

Status
colourRed
titleMUST

Compliance, Assurance and Testing

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

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 - GP Summary Requirements v5.8.3

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

Expand
title Click here to view historical assurance approach

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 advice

Suppliers will be asked to demonstrate adherence to the following specifications:

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 or visit 

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

 document

.docx document provides guidance on the clinical safety validation processes for SCR messaging.

Documentation

SCR FHIR API

For Suppliers of new Services or applications:

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

NHS Summary Care Record Service - GP Summary Requirements v5.8.3

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

Expand
titleClick here to view previous SCR requirements documentation

Summary Care Record Creation

GP Summaries are created and sent to the Summary Care Record repository (on Spine) via messaging from GP

systems

Systems which implement the Patient Information Maintenance - GP

capability

 capability.

To create

summary care records

Summary Care Records and provide them to the

service

Service,

suppliers

Suppliers must implement the requirements detailed in GP Summary Requirements v5.8.3.

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

 for

.doc for all representations of medication-related adverse clinical events.

Implementations must comply with the SCR GP Summary Sending Compliance v3 - Baseline Index v6.0

Message definitions are detailed in

the

the Domain Message Specification (DMS)

for

 for Summary Care

Record  

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

 NB version 4.2

is

 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 Summary Care Record Permission To View Guidelines.pdf

General requirements for SCR viewing (regardless of implementation mechanism) are set out in NPFIT-FNT-TO-DPM-0929.03 SCR Viewing Requirements v1.6 (Approved).docx

Guidance for implementing Role-Based Access Control for SCR viewing is found in NPFIT-SI-SIGOV-0073 04 Guidance on Implementing RBAC for PSIS and PDS v2.0.doc

Suppliers have a number of options for implementing

summary care record

Summary Care Record viewing, as detailed below:

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

Patient.

NPFIT-FNT-TO-DPM-1023 SCR 1-Click Supplier Requirements v2 7.docx

Spine mini

services

Services

Spine mini

services

Services (SMS)

are

 are a more lightweight way of developing read-only integration with some national Spine

services

Services. SMS Client

systems

Systems allow SCR access with

patient

Patient permission and for Emergency Reasons. SCR Viewing

systems

Systems will be able “plug into” the SCR Spine Mini-Service functionality of the SMS Provider. The SMS Provider

system

System provides various defined functions and

services

Services for SCR Viewing

systems

Systems, e.g. the SMS Provider would retrieve GP Summaries and manage “Permission to View” on behalf of viewing

systems

Systems (clients).

SCR - Spine Mini Service Provider Requirements-v1.3.docx

SCR - Spine Mini Service Client Requirement04.1.docx

Full SCR integration

Integration of SCR information into the GP clinical

system

System. 

A GP

system

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

System.

SCR_Viewing_Requirements_v3.0_(Approved).docx

Summary Care Record DMS 5.8

Message Implementation Manual (MIM 7.2)

PSIS

 PSIS Query

NPFIT-FNT-TO-TIN-1228 14 Compliance Specification - Clinical Message Handling Addendum v4-0

 

.doc (sections relevant to PSIS Query)

MIM 7

.

2

.

02 Known Issues 1.3.doc

Dependencies

Creating a compliant implementation requires implementing the following dependent interface

standards

Standards:

SCR FHIR API

Excerpt

For Suppliers of new Services or applications:

NHS Summary Care Record Service - GP Summary Requirements v5.8.3

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

Expand
titleClick here to view historical dependencies

Roadmap

Items on the Roadmap which impact or relate to this Standard

Page Properties Report
firstcolumnRoadmap Item
headings Standards and Capabilities, Status, Effective Date, Description, Change Type, Change Route
pageSize300sortByEffective Date
cqllabel = "
S60
s60" and space
=
in ( currentSpace ( ) , "DCSDCS" , "DCSDR" )