This page shows the technical details of what happened when authorised researcher Brian requested one or more actions to be run against real patient data in the project, within a secure environment.
By cross-referencing the indicated Requested Actions with the
Pipeline section below, you can infer what
various outputs were written to. Outputs marked as
can never be viewed directly by a researcher; they can only
request that code runs against them. Outputs marked as
can be viewed by an approved researcher by logging into a highly
secure environment. Only outputs marked as
can be requested for release to the public, via a controlled
output review service.
version: '3.0' expectations: population_size: 500 actions: generate_measure_cohort: run: cohortextractor:latest generate_cohort --study-definition study_definition --index-date-range "2016-01-04 to 2021-01-10 by week" outputs: highly_sensitive: cohort: output/input*.csv calculate_measures: run: cohortextractor:latest generate_measures --study-definition study_definition needs: [generate_measure_cohort] outputs: moderately_sensitive: measure: output/measure_*_rate.csv standardise_and_plot: run: python:latest python analysis/time_series_plots.py needs: [calculate_measures] outputs: moderately_sensitive: tables: output/*_rate.csv graph: output/time_series_plot.svg
These timestamps are generated and stored using the UTC timezone on the backend.