Unofficial. This site is an experimental reformatting of data published by NHS England. It is not endorsed by NHS England. Always check the official Data Uses Register before relying on anything here.

OpenSAFELY and High Cost Drugs Linkage

No longer in the register. This agreement was last published in the January 2023 edition and was not in the February 2023 edition. NHS Digital merged into NHS England on 1 February 2023, and agreements within the merged organisation moved to a separate internal register, so this agreement most likely moved rather than ended. This page shows what the register last said, and it is not counted in this site's figures.

NHS England (Quarry House) · Agency/Public Body

Listed under NHS England.

Reference
DARS-NIC-397618-T8L8Z
Latest version
v6.2
Term of latest version
1 November 2022 to 30 April 2023
Start date
15 September 2020
Data controller
Sole Data Controller
Commercial purposes
No
Sublicensing
No
Files released to date
0

Why the data was released

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data). All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/ and approved projects are available here - https://approved-projects.opensafely.pages.dev/approved-projects/

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data has been pseudonymized at source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold honorary contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

As both TPP and EMIS would have the technical ability to re-identify the data through the use of mapping tables, the data is considered as confidential and requires COPI to address the common law duty of confidentiality.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of February 2022, 9 developers (with NHS England honorary contracts) have access to the level 2 or level 3 environment for development and maintenance purposes only. The Level 2 environment is where the event level pseudonymised data is held. The Level 3 environment is where the specific analysis’ cohort data is held.

Researchers now only access the Level 4 environment where the aggregated results of their studies are held. The Level 4 environment is where researchers review the results and apply disclosure controls before requesting the data to be released. Two independent output-checkers review the results and only release them if there are no disclosure concerns. 72 researchers have access to the Level 4 environment; the 9 developers also have access to this Level 4 environment

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

Community - Local Provider Flow

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available. A draft report has also been produced on the use of the data so far.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a future waves.

Other NHS Digital Datasets

NHS England will also use datasets it receives from NHS Digital under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L in the OpenSafely platform to further enhance the data. These dataset include:

- Secondary Uses Services Data (SUS+)

- Second generation surveillance system (SGSS)

- Civil Registration Data - Deaths

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic. As COVID-19 continually is evolving, this is a continuous activity.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider network of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England has an established Oversight Board. The Oversight Board has had 4 meetings and their agenda, documents and meetings notes are publicly available: https://www.opensafely.org/governance/

Amendment to change data frequency

The current dataset in OpenSAFELY-TPP is a one off collection covering submissions from FY 2018/19 and FY 2019/20, and there is no process in place to routinely update the information available in the High Cost Drug dataset. Whilst this is very useful for assessing events and outcomes early in the COVID-19 pandemic, a routine update of the data is needed to assess current high-priority questions and future important questions. For example, a routine update to this data will allow assessment of COVID-19 vaccine effectiveness in people using high-cost medicines or indeed people with a recorded diagnosis likely to be treated with a High Cost Drug. Therefore the controller is requesting the data frequency is changed to adhoc. This will allow regular (likely to be monthly) refreshes of the data that will better inform the changing medications required to treat COVID-19 as the virus continually evolves and effects patients differently.

NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO). North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data.

Legal Basis for Processing Data

Data accessed under this Agreement will be processed in accordance with GDPR Article 6(1)(e) (processing is necessary for the performance of a task in the public interest or in the exercise of official authority vested in the controller) and Article 9(2)(i) (processing is necessary for reasons of public interest in the area of public health, such as protecting against serious cross-border threats to health or ensuring high standards of quality and safety of health care and of medicinal products or medical devices, on the basis of Union or Member State law which provides for suitable and specific measures to safeguard the rights and freedoms of the data subject, in particular professional secrecy).

Common Law Duty of Confidentiality

Although the data is pseudonymised when it is disseminated, as TPP and EMIS are in receipt of the SALT key used for this project, the data is considered as confidential. NHS England are relying on Reg 3 (3) of the COPI Notice (2002) to allow the dissemination of confidential patient information without consent.

Processing activities

All organisations party to this agreement must comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract i.e: employees, agents and contractors of the Data Recipient who may have access to that data).

Approximately 24m patient (circa 17m adults) pseudonyms from TPP, and approximately 35m from EMIS, will be given to the DSCRO’s (Data Services for Commissioners Regional Offices) to match against local flow high cost drug data.

Community - Local Provider Flows

DSCROs (via the CSU) will share pseudonymised high cost drugs data directly with the electronic health record (EHR) vendors, TPP, NHS North of England Commissioning Support Unit and EMIS respectively, who are acting as data processor for NHS England. Message transport is flexible, and can include MESH, depending on the capabilities of the DSCROs. The DSCROs have already been provided with the dataset schema required and the pseudonymisation salt. TPP and EMIS are the only data processors being used by NHS England for their Coronavirus (COVID-19) research platform, which used the OpenSAFELY analytics software. EMIS subcontract Amazon Web Services as a processor to host the EMIS patient data on it's server - therefore they are also added as a processor to this agreement.

Other NHS Digital Datasets

Datasets supplied under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L will be converted from their original salt key into the TPP and EMIS salt key through a mapping table that is provided by the DSCRO. The data is then sent to TPP and EMIS. When the datasets are converted into the TPP and EMIS salt, they are considered as confidential and must abide by the terms of this agreement.

External Datasets

The Secretary of State for Health issued NHS England/Improvement a notice under the Health Service (Control of Patient Information) Regulations 2002 3(4) which enabled NHS England to collect the data required from GP practices directly from their EHR vendor. All information governance for this urgent project is handled by NHS England. The Data Protection Impact Assessment details data flows and access, approves linking pseudonymised and de-identified GP data to outcomes data from the new NHS England and NHSX data store and other sources such as but not exclusive to: COVID–19 Patient Notification System (CPNS) deaths data; Intensive Care National Audit & Research Centre (ICNARC), Intensive Treatment Unit (ITU) admissions data; Second Generation Surveillance System (SGSS), testing data; Emergency Care Data Set/A&E patient-level data; Office of National Statistics death data.

The data flow is as follows:

High cost drugs (HCDs) matched by the DSCRO against TPP pseudonyms are only sent to TPP, and the HCDs matched by the DSCRO to EMIS pseudonyms are only sent to EMIS. Once inside TPP or EMIS, respectively, this data stays there.

In effect, there are two instances of OpenSAFELY: OpenSAFELY-EMIS , and OpenSAFELY-TPP. These are separate and remain so; TPP only have the TPP matched data and EMIS only the EMIS matched data.

Technically, the pseudonymised data ONLY resides inside the infrastructure/systems of TPP (or EMIS). TPP holds this on a local server (EMIS uses Amazon Web Services).

AWS receives the data from EMIS and it receives the data (HCD) from NHS Digital via EMIS also. It is also the place where the analysts carry out the analytics processing as part of OpenSAFELY-EMIS.

The OpenSAFELY analytics software is designed to protect patient privacy: the pseudonymised and de-identified patient data (and any data linked from external data providers) is processed into increasingly less disclosive tables (or “levels”), while preserving all the required detail in the data for research analysis. These Level 2, 3, and 4 data do not leave the environment of TPP (or EMIS).

Pseudonymised data from external databases (or data providers), such as HCDs from NHS Digital, once inside either OpenSAFELY-TPP (or OpenSAFELY-EMIS), does not leave the environment of TPP (or EMIS), except as aggregated and anonymous outcomes data after level 4 controls (such as small number suppression) are applied.

When reference is made to “OpenSAFELY-TPP” (or “OpenSAFELY-EMIS”), this is describing the level 2, 3 and 4 pseudonymised and de-identified data/database inside TPP (or EMIS) and the combined set of open-source analytics tools, code and codelists that are used by researchers to study this pseudonymised data.

These tools, code, codelists of OpenSAFELY, when run against (i.e. processing) the pseudonymised and de-identified EHR data, need to be downloaded to the environments of TPP (or EMIS) before they can be executed; this is initiated by a restricted group of researchers with approved access controls.

This below describes how the data available is managed to maintain patient privacy at different levels; the design is purposeful to support rapid research studies whilst keeping the data as minimally disclosive as possible. Once controls are applied to level 4 data, the aggregated study results are made openly available, such as in research papers and short data reports.

LEVEL 1:

Data type held: Identifiable patient data of EMIS and TPP

Where data is held: Held within EMIS and TPP

Controls applied: Under control of GP data controller restrictions eg. smart card access / role based access, with contracts with appropriate data processors, namely EMIS and TPP.

Accessed by: GP clinical staff for direct care.

Restricted access to data processor staff in EMIS and TPP respectively (for de-identification/pseudonymisation to create Level 2 data), working within their existing GPSoC / GPITF infrastructure.

LEVEL 2:

Data type held: Pseudonymised and de-identified event level coded data only. Linkage via pseudonym to similarly pseudonymised and de-identified data from external data providers

Where data is held: OpenSAFELY-EMIS and OpenSAFELY-TPP. OpenSAFELY is a suite of analytic software that is deployed inside the existing GPSoC / GPITF infrastructure of EMIS and TPP OpenSAFELY to run studies on the data made available.

Controls applied: Pseudonymisation and de-identification as per the DPIA. Only coded data is included (plus any associated numerical information). The following codes have been restricted from the dataset:

codes pertaining to gender related issues (such as reassignment), codes pertaining to treatment for assisted fertility (such as IVF), codes pertaining to treatment associated with termination of pregnancy, and codes pertaining/related to sexuality and sexual activity.

Researchers access via secure encrypted link

Whilst accessing OpenSAFELY, internet access on OpenSAFELY is restricted to GitHub; research study code and statistical modelling code are developed in GitHub. Once code is validated on test data, it is downloaded onto OpenSAFELY-EMIS or OpenSAFELY-TPP. Once the code is validated on test data, it is run against the pseudonymised and de-identified data. For the avoidance of doubt, the test data is all synthetic and created from OpenSAFELY analytics software code (no patient data is used to generate this), simply as data to test the statistical models on.

Accessed by: Researchers* who hold honorary contracts with NHS England and have signed Data Access Agreements to relevant access level. Currently researchers are from the University of Oxford Datalab team and the EHR Group of London School of Hygiene and Tropical Medicine (who work for the PI's of OpenSAFELY).

LEVEL 3:

Data Type Held: Study data of 1 row per pseudonym (patient). For example - male; over 70; has a history of cardiovascular disease; has been prescribed NSAIDs on repeat prescriptions; has no history of COPD; and has been diagnosed with COVID

Where data is held: As per LEVEL 2.

Controls applied: As per LEVEL 2.

Accessed by: As per LEVEL 2.

LEVEL 4: Aggregated study results following application of statistical models. An example of a raw study result: "An example raw study result: people on a blood pressure tablet have 1.4 times higher chance of being admitted to ITU with Covid-19", or "people with asthma are no more likely to be admitted to ITU with Covid-19 than anybody else"

Where data is held: As per LEVEL 2 and 3

Controls Applied: As per LEVEL 2 and 3. Also, study researchers review the aggregated study results for inconsistent outputs and apply both computational and human small number suppression to result cells before release outside of OpenSAFELY-EMIS or OpenSafely-TPP.

It is important to remember that the tools, code and codelists for the OpenSAFELY analytics software are made available as open-source on GitHub. The processing of the patient data occurs inside the TPP and EMIS EHR systems.

There are therefore only 2 dataflows of the data from NHS Digital that the DSCRO provides under this agreement - one to OpenSAFELY-TPP only, one to OpenSAFELY-EMIS only.

All data that carries any privacy risk (even a theoretical risk, and even when pseudonymised) remains within the secure data centre of the EHR vendor, where it already resides. This also means that all activity is logged for independent review. All processing takes place in the same secure data centre, where the patients’ electronic records were already stored. The only information to ever leave the data centre is summary tables (with low numbers suppressed) from statistical models. Within the data centre, all pseudonymised data is stored in a tiered system of increasingly less disclosive data stores tailored to each analysis. All underlying software and research code is open to review for security profiling, scientific evaluation, and to re-use as open source tools improving science across the community. Overall this approach is therefore highly secure, and supports high quality science: in contrast to working on intermittent “data extracts”, this approach also ensures that the statistical models run across up-to-date records, which is vital during a global health emergency.

Approximately 24m patient (circa 17m adults) identifiers will be given to the DSCRO’s to match against local flow high cost drug data. DSCROs will share the high cost drugs data with the electronic health record (EHR) vendors who are acting as data processors for NHS England.

The approach to privacy and security exceeds standards for many other current EHR analysis projects. SQL (Structured Query Language - commands to extract data from a database) query access to the “event-level” data (level 2), which would otherwise present the highest theoretical privacy risk is severely restricted. NHS England then abstract the key clinical features of each patient for each analysis into a “feature store” for statistical analysis (level 3): this summary data is perfectly matched to the needs of each project, but substantially less vulnerable to re-identification attacks; it is nonetheless still managed to the highest privacy standards, as if it were security-critical event-level data. All access to the data on OpenSAFELY is over highly secure VPN for a very small number of highly trusted, named and experienced analysts whose activity is all fully logged. By building the analytics software inside the originating EHR vendors’ data centre, NHS England/OpenSafely completely avoid transporting large raw primary care datasets which would otherwise present a substantial privacy risk, even when pseudonymised.

Data in OpenSAFELY-EMIS and OpenSAFELY-TPP has both technical and organisational controls to make it de-identified; after pseudonymisation at source, it is de-identified (see below), and researchers have restricted access – they cannot access the event level data, and only a restricted group have contractual permissions to access minimally disclosive data e.g. patient 1, diabetes (y/n), ), covid -19 death (y/n). This undergoes statistical analysis and only aggregated outputs with small number suppression (including human and computer review) are published externally.

De-identification by:

Removal of intentional identifiers: NHS numbers, old format NHS Numbers, all hospital numbers, personal unique codes, unique pupil numbers (UPN), national insurance numbers, all other localised identification numbers, GMC (General Medical Council) numbers, NMC (Nursing Midwifery Council) numbers, GP national codes, prescribing authority identifiers, all other professional body identifiers, Organisation Data Service codes, Workgroup codes, Site codes, all usernames.

· Removal of associational identifiers: Mobile phone numbers, email addresses, telephone numbers, hardware and software unique identifiers, IP addresses.

· Removal of transactional unique identifiers: all unique booking reference numbers for appointments, contacts and referrals.

· Removal of functional unique identifiers: Titles, forenames, middle names, surnames, full dates of birth, full dates of death, house name, house number, street, full postcode.

· Removal of narrative text data: All narrative text on patient records is removed. In line with other UK primary care research database permissions, the dosage and quantity fields on prescribed medication are retained, but any script notes are removed.

· Removal of additional unstructured context: scanned images, medical drawings, letters, and all other record attachments.

· Derived data items and removal of exact original values: date of birth (MM/YYYY), partial postcodes at sector level, indices of multiple deprivation, the rurality-urban classification, geographic super-output area codes at each super output area level. Note – for organisations, the only geographic indicators stored are the lower super output areas and / or middle-level super output area code and the Local Authority code.

The data is not permitted to be re-identified.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

A further detailed report on the outputs of the data can also be found here - https://wellcomeopenresearch.org/articles/6-360

Expected measurable benefits

To determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning.

Rapidly assess specific hypotheses around treatment or prevention as they arise.

Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need.

Measure and mitigate the indirect health impacts of Covid-19

Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions).

Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid.

In addition, with regard to “high cost drugs”, NHS England will be able to deliver specific analysis on various medicines and it is possible that the analysis will identify new treatment targets or identify currently unknown risks to patients on these medications. An analytical protocol has been drafted to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes amongst adults in England.

Another example is that “high-cost drugs” data can be used in studies on other medications prescribed by GPs to adjust for potential “confounders” and improve the assertions that can already be made using OpenSAFELY. For example, NHS England have assessed the relationship between non-steroidal anti-inflammatories (NSAIDs), such as ibuprofen, and negative COVID outcomes in people with rheumatoid arthritis (preprint submitted and expected to be available online within 48hours). NSAIDs are the mainstay of treatment in rheumatoid arthritis however in more severe forms of the disease “high-cost drugs” like adalimumab are also used. In the current study NHS England are not able to accurately measure disease severity which may give misleading results, or assess any positive or negative confounding effects of such high-cost drugs.

Another important analysis NHS England can conduct rapidly using the “high cost drugs” data relates to shielding. The UK government shielding guidance on people who are clinically extremely vulnerable from COVID-19 explicitly required people who are taking treatments that affect the immune response to shield since the outbreak of the pandemic. Many of these medications are contained in the “high-cost drugs” dataset and using this data in OpenSAFELY-EMIS and OpenSAFELY-TPP, NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of additional waves.

Failure to obtain sufficient data could significantly hamper the national COVID pandemic planning and response and adversely affect the preparedness for additional waves.

Benefits reported so far

NHS England has used OpenSafely for informing policy on shielding and vaccine prioritisation; they have added substantially to the evidence base for how several drugs, like hydroxychloroquine and inhaled corticosteroids are associated with COVID-19; and work on vaccine uptake has highlighted the large discrepancies in coverage between different ethnicities and socioeconomic groups. This impact will continue throughout the pandemic, for example with work on vaccine efficacy and long COVID follow-up.

The OpenSAFELY platform has given the power to quickly respond to emerging clinical population health and policy challenges with precise data and open methods.

Further details of benefits obtained through the processing of this data can be found here https://www.medrxiv.org/content/10.1101/2021.09.03.21262888v1

Datasets on the latest version

Legal basis for provision: CV19: Regulation 3 (4) of the Health Service (Control of Patient Information) Regulations 2002; Health and Social Care Act 2012 - s261(5)(d)

Datasets approved under DARS-NIC-397618-T8L8Z-v6.2
DatasetType of dataSensitivity FrequencyConfidential data
Community-Local Provider Flows Identifiable Sensitive One-Off Statutory exemption to flow confidential data without consent

Files released

Files released counts only files released externally by DARS. Access granted in NHS England's own systems, such as its Secure Data Environment, is not included.

No files recorded as released under this agreement.

Version history

The register lists each renewal of this agreement as a separate row. This site has 7 versions.

DARS-NIC-397618-T8L8Z-v6.2 1 November 2022 to 30 April 2023
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

What changed from DARS-NIC-397618-T8L8Z-v5.3

Text removed is struck through; text added is underlined. Unchanged paragraphs are summarised rather than repeated.

Fields changed from DARS-NIC-397618-T8L8Z-v5.3
FieldWasBecame
Start date2022-10-052022-11-01
End date2022-10-312023-04-30

Unchanged: Objective for processing, Processing activities, Expected output, Expected measurable benefits, Benefits reported.

DARS-NIC-397618-T8L8Z-v5.3 5 October 2022 to 31 October 2022
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

What changed from DARS-NIC-397618-T8L8Z-v4.2

Text removed is struck through; text added is underlined. Unchanged paragraphs are summarised rather than repeated.

Fields changed from DARS-NIC-397618-T8L8Z-v4.2
FieldWasBecame
Start date2022-07-142022-10-05

Objective for processing

[38 paragraphs unchanged] NHS North of England Commissioning Support Unit NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO). North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data. NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO). North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data. [4 paragraphs unchanged]

Unchanged: Processing activities, Expected output, Expected measurable benefits, Benefits reported.

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data). All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/ and approved projects are available here - https://approved-projects.opensafely.pages.dev/approved-projects/

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data has been pseudonymized at source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold honorary contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

As both TPP and EMIS would have the technical ability to re-identify the data through the use of mapping tables, the data is considered as confidential and requires COPI to address the common law duty of confidentiality.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of February 2022, 9 developers (with NHS England honorary contracts) have access to the level 2 or level 3 environment for development and maintenance purposes only. The Level 2 environment is where the event level pseudonymised data is held. The Level 3 environment is where the specific analysis’ cohort data is held.

Researchers now only access the Level 4 environment where the aggregated results of their studies are held. The Level 4 environment is where researchers review the results and apply disclosure controls before requesting the data to be released. Two independent output-checkers review the results and only release them if there are no disclosure concerns. 72 researchers have access to the Level 4 environment; the 9 developers also have access to this Level 4 environment

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

Community - Local Provider Flow

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available. A draft report has also been produced on the use of the data so far.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a future waves.

Other NHS Digital Datasets

NHS England will also use datasets it receives from NHS Digital under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L in the OpenSafely platform to further enhance the data. These dataset include:

- Secondary Uses Services Data (SUS+)

- Second generation surveillance system (SGSS)

- Civil Registration Data - Deaths

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic. As COVID-19 continually is evolving, this is a continuous activity.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider network of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England has an established Oversight Board. The Oversight Board has had 4 meetings and their agenda, documents and meetings notes are publicly available: https://www.opensafely.org/governance/

Amendment to change data frequency

The current dataset in OpenSAFELY-TPP is a one off collection covering submissions from FY 2018/19 and FY 2019/20, and there is no process in place to routinely update the information available in the High Cost Drug dataset. Whilst this is very useful for assessing events and outcomes early in the COVID-19 pandemic, a routine update of the data is needed to assess current high-priority questions and future important questions. For example, a routine update to this data will allow assessment of COVID-19 vaccine effectiveness in people using high-cost medicines or indeed people with a recorded diagnosis likely to be treated with a High Cost Drug. Therefore the controller is requesting the data frequency is changed to adhoc. This will allow regular (likely to be monthly) refreshes of the data that will better inform the changing medications required to treat COVID-19 as the virus continually evolves and effects patients differently.

NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO). North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data.

Legal Basis for Processing Data

Data accessed under this Agreement will be processed in accordance with GDPR Article 6(1)(e) (processing is necessary for the performance of a task in the public interest or in the exercise of official authority vested in the controller) and Article 9(2)(i) (processing is necessary for reasons of public interest in the area of public health, such as protecting against serious cross-border threats to health or ensuring high standards of quality and safety of health care and of medicinal products or medical devices, on the basis of Union or Member State law which provides for suitable and specific measures to safeguard the rights and freedoms of the data subject, in particular professional secrecy).

Common Law Duty of Confidentiality

Although the data is pseudonymised when it is disseminated, as TPP and EMIS are in receipt of the SALT key used for this project, the data is considered as confidential. NHS England are relying on Reg 3 (3) of the COPI Notice (2002) to allow the dissemination of confidential patient information without consent.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

A further detailed report on the outputs of the data can also be found here - https://wellcomeopenresearch.org/articles/6-360

Benefits reported

NHS England has used OpenSafely for informing policy on shielding and vaccine prioritisation; they have added substantially to the evidence base for how several drugs, like hydroxychloroquine and inhaled corticosteroids are associated with COVID-19; and work on vaccine uptake has highlighted the large discrepancies in coverage between different ethnicities and socioeconomic groups. This impact will continue throughout the pandemic, for example with work on vaccine efficacy and long COVID follow-up.

The OpenSAFELY platform has given the power to quickly respond to emerging clinical population health and policy challenges with precise data and open methods.

Further details of benefits obtained through the processing of this data can be found here https://www.medrxiv.org/content/10.1101/2021.09.03.21262888v1

DARS-NIC-397618-T8L8Z-v4.2 14 July 2022 to 31 October 2022
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

What changed from DARS-NIC-397618-T8L8Z-v3.2

Text removed is struck through; text added is underlined. Unchanged paragraphs are summarised rather than repeated.

Fields changed from DARS-NIC-397618-T8L8Z-v3.2
FieldWasBecame
Start date2022-04-012022-07-14
End date2022-06-302022-10-31

Unchanged: Objective for processing, Processing activities, Expected output, Expected measurable benefits, Benefits reported.

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data). All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/ and approved projects are available here - https://approved-projects.opensafely.pages.dev/approved-projects/

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data has been pseudonymized at source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold honorary contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

As both TPP and EMIS would have the technical ability to re-identify the data through the use of mapping tables, the data is considered as confidential and requires COPI to address the common law duty of confidentiality.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of February 2022, 9 developers (with NHS England honorary contracts) have access to the level 2 or level 3 environment for development and maintenance purposes only. The Level 2 environment is where the event level pseudonymised data is held. The Level 3 environment is where the specific analysis’ cohort data is held.

Researchers now only access the Level 4 environment where the aggregated results of their studies are held. The Level 4 environment is where researchers review the results and apply disclosure controls before requesting the data to be released. Two independent output-checkers review the results and only release them if there are no disclosure concerns. 72 researchers have access to the Level 4 environment; the 9 developers also have access to this Level 4 environment

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

Community - Local Provider Flow

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available. A draft report has also been produced on the use of the data so far.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a future waves.

Other NHS Digital Datasets

NHS England will also use datasets it receives from NHS Digital under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L in the OpenSafely platform to further enhance the data. These dataset include:

- Secondary Uses Services Data (SUS+)

- Second generation surveillance system (SGSS)

- Civil Registration Data - Deaths

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic. As COVID-19 continually is evolving, this is a continuous activity.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider network of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England has an established Oversight Board. The Oversight Board has had 4 meetings and their agenda, documents and meetings notes are publicly available: https://www.opensafely.org/governance/

Amendment to change data frequency

The current dataset in OpenSAFELY-TPP is a one off collection covering submissions from FY 2018/19 and FY 2019/20, and there is no process in place to routinely update the information available in the High Cost Drug dataset. Whilst this is very useful for assessing events and outcomes early in the COVID-19 pandemic, a routine update of the data is needed to assess current high-priority questions and future important questions. For example, a routine update to this data will allow assessment of COVID-19 vaccine effectiveness in people using high-cost medicines or indeed people with a recorded diagnosis likely to be treated with a High Cost Drug. Therefore the controller is requesting the data frequency is changed to adhoc. This will allow regular (likely to be monthly) refreshes of the data that will better inform the changing medications required to treat COVID-19 as the virus continually evolves and effects patients differently.

NHS North of England Commissioning Support Unit

NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO).

North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data.

Legal Basis for Processing Data

Data accessed under this Agreement will be processed in accordance with GDPR Article 6(1)(e) (processing is necessary for the performance of a task in the public interest or in the exercise of official authority vested in the controller) and Article 9(2)(i) (processing is necessary for reasons of public interest in the area of public health, such as protecting against serious cross-border threats to health or ensuring high standards of quality and safety of health care and of medicinal products or medical devices, on the basis of Union or Member State law which provides for suitable and specific measures to safeguard the rights and freedoms of the data subject, in particular professional secrecy).

Common Law Duty of Confidentiality

Although the data is pseudonymised when it is disseminated, as TPP and EMIS are in receipt of the SALT key used for this project, the data is considered as confidential. NHS England are relying on Reg 3 (3) of the COPI Notice (2002) to allow the dissemination of confidential patient information without consent.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

A further detailed report on the outputs of the data can also be found here - https://wellcomeopenresearch.org/articles/6-360

Benefits reported

NHS England has used OpenSafely for informing policy on shielding and vaccine prioritisation; they have added substantially to the evidence base for how several drugs, like hydroxychloroquine and inhaled corticosteroids are associated with COVID-19; and work on vaccine uptake has highlighted the large discrepancies in coverage between different ethnicities and socioeconomic groups. This impact will continue throughout the pandemic, for example with work on vaccine efficacy and long COVID follow-up.

The OpenSAFELY platform has given the power to quickly respond to emerging clinical population health and policy challenges with precise data and open methods.

Further details of benefits obtained through the processing of this data can be found here https://www.medrxiv.org/content/10.1101/2021.09.03.21262888v1

DARS-NIC-397618-T8L8Z-v3.2 1 April 2022 to 30 June 2022
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

What changed from DARS-NIC-397618-T8L8Z-v2.2

Text removed is struck through; text added is underlined. Unchanged paragraphs are summarised rather than repeated.

Fields changed from DARS-NIC-397618-T8L8Z-v2.2
FieldWasBecame
Start date2021-10-012022-04-01
End date2022-03-312022-06-30
Community-Local Provider Flows: type of dataAnonymised - ICO Code CompliantIdentifiable

Objective for processing

[1 paragraph unchanged] OpenSAFELY is a new suite of analytics software that is deployed inside an existing EHR system [28 words unchanged] 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data), with analyses about to begin using OpenSAFELY-EMIS and OpenSAFELY-TPP. data). All the analytic software is open for security review, scientific review, and [78 words unchanged] delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/. https://opensafely.org/outputs/ and approved projects are available here - https://approved-projects.opensafely.pages.dev/approved-projects/ [1 paragraph unchanged] Patient data have has been pseudonymized as at source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). [22 words unchanged] connection, restricted to a small group of researchers. The researchers, who hold honorary contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database [21 words unchanged] anonymization of results such as statistical disclosure control for low cell counts. [2 paragraphs unchanged] As both TPP and EMIS would have the technical ability to re-identify the data through the use of mapping tables, the data is considered as confidential and requires COPI to address the common law duty of confidentiality. [1 paragraph unchanged] As of writing, 15 researchers are level 2 and 3 approved (accessing OpenSafely-EMIS and OpenSafely-TPP to initiate database queries and statistical models, the code for which are openly available on online on GitHub - a leading software development platform which has tools available for analysts and developers); 11 researchers are level 4 approved (they can only access and review the outputs of the statistical models ie the raw study results). In this tiered model the data between Level 2, 3 and 4 is increasingly less disclosive. As of February 2022, 9 developers (with NHS England honorary contracts) have access to the level 2 or level 3 environment for development and maintenance purposes only. The Level 2 environment is where the event level pseudonymised data is held. The Level 3 environment is where the specific analysis’ cohort data is held. Researchers now only access the Level 4 environment where the aggregated results of their studies are held. The Level 4 environment is where researchers review the results and apply disclosure controls before requesting the data to be released. Two independent output-checkers review the results and only release them if there are no disclosure concerns. 72 researchers have access to the Level 4 environment; the 9 developers also have access to this Level 4 environment [3 paragraphs unchanged] Community - Local Provider Flow [2 paragraphs unchanged] A drafted protocol has been created to support examination of the association between the [23 words unchanged] start the analysis immediately if the high-cost drugs data is made available. A draft report has also been produced on the use of the data so far. [1 paragraph unchanged] High cost drug data can also be used to answer questions directly [49 words unchanged] could inform important future decisions on shielding in the event of a second wave. future waves. Other NHS Digital Datasets NHS England will also use datasets it receives from NHS Digital under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L in the OpenSafely platform to further enhance the data. These dataset include: - Secondary Uses Services Data (SUS+) - Second generation surveillance system (SGSS) - Civil Registration Data - Deaths [1 paragraph unchanged] - Determine which people are at highest risk of hospital admission, ventilation, [47 words unchanged] need to be in the high-risk group for self-seclusion during the pandemic. As COVID-19 continually is evolving, this is a continuous activity. [7 paragraphs unchanged] Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s and NHSX’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server. The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider networks network of public health doctors and scientists advising the government, such as SAGE [15 words unchanged] Advisor, and have drawn on such networks and individuals to inform analyses. NHS England and NHSX is currently working on a model to establish an Interim Oversight Board, with a view to a permanent and formalised independent Oversight Board and user group, to advise on the research pipeline and development roadmap, as well as holding the OpenSAFELY collaborative (TPP, EMIS, University of Oxford DataLab, EHR group of London School of Hygiene and Tropical Medicine, NHS England) to account on the ethical and efficient use of patient data. Details of this can be made available as soon as plans have been finalised. NHS England has an established Oversight Board. The Oversight Board has had 4 meetings and their agenda, documents and meetings notes are publicly available: https://www.opensafely.org/governance/ Amendment to change data frequency The current dataset in OpenSAFELY-TPP is a one off collection covering submissions from FY 2018/19 and FY 2019/20, and there is no process in place to routinely update the information available in the High Cost Drug dataset. Whilst this is very useful for assessing events and outcomes early in the COVID-19 pandemic, a routine update of the data is needed to assess current high-priority questions and future important questions. For example, a routine update to this data will allow assessment of COVID-19 vaccine effectiveness in people using high-cost medicines or indeed people with a recorded diagnosis likely to be treated with a High Cost Drug. Therefore the controller is requesting the data frequency is changed to adhoc. This will allow regular (likely to be monthly) refreshes of the data that will better inform the changing medications required to treat COVID-19 as the virus continually evolves and effects patients differently. NHS North of England Commissioning Support Unit NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO). North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data. Legal Basis for Processing Data Data accessed under this Agreement will be processed in accordance with GDPR Article 6(1)(e) (processing is necessary for the performance of a task in the public interest or in the exercise of official authority vested in the controller) and Article 9(2)(i) (processing is necessary for reasons of public interest in the area of public health, such as protecting against serious cross-border threats to health or ensuring high standards of quality and safety of health care and of medicinal products or medical devices, on the basis of Union or Member State law which provides for suitable and specific measures to safeguard the rights and freedoms of the data subject, in particular professional secrecy). Common Law Duty of Confidentiality Although the data is pseudonymised when it is disseminated, as TPP and EMIS are in receipt of the SALT key used for this project, the data is considered as confidential. NHS England are relying on Reg 3 (3) of the COPI Notice (2002) to allow the dissemination of confidential patient information without consent.

Processing activities

[2 paragraphs unchanged] DSCROs will share pseudonymised high cost drugs data directly with the electronic health record (EHR) vendors, TPP and EMIS respectively, who are acting as data processor for NHS England . Message transport is flexible, and can include MESH, depending on the capabilities of the DSCROs. The DSCROs have already been provided with the dataset schema required and the pseudonymisation salt. TPP and EMIS are the only data processors being used by NHSE England for their Coronavirus (COVID-19) research platform, which used the OpenSAFELY analytics software. EMIS subcontract Amazon Web Services as a processor to host the EMIS patient data on it's server - therefore they are also added as a processor to this agreement. Community - Local Provider Flows The Secretary of State for Health issued NHS England/Improvement a notice under the Health Service (Control of Patient Information) Regulations 2002 3(4) which enabled NHS England to collect the data required from GP practices directly from their EHR vendor. All information governance for this urgent project is handled by NHS England. The Data Protection Impact Assessment that was drafted approving data flows and access, approves linking pseudonymised and de-identified GP data to outcomes data from the new NHS England and NHSX data store and other sources, such as but not exclusive to: COVID–19 Patient Notification System (CPNS) deaths data; Intensive Care National Audit & Research Centre (ICNARC), Intensive Treatment Unit (ITU) admissions data; Second Generation Surveillance System (SGSS) Public Health England test data; Emergency Care Data Set/A&E patient-level data; Office of National Statistics death data. DSCROs (via the CSU) will share pseudonymised high cost drugs data directly with the electronic health record (EHR) vendors, TPP, NHS North of England Commissioning Support Unit and EMIS respectively, who are acting as data processor for NHS England. Message transport is flexible, and can include MESH, depending on the capabilities of the DSCROs. The DSCROs have already been provided with the dataset schema required and the pseudonymisation salt. TPP and EMIS are the only data processors being used by NHS England for their Coronavirus (COVID-19) research platform, which used the OpenSAFELY analytics software. EMIS subcontract Amazon Web Services as a processor to host the EMIS patient data on it's server - therefore they are also added as a processor to this agreement. Other NHS Digital Datasets Datasets supplied under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L will be converted from their original salt key into the TPP and EMIS salt key through a mapping table that is provided by the DSCRO. The data is then sent to TPP and EMIS. When the datasets are converted into the TPP and EMIS salt, they are considered as confidential and must abide by the terms of this agreement. External Datasets The Secretary of State for Health issued NHS England/Improvement a notice under the Health Service (Control of Patient Information) Regulations 2002 3(4) which enabled NHS England to collect the data required from GP practices directly from their EHR vendor. All information governance for this urgent project is handled by NHS England. The Data Protection Impact Assessment details data flows and access, approves linking pseudonymised and de-identified GP data to outcomes data from the new NHS England and NHSX data store and other sources such as but not exclusive to: COVID–19 Patient Notification System (CPNS) deaths data; Intensive Care National Audit & Research Centre (ICNARC), Intensive Treatment Unit (ITU) admissions data; Second Generation Surveillance System (SGSS), testing data; Emergency Care Data Set/A&E patient-level data; Office of National Statistics death data. [9 paragraphs unchanged] This table below describes how the data available is managed to maintain patient privacy at [33 words unchanged] made openly available, such as in research papers and short data reports. [23 paragraphs unchanged] There are therefore only 2 dataflows of the data from NHS Digital that the DSCRO provides under this agreement - one to OpenSAFELY-TPP only, one to OpenSAFELY-EMIS only. The only data being requested under this agreement is Community Local Flow Provider Data. Further amendments/iterations of this Data Sharing Agreement will be submitted for approval to NHS Digital in the future should the scope of this work go outside the high cost drugs project that it currently covers. [1 paragraph unchanged] Approximately 24m patient (circa 17m adults) identifiers will be given to the [18 words unchanged] with the electronic health record (EHR) vendors who are acting as data processor processors for NHS England. [11 paragraphs unchanged]

Expected output

[9 paragraphs unchanged] A further detailed report on the outputs of the data can also be found here - https://wellcomeopenresearch.org/articles/6-360

Expected measurable benefits

[6 paragraphs unchanged] In addition, with regard to “high cost drugs”, NHS England will be [48 words unchanged] treat immune mediated inflammatory diseases and severe COVID-19 outcomes amongst adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available. England. [1 paragraph unchanged] Another important analysis NHS England can conduct rapidly using the “high cost [94 words unchanged] information could inform important future decisions on shielding in the event of a second wave. additional waves. Failure to obtain sufficient data could significantly hamper the national COVID pandemic planning and response and adversely affect the preparedness for a potential second wave. additional waves.

Benefits reported

No yielded benefits have yet been obtained, as continued analysis work is still ongoing for this project. NHS England has used OpenSafely for informing policy on shielding and vaccine prioritisation; they have added substantially to the evidence base for how several drugs, like hydroxychloroquine and inhaled corticosteroids are associated with COVID-19; and work on vaccine uptake has highlighted the large discrepancies in coverage between different ethnicities and socioeconomic groups. This impact will continue throughout the pandemic, for example with work on vaccine efficacy and long COVID follow-up. The OpenSAFELY platform has given the power to quickly respond to emerging clinical population health and policy challenges with precise data and open methods. Further details of benefits obtained through the processing of this data can be found here https://www.medrxiv.org/content/10.1101/2021.09.03.21262888v1

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data). All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/ and approved projects are available here - https://approved-projects.opensafely.pages.dev/approved-projects/

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data has been pseudonymized at source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold honorary contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

As both TPP and EMIS would have the technical ability to re-identify the data through the use of mapping tables, the data is considered as confidential and requires COPI to address the common law duty of confidentiality.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of February 2022, 9 developers (with NHS England honorary contracts) have access to the level 2 or level 3 environment for development and maintenance purposes only. The Level 2 environment is where the event level pseudonymised data is held. The Level 3 environment is where the specific analysis’ cohort data is held.

Researchers now only access the Level 4 environment where the aggregated results of their studies are held. The Level 4 environment is where researchers review the results and apply disclosure controls before requesting the data to be released. Two independent output-checkers review the results and only release them if there are no disclosure concerns. 72 researchers have access to the Level 4 environment; the 9 developers also have access to this Level 4 environment

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

Community - Local Provider Flow

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available. A draft report has also been produced on the use of the data so far.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a future waves.

Other NHS Digital Datasets

NHS England will also use datasets it receives from NHS Digital under DARS-NIC-139035-X4B7K and DARS-NIC-384608-C9B4L in the OpenSafely platform to further enhance the data. These dataset include:

- Secondary Uses Services Data (SUS+)

- Second generation surveillance system (SGSS)

- Civil Registration Data - Deaths

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic. As COVID-19 continually is evolving, this is a continuous activity.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider network of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England has an established Oversight Board. The Oversight Board has had 4 meetings and their agenda, documents and meetings notes are publicly available: https://www.opensafely.org/governance/

Amendment to change data frequency

The current dataset in OpenSAFELY-TPP is a one off collection covering submissions from FY 2018/19 and FY 2019/20, and there is no process in place to routinely update the information available in the High Cost Drug dataset. Whilst this is very useful for assessing events and outcomes early in the COVID-19 pandemic, a routine update of the data is needed to assess current high-priority questions and future important questions. For example, a routine update to this data will allow assessment of COVID-19 vaccine effectiveness in people using high-cost medicines or indeed people with a recorded diagnosis likely to be treated with a High Cost Drug. Therefore the controller is requesting the data frequency is changed to adhoc. This will allow regular (likely to be monthly) refreshes of the data that will better inform the changing medications required to treat COVID-19 as the virus continually evolves and effects patients differently.

NHS North of England Commissioning Support Unit

NHS North of England Commissioning Support Unit (CSU) host the North of England Data Services for Commissioners Regional Officer (DSCRO).

North of England CSU is only being utilised for the dissemination of the data as this is processed through the CSU servers. The CSU does no further processing on the data.

Legal Basis for Processing Data

Data accessed under this Agreement will be processed in accordance with GDPR Article 6(1)(e) (processing is necessary for the performance of a task in the public interest or in the exercise of official authority vested in the controller) and Article 9(2)(i) (processing is necessary for reasons of public interest in the area of public health, such as protecting against serious cross-border threats to health or ensuring high standards of quality and safety of health care and of medicinal products or medical devices, on the basis of Union or Member State law which provides for suitable and specific measures to safeguard the rights and freedoms of the data subject, in particular professional secrecy).

Common Law Duty of Confidentiality

Although the data is pseudonymised when it is disseminated, as TPP and EMIS are in receipt of the SALT key used for this project, the data is considered as confidential. NHS England are relying on Reg 3 (3) of the COPI Notice (2002) to allow the dissemination of confidential patient information without consent.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

A further detailed report on the outputs of the data can also be found here - https://wellcomeopenresearch.org/articles/6-360

Benefits reported

NHS England has used OpenSafely for informing policy on shielding and vaccine prioritisation; they have added substantially to the evidence base for how several drugs, like hydroxychloroquine and inhaled corticosteroids are associated with COVID-19; and work on vaccine uptake has highlighted the large discrepancies in coverage between different ethnicities and socioeconomic groups. This impact will continue throughout the pandemic, for example with work on vaccine efficacy and long COVID follow-up.

The OpenSAFELY platform has given the power to quickly respond to emerging clinical population health and policy challenges with precise data and open methods.

Further details of benefits obtained through the processing of this data can be found here https://www.medrxiv.org/content/10.1101/2021.09.03.21262888v1

DARS-NIC-397618-T8L8Z-v2.2 1 October 2021 to 31 March 2022
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

What changed from DARS-NIC-397618-T8L8Z-v1.2

Text removed is struck through; text added is underlined. Unchanged paragraphs are summarised rather than repeated.

Fields changed from DARS-NIC-397618-T8L8Z-v1.2
FieldWasBecame
Start date2021-03-312021-10-01
End date2021-09-302022-03-31

Unchanged: Objective for processing, Processing activities, Expected output, Expected measurable benefits, Benefits reported.

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a new suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data), with analyses about to begin using OpenSAFELY-EMIS and OpenSAFELY-TPP. All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/.

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data have been pseudonymized as source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of writing, 15 researchers are level 2 and 3 approved (accessing OpenSafely-EMIS and OpenSafely-TPP to initiate database queries and statistical models, the code for which are openly available on online on GitHub - a leading software development platform which has tools available for analysts and developers); 11 researchers are level 4 approved (they can only access and review the outputs of the statistical models ie the raw study results). In this tiered model the data between Level 2, 3 and 4 is increasingly less disclosive.

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A drafted protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a second wave.

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s and NHSX’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider networks of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England and NHSX is currently working on a model to establish an Interim Oversight Board, with a view to a permanent and formalised independent Oversight Board and user group, to advise on the research pipeline and development roadmap, as well as holding the OpenSAFELY collaborative (TPP, EMIS, University of Oxford DataLab, EHR group of London School of Hygiene and Tropical Medicine, NHS England) to account on the ethical and efficient use of patient data. Details of this can be made available as soon as plans have been finalised.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

Benefits reported

No yielded benefits have yet been obtained, as continued analysis work is still ongoing for this project.

DARS-NIC-397618-T8L8Z-v1.2 31 March 2021 to 30 September 2021
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

What changed from DARS-NIC-397618-T8L8Z-v0.2

Text removed is struck through; text added is underlined. Unchanged paragraphs are summarised rather than repeated.

Fields changed from DARS-NIC-397618-T8L8Z-v0.2
FieldWasBecame
Start date2020-09-152021-03-31
End date2021-03-302021-09-30

Benefits reported

Yielded Benefits is not a requirement for new applications. No yielded benefits have yet been obtained, as continued analysis work is still ongoing for this project.

Unchanged: Objective for processing, Processing activities, Expected output, Expected measurable benefits.

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a new suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data), with analyses about to begin using OpenSAFELY-EMIS and OpenSAFELY-TPP. All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/.

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data have been pseudonymized as source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of writing, 15 researchers are level 2 and 3 approved (accessing OpenSafely-EMIS and OpenSafely-TPP to initiate database queries and statistical models, the code for which are openly available on online on GitHub - a leading software development platform which has tools available for analysts and developers); 11 researchers are level 4 approved (they can only access and review the outputs of the statistical models ie the raw study results). In this tiered model the data between Level 2, 3 and 4 is increasingly less disclosive.

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A drafted protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a second wave.

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s and NHSX’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider networks of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England and NHSX is currently working on a model to establish an Interim Oversight Board, with a view to a permanent and formalised independent Oversight Board and user group, to advise on the research pipeline and development roadmap, as well as holding the OpenSAFELY collaborative (TPP, EMIS, University of Oxford DataLab, EHR group of London School of Hygiene and Tropical Medicine, NHS England) to account on the ethical and efficient use of patient data. Details of this can be made available as soon as plans have been finalised.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

Benefits reported

No yielded benefits have yet been obtained, as continued analysis work is still ongoing for this project.

DARS-NIC-397618-T8L8Z-v0.2 15 September 2020 to 30 March 2021
Title
OpenSAFELY and High Cost Drugs Linkage
Commercial
No
Sublicensing
No
Datasets
1
Files released
0

Datasets: Community-Local Provider Flows

Objective for processing

NHS England request this data to support their Coronavirus (COVID-19) research platform work (https://www.england.nhs.uk/contact-us/privacy-notice/how-we-use-your-information/covid-19-response/coronavirus-covid-19-research-platform/) which uses the OpenSAFELY secure analytics software (www.opensafely.org). NHS England is the data controller. NHS England has established honorary contracts with researchers at the DataLab at the University of Oxford and the Electronic Health Records (EHR) group at the London School of Hygiene and Tropical Medicine to assist in conducting Covid-19 relevant studies using the OpenSAFELY suite of analytic software - deployed inside existing electronic health record systems. The Phoenix Partnership (TPP) and Egton Medical Information Systems EMIS (GP electronic health record (EHR) software companies ) are the data processor listed in this agreement, under contract with NHS England. NHS England is the sole data controller; currently NHS England, TPP and EMIS are the data processors; GP Data from TPP and EMIS remains within the IT infrastructure of TPP and EMIS. There are therefore currently two examples of where the OpenSAFELY suite of analytics software are being used - OpenSafely-EMIS, and OpenSafely-TPP.

OpenSAFELY is a new suite of analytics software that is deployed inside an existing EHR system to carry out studies (using the underlying data) - created to deliver urgent results during the global COVID-19 emergency. It is now successfully delivering analyses across more than 24 million patients’ full pseudonymised primary care NHS records (TPP patient GP data), with analyses about to begin using OpenSAFELY-EMIS and OpenSAFELY-TPP. All the analytic software is open for security review, scientific review, and re-use. OpenSAFELY analytics software uses a new model for enhanced security and timely access to data: it does not transport large volumes of potentially disclosive pseudonymised patient data outside of the secure environments managed by the electronic health record software company; instead, trusted analysts can run large scale computation across near real-time pseudonymised patient records inside the data centre of the electronic health records software company. This pragmatic and secure approach has allowed the first analyses to be delivered in just five weeks from project start. Outputs are available here: https://opensafely.org/outputs/.

The GP infrastructure is accredited to the ISO 27001 information security standard and is NHS Data Security and Protection Toolkit compliant.

Patient data have been pseudonymized as source for analysis and linkage using industry standard cryptographic hashing techniques (SHA512+salt). All pseudonymized datasets transmitted for linkage onto OpenSAFELY are encrypted. Access to OpenSafely-EMIS and OpenSafely-TPP is through a virtual private network (VPN) connection, restricted to a small group of researchers. The researchers, who hold contracts with NHS England, only access OpenSafely-TPP or OpenSafely-EMIS to initiate database queries and statistical models; all database activity is logged; and only aggregate statistical outputs leave the environment following best practice for anonymization of results such as statistical disclosure control for low cell counts.

A pseudonym is generated from the NHS number using the SHA 512 cryptographic hashing algorithm, in combination with a ‘salt’. This pseudonym is used to link datasets. The salt is transferred between data sharing organisations separately in an encrypted email, and a phone call is made to provide the decryption key to unencrypt the salt. The same salt is used by TPP and EMIS; the salt will be refreshed at 6 monthly intervals. Only restricted individuals in TPP, EMIS and the external data providers are aware of the salt.

As a concrete example, TPP created an appropriate salt, which was shared by the process described above with the relevant individual in the Office of National Statistics (ONS). Both TPP and ONS applied the SHA 512 algorithm, in combination with a salt, to their NHS numbers. This creates a unique pseudonym for each NHS number which can be used to match records. The purpose of using a salt (only known to limited individuals involved in the data flow process) is to further reduce the risk of re-identifying any pseudonymised datasets through the use of brute force attacks.

There is a tiered level of restricted researcher access to the pseudonymised and de-identified data within OpenSafely-EMIS and OpenSafely-TPP providing enhanced security and privacy protections to the underlying dataset. The descriptions of these 'levels' are described in Processing Activities below. They range from Level 1 - Level 4.

As of writing, 15 researchers are level 2 and 3 approved (accessing OpenSafely-EMIS and OpenSafely-TPP to initiate database queries and statistical models, the code for which are openly available on online on GitHub - a leading software development platform which has tools available for analysts and developers); 11 researchers are level 4 approved (they can only access and review the outputs of the statistical models ie the raw study results). In this tiered model the data between Level 2, 3 and 4 is increasingly less disclosive.

For the avoidance of doubt, no researchers can access the Level 1 data (which is where the identifiable data is de-identified and hashed). The full explanation of the levels is contained in processing activities below.

With respect to the GP providers, TPP and EMIS, Level 1 refers to the source identifiable GP data which undergoes pseudonymisation and de-identification before being readied for linkage to create Level 2 data.

This approach to maintaining patient privacy has support from MedConfidential: “It (OpenSAFELY) was designed and built to promote both research and patient confidentiality at the same time, rather than suggesting they’re opposites,” says one of the (MedConfidential’s) co-founders. https://www.economist.com/science-and-technology/2020/05/14/the-pandemic-has-spawned-a-new-way-to-study-medical-records

NHS England will use OpenSafely-EMIS and OpenSafely-TPP to process community local flow provider data provided by NHS Digital (filtered and specified to provide detail on high-cost drugs) to deliver specific analysis on various medicines with the potential to identify treatment targets or identify currently unknown risks to patients on these medications.

The National Tariff High Cost Drugs List contains the High Cost Drugs which are not covered by national prices under the National Tariff Payment System. These drugs are typically used in a relatively small number of specialist centres rather than across all Trusts. Commissioners and providers are required to agree prices locally (https://www.gov.uk/government/news/high-cost-drugs).

A drafted protocol has been created to support examination of the association between the use of immunosuppression to treat immune mediated inflammatory diseases and severe COVID-19 outcomes among adults in England and NHS England are ready to start the analysis immediately if the high-cost drugs data is made available.

The purposes for processing are to identify medical conditions and medications that affect the risk or impact of Covid-19 infection on individuals; this will assist with identifying risk factors associated with poor patient outcomes as well as information to monitor and predict demand on health services.

High cost drug data can also be used to answer questions directly related to 'confounders' and those people in the UK who are shielding. NHS England can rapidly review how such specific medications are associated with COVID-19 related outcomes, such as mortality, to help inform clinical and policy decisions on shielding criteria. Although shielding restrictions have recently been relaxed, this information could inform important future decisions on shielding in the event of a second wave.

Data provided via NHS Digital will be used to:

- Determine which people are at highest risk of hospital admission, ventilation, or death, to inform 111 advice, management choices, seclusion advice, and service planning. For example, there may be certain pre-existing medical problems that put people at much higher risk of Covid-related admission or death, that have not yet been identified, and which mean new categories of people need to be in the high-risk group for self-seclusion during the pandemic.

- Rapidly assess specific hypotheses around treatment or prevention as they arise including: the possible benefits of chloroquine or antiretroviral medication for HIV; the possible hazards of ibuprofen; the possible benefits of inhaled corticosteroids; the benefits or hazards of drugs that up-regulate ACE2 receptors (such as ACE inhibitors and angiotensin receptor blockers); possible beneficial effects from the JAK inhibitor baricitinib. These can all be rapidly assessed by assessing rates of admission and death among those who have, and have not, been routinely taking such medications in primary care.

- Combine disease dynamics modelling with near-real-time hyperlocal clinical data on prevalence and population at risk, to predict local spread and service need, and (for example) to design and evaluate exit strategies from lockdown.

- Measure and mitigate the indirect health impacts of Covid-19: subject to approval NHS England can monitor the data to identify “Covid Aftershocks” and give early warning on clinical work displaced, such as cancer referrals, cardiovascular management, and vaccinations. NHS England can also help identify NHS organisations in need of additional support around delivering good care as the pandemic continues; and rapidly identify success stories from new best practice that others can learn from.

- Rapidly evaluate the impact of national interventions (and collect outcomes data for pragmatic cluster randomised trials of preventative or treatment interventions), especially on specific patient groups.

- Inform operational issues such as identifying NHS organisations in need of additional support around delivering good care on Covid, and non-Covid care as the pandemic continues; or identify the best practice others can learn from.

OVERSIGHT OF PROJECT:

Currently, given the need to rapidly prioritise the research questions that should be answered, the first wave of analyses have been decided by consensus amongst the team of OpenSAFELY researchers at the University of Oxford DataLab and the EHR group at the London School of Hygiene and Tropical Medicine. These researchers hold honorary contracts with NHS England and are operating in line with NHS England's requirements to support the response to COVID-19. The researchers discuss research protocols with the EHR vendors to ensure that the data within the EHR can be reasonably expected to answer the questions raised. A specific study protocol is written by the OpenSAFELY researchers and a Principle Investigator must give approval for the research to proceed. External researchers may provide advice on the study protocol.

Following generation of the results, a paper is drafted which is shared with appropriate charity/professional representative groups for review. The pre-publication draft is shared with NHS England’s and NHSX’s information governance team for review. Following revisions, the paper is submitted for publication in a peer-reviewed journal alongside being made openly available on a pre-print server.

The OpenSAFELY researchers have deep expertise in the use of EHR data as well as epidemiological research. They also have access to a wider networks of public health doctors and scientists advising the government, such as SAGE (Scientific Advisory Group for Emergencies), with contact with the Chief Medical Officer and Chief Scientific Advisor, and have drawn on such networks and individuals to inform analyses.

NHS England and NHSX is currently working on a model to establish an Interim Oversight Board, with a view to a permanent and formalised independent Oversight Board and user group, to advise on the research pipeline and development roadmap, as well as holding the OpenSAFELY collaborative (TPP, EMIS, University of Oxford DataLab, EHR group of London School of Hygiene and Tropical Medicine, NHS England) to account on the ethical and efficient use of patient data. Details of this can be made available as soon as plans have been finalised.

Expected output

Reports commissioned by Scientific Advisory Group on Emergencies (SAGE), or Department of Health Chief Medical Officer (CMO) / Chief Scientific Advisor (CSA), Joint Biosecurity Centre, or requests that come through the NHS England single point of access that are relevant to the COVID-19 public health emergency.

Work is ongoing to onboard other researcher organisations to use the OpenSAFELY analytics software

Analyses, including supplements, will be openly published online, often initially to a pre-print journal, before submission to a peer review journal and be made available on the OpenSAFELY website as soon as possible (subject to journal restrictions on open access timelines): https://opensafely.org/outputs/

Abstracts/summaries may be used in conferences and for presentations.

As described above, all data outputs that leave OpenSAFELY-EMIS or OpenSAFELY-TPP will be aggregated and anonymised with small number suppression. There will be no restrictions on sharing such outputs which will also be shared with policy makers, the wider research community as well as the public.

The OpenSAFELY analytics software and associated tools and codelists are all open source and available for re-use (https://opensafely.org/code/); derived data that is published are not subject to any intellectual property.

All published outputs will only contain aggregated results with small number suppression applied.

An article has been published already about the use of the OpenSAFELY analytics software in regards to how it was used to characterise factors associated with COVID-19 death in 17 million patients.

https://www.nature.com/articles/s41586-020-2521-4

Benefits reported

Yielded Benefits is not a requirement for new applications.

Register history

When this agreement appeared in, or was edited in, each monthly edition of the register. Built by comparing every edition this site holds, the earliest of which is July 2021.

Cite this page

NHS England (2023) Data Uses Register, January 2023 edition, agreement DARS-NIC-397618-T8L8Z, “OpenSAFELY and High Cost Drugs Linkage”. Read via NHS Data Access Explorer (unofficial), https://healthdatauses.uk/agreements/dars-nic-397618-t8l8z/ (accessed [date]).

This address stays the same, but the page is rebuilt with each monthly edition, so the citation names the edition it shows. Every edition's data is kept in the facts store.

Source: datausesregister_september2026.xlsx, September 2026 edition of the NHS England Data Uses Register. Search that workbook for DARS-NIC-397618-T8L8Z to see the original rows.