-
Cluster Care and protection order (CPO) DSS Pilot (2010) Optional 1 - Child protection notification—identifier, NX[X(13)] Conditional obligation:
Only applicable if the jurisdiction records a notification identifier.DSS specific information:
This data element should align with the identifier recorded in the Notifications, investigations, and substantiations (NIS) DSS.
This not a mandatory field and there will be cases where children are on an order without a preceding notification.
Conditional 1 - Child—first care and protection order indicator, yes/no/not stated/inadequately described code N DSS specific information:
In the Care and protection order episode DSS, this data element refers to whether the current order is the first time an order has been applied to an individual within a specific jurisdiction.
Mandatory 1 - Order episode—order start date, DDMMYYYY DSS specific information:
An entry date should be recorded for each separate care and protection order episode of the child.
A new episode will begin and an entry date will be recorded in the following circumstances:
A child is placed on a care and protection order for the first time in their life. A child is placed on a higher level order than the one they are currently on. The higher level order expires and the child is placed on a lower level order. This date will be recorded once the higher level order expires. A child moves from one jurisdiction to another and the order is transferred to the second jurisdiction.
In some circumstances, the entry date will be the same as the exit date from a previous episode, e.g. when a child moves directly from one level order to a different level order.
This data item delineates a care and protection order episode and is qualified by reason for entry.
If the date is unknown, the date 01011900 should be provided.
Mandatory 1 - Order—order type, care and protection code N[N] Mandatory 1 - Person—order type (local), identifier X[50] DSS specific information:
This refers to the local code used within the jurisdiction to identify the type of care and protection order to which a child was subject.Mandatory 1 - Person—order type (local), text A[A(99)] DSS specific information:
This refers to the local description within the jurisdiction of the type of care and protection order to which the child was subject.Mandatory 1 - Person—person identifier, child protection NX[X(11)] Mandatory 1 - Service episode—order end date, DDMMYYYY Conditional obligation:
Only applicable if an order has expired.DSS specific information:
An order expiry date is when the order the child is under is no longer applicable. This can be for a number of reasons including:
The child is placed on another type of order The child turns 18 years The child moves interstate/overseas The child dies The child is no longer considered by the child protection authority to be at risk/in need of protection.
The order expiry date should be recorded for each separate care and protection order. In some circumstances, the date of expiry will be the same as the entry date from a previous episode, e.g. when a child moves directly from one level order to another level order.
If the order did not expire during the year, the date 11111111 should be used to indicate this.
If the date is unknown, the date 01011900 should be provided.
Conditional 1 - Service episode—reason for order expiry, care and protection code N[N] Conditional obligation:
Only applicable if an order has expired.Conditional 1 -
Cluster Child protection and support services (CPSS) client DSS Pilot (2010) Mandatory 1 -
Cluster Child protection client alias cluster Conditional obligation:
This cluster should only be collected if the client has been known to the Department responsible for child protection prior to this instance of being a client.Conditional 1 - Person—letters of family name, text XXX DSS specific information:
The 2nd, 3rd and 5th letters of the client's family name are combined with the 2nd and 3rd letters of the client's given name to obtain the 5 digit letters of the client's name.Mandatory 99 - Person—letters of given name, text XX DSS specific information:
The 2nd and 3rd letters of the client's given name are combined with the 2nd, 3rd and 5th letters of the client's family name to obtain the 5 digit letters of the client's name.Mandatory 99 - Person—person identifier, child protection NX[X(11)] DSS specific information:
This item is collected at least twice in the client alias file. The first occurence of this data element must match the identifier in the Child protection and support services (CPSS) client DSS exactly. The second and subsequent occurrences are identifiers which may have been allocated prior to the child being identified as an existing client.Mandatory 99 - Date—estimate indicator, code N Conditional obligation:
Only applicable if date of birth or date of death are uncertain.DSS specific information:
The date estimate indicator is applied to both the date of birth and the date of death (if applicable). Conditional 2 - Person (address)—Australian postcode, code (Postcode datafile) {NNNN} DSS specific information:
In the client file the postcode of the child refers to their postcode prior to first ever entry into care.Mandatory 1 - Person (address)—suburb/town/locality name, text A[A(49)] DSS specific information:
In the client file the suburb/town/locality of the child refers to their suburb/town/locality prior to first ever entry into care.Mandatory 1 - Person—date of birth, DDMMYYYY DSS specific information:
For unborn children, estimated age can be calculated (e.g. – 1 month if due to be born in one month) from which an estimated DOB can be determined. DOB would be updated when the child is born.Mandatory 1 - Person—date of death, DDMMYYYY Conditional obligation:
Conditional on a death of the child in the CPSS collection. Conditional 1 - Person—disability group, child protection code N[N] Conditional obligation:
Conditional on responding '1. Yes' to the disability status data element.DSS specific information:
If a child has multiple disabilities, each disability group experienced by the child should be recorded.Conditional 6 - Person—disability status, code N Mandatory 1 - Person—geographic location (LGA), code (ASGC 2010) NNNNN DSS specific information:
In the client file the local government area of the child refers to their local government area prior to first ever entry into care.Mandatory 1 - Person—Indigenous status, code N Mandatory 1 - Person—letters of family name, text XXX DSS specific information:
The 2nd, 3rd and 5th letters of the client's family name are combined with the 2nd and 3rd letters of the client's given name to obtain the 5 digit letters of the client's name.
Mandatory 1 - Person—letters of given name, text XX DSS specific information:
The 2nd and 3rd letters of the client's given name are combined with the 2nd, 3rd and 5th letters of the client's family name to obtain the 5 digit letters of the client's name.Mandatory 1 - Person—main language other than English spoken at home, code (ASCL 2005) NN{NN} Mandatory 1 - Person—person identifier, child protection NX[X(11)] Mandatory 1 - Person—sex, code N DSS specific information:
For unborn children whose sex is unknown, 9 'Not stated/inadequately described' should be recorded.Mandatory 1 -
Cluster Living arrangements for children under care (LA) DSS Pilot (2010) Optional 1 - Child protection notification—identifier, NX[X(13)] Conditional obligation:
Only applicable if the jurisdiction records a notification identifier.DSS specific information:
This data element should align with the identifier recorded in the Notifications, investigations, and substantiations (NIS) DSS.
This not a mandatory field and there will be cases where children are on an order or in funded out-of-home care placements without a preceding notification.
Conditional 1 - Child—care arrangement end date, DDMMYYYY DSS specific information:
In the Living Arrangements DSS, this refers to the date the living arrangements ended for a child under the care of the Department responsible for child protection.Mandatory 1 - Child—care arrangements, child protection code N[N] Mandatory 1 - Child—out-of-home care exit status, code N[N] Conditional obligation:
Conditional on the child being in an out-of-home placement.
Conditional 1 - Person (address)—Australian postcode, code (Postcode datafile) {NNNN} DSS specific information:
The postcode of the child’s living arrangement.Mandatory 1 - Person (address)—suburb/town/locality name, text A[A(49)] DSS specific information:
The suburb/town/locality name of the child’s living arrangement.Mandatory 1 - Person—care arrangement start date, DDMMYYYY DSS specific information:
In the Living Arrangements DSS, this refers to the date the living arrangements started for a child under the care of the Department responsible for child protection.Mandatory 1 - Person—geographic location (LGA), code (ASGC 2010) NNNNN DSS specific information:
The local government area of the child’s living arrangement.Mandatory 1 - Person—Indigenous status, code N DSS specific information:
In the Living arrangements for children under care DSS, this metadata item refers to the Indigenous status of the child and the carer.Mandatory 2 - Person—person identifier, child protection NX[X(11)] DSS specific information:
This data element is collected twice in the Living arrangements for children under care DSS:
for the child within a state or territory’s child protection system and for the carer, i.e. an individual that provides funded out-of-home care within a state or territory’s child protection system Mandatory 2 - Person—relationship to reference person, relationship of carer to child code N[N] Mandatory 1 - Service episode—financial payment indicator, out-of-home placement code N Conditional obligation:
Conditional on the child being in an out-of-home placement. Conditional 1 - Service provider organisation—Indigenous specific organisation indicator, code N Conditional obligation:
Conditional on the child being in an out-of-home placement.DSS specific information:
In the Living arrangements DSS, the metadata item is used to determine whether the organisation provides funded out-of-home care placements specifically for, and by Indigenous people.Conditional 1 - Service provider organisation—Indigenous specific site indicator, code N Conditional obligation:
Conditional on the child being in an out-of-home placement.DSS specific information:
In the Living arrangements DSS, the metadata item is used to determine whether the physical location of a funded out-of-home care placement is provided specifically for, and by Indigenous people.Conditional 1 - Service provider organisation—organisation identifier, child protection NX[X(13)] Conditional obligation:
Conditional on the child being in an out-of-home placement.DSS specific information:
In the Living arrangements DSS, the organisation identifier refers to the organisation that provides funded out-of-home care within a state or territory.Conditional 1 - Service provider organisation—site identifier, child protection NX[X(13)] Conditional obligation:
Conditional on the child being in an out-of-home placement.DSS specific information:
In the Living arrangements DSS, the site identifier refers to the physical location where funded out-of-home care is provided within a state or territory.Conditional 1 -
Cluster Notifications, investigations, and substantiations (NIS) DSS Pilot 2010 Optional 1 - Child protection notification—actions related to substantiated abuse, text [X(100)] Conditional obligation:
Conditional on the substantiation of abuse/neglect.Conditional 1 - Child protection notification—assistance type, child protection code N Conditional 6 - Child protection notification—course of action decision date, DDMMYYYY Mandatory 1 - Child protection notification—course of action, code N Mandatory 1 - Child protection notification—employment service type, child protection code N[N] Mandatory 1 - Child protection notification—identifier, NX[X(13)] Optional 1 - Child protection notification—injuries related to substantiated abuse, text [X(100)] Conditional obligation:
Conditional on the substantiation of abuse/neglect.Conditional 1 - Child protection notification—investigation commencement date, DDMMYYYY Conditional obligation:
Conditional on the outcome of the notification assessment deeming investigation necessary.Conditional 1 - Child protection notification—investigation conclusion date, DDMMYYYY DSS specific information:
Conditional on the outcome of the notification assessment deeming investigation necessary.Conditional 1 - Child protection notification—investigation status, code N[N] DSS specific information:
Conditional on the outcome of the notification assessment deeming investigation necessary.Conditional 1 - Child protection notification—no suitable caregiver indicator, yes/no code N Mandatory 1 - Child protection notification—notification date, DDMMYYYY Mandatory 1 - Child protection notification—relationship to child of person believed responsible for abuse or neglect, code NN Mandatory 1 - Child protection notification—source of notification, code N[N] Mandatory 1 - Child protection notification—unborn child status, code N Mandatory 1 - Child—household parental care type, code N[N] Conditional obligation:
DSS specific information:
Refers to the care type at the time of notification of child abuse or neglect.Mandatory 1 - Child—other type of abuse or neglect, code N[N] Conditional obligation:
Only to be used when more than one type of abuse has been identified.DSS specific information:
This item may have multiple occurences with two collection periods:
Any other types of abuse or neglect identifed in the notification to the department responsible for child protection
Any other types of abuse or neglect substantiated by the investigating officer Conditional 6 - Child—primary type of abuse or neglect, code N[N] DSS specific information:
This item may have two occurences:
the primary type of abuse or neglect identifed in the notification to the department responsible for child protection
The primary type of abuse or neglect substantiated by the investigating officer Mandatory 2 - Person (address)—Australian postcode, code (Postcode datafile) {NNNN} Conditional obligation:
In the Notifications, investigations and substantiations (NIS) cluster the data element refers to the postcode where the child was living at the time of the notification.
Mandatory 1 - Person (address)—suburb/town/locality name, text A[A(49)] DSS specific information:
In the Notifications, investigations and substantiations (NIS) cluster the data element refers to the suburb/town/locality name where the child was living at the time of the notification.
Mandatory 1 - Person—geographic location (LGA), code (ASGC 2010) NNNNN Conditional obligation:
In the Notifications, investigations and substantiations (NIS) cluster the data element refers to the local government area (LGA) where the child was living at the time of the notification.
Mandatory 1 - Person—person identifier, child protection NX[X(11)] DSS specific information:
The identifier recorded under this data element should match the identifier recorded in the Child protection and support services (CPSS) client DSS.
Mandatory 1 -
Cluster Safety in out-of-home care (Safety) DSS Pilot 2010 Optional 1 1 Person—person identifier, child protection NX[X(11)] Mandatory 1 2 Child—substantiation whilst in care indicator, yes/no code N Mandatory 1 3 Child—living in the same household as person believed responsible for abuse, neglect or risk of harm indicator, code N Conditional obligation:
This data element is only valid if 'yes' is recorded for Child—substantiation whilst in care indicator, yes/no code N.Conditional 1 4 Person—substantiation date for an abuse or neglect claim within an out-of-home care placement, DDMMYYYY Conditional obligation:
This data element is only valid if 'yes' is recorded for Child—substantiation whilst in care indicator, yes/no code N.Conditional 1