Fit for purpose - developing a software platform to support the modern challenges of data linkage in Western Australia

Tom Walter Eitelhuber,Steve Hodges,Janine Alan,James Thackray

doi:10.23889/ijpds.v3i3.435

Abstract

The Western Australia Data Linkage System (WADLS) is maintained and operated by the WA Data Linkage Branch (DLB) at the Western Australian Department of Health. DLB has pioneered a number of data linkage innovations, including the facilitation of genealogical research via the Family Connections system and streamlined data delivery via the Custodian Administered Research Extract Server. DLB’s latest innovation is a new data linkage system called “DLS3”, which improves DLB’s capability and capacity to handle the increasing volume and complexity of its routine operations. DLS3 was built entirely in-house and customised to meet the specific challenges that DLB has encountered throughout over twenty years of experience with a wide variety of linkages. This article describes the development and rollout of DLS3, including its design, architecture, benefits and limitations.

Highlights

Western Australia (WA) covers approximately a third (2.5M square kilometres) of Australia’s total landmass and 10 per cent (2.6M people) of its population [1]
The WA Department of Health is responsible for the overall management, performance, and strategic direction of the WA public health system to ensure the delivery of high-quality, safe, timely and accessible health services [2]
Established in 1995[5], the WA Data Linkage System (WADLS) is the longest operating Australian linkage system and it is underpinned by strong privacy and security principles [6,7]

Summary

Introduction

Western Australia (WA) covers approximately a third (2.5M square kilometres) of Australia’s total landmass and 10 per cent (2.6M people) of its population [1]. DLB uses probabilistic linkage processes, where groups of records are compared using complex field matching algorithms. Important linkage functions, including: data cleaning and standardisation; importation, storage and extraction of data; loading, storage and extraction of links; clerical review processes; quality checking processes; and maintaining system metadata such as the history of decisions.

Results

Conclusion