This page shows the technical details of what happened when authorised researcher Peter Inglesby 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: 1000 actions: generate_study_population: run: cohortextractor:latest generate_cohort --output-format feather --study-definition study_definition outputs: highly_sensitive: cohort: output/input.feather rotate_study_population: run: python:latest python analysis/rotate_study_population.py needs: [generate_study_population] outputs: highly_sensitive: cohort: output/input-last.feather generate_summary_notebook: run: python:latest jupyter nbconvert notebooks/summary.ipynb --to=html --output-dir=output/ --execute --ExecutePreprocessor.timeout=86400 needs: [generate_study_population, rotate_study_population] outputs: moderately_sensitive: notebook: output/summary.html
These timestamps are generated and stored using the UTC timezone on the backend.