This page shows the technical details of what happened when authorised researcher dgrint requested one or more actions to be run against real patient data in the SGTF 617 project, within a secure environment.
By cross-referencing the indicated Requested Actions with the Pipeline section below, you can infer what
security level various outputs were written to. Outputs
highly_sensitive can never be viewed directly by a
researcher; they can only request that code runs against them. Outputs marked as
moderately_sensitive can be
viewed by an approved researcher by logging into a highly secure environment. Only outputs marked as
moderately_sensitive can be requested for release to the public, via a controlled output review service.
Show Hide project.yaml
version: '3.0' expectations: population_size: 50000 actions: generate_cohort: run: cohortextractor:latest generate_cohort --study-definition study_definition outputs: highly_sensitive: cohort: output/input.csv crMAIN: run: stata-mp:latest analysis/cr_analysis_dataset.do needs: [generate_cohort] outputs: moderately_sensitive: log: logs/cr_analysis_dataset.log highly_sensitive: data: output/cr_analysis_dataset.dta anTAB1: run: stata-mp:latest analysis/an_table1.do needs: [crMAIN] outputs: moderately_sensitive: log: logs/an_table1.log table1text: output/table1.txt table1xlsx: output/table1.xlsx figure1: output/alpha_ageband.svg figure2: output/delta_ageband.svg figure3: output/delta_cumcase.svg figure4: output/alpha_cumcase.svg figure5: output/ae_hist.svg figure6: output/ae_kden.svg
State is inferred from the related Jobs.
Timings set to UTC timezone.
- Runtime: 00:02:09