<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "JATS-journalpublishing1.dtd" [
]>
<article xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML"
  dtd-version="1.2" article-type="abstract">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">IJPDS</journal-id>
      <journal-title-group>
        <journal-title>International Journal of Population Data Science</journal-title>
        <abbrev-journal-title>IJPDS</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="epub">2399-4908</issn>
      <publisher>
        <publisher-name>Swansea University</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.23889/ijpds.v9i5.2609</article-id>
      <article-id pub-id-type="publisher-id">9:5:125</article-id>
      <title-group>
        <article-title>A UK Specification for Trusted Research Environments</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>Sood</surname>
            <given-names initials="H">Hari</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Li</surname>
            <given-names initials="S">Simon</given-names>
          </name>
          <xref ref-type="aff" rid="affil-2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Machin</surname>
            <given-names initials="T">Tim</given-names>
          </name>
          <xref ref-type="aff" rid="affil-3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Oldfield</surname>
            <given-names initials="K">Katie</given-names>
          </name>
          <xref ref-type="aff" rid="affil-4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Chuter</surname>
            <given-names initials="A">Antony</given-names>
          </name>
          <xref ref-type="aff" rid="affil-5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Beggs</surname>
            <given-names initials="J">Jillian</given-names>
          </name>
          <xref ref-type="aff" rid="affil-5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Coleman</surname>
            <given-names initials="S">Sonya</given-names>
          </name>
          <xref ref-type="aff" rid="affil-6">6</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Kerr</surname>
            <given-names initials="D">Dermot</given-names>
          </name>
          <xref ref-type="aff" rid="affil-6">6</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Chalstrey</surname>
            <given-names initials="E">Ed</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Craddock</surname>
            <given-names initials="M">Matthew</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Madge</surname>
            <given-names initials="J">Jim</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Sarmiento-Perez</surname>
            <given-names initials="D">David</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Robinson</surname>
            <given-names initials="J">James</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>O'Donovan</surname>
            <given-names initials="C">Cian</given-names>
          </name>
          <xref ref-type="aff" rid="affil-3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>O'Reilly</surname>
            <given-names initials="M">Martin</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Cole</surname>
            <given-names initials="C">Christian</given-names>
          </name>
          <xref ref-type="aff" rid="affil-2">2</xref>
        </contrib>
      </contrib-group>
      <aff id="affil-1"><label>1</label><institution>The Alan Turing Institute</institution></aff>
      <aff id="affil-2"><label>2</label><institution>University of Dundee</institution></aff>
      <aff id="affil-3"><label>3</label><institution>University College London</institution></aff>
      <aff id="affil-4"><label>4</label><institution>Research Data Scotland</institution></aff>
      <aff id="affil-5"><label>5</label><institution>Public Member</institution></aff>
      <aff id="affil-6"><label>6</label><institution>Ulster University</institution></aff>
      <pub-date date-type="pub" publication-format="electronic">
        <day>18</day>
        <month>09</month>
        <year>2024</year>
      </pub-date>
      <pub-date date-type="collection" publication-format="electronic">
        <year>2024</year>
      </pub-date>
      <volume>9</volume>
      <issue>5</issue>
      <elocation-id>2609</elocation-id>
      <permissions>
        <license license-type="open-access" xlink:href="https://creativecommons.org/licences/by/4.0/">
          <license-p>This work is licenced under a Creative Commons Attribution 4.0 International License.</license-p>
        </license>
      </permissions>
      <self-uri xlink:href="https://ijpds.org/article/view/2609">This article is available from the IJPDS website at: https://ijpds.org/article/view/2609</self-uri>
    </article-meta>
  </front>
  <body>
    <sec>
      <title>Objectives</title>
      <p>The need for Trusted Research Environments (TREs) is clear. Several influential reports have highlighted that personal or sensitive data which have been collected for operational, commercial or governmental reasons need to be managed securely in an environment that encourages best practices.</p>
      <p>TREs are designed to enable only authorised projects and researchers access to sensitive data whilst minimising risk of data exposure. Yet the TRE landscape has grown organically over at least the last decade resulting in heterogeneous environments, making  it harder for data to be discovered, shared and used for public benefit.</p>
      <p>A baseline specification for TREs is required.</p>
    </sec>
    <sec>
      <title>Approach</title>
      <p>We engaged with around 60 organisations covering government, industry, health and academia through regular, online, shared spaces or “Collaboration Cafés”. We also embedded the public voice within the project by having members of the public within the research team and developed a series of workshops to include and reflect their input to the architecture. The whole project was developed in the open to instil trustworthiness.</p>
    </sec>
    <sec>
      <title>Results</title>
      <p>The SATRE project has produced a reference TRE architecture and implementation through significant engagement with the UK TRE community. This baseline specification for UK TREs includes a set of four pillars, 28 capabilities and 160 statements.</p>
    </sec>
    <sec>
      <title>Conclusions and Implications</title>
      <p>An open and transparent TRE specification and architecture for a wide range of stakeholders has been developed. TREs can now use the SATRE specification to evaluate their environments against a common baseline.</p>
    </sec>
  </body>
</article>