Skip to main content

Platform news

  1. User, project, and organisation Event Logs added

    OpenSAFELY Jobs has been updated with new Event Log pages for users, projects, and organisations. These pages provide specific information about current Job Requests, and allow users to see a complete audit log of all previous Job Requests. Examples of new Event Log pages include: The global OpenSAFELY Job Server…

  2. New opensafely clean command

    We have added a command to the opensafely command line tool: opensafely clean This command will safely remove any leftover OpenSAFELY docker artifacts from your system. Specifically, it removes old images, job containers, and file volumes that may have been created when running jobs locally on a user’s computer. Users who…

  3. Improved access to OpenSAFELY Jobs from secure environments

    OpenSAFELY Jobs is used by researchers from within the secure environments (such as TPP level 4) to support the review and output checking of files. We’ve added an easier way for users to log in to OpenSAFELY Jobs from the TPP secure environment, by implementing auto-generated single use tokens. Previously,…

  4. Updates to the OpenSAFELY Jobs home page

    OpenSAFELY Jobs home page has been updated to create a personalised dashboard for users. Once logged in, users will now be able to view: Alongside the new home page, users are now able to access a personalised list of: For visitors to the website who don’t have an account, a…

  5. Introducing the opensafely exec command for interactive sessions

    There is new opensafely exec command in recent versions of the opensafely tool. It is designed to aid in development of analysis code using the published OpenSAFELY docker images. The need to add your your work-in-progress code to project.yaml in order to test it is awkward. This leads some users to use their own…

  6. New build of the OpenSAFELY R image

    We have just published a new build of the R image. No action needed, but more information below! What has not changed? This is not a semantic change – the same versions of the same set of libraries are installed. However the way the image is built has been reworked, in order to…

  7. Using compressed data files by default

    Using compressed files is now the default recommendation in documentation and templates. On the backends, where datasets can be very large, using uncompressed files significantly slows execution and consumes more disk space. The research-template has been updated to generate csv.gz files from cohortextractor by default, and the examples…

  8. Improve handling of stale medication codelists in cohort-extractor

    dm+d codes for Virtual Medicinal Products (VMPs) can change over time, with the result that codelists that contain VMP codes can become stale. As a consequence, studies that use patients.with_these_medications() with an old codelist may not have captured all the medication events that the author intended. Until now, the mitigation…

  9. Added support for parameterised study definitions

    Study definitions can now be “parameterised” so they accept values passed in by the action. This allows multiple cohorts with different properties to be generated by a single study definition.

  10. Add rounding instructions to disclosure documentations

    Added instructions regarding rounding to our disclosure control documentation, including an example.

Subscribe to Platform News updates

Receive an email alert when the OpenSAFELY platform is updated.

What type of news do you want to receive?

You can unsubscribe at any time by clicking the link in the footer of our emails.

We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing.

Learn more about Mailchimp's privacy practices here.