CPRD (Clinical Practice Research Datalink)
Clinical Practice Research Datalink (CPRD) is the MHRA’s real-world data research service, supporting public health and clinical studies using routinely collected health information. It developed from the General Practice Research Database (GPRD). Its data resources include primary care records and linked datasets, accessed through defined governance arrangements rather than unrestricted reuse.
Key takeaways
- CPRD supports research using routinely recorded healthcare data.
- Approved access requires governance and licensing arrangements.
- Pseudonymised collection and anonymised research releases are distinct.
Which Data and Permissions Are Involved?
The history of CPRD explains its GPRD origins. Its study approval process assesses proposed research use. As an operational recommendation, check dataset suitability, population coverage, linkage availability and the approved protocol before committing to an analysis. A familiar dataset name does not establish that every required variable or follow-up period is available.
Why It Matters for Data Protection
The CPRD patient privacy notice distinguishes pseudonymised records received by CPRD from anonymised data released for approved research. It sets out UK GDPR bases for CPRD’s own processing. Those bases are not a universal permission for another organisation’s independent data collection or linkage. As an operational recommendation, document the precise access model and assessing any additional information brought into the project.
Hypothetical example: A sponsor plans an observational safety study using primary care and linked hospital data. Its team recommends aligning the cohort, outcomes and linkage needs with the approved protocol, while checking that imported reference files do not contain prohibited personal information.
Frequently Asked Questions
Is CPRD the old GPRD?
CPRD developed from GPRD, but its present service and resources are broader.
Do researchers receive patients’ names?
CPRD describes its approved research releases as anonymised, not direct-identifier exports.
Does coding automatically remove UK GDPR obligations?
No. CPRD’s own notice distinguishes pseudonymised processing from anonymised research releases.
Related reading: real-world data, secondary use of health data.
For practical implementation, explore clinical research support.
Updated: 27 October 2026
