Identifying and definitional attributes | |
Metadata item type: | Data Element |
---|---|
Short name: | Offence identifier |
METEOR identifier: | 512520 |
Registration status: | Youth Justice, Standard 15/02/2022 |
Definition: | An alphanumeric identifier for the offence for which a person has been placed on a legal order or arrangement. |
Data element concept attributes | |
Identifying and definitional attributes | |
Data element concept: | Order—offence identifier |
---|---|
METEOR identifier: | 512517 |
Registration status: | Youth Justice, Standard 15/02/2022 |
Definition: | An identifier for the offence for which a person has been placed on a legal order or arrangement. |
Object class: | Order |
Property: | Offence identifier |
Value domain attributes | |
Identifying and definitional attributes | |
Value domain: | Identifier X[X(49)] |
---|---|
METEOR identifier: | 429188 |
Registration status: | Youth Justice, Standard 15/02/2022 |
Definition: | A combination of alphanumeric characters that identify an object or entity. |
Representational attributes | ||
Representation class: | Identifier | |
---|---|---|
Data type: | String | |
Format: | X[X(49)] | |
Maximum character length: | 50 |
Source and reference attributes | |
Submitting organisation: | Australian Institute of Health and Welfare |
---|
Data element attributes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Collection and usage attributes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Collection methods: | If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Relational attributes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementation in Data Set Specifications: | Juvenile Justice Charge file cluster Youth Justice, Superseded 23/08/2022 Conditional obligation: Conditional on a charge resulting in a conviction. If charges cannot be linked with offences, do not supply data for this item. DSS specific information: The offence identifier (charge file) allows for a charge to be linked with the resulting offence. If charges cannot be linked with offences, do not supply data for this item. For example, following their first court appearance, a young person is placed on remand for a particular offence (order ID 333). At their second court appearance, they are released on supervised bail (order ID 334). At the third court appearance, the young person is sentenced to a supervised order in relation to the charge. The resulting order is order ID 6 in the order file. The first record shows that the person was charged with an offence and that the related order is order ID333. The offence ID field is blank because for this order, the charge did not result in a conviction. The second record shows that the charge ID is the same as the first record and so the charge is the same. It requires a new record because the order ID is different. At the end of this order, the charge resulted in a conviction, so the offence ID field contains ID of the corresponding offence record.
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. Null values Leave the field blank if: • The offence identifier is unknown • The offence identifier is not applicable. Juvenile Justice Offence file cluster Youth Justice, Superseded 23/08/2022 DSS specific information: The offence identifier allows for a single offence to be mapped to multiple orders. For example, a young person is serving a sentence in detention for offence type 1350. They are released on parole/supervised release in relation to this offence. The first record shows the young person was supervised under order ID 12 (the sentenced detention) in relation to offence type 1350. In the second record, the offence is the same as in the first record because a) the offence types are the same and b) the offence ID is the same. A second record is required because the order ID is different (the parole order).
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. No null values. Youth Justice Charge file cluster Youth Justice, Superseded 25/06/2024 Conditional obligation: Conditional on a charge resulting in a conviction. If charges cannot be linked with offences, do not supply data for this item. DSS specific information: The offence identifier (charge file) allows for a charge to be linked with the resulting offence. If charges cannot be linked with offences, do not supply data for this item. For example, following their first court appearance, a young person is placed on remand for a particular offence (order ID 333). At their second court appearance, they are released on supervised bail (order ID 334). At the third court appearance, the young person is sentenced to a supervised order in relation to the charge. The resulting order is order ID 6 in the order file. The first record shows that the person was charged with an offence and that the related order is order ID333. The offence ID field is blank because for this order, the charge did not result in a conviction. The second record shows that the charge ID is the same as the first record and so the charge is the same. It requires a new record because the order ID is different. At the end of this order, the charge resulted in a conviction, so the offence ID field contains ID of the corresponding offence record.
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. Null values Leave the field blank if: • The offence identifier is unknown • The offence identifier is not applicable. Youth Justice Charge file cluster Youth Justice, Superseded 23/08/2022 Conditional obligation: Conditional on a charge resulting in a conviction. If charges cannot be linked with offences, do not supply data for this item. DSS specific information: The offence identifier (charge file) allows for a charge to be linked with the resulting offence. If charges cannot be linked with offences, do not supply data for this item. For example, following their first court appearance, a young person is placed on remand for a particular offence (order ID 333). At their second court appearance, they are released on supervised bail (order ID 334). At the third court appearance, the young person is sentenced to a supervised order in relation to the charge. The resulting order is order ID 6 in the order file. The first record shows that the person was charged with an offence and that the related order is order ID333. The offence ID field is blank because for this order, the charge did not result in a conviction. The second record shows that the charge ID is the same as the first record and so the charge is the same. It requires a new record because the order ID is different. At the end of this order, the charge resulted in a conviction, so the offence ID field contains ID of the corresponding offence record.
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. Null values Leave the field blank if: • The offence identifier is unknown • The offence identifier is not applicable. Youth Justice Charge file cluster Youth Justice, Standard 24/06/2024 Implementation start date: 01/07/2023 Conditional obligation: Conditional on a charge resulting in a conviction. If charges cannot be linked with offences, do not supply data for this item. DSS specific information: The offence identifier (charge file) allows for a charge to be linked with the resulting offence. If charges cannot be linked with offences, do not supply data for this item. For example, following their first court appearance, a young person is placed on remand for a particular offence (order ID 333). At their second court appearance, they are released on supervised bail (order ID 334). At the third court appearance, the young person is sentenced to a supervised order in relation to the charge. The resulting order is order ID 6 in the order file. The first record shows that the person was charged with an offence and that the related order is order ID333. The offence ID field is blank because for this order, the charge did not result in a conviction. The second record shows that the charge ID is the same as the first record and so the charge is the same. It requires a new record because the order ID is different. At the end of this order, the charge resulted in a conviction, so the offence ID field contains ID of the corresponding offence record.
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. Null values Leave the field blank if: • The offence identifier is unknown • The offence identifier is not applicable. Youth Justice Offence file cluster Youth Justice, Superseded 23/08/2022 DSS specific information: The offence identifier allows for a single offence to be mapped to multiple orders. For example, a young person is serving a sentence in detention for offence type 1350. They are released on parole/supervised release in relation to this offence. The first record shows the young person was supervised under order ID 12 (the sentenced detention) in relation to offence type 1350. In the second record, the offence is the same as in the first record because a) the offence types are the same and b) the offence ID is the same. A second record is required because the order ID is different (the parole order).
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. No null values. Youth Justice Offence file cluster Youth Justice, Standard 24/06/2024 Implementation start date: 01/07/2023 DSS specific information: The offence identifier allows for a single offence to be mapped to multiple orders. For example, a young person is serving a sentence in detention for offence type 1350. They are released on parole/supervised release in relation to this offence. The first record shows the young person was supervised under order ID 12 (the sentenced detention) in relation to offence type 1350. In the second record, the offence is the same as in the first record because a) the offence types are the same and b) the offence ID is the same. A second record is required because the order ID is different (the parole order).
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. No null values. Youth Justice Offence file cluster Youth Justice, Superseded 24/06/2024 DSS specific information: The offence identifier allows for a single offence to be mapped to multiple orders. For example, a young person is serving a sentence in detention for offence type 1350. They are released on parole/supervised release in relation to this offence. The first record shows the young person was supervised under order ID 12 (the sentenced detention) in relation to offence type 1350. In the second record, the offence is the same as in the first record because a) the offence types are the same and b) the offence ID is the same. A second record is required because the order ID is different (the parole order).
If the offence identifier matches the offence identifier of another record for the same person identifier, the offence types must be the same. No null values. |