Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Change]: Review of main landing page #278

Open
jawsgrant opened this issue Oct 5, 2023 · 0 comments
Open

[Change]: Review of main landing page #278

jawsgrant opened this issue Oct 5, 2023 · 0 comments
Labels
proposed change A proposed change to the specification

Comments

@jawsgrant
Copy link

Summary

Suggestions on landing page

Source

Personal contribution

Detail

Principally suggestions on changes for the landing page, to remove duplication and add more information around the context for the project and previous work.

A general theme rather than specific proposal for this page is that it would be useful to have a page with some key references that are directly related to this work e.g. 5 Safes, DEA, ISO, Turing paper, HDR UK green papers, Statistical Disclosure Control Handbook, other DARE UK Sprint/Driver projects and the federated blueprint.

I think this would be different from the discussion on #266 and the suggestion to create a page of useful references on the UK TRE website.

Where

https://satre-specification.readthedocs.io/en/latest/

Proposal

What is SATRE? section appears to repeat the opening section

Perhaps the combine these so the first section could be:

The SATRE project provides a Standard Architecture for Trusted Research Environments (TREs). It incorporates knowledge and best practices from multiple institutions and sectors across the UK. This includes all aspects of TRE provision such as information governance procedures, computing technology, data management and other capabilities.

This specification should be useful if you are

  • A TRE operator wanting to evaluate or improve their TRE with the suggested capabilities.
  • A Developers and Builders of new TREs looking for guidance in their thinking and decision making.

We encourage all TREs in the UK to evaluate themselves against the SATRE specification, and to contribute to the project.

*why are we doing this states TREs are needed then defines what they are. Perhaps add a new section stating what TREs do, then have Why are we doing this (now)? section

? Why do we need TREs?

Personal or sensitive data which have been collected for operational, commercial or governmental reasons need to be managed securely and safely. A TRE enables researchers to access the data in a secure environment following best practice. This should ensure that research projects are properly authorised and that researchers only access the data they need, whilst whilst minimising risk of data release or exposure.

? Why are we doing this now?

The need for trusted research environments (TREs) is clear. Influential reports from DARE UK and Health Data Research UK, together with the UK Government Goldacre review and ‘Data Saves Lives’ policy paper, have all highlighted the need for change in how sensitive data are handled. [add links](to all these external references, or a link to a references page in the specification)

At present there a range of [frameworks, legislatation and standards](reference/link to references: 5 safes, UKRDA greenpapers, Turing Paper) that operators have to interpret in building and running a TRE. This makes for inconsistent governance standards and makes it hard for researchers to work consistently in different environments.

A common specification for TREs will improve governance and practice across the sector, simplify researcher and operator journeys. Furthermore it will lay a foundation for interoperability that is required to maximise the impact of research by providing a trusted ecosystem for providing access to currently disparate and siloed data.

I think it would be nice to have a section ? Who are we? Perhaps this is the original team, and given the looming end of the project could move to update to reference whatever governance structure the community arrives at. Could be more specific on team leading this but also useful to give some motivation

Who are we?

The SATRE team contains representatives from several existing UK TREs, which host many different types of sensitive data. We will use the reference architecture specified here to bring these into closer alignment and make it easy for others to do the same. This supports DARE UK’s aim of developing a coordinated national data research infrastructure.

Contributing

SATRE operates as a ?community project? and we welcome contributions ...

Who can help

No response

@jawsgrant jawsgrant added the proposed change A proposed change to the specification label Oct 5, 2023
jawsgrant pushed a commit to jawsgrant/satre-specification that referenced this issue Oct 11, 2023
craddm added a commit that referenced this issue Oct 11, 2023
Updates index.html based on #278 proposal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposed change A proposed change to the specification
Projects
None yet
Development

No branches or pull requests

1 participant