| Page Properties | |||||
|---|---|---|---|---|---|
|
|
|
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
Health or Care Professionals 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:
The creation and updating of the Summary Care Record
Providing the ability for
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 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. |
| ||||||
SCR02 | Implement and maintain the SCR FHIR API inline with the GP Summary Requirements Refactored latest specification version.
|
|
|
| |||||||||
SCR03 | Implement and maintain the SCR FHIR API inline with the GP Summary Presentation Text Specification Refactored latest specification version.
|
|
|
| |||||||
SCR04 | Implement and maintain the SCR FHIR API inline with the SCR Viewing Requirements Refactored latest specification version.
|
|
|
| |||||||||
SCR05 | Implement and maintain the SCR FHIR API inline with the Technical Specification for GP Summary XHTML latest specification version.
|
|
|
| |||||||
SCR06 | Implement and maintain the requirements detailed in the COVID-19 SCR Additional Information Requirements latest specification version.
|
|
|
| |||
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
|
|
|
|
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 | ||
|---|---|---|
| ||
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:
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:
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 | ||
|---|---|---|
| ||
Summary Care Record CreationGP 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 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.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 |
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 ViewingSCR 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 viewing, as detailed below:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Dependencies
Creating a compliant implementation requires implementing the following dependent interface 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 | |
|---|---|
|
|
|
|
Roadmap
Items on the Roadmap which impact or relate to this Standard | ||||||
|---|---|---|---|---|---|---|
|
|
|
|
|