Out-of-home care longitudinal data asset

In use from 30 June 2019.

File name of the data file being ingested

Name generated during ingestion of data file, which can be used to trace errors

The unique ID produced in Salesforce for a child. This can be merged and therefore a childs ID can change over time.

Known data quality issues: Six CYP who have blank ChildStoryID but a LegacKidsPersonNumber. Issues caused due to extremely old records (e.g. those starting OOHC in 1986) not being migrated to ChildStory as well as other data issues (e.g. some records may have had duplicate IDs in the old system that were merged into a single ID in ChildStory)

Unique Person Number from the KiDS legacy source system migrated to ChildStory with the LEGACY_ID legacy person record ID, used for verification and matching only.

Gender on person record at time of extraction

Primary first name of the child

Primary last name of the child

Aboriginal status on person record at time of extraction grouped for reporting purposes (Aboriginal, non-Aboriginal, other, blank) (Not stated is grouped into other)

Only applies to Aboriginal children. Is a combination of placement type and Aboriginality of the carer. Used for APP reporting

Only applies to Aboriginal children. Identifies whether the carer is Aboriginal. Grouped to Aboriginal/Non Aboriginal/Independent.

Calculated Aboriginal status of the household based in the Office of the Children's Guardian (OCG) database, the Aboriginality of member persons

Pathname

Start date of the placement set by the caseworker on the placement record. This is different to the placement creation date

End date of the placement set by the caseworker on the placement record. Field can be blank/NULL as the child may still be in care at the time of reporting.

Placement type

Placement type grouped. Used for reporting purposes. There are a number of placement groups used for various purposes. This grouping changes over time

The latest recorded purpose of the placement at time of extraction. Placement purpose is where respite placements are identified.

The placement exit reason includes both movement in care and exit from care reasons. This field is used for permancy calculations.

Start date of the placement set by the caseworker on the placement record. This is different to the placement creation date

End date of the placement set by the caseworker on the placement record. Field can be blank/NULL as the child may still be in care at the time of reporting.

Placement type grouped. Used for reporting purposes. There are a number of placement groups used for various purposes. This grouping changes over time.

The latest recorded purpose of the placement at time of extraction. Placement purpose is where respite placements are identified.

The placement exit reason includes both movement in care and exit from care reasons. This field is used for permanency calculations.

Start date of first ever OOHC care category.
Known data quality issues: These dates may differ for a given ChildStoryID when comparing this dataset vs CIW. This is due to CIW containing only records that had the new definition of OOHC applied.

Last known exit date or imputed end date (18th birthday of CYP) if CYP still in care.
Known data quality issues: These dates may differ for a given ChildStoryID when comparing this dataset vs CIW. This is due to CIW containing only records that had the new definition of OOHC applied.

The recorded order type on the legal order. (final/interim/PR only/other)

The start of the legal order as set by the court or administrative arrangement.

The end of the legal order as set by the court or administrative arrangement. Some orders are recorded without an end date.

Derived from the position of the caseworker indicating which district owns the record at time of extract.

Derived from the position of the care worker indicating which CSC currently owns the record at time of extract or at time of exiting from Out-of-Home Care.

Legal parental responsibility (based on a legal order) grouped at time of extraction for an open row, or at the end, calculated as current for open placements or at exit for placements that are closed.

Parental Responsibility PR at time of extraction, calculated as current for open placements or at exit for placements that are closed.

Calculated to indicate the party responsible for the Case Plan management (FACS, NGO or OTHER) at time of extraction.

High level breakdown of primary legal order care type (statutory, supported care etc)

CYP who are on a care and protection order are those who have been determined by the Children's Court to be at ROSH if they were to be returned to their families at the point of order date.

High level breakdown of OOHC type.

Placement record ID created by Salesforce for hyperlinking directly to a record

Placement legacy id on systems prior to Childstory N-X(7)-X(6)

Indicator of whether the record comes from CIW or are from KiDs. 1617 indicates records from KiDs 1718 indicates records from ChildStory

Indicates whether the Child or Young Person was in care during [extraction period].

Indicates whether the Child or Young Person was in care as at [extraction date].

Primary placement for CYP in OOHC as at [extraction date].

Indicates whether the Child or Young Person exited care during [extraction period].

CYP who exited OOHC during [extraction period]. (first exit care category and last care event).

Number of days a CYP has stayed in OOHC since their first ever entry up to [extraction date] (calculated using 

Total number of actual placements a child has ever had. Pre 1718 data calculates the number placements by: 1. Select actual placements >= 7 days in length) 2. Where carer household ids are available, count distinct number of carer household ids 3. For records where care household ids are null but placement provider ids are available, count distinct number of placement provider ids 4. For recrods where both carer household and placement provider ids are not available, count distinct number of actual placemen types 5. Add 2 to 4 for placements up t o 1617 1718 and onwards uses Distinct Placements - Care Category under the Care Event - FACT folder.

CYP has records in both KiDs and ChildStory.

CYP has records only in KiDs.

CYP has records only in ChildStory.

These are cases where the end date have been changed by a caseworker within ChildStory and old records from 1617 OOHC overtime file had their Care Category end dates imputed to match with the updated dates.

These are cases where the start dates from 1617 OOHC overtime file had been updated by a caseworker. The end dates from 1617 > start date from 1718 were imputed to be the start of 1718. Example: 1. Historic file had start date of 01-01-2017 and end date of 01-01-2018. 2. New file had start date of 01-05-2017 and end date of 01-05-2018. 3. Dates were imputed so child has care categories where the dates were now 01-01-2017 to 01-05-2017 and the next one was 01-05-2017 to 01-05-2018.

Flag indicating whether a person has a current disability recorded on Childstory at point of extract

Concatinated string of all recorded disability types

Calculation showing the exit reason of the final placement in the OOHC care period on all placements in that OOHC care period.

Aboriginal placement principle APP flag 'Y/N'. A calculated proxy using national counting rules taking into account other factors such as Aboriginality of the carer and placement type. This flag only applied to children who are identified as Aboriginal.

First used in 2021.

Current known postcode from the current address recorded on ChildStory source system

Placement ID as displayed on ChildStory source system (PLA - nnnnnn), and also referred to as the Placement Number. In use from 2021 onward.

The case plan number (unique ID) of the OOHC - the common reference number of the plan visibile on the screen

The record row ID of the case plan of the OOHC care category - salesforce UID for hyperlinking directly to the record

The start date of the OOHC case plan as recorded on the source system (this is different to the record creation date). In use from 2021 onwards

The end date of the oohc case plan derived from recorded date or imputed based on subsequent case plan start date or exiting OOHC

The approval status of the case plan record. Redundent as only approved plans are considered valid for the the purpose of the data extraction. In use from 2021 onwards.

Name of the caseworker associated with a case at time of extract. In use form 2021 onwards.

The OOHC care arrangement for which the case plan is part to (Statutory - Final Order, Statutory- Interim Order, Supported or Unspecified). Not to be used for reporting the legal care arrangement - see CARE_ARRANGEMENT. In use from 2021 onwards.

Provides the recorded Child Participation in the case plan at creation or at review. In use form 2021 onwards.

A grouped plan goal used for the main goal of the case plan at the conclusion of the service event or the time of data extraction (for current events). In use from 2021 onwards.

The plan goal of the case plan at the conclusion of the service event or the time of data extraction (for current events) including cleaning rules for equivalent values from deprecated historical goal labels. In use from 2021 onwards.

In use from 2021 onwards.

Y/N to indicate if the Case Plan is a Leaving Care Plan. If created or reviewed after the child is 15, a plan is automatically considered a Leaving Care Plan. In use from 2021 onwards.