<?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.2516</article-id>
      <article-id pub-id-type="publisher-id">9:5:34</article-id>
      <title-group>
        <article-title>Improving Responsiveness: Our Journey from Manual Yearly Updates to Automated Linkage for Near Real-Time Understanding of Outcomes and Modelling Future Service Demand</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>Witowski</surname>
            <given-names initials="P">Philip</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Sipthorp</surname>
            <given-names initials="M">Mark</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Ismail</surname>
            <given-names initials="A">Adam</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Sulaiman</surname>
            <given-names initials="W">Windra</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Phillips</surname>
            <given-names initials="B">Beverley</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Williams</surname>
            <given-names initials="S">Sharon</given-names>
          </name>
          <xref ref-type="aff" rid="affil-1">1</xref>
        </contrib>
      </contrib-group>
      <aff id="affil-1"><label>1</label><institution>Centre for Victorian Data Linkage</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>2516</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/2516">This article is available from the IJPDS website at: https://ijpds.org/article/view/2516</self-uri>
    </article-meta>
  </front>
  <body>
    <sec>
      <title>Objective</title>
      <p>Demand for real-time data during the COVID-19 pandemic revealed a need to increase efficiencies in manual linkage processes to respond to events in near real-time. In response, our jurisdictional linkage agency transitioned from yearly to daily, weekly and monthly linkage practices through increasing automation and improving process flows.</p>
    </sec>
    <sec>
      <title>Approach</title>
      <p>Our linkage agency transitioned to a fully automated process utilising scalable cloud infrastructure. Source data is now provided directly to a common data platform. This data is split into linkage and content, cleansed and quality assured in Python and set to automatically run via Azure data pipelines. The data is then linked via a combination of deterministic and probabilistic criteria, with data quality checks automatically performed along the way. Researchers can analyse this data in a secure virtual machine that only they can access and retrieve data from.</p>
    </sec>
    <sec>
      <title>Results</title>
      <p>This infrastructure expedites the data linkage process allowing daily linkage results to select datasets, and enables advanced research such as a predictive micro-simulation model, which leverages the platform to predict and intervene on outcomes influenced by governmental policies. This model relies on timely administrative data to build targeted interventions for groups with poor future outcomes, tests these interventions, and monitors outcomes in near real-time.</p>
    </sec>
    <sec>
      <title>Conclusion</title>
      <p>Our linkage agency has transitioned from manual to automated linkage processes in response to increasing need for timely data. By embracing cloud infrastructure and leveraging automation, we have streamlined our operations, enabling responsive linkage depending on need and expediting the provision of de-identified, linked data to researchers.</p>
    </sec>
  </body>
</article>