Skip to content Learn about the access keys available for Aristotle.Cloud

Juvenile Justice Order file cluster

Definition

The Order file contains information about the supervised orders handed down by courts and parole boards to young people under juvenile justice supervision.

Metadata items in this Data Set Specification

Below is a list of all the components within this Dataset Specification.
Each entry includes the item name, whether the item is optional, mandatory or conditional and the maximum times the item can occur in a dataset.
If the items must occur in a particular order in the dataset, the sequence number is included before the item name.

Data Elements
Reference Data Element Data Type Length Inclusion #
Address: Australian Postcode, (Postcode datafile) NNNN Number 4 conditional 0
Address: Australian State/Territory Identifier, Code N Number 1 conditional 0
Address—suburb/town/locality name, text X[X(45)] - - conditional 0
Person—person identifier, XXXXXX[X(14)] - - mandatory 1
Service episode—episode end date, DDMMYYYY
Specific Information:

Guide for use - Order file

The Episode end date or Order end date is the date the order ceases to be in effect, as specified on the order.

If a young person ceases to be under the supervision relating to the order, but the order is still in effect, the order does not end. For example, if a young person is given a sentenced detention order with an end date of 1 December but is released on supervised release or parole on 1 November, the order end date remains 1 December unless the court varies the end date of the order.

If the court varies the end date of the order, the new (varied) end date is the Order end date.

If an order is revoked or cancelled, the Episode end date or Order end date is the date that the order was revoked or cancelled. This includes orders that are revoked or cancelled due to re-offending or failure to comply with conditions and orders that are cancelled, quashed or varied on appeal.

If an order extends over two or more extraction periods and the Order end date changes because the order was revoked, cancelled, quashed or varied, the Order end date and the Order end reason will differ between the extraction periods. The changed Order end date should be supplied in the extraction period in which the order was revoked, cancelled, quashed or varied; however, related records supplied in previous extraction periods should not be updated.

 Date/Time 8 mandatory 1
Service episode—episode start date, DDMMYYYY
Specific Information:

Guide for use - Order file

This date may not be the date that supervision began; for example, if a sentence of detention is backdated to the start of the young person’s remand period, the order start date will be before the period of sentenced detention actually began.

Orders may be concurrent and overlap; that is, the Episode start date or Order start date may be before the Order end date of the previous order.

 Date/Time 8 mandatory 1
Service episode—legal order/arrangement type, code NN - - mandatory 1

Comments

Guide for use:

The Juvenile Justice Order file cluster contains the following Data Elements:

  • Person—person identifier, XXXXXX[X(14)]
  • Service episode—order identifier, XXXXX[15]
  • Service episode—episode start date, DDMMYYYY
  • Service episode—episode end date, DDMMYYYY
  • Service episode—order end reason code N[N]
  • Service episode—legal order/arrangement type, juvenile justice code NN

References


This content Based on Australian Institute of Health and Welfare material. Attribution provided as required under the AIHW CC-BY licence.

Related content

Relation Count
As a numerator in an Indicator 0
As a denominator in an Indicator 0
As a disaggregation in an Indicator 0