This collection is called GP Data for Planning and and its purpose is to support the data needs of the health and social care system including policy development, public health, planning and commissioning of services and research. This new collection is designed to reduce the number of requests for access to data received by General Practice.
Once fully established, NHS Digital will undertake a managed transition from the General Practice Extraction Service (GPES) to the new GP data service. NHS Digital will also work with other organisations to enable transition from existing data flows to the new service.
More information about this data collection and the General Practice obligation to provide data for this purpose is contained in the issued by NHS Digital to GP Practices. The Data Provision Notice includes appendices which explain data minimisation, additional protections, pseudonymisation and the data collection specification.
The GPDfPR is a daily extract of both Patient and appointment data provided by GP Clinical Systems.
It is recognised that some suppliers may deliver appointment modules only and will not collect clinical data. These suppliers will still be required to provide the GPDfPR appointments feed. These suppliers should contact NHS Digital so that only the relevant requirements are applied and an appropriate assurance model is put in place. For detail contact firstname.lastname@example.org.
The below document details the overarching high level requirements that must be assured against to be compliant with the standard. This covers the operational management, different file feeds, timing of submissions, configuration items and messaging.
GP Data for Secondary Uses Supplier Requirements.docx
The below is intended to provide a comprehensive technical view of the provider submission.
GPDfPR Technical Output Specification
The data set tables include attribute (data item) level detail necessary to construct an output data set suitable for submission. The data set tables also include additional information explaining:
- Which attributes are mandatory/optional
- Attribute’s format and type
- Linkages between the tables
- What attributes must be de
The below document provides technical guidance for suppliers generating and populating the GP data extract message and counterpart organisations receiving and processing GP d
GP Data Extract Supplier Implementation Guidance
This document defines the technical interface and contact between the GP data extraction Subsystem within source systems and the Landing Platform, the component of DPS responsible for receiving, validating and processing GP data extracts prior to utilisation.
GPDfSU GP Data Interface Specification.docx
The below zip file contains the xml Schema, Schematron and sample Patient, appointment and acknowledgement xml files.
GP Data Schema.zip
*May alternatively use AWS Direct S3-S3 transfers as the secure transport mechanism
- De-identification is performed via an NHS Digital supplied de-identification toolkit. This process yields ‘transit pseudonyms’ which render the de-identified fields suitable for transmission across the organisational boundary between source system and NHS Digital landing platform. The transit pseudonym provides an encrypted wrapper which ensures the de-identified field is not persisted or processed as clear text within the data store.
To maintain security further information about Privitar and de-identification will be provided on request, although an overview can be found in the interface specification.
The GPDPR Solution Assurance Approach describes the compliance, assurance and testing that suppliers must complete to achieve compliance with the GPDPR capability.