Y24-086 As NPG we would like an extra "Contaminated Human Data Access Group" field on the New Study Page so that access to the "likely human" read data that NPG already creates separately.

[TWJW-SANGER]

User story As NPG we would like an extra "Contaminated Human Data Access Group" field on the New Study Page so that access to the "likely human" read data that NPG already creates separately.

Who are the primary contacts for this story Jillian D David J SSR team

Who is the nominated tester for UAT The SSR team (Liz C)

Acceptance criteria To be considered successful the solution must allow:

• [ ] Add an additional field "Contaminated human data access group"
• [ ] Add the following help text for the field "Contaminated human data access group" - "Allows the specified Unix groups and users access to data separated from out from the main data product as likely contaminated with human - typically rarely used and only for validating the separation process as we may not have the ethical or legal authorisation to use it beyond that"
• [ ] The "Contaminated Data access group" value should be exported to the MLWH database as an extra column in the study table contaminated_human_data_access_group as VARCHAR(255) defaulting to NULL.

Additional context This story has been generated from RT#801935.

When processing non-human samples that have been extracted from humans, e.g. Covid virus extracted from human saliva, the sequence data files can contain fragments of human DNA/RNA in addition to the viral or parasitic DNA/RNA.

Studies producing non-human sequence data DO NOT have the ethical approval or legal consent to publish any human sequence data. NPG offers a service to remove human derived DNA/RNA fragments from the data output of the sequencing machine.

The existing Data Access Group controls access to the data set with human reads removed.

There is a need for different, more privileged, user groups to access to the data sets containing human reads in order to perform quality checks.