This page shows the technical details of what happened when authorised researcher Helen Curtis 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
security level
various outputs were written to. Outputs marked as
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.
Jobs
-
- Job identifier:
-
mftzmair7vjhguf3
-
- Job identifier:
-
fpfmyt4azepkakum
-
- Job identifier:
-
ytrpuvhixyhhzzn6
Pipeline
Show project.yaml
version: '3.0'
expectations:
population_size: 1000
actions:
generate_population:
run: cohortextractor:latest generate_cohort --study-definition study_definition --output-format 'feather'
outputs:
highly_sensitive:
cohort: output/input.feather
generate_report:
run: cohort-report:v3.0.0 output/input.feather
needs: [generate_population]
config:
output_path: output/cohort_reports_outputs
outputs:
moderately_sensitive:
reports: output/cohort_reports_outputs/descriptives_input.html
summary_html:
run: jupyter:latest jupyter nbconvert /workspace/notebooks/data_summary.ipynb --execute --to html --output-dir=/workspace/output --ExecutePreprocessor.timeout=86400 --debug
needs: [generate_population]
outputs:
moderately_sensitive:
html: output/data_summary.html
Timeline
-
Created:
-
Started:
-
Finished:
-
Runtime: 03:43:31
These timestamps are generated and stored using the UTC timezone on the backend.