The Bennett Institute for Applied Data Science at the University of Oxford has been established to pioneer the better use of data, evidence and digital tools in healthcare and policy, optimizing the impact of interventions to achieve improved outcomes.
All new users of the OpenSAFELY platform get access to our supportive co-pilot programme, where each new OpenSAFELY user is assigned a member of the OpenSAFELY team as their co-pilot for the duration of their project.
This week sees the publication of an independent Citizens’ Jury commissioned for NHSx and the National Data Guardian which found that OpenSAFELY was by far the most strongly and consistently supported of all NHS COVID data projects examined.
On our first anniversary, from the Policy Lead in the Bennett Institute, this is the brief story of the positive side from all our lives: how OpenSAFELY came to life, and what we’ve achieved so far.
This is a draft discussion paper, the first of a series exploring “open team science” approaches to managing health data, and specifically how to create a collaborative computational data science ecosystem where the sharing and re-use of objects such as codelists and code is facilitated, encouraged, recognised, and rewarded. As a microcosm of this we have first explored “codelists”. There are currently no ‘answers’ or preferred solutions given. We will be holding an open discussion with the research community on 2nd March at 3pm - you can book to join us here.
This is the website code for openprescribing.net - a Django application that provides a REST API and dashboards for the English Prescribing Dataset published by the NHS Business Services Authority. Information about data sources used on OpenPrescribing can be found here.
This is the repository for the OpenSAFELY job runner. A job runner is a service that encapsulates: the task of checking out an OpenSAFELY study repo; executing actions defined in its project.yaml configuration file when requested via a jobs queue; and storing its results in a particular locations.
The documentation is aimed at developers looking for an overview of how the system works. It also has some parts relevant for end users, particularly the project.yaml documentation.
This is the code for the OpenSAFELY job server designed for mediating jobs that can be run in an OpenSAFELY secure environment. The Django app provides a simple REST API which provides a channel for communicating between low-security environments (which can request that jobs be run) and high-security environments (where jobs are run).
Working on behalf of NHS England we have now built a full, open source, highly secure analytics platform running across the full pseudonymised primary care records of 24 million people, rising soon to 55 million, 95% of the population of England. We have pursued a new model: for privacy, security, low cost, and near-real-time data access, we have built the analytics platform inside the EHR data centre of the major EHR providers, where the data already resides; in addition we have built software that uses tiered increasingly non-disclosive tables to prevent researchers ever needing direct access to the disclosive underlying data to run analyses; code is developed against simulated data using open platforms before moving to the live data environment. Everything has run smoothly. We are fully live inside TPP; we are signed off with full data access and end-stage tech development for the computational platform with EMIS.