Page 4780 - Week 12 - Thursday, 1 November 2018

Next page . . . . Previous page . . . . Speeches . . . . Contents . . . . Debates(HTML) . . . . PDF . . . . Video

(5) What individuals and groups were consulted as part of the development process for the Common Dataset.

(6) Who are the key stakeholders that make up the Common Dataset Working Group, and why were they selected to be part of the group.

(7) When were data quality processes undertaken throughout the year 2018 to date, and what was the nature of each process.

(8) What issues were identified during these processes, and how are they being addressed.

(9) Can the Minister provide a copy of the Common Dataset as an attachment; if not, why not.

Mr Steel: The answer to the member’s question is as follows:

(1) The Common Dataset provides a guide for the collection of relevant client data. The Common Dataset is not intended to provide an exhaustive list of data required across all service delivery programs, but rather to provide a consistent approach to commonly collected data. It is therefore, anticipated that services will continue to collect additional information specific to their service delivery needs.

Some areas are implementing different parts of the Common Dataset dependent on the service they offer or the limitations of their data collection system. Areas collecting information relating to cultural and linguistic diversity include:

Child Development Service

Child Protection services

Youth Justice

Housing ACT

All services that will transition to the new Client Management System will be collecting their data using the Common Dataset as a guide. Culturally and linguistically diverse (CALD) backgrounds is a mandatory collection requirement within the Common Dataset.

(2) The Common Dataset is being implemented across the Directorate through an iterative process. For some business areas the whole of the Common Dataset is not relevant to the service they offer.

All data collecting areas within the Community Services Directorate are implementing relevant items within the Common Dataset.

Full implementation will continue to be undertaken in an iterative way, at natural points of review. This process will take time, but will ensure the Common Dataset is embedded in the most meaningful and effective way. For example, the new client management system will ensure all services using the system are collecting comparable data items.

(3) The purpose of the Common Dataset is to create a consistent approach to data collection, enabling comparability of client information across services. Differences in data collection relate specifically to the structure and/or format of the data, and the way in which it is collected.

Next page . . . . Previous page . . . . Speeches . . . . Contents . . . . Debates(HTML) . . . . PDF . . . . Video