From 6ccfe3a27df7fbf52dc57c37fc205d18dcc9589b Mon Sep 17 00:00:00 2001 From: Simon Li Date: Thu, 5 Oct 2023 13:45:31 +0100 Subject: [PATCH 1/7] Closes https://github.com/sa-tre/satre-specification/issues/255 --- docs/source/pillars/supporting.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md index 86f68a00..5cd0e466 100644 --- a/docs/source/pillars/supporting.md +++ b/docs/source/pillars/supporting.md @@ -198,9 +198,11 @@ How the {ref}`TRE operator ` involves the public in its pr - This may be via the TRE website or annual reports. - Optional * - 4.8.3. - - You could include members of the public in your approvals process. - - This may be carried out via a separate public panel or by including members of the public on an approvals panel. - - Optional + - Members of the public should be included in TRE operations and/or oversight. + - Members of the public can be involved via presence on steering groups or project approvals panels. + Alternatively TRE's can establish separate public panels available for both researchers and TRE staff to consult. + This is especially relevant for TREs with public sector data. + - Mandatory (for TREs with public sector data), otherwise Optional * - 4.8.4. - You should publicly share details of incidents, near misses, and mitigations in a timely fashion, in line with good practices for responsible disclosure. - This may be via the TRE website or annual reports. From 16be81d35f79b7973c44c38ebf6bf78d275a35be Mon Sep 17 00:00:00 2001 From: Simon Li Date: Thu, 5 Oct 2023 13:47:53 +0100 Subject: [PATCH 2/7] Closes https://github.com/sa-tre/satre-specification/issues/258 --- docs/source/pillars/supporting.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md index 5cd0e466..a0cdefde 100644 --- a/docs/source/pillars/supporting.md +++ b/docs/source/pillars/supporting.md @@ -194,9 +194,12 @@ How the {ref}`TRE operator ` involves the public in its pr This could include following guidelines such as [PEDRI](https://www.pedri.org.uk/). - Recommended * - 4.8.2. - - You could publicly share the details of any projects which use the TRE. - - This may be via the TRE website or annual reports. - - Optional + - Details of TRE operations, data available and projects which have accessed the data should be publicly available. + - TREs should be as transparent as possible by providing information online. + Where information is made available online this should be written in clear language understandable to general public. + A record of projects which have accessed data via the TRE should be kept and made available. + Where possible it should include name, summaries, public benefit (if relevant) and organisations involved + - Mandatory (for TREs with public sector data), otherwise Optional * - 4.8.3. - Members of the public should be included in TRE operations and/or oversight. - Members of the public can be involved via presence on steering groups or project approvals panels. From 3bca3209cfdf18f4e88327a5e0e697fba9c2c5f0 Mon Sep 17 00:00:00 2001 From: Simon Li Date: Thu, 5 Oct 2023 13:48:12 +0100 Subject: [PATCH 3/7] Closes https://github.com/sa-tre/satre-specification/issues/259 --- docs/source/pillars/supporting.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md index a0cdefde..8b61d55e 100644 --- a/docs/source/pillars/supporting.md +++ b/docs/source/pillars/supporting.md @@ -189,10 +189,11 @@ How the {ref}`TRE operator ` involves the public in its pr - Guidance - Importance * - 4.8.1. - - You should ensure that all public engagement activities are representative and inclusive. - - Any public engagement activity carried out by TREs should make sure they are involving a representative sample where possible and that activities are accessible and open. + - All public engagement activities must be representative and inclusive. + - Any public engagement activity carried out by TREs should involve diverse participants and that activities are accessible. + Recruitment plans should consider how to proactively reach a representative sample of people or target particular groups of people where relevant This could include following guidelines such as [PEDRI](https://www.pedri.org.uk/). - - Recommended + - Mandatory (for TREs with public sector data), otherwise Optional * - 4.8.2. - Details of TRE operations, data available and projects which have accessed the data should be publicly available. - TREs should be as transparent as possible by providing information online. From 502ffc3fbd636f61fb44413366600057b3b140a5 Mon Sep 17 00:00:00 2001 From: Simon Li Date: Tue, 10 Oct 2023 09:12:34 +0100 Subject: [PATCH 4/7] Replace conditional mandatory with `Mandatory*` --- docs/source/pillars/supporting.md | 12 ++++++------ docs/source/specification.md | 3 +++ 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md index 8b61d55e..6aa2cf8f 100644 --- a/docs/source/pillars/supporting.md +++ b/docs/source/pillars/supporting.md @@ -189,24 +189,24 @@ How the {ref}`TRE operator ` involves the public in its pr - Guidance - Importance * - 4.8.1. - - All public engagement activities must be representative and inclusive. + - All public engagement activities must be representative and inclusive (\*optional for TREs without public sector data). - Any public engagement activity carried out by TREs should involve diverse participants and that activities are accessible. Recruitment plans should consider how to proactively reach a representative sample of people or target particular groups of people where relevant This could include following guidelines such as [PEDRI](https://www.pedri.org.uk/). - - Mandatory (for TREs with public sector data), otherwise Optional + - Mandatory\* * - 4.8.2. - - Details of TRE operations, data available and projects which have accessed the data should be publicly available. + - Details of TRE operations, data available and projects which have accessed the data should be publicly available (\*optional for TREs without public sector data). - TREs should be as transparent as possible by providing information online. Where information is made available online this should be written in clear language understandable to general public. A record of projects which have accessed data via the TRE should be kept and made available. Where possible it should include name, summaries, public benefit (if relevant) and organisations involved - - Mandatory (for TREs with public sector data), otherwise Optional + - Mandatory\* * - 4.8.3. - - Members of the public should be included in TRE operations and/or oversight. + - Members of the public should be included in TRE operations and/or oversight (\*optional for TREs without public sector data). - Members of the public can be involved via presence on steering groups or project approvals panels. Alternatively TRE's can establish separate public panels available for both researchers and TRE staff to consult. This is especially relevant for TREs with public sector data. - - Mandatory (for TREs with public sector data), otherwise Optional + - Mandatory\* * - 4.8.4. - You should publicly share details of incidents, near misses, and mitigations in a timely fashion, in line with good practices for responsible disclosure. - This may be via the TRE website or annual reports. diff --git a/docs/source/specification.md b/docs/source/specification.md index d62cbca4..b60ff538 100644 --- a/docs/source/specification.md +++ b/docs/source/specification.md @@ -73,6 +73,9 @@ These components are each labelled with an importance: :Recommended: Most TREs should have this component, but it is not essential. :Optional: Many TREs would benefit from this component, however, we recognise there are reasons a {ref}`TRE operator ` may actively choose not to implement it. +Some components are mandatory in some circumstances but not others. +These are indicated by an asterisk `Mandatory*`, with details provided in the statement. + {ref}`TRE operator `s are able to demonstrate that they meet the specification by showing they can fulfil all **mandatory** components. Future versions of the specification may introduce more granular levels of evaluation, for instance tiered level of accreditation based on fulfilment of mandatory, recommended and optional components respectively. From 17e0ee53050c876f3b903164d03120ab0fb924fb Mon Sep 17 00:00:00 2001 From: Simon Li Date: Thu, 12 Oct 2023 15:48:13 +0100 Subject: [PATCH 5/7] Apply suggestions from code review --- docs/source/pillars/supporting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md index 6aa2cf8f..1009a620 100644 --- a/docs/source/pillars/supporting.md +++ b/docs/source/pillars/supporting.md @@ -189,20 +189,20 @@ How the {ref}`TRE operator ` involves the public in its pr - Guidance - Importance * - 4.8.1. - - All public engagement activities must be representative and inclusive (\*optional for TREs without public sector data). + - All public engagement activities must include a range of perspectives and be inclusive (\*optional for TREs without personal data). - Any public engagement activity carried out by TREs should involve diverse participants and that activities are accessible. Recruitment plans should consider how to proactively reach a representative sample of people or target particular groups of people where relevant This could include following guidelines such as [PEDRI](https://www.pedri.org.uk/). - Mandatory\* * - 4.8.2. - - Details of TRE operations, data available and projects which have accessed the data should be publicly available (\*optional for TREs without public sector data). + - Details of TRE operations, data available and projects which have accessed the data should be publicly available (\*optional for TREs without personal data). - TREs should be as transparent as possible by providing information online. Where information is made available online this should be written in clear language understandable to general public. A record of projects which have accessed data via the TRE should be kept and made available. Where possible it should include name, summaries, public benefit (if relevant) and organisations involved - Mandatory\* * - 4.8.3. - - Members of the public should be included in TRE operations and/or oversight (\*optional for TREs without public sector data). + - Members of the public should be included in TRE operations and/or oversight (\*optional for TREs without personal data). - Members of the public can be involved via presence on steering groups or project approvals panels. Alternatively TRE's can establish separate public panels available for both researchers and TRE staff to consult. This is especially relevant for TREs with public sector data. From 5a050c4c9a8cedc562edf5f7a0b43b20f3a04da9 Mon Sep 17 00:00:00 2001 From: Simon Li Date: Thu, 12 Oct 2023 15:52:06 +0100 Subject: [PATCH 6/7] Update evaluation section with `Mandatory*` --- docs/source/evaluation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/evaluation.md b/docs/source/evaluation.md index 320d74b4..60b08326 100644 --- a/docs/source/evaluation.md +++ b/docs/source/evaluation.md @@ -40,7 +40,7 @@ You should score your TRE against each statement in the SATRE specification usin :0 Not met: The TRE does not meet this requirement (if this is **Mandatory** this means the TRE is not SATRE compliant) :1 Sufficient: The TRE meets this requirement met but there is substantial scope for improvement :2 Satisfied: The TRE meets this requirement met but there may still be scope for improvement -:N/A: Not applicable: The statement is not relevant to a TRE, may apply to **Recommended** or **Optional** statements +:N/A: Not applicable: The statement is not relevant to a TRE, may apply to **Recommended** or **Optional** statements, and a very limited number of **Mandatory\*** statements. A score of **1** or above means you have met the requirement. Optionally you can use **1** and **2** to indicate potential areas of improvement in your TRE. From 4f38fa99ae214e7b73863befe02a3dff4f8f22f2 Mon Sep 17 00:00:00 2001 From: Simon Li Date: Thu, 12 Oct 2023 15:59:24 +0100 Subject: [PATCH 7/7] public: remove redundant line --- docs/source/pillars/supporting.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md index 1009a620..746b9481 100644 --- a/docs/source/pillars/supporting.md +++ b/docs/source/pillars/supporting.md @@ -205,7 +205,6 @@ How the {ref}`TRE operator ` involves the public in its pr - Members of the public should be included in TRE operations and/or oversight (\*optional for TREs without personal data). - Members of the public can be involved via presence on steering groups or project approvals panels. Alternatively TRE's can establish separate public panels available for both researchers and TRE staff to consult. - This is especially relevant for TREs with public sector data. - Mandatory\* * - 4.8.4. - You should publicly share details of incidents, near misses, and mitigations in a timely fashion, in line with good practices for responsible disclosure.