<?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.2539</article-id>
      <article-id pub-id-type="publisher-id">9:5:55</article-id>
      <title-group>
        <article-title>Improving transparency and quality assurance: Operationalising semi-automated data provenance tracking in a Trusted Research Environment</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>O'Sullivan</surname>
            <given-names initials="K">Katherine</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Markovic</surname>
            <given-names initials="M">Milan</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Dymiter</surname>
            <given-names initials="J">Jaroslaw</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Martin</surname>
            <given-names initials="A">Adrian</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Odo</surname>
            <given-names initials="C">Chinasa</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Rowlands</surname>
            <given-names initials="H">Helen</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Ciocarlan</surname>
            <given-names initials="A">Ana</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Wilde</surname>
            <given-names initials="K">Katie</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Casey</surname>
            <given-names initials="A">Arlene</given-names>
          </name>
          <xref ref-type="aff" rid="affil-2">2</xref>
        </contrib>
      </contrib-group>
      <aff id="affil-1"><label>1</label><institution>University of Aberdeen</institution></aff>
      <aff id="affil-2"><label>2</label><institution>University of Edinburgh</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>2539</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/2539">This article is available from the IJPDS website at: https://ijpds.org/article/view/2539</self-uri>
    </article-meta>
  </front>
  <body>
    <p>We present a prototype solution for improving transparency and quality assurance of the data linkage process through a data provenance dashboard designed to assist data analysts, researchers and information governance teams in authenticating and auditing data workflows within a trusted research environment (TRE). Building on prior research (Scheliga, et al., 2022), this work describes our first operationalised prototype tested in a real-world setting.</p>
    <p>The prototype development involved four stages: (1) Co-design of interfaces with end users for provenance data collection and visualisation, producing a low-fidelity design; (2) Extension and refinement of the Safe Haven Provenance (SHP) ontology (<uri>https://tre-provenance.github.io/SHP-ontology/releases/v0.2/index-en.html</uri>); (3) Design and implementation of mechanisms for semi-automated collection of data linkage provenance using the SHP ontology; (4) Implementation and user evaluation of the dashboard.</p>
    <p>A participatory design process with data analysts, researchers and information governance teams resulted in a low-fidelity prototype and was validated via public consultations to ensure it met public trust. The resulting prototype dashboard (<uri>https://tre-provenance.github.io/</uri>) was built as an offline desktop app to match the deployment TRE requirements. The interactive dashboard displays the data linkage information extracted from a knowledge graph described using the SHP ontology (e.g., modifications of datasets, data release) and results of rule-based validation checks (e.g., checking extracted data against researchers' specification). User evaluations confirmed the dashboard would contribute to better quality of data linkage.</p>
    <p>This project demonstrates the next stage in advancing transparency and quality assurance within TREs by semi-automating and systematising data tracking from ingress to egress in a single tool.</p>
  </body>
</article>