| 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 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:
- The creation and updating of the summary care record
- 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 |
|---|---|---|
| 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 GP in GP Summary Requirements v5.8.3 or 3 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 - GP GP Summary Requirements v5.8.3
For Suppliers of services which ARE currently deployed into an operational environment:
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 - GP GP Summary Requirements v5.8.3
For Suppliers of services which ARE currently deployed into an operational environment.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
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 GP 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 the SCR GP Summary Sending Compliance v3 - Baseline Index v6.0 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 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:
|
Roadmap
Page Properties Report headings Standards and Capabilities, Status, Effective Date, Description, Change Type, Change Route pageSize 300 sortBy Effective Date cql label = "S60" and space in ( currentSpace ( ) , "DCSDR" , "DCSDCS" )