1 | Child protection (CP) client file cluster | 492589 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: The person identifier (ID) is the identifier for the child (the child protection client). Each ID is used by only one client and each client has only one ID. The person ID in the Child protection client file must appear in at least one of the Notifications, investigations and substantiations (NIS), Care and protection order (CPO) and/or Living arrangements for children under care (LA) files. All person IDs in the NIS, CPO, LA, National out-of-home care standards, and Sibling files must appear once in the client file. |
2 | Letters of family name | 349481 | String
[3]
| XXX A combination of alphanumeric characters. | DSS specific information: 'Letters of name' is collected as one item in cell number 2 in the Client file of the CP National minimum data set (NMDS). 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. For children who were unborn at the time of the notification and who were subsequently born by 31 August, letters of name should reflect the name given to the child following birth. |
3 | Letters of given name | 349483 | String
[2]
| XX A combination of alphanumeric characters. | DSS specific information: 'Letters of name' is collected as one item in cell number 2 in the Client file of the CP NMDS. 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. For children who were unborn at the time of the notification and who were subsequently born by 31 August, letters of name should reflect the name given to the child following birth. |
4 | Date of birth | 287007 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | DSS specific information: For children who were unborn at the time of the notification, estimated age can be calculated (e.g. – 1 month if due to be born in one month) from which an estimated date of birth (DOB) can be determined. For children who were unborn at the time of the notification and who were subsequently born by 31 August, date of birth should be updated where possible. When an estimate is required, all known fields should be entered (e.g. if only year is known use 01/01/YYYY, if year and month are known use 01/MM/YYYY. If the date is not known and cannot be estimated, record as 01/01/1900. If it is not applicable to record a date (i.e. the child has not not been born by 31 August), record as 01/01/9999. |
5 | Sex | 287316 | Number
[1]
| 1 | Male | 2 | Female | 3 | Intersex or indeterminate | 9 | Not stated/inadequately described |
| DSS specific information: For unborn children whose sex is unknown, 97 'Not applicable' should be recorded. Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection NMDS collection manual. |
6 | Indigenous status | 291036 | Number
[1]
| 1 | Aboriginal but not Torres Strait Islander origin | 2 | Torres Strait Islander but not Aboriginal origin | 3 | Both Aboriginal and Torres Strait Islander origin | 4 | Neither Aboriginal nor Torres Strait Islander origin | 9 | Not stated/inadequately described |
| DSS specific information: Record 5 'Indigenous - not further specified' where no differentiation between Aboriginal and Torres Strait Islander is made. This code is used in the CP NMDS and is not mappable to the Indigenous status standard. Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection NMDS collection manual. |
7 | Main language other than English spoken at home | 460125 | Number
[4]
| NN{NN} The Australian Standard Classification of Languages (ASCL 2011) code set representing languages. | |
8 | Disability status | 608048 | Boolean
[1]
| 1 | Yes | 2 | No | 9 | Not stated/inadequately described |
| DSS specific information: For unborn children, 97 ‘Not applicable’ should be recorded. Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection NMDS collection manual. |
9 | Child protection new client indicator | 521821 | Boolean
[1]
| 1 | Yes | 2 | No | 9 | Not stated/inadequately described |
| DSS specific information: Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection NMDS collection manual. |
2 | Notifications, investigations, and substantiations (NIS) file cluster | 492995 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: The identifier should match the child's identifier in the Child protection (CP) client file cluster. |
2 | Notification date | 455248 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | |
3 | Australian state/territory identifier (person) | 286919 | Number
[1]
| 1 | New South Wales | 2 | Victoria | 3 | Queensland | 4 | South Australia | 5 | Western Australia | 6 | Tasmania | 7 | Northern Territory | 8 | Australian Capital Territory | 9 | Other territories (Cocos (Keeling) Islands, Christmas Island and Jervis Bay Territory) |
| DSS specific information: The state/territory of the child’s usual place of residence at the time of the notification. |
4 | Suburb/town/locality name within address | 429889 | String
[46]
| X[X(45)]
A combination of alphanumeric characters. | DSS specific information: Any valid suburb, town or locality name of the child's usual place of residence at the time of notification. May be 'No fixed abode' or 'Not known'. |
5 | Australian postcode (address) | 429894 | Number
[4]
| {NNNN}
The Postcode datafile code set representing Australian postcodes as defined by Australia Post. | DSS specific information: The postcode of the child's usual place of residence at the time of notification. |
6 | Statistical area level 2 (SA2) | 457289 | String
[9]
| N(9) A code set representing a medium-sized area built from whole Statistical areas level 1 (SA1s). The aim of Statistical areas level 2 (SA2s) is to represent a community that interacts together socially and economically. | DSS specific information: The Statistical Area level 2 (SA2) of the child's usual place of residence at the time of the notification. |
7 | Source of notification | 655834 | Number
[2]
| 1 | Subject child | 2 | Parent/guardian | 3 | Sibling/Other relative | 4 | Friend/neighbour | 5 | Medical practitioner | 6 | Other health personnel | 7 | Hospital/health centre | 8 | Social worker | 9 | School personnel | 10 | Child care personnel | 11 | Police | 12 | Departmental officer | 13 | Non-government organisation | 14 | Anonymous | 88 | Other | 99 | Not stated/inadequately described |
| |
8 | Notification course of action | 455327 | Number
[1]
| 1 | Investigation required and commenced | 2 | Investigation required but not yet commenced | 3 | Other intervention required | 4 | No further action/no issue | 5 | Advice/referral to another agency required | 6 | Assessment decision in process |
| |
9 | Course of action decision date | 455338 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | |
10 | Investigation commencement date (child protection) | 455361 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | Conditional obligation: Conditional on the outcome of the notification assessment deeming investigation necessary. |
11 | Investigation conclusion date (child protection notification) | 456528 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | DSS specific information: Conditional on the outcome of the notification assessment deeming investigation necessary. |
12 | Investigation status (child protection) | 455404 | Number
[2]
| 1 | Substantiated | 2 | Not substantiated | 3 | Investigation in process | 4 | Investigation closed - no outcome possible | 97 | Not applicable |
| DSS specific information: Conditional on the outcome of the notification assessment deeming investigation necessary. |
13 | Household parental care type (child protection) | 455803 | Number
[2]
| 1 | Two parent— natural | 2 | Two parent—step or blended | 3 | One parent— female | 4 | One parent— male | 5 | Other relatives/kin | 6 | Foster care | 88 | Other | 99 | Not stated/inadequately described |
| DSS specific information: Refers to the care type at the time of notification of child abuse or neglect. |
14 | Primary type of abuse or neglect (child protection) | 455487 | Number
[2]
| 1 | Physical abuse | 2 | Sexual abuse | 3 | Emotional abuse | 4 | Neglect | 97 | Not applicable | 99 | Not stated/inadequately described |
| |
15 | Other type of abuse or neglect (child protection) | 455510 | Number
[2]
| 1 | Physical abuse | 2 | Sexual abuse | 3 | Emotional abuse | 4 | Neglect | 97 | Not applicable | 99 | Not stated/inadequately described |
| Conditional obligation: Only to be used when more than one type of abuse has been identified. DSS specific information: Four separate data items are used to collect the other types of abuse identified as part of the substantiation: physical abuse (cell number 15); sexual abuse (cell number 16); emotional abuse (cell number 17); and neglect (cell number 18). |
3 | Care and protection order (CPO) file cluster | 492993 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: The person identifier (ID) is the identifier for the child (the child protection client) within a State or Territory. The person ID in the Care and protection order file must appear in the Child Protection client file. |
2 | Order start date | 536550 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | DSS specific information: 'Order start date' is the date the Care and protection order came into effect and must be equal to or preceding 'Order end date'. Valid date occurs on or before the 31 August reference period. When an estimate is required, all known fields should be entered (e.g. if year and month are known use 01/MM/YYY; if the exact date is unknown but the reporting period to which it relates can be determined, use 01/07/YYYY). If the date is not known and can't be estimated, please record 01/01/1900. |
3 | Care and protection order type | 458546 | Number
[2]
| 1 | Finalised guardianship or custody order | 2 | Finalised third party parental responsibility order | 3 | Finalised supervisory order | 4 | Interim and temporary order | 5 | Administrative arrangement | 6 | Assessment order | 7 | Other | 99 | Not stated/inadequately described |
| |
4 | First order indicator (child protection) | 458347 | Boolean
[1]
| 1 | Yes | 2 | No | 9 | Not stated/inadequately described |
| DSS specific information: Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection national minimum data set collection manual. |
5 | NOOHCS order indicator | 527865 | Boolean
[1]
| 1 | Yes | 2 | No | 9 | Not stated/inadequately described |
| DSS specific information: Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection national minimum data set collection manual. |
6 | Order end date | 536554 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | DSS specific information: 'Order end date' is the date the care and protection order is no longer applicable and must be equal to or later than 'Order start date'. Valid date, if applicable, occurs between 1 July of the first reporting period and 31 August following the last reporting period.
When an estimate is required, all known fields should be entered (e.g. if year and month are known use 01/MM/YYY; if the exact date is unknown but the reporting period to which it relates can be determined, use 01/07/YYYY). If the date is not known and can't be estimated, please record 01/01/1900. If it is not applicable to record a date (i.e. the order had not ended by the end of the reference period) please record 01/01/9999 for this item. |
7 | Episode start date | 651687 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | DSS specific information: Where the care and protection order was part of a preceding continuous order episode, this item records the start date of the first order in the episode. An order episode is the period of time in which a child remains on an order. During this period, a child may be on one or more different orders. If a child is discharged from an order and a new care and protection order/arrangement is applied in five (5) days or less of the discharge, the orders are deemed to be consecutive (i.e. the continuous episode of care will include both order). However, a break of more the five (5) days will break the continuity of care. Valid date, if applicable, occurs on or before 31 August following the reference period. Date must precede 'Order start date'. When an estimate is required, all known fields should be entered (e.g. if year and month are known use 01/MM/YYYY; if the exact date is unknown but the reporting period to which it relates can be determined, use 01/07/YYYY). If the date is not known and can’t be estimated, record 01/01/1900. If it is not applicable to record a date (i.e. the order was not part of a preceding continuous order episode), please record 01/01/9999. |
4 | Living arrangements for children under care (LA) file cluster | 492989 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: The person identifier (ID) is the identifier for the child (the child protection client). Each ID is used by only one client and each client has only one ID.
The person ID in the Living arrangements file must appear in the Client file. |
2 | Living arrangement start date | 474217 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | |
3 | Suburb/town/locality name within address | 429889 | String
[46]
| X[X(45)]
A combination of alphanumeric characters. | DSS specific information: The suburb/town/locality name of the child's living arrangement. |
4 | Australian postcode (address) | 429894 | Number
[4]
| {NNNN}
The Postcode datafile code set representing Australian postcodes as defined by Australia Post. | DSS specific information: The postcode of the child's living arrangement. Record code 9999 for 'not stated/inadequately described'. |
5 | Statistical area level 2 (SA2) | 457289 | String
[9]
| N(9) A code set representing a medium-sized area built from whole Statistical areas level 1 (SA1s). The aim of Statistical areas level 2 (SA2s) is to represent a community that interacts together socially and economically. | DSS specific information: The Statistical area level 2 (SA2) of the child's living arrangement. Record 99 for 'not stated/inadequately described'. |
6 | Financial payment indicator for out-of-home care placement | 652697 | Number
[2]
| 1 | Child protection authority made a direct financial contribution | 2 | Child protection authority offered a direct financial contribution but it was declined by the carer | 3 | Child protection authority made no financial contribution | 99 | Not stated/inadequately described |
| |
7 | Living arrangement type | 620517 | Number
[2]
| 1 | Residential care | 2 | Family group home | 3 | Relatives/kin who are reimbursed | 4 | Foster care | 5 | Other home-based care (reimbursed) | 6 | Relatives/kin who are not reimbursed | 7 | Independent living | 8 | Parents | 9 | Detention | 88 | Other living arrangement | 99 | Not stated/inadequately described |
| |
8 | Respite placement indicator | 529749 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| Conditional obligation: Conditional on the child living in a funded out-of-home care placement provided by a funded agency. DSS specific information: This data collection uses an alternate code set. Code 97 ('Not applicable') should be mapped to Code 7 ('Not applicable') in the data element. Code 99 ('Not stated/inadequately described') should be mapped to Code 9 ('Not stated/inadequately described') in the data element. |
9 | Relationship of carer to child | 652013 | Number
[2]
| 1 | Grandparent | 2 | Aunt or uncle | 3 | Sibling | 4 | Other relative | 5 | Non-familial relationship | 6 | Other Indigenous kinship relationship | 88 | Other | 97 | Not applicable | 99 | Not stated/inadequately described |
| |
10 | Indigenous agency placement indicator | 529740 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| Conditional obligation: Conditional on the child being Indigenous and living in a funded out-of-home care placement provided by a funded agency. DSS specific information: This data collection uses an alternate code set. Code 97 ('Not applicable') should be mapped to Code 7 ('Not applicable') in the data element. Code 99 ('Not stated/inadequately described') should be mapped to Code 9 ('Not stated/inadequately described') in the data element. |
11 | Caregiver type for Indigenous child | 524944 | Number
[2]
| 1 | Indigenous relative/kin | 2 | Other relative/kin | 3 | Other Indigenous caregiver | 4 | Indigenous residential care | 5 | Indigenous family group home | 6 | Other non-Indigenous caregiver | 7 | Non-Indigenous residential care | 8 | Non-Indigenous family group home | 9 | Independent living | 88 | Other | 97 | Not applicable | 99 | Not stated/inadequately described |
| Conditional obligation: Conditional on the child being Indigenous and living in a funded out-of-home care placement provided by a funded agency. DSS specific information: For the purpose of this data element cluster, the object class of this data element is understood to include residential care and family group homes, which are not private households. |
12 | Carer household identifier | 529752 | String
[13]
| | DSS specific information: Each carer household has only one ID. Each ID is only used by one carer household. Each carer household may include one or more authorised carers (i.e. one or more Carer (person) IDs may be recorded under each carer household ID). Code 97 'Not applicable' should be recorded if it is not applicable to record carer household ID (i.e. if the child is not living with a carer in a funded out-of-home care placement (e.g. living with parents, independent living, other living arrangements)). For the purpose of this data element cluster, the object class of this data element is understood to include residential care and family group homes, which are not private households. This means that the carer household ID in the Carer household authorisation file will be a subset of the carer household ID in the Living arrangements file as residential care and family group homes are not included in the scope of carers in the carer household authorisation file. |
13 | Living arrangement end date | 474223 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | |
14 | Episode start date | 651687 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | Conditional obligation: Conditional on the child being in a funded out-of-home care placement. DSS specific information: Where the funded out-of-home care placement was part of a preceding continuous episode of care, this is the start date of the first placement in the episode. Episode of care is the period of time in which a child remains in out-of-home care. During this period, a child may have one or more different out-of-home care placements, including respite/temporary placements lasting less than 7 days. If a child has a return home or break of less than 60 days before returning to the same or different placement they are considered to be continuously in care during this period. However, any break of 60 days or more is deemed to be an exit from out-of-home care and will break the continuity of care. Valid date, if applicable, occurs on or before 31 August following the reference period. The date must be preceding 'Living arrangement start date'. Note: Respite/temporary funded out-of-home care placements lasting less than 7 days should be included when determining the start date of a continuous episode of care. When an estimate is required, all known fields should be entered (e.g. if year and month are known use 01MMYYYY; if the exact date is unknown but the reporting period to which it relates can be determined, use 0107YYYY). If the date is not known and can’t be estimated, record 01011900. If it is not applicable to record a date (i.e. the living arrangement is not a funded out-of-home care placement or was not part of a preceding continuous episode of care e.g. this is the first placement in an episode of care), please record 01019999. |
15 | Number of funded out-of-home care placements | 652026 | Number
[3]
| N[NN] The total, sum, count, or aggregate of a collection of units. | Conditional obligation: Conditional on the child being in funded out-of-home care placements. DSS specific information: This data element should reflect an iterative count of the number of unique placements as at each record in the episode. If this cannot be provided the total unique placements for the episode can be recorded. |
5 | Carer demographics file cluster | 493178 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: The person identifier is the identifier of the carer. |
2 | Letters of family name | 349481 | String
[3]
| XXX A combination of alphanumeric characters. | DSS specific information: 'Letters of carer's name' is collected as one item in cell number 2 in the Carer demographics file of the CP NMDS. The 2nd, 3rd and 5th letters of the carer's family name are combined with the 2nd and 3rd letters of the carer's given name to obtain the 5 digit letters of the carer's name. |
3 | Letters of given name | 349483 | String
[2]
| XX A combination of alphanumeric characters. | DSS specific information: 'Letters of carer's name' is collected as one item in cell number 2 in the Carer demographics file of the CP NMDS. The 2nd, 3rd and 5th letters of the carer's family name are combined with the 2nd and 3rd letters of the carer's given name to obtain the 5 digit letters of the carer's name. |
4 | Date of birth | 287007 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | DSS specific information: The date of birth of the carer. When an estimate is required, all known fields should be entered (e.g. if only year is known use 01/01/YYYY, if year and month are known use 01/MM/YYYY. If the date is not known and cannot be estimated, record as 01/01/1900. |
5 | Sex | 287316 | Number
[1]
| 1 | Male | 2 | Female | 3 | Intersex or indeterminate | 9 | Not stated/inadequately described |
| DSS specific information: The biological sex of the carer. Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection national minimum data set collection manual. |
6 | Indigenous status | 291036 | Number
[1]
| 1 | Aboriginal but not Torres Strait Islander origin | 2 | Torres Strait Islander but not Aboriginal origin | 3 | Both Aboriginal and Torres Strait Islander origin | 4 | Neither Aboriginal nor Torres Strait Islander origin | 9 | Not stated/inadequately described |
| DSS specific information: Record 5 'Indigenous - not further specified' where no differentiation between Aboriginal and Torres Strait Islander is made. This code is used in the CP NMDS and is not mappable to the Indigenous status standard. Code 9 'Not stated/inadequately described' in the data element is equivalent to code 99 in the Child protection national minimum data set collection manual. |
6 | Carer household authorisation file cluster | 493492 |
|
| |
1 | Carer household identifier | 529752 | String
[13]
| | DSS specific information: Each carer household has only one identifier (ID). Each ID is only used by one carer household. Each carer household may include one or more authorised carers (i.e. one or more Carer (person) IDs may be recorded under each carer household ID). Note: The carer household ID in the Carer household authorisation file will be a subset of the carer household ID in the Living arrangements file as residential care and family group homes are not included in the scope of carers in the Carer household authorisation file. |
2 | Carer household authorisation type | 531748 | Number
[2]
| 1 | Foster care only | 2 | Relative/kinship care only | 3 | Both foster and relative/kinship care | 4 | Provisionally approved | 5 | Respite only | 6 | Long term guardianship | 99 | Not stated/inadequately described |
| |
3 | Carer household authorisation start date | 531704 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | |
4 | Carer household authorisation end date | 531768 | Date/Time
[8]
| DDMMYYYY
The day of a particular month and year. | |
5 | New carer household indicator | 532827 | Boolean
[1]
| 1 | Yes | 2 | No | 9 | Not stated/inadequately described |
| |
6 | Indigenous carer household | 531773 | Boolean
[1]
| 1 | Yes | 2 | No | 9 | Not stated/inadequately described |
| |
7 | Number of carers | 532834 | Number
[2]
| 99 | Not stated/inadequately described |
| |
8 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: The person identifier is the Carer ID and is recorded for each individual carer authorised to provide care in a carer household (e.g. Carer ID 1, Carer ID 2, Carer ID 3, etc). |
7 | National Out-of-Home Care Standards (NOOHCS) file cluster | 493020 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: This identifier is for the child. |
2 | Case plan required indicator | 610414 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: Refers to a case plan at 30 June in the reference period. This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
3 | Current case plan indicator | 610411 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: Refers to a current case plan at 30 June in the reference period. This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
4 | Cultural support plan required indicator | 529655 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: Refers to a cultural support plan at 30 June in the reference period. This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
5 | Current cultural support plan indicator | 529663 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: Refers to a current cultural support plan at 30 June in the reference period. This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
6 | Leaving care plan required indicator | 493090 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: Refers to a leaving care plan at 30 June of the reference period. This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
7 | Current leaving care plan indicator | 493102 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: Refers to a current and approved current leaving care plan at 30 June in the reference period. This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
8 | Initial health check required indicator | 529672 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
9 | Initial health check conducted indicator | 529681 | Number
[1]
| 1 | Yes | 2 | No | 7 | Not applicable | 9 | Not stated/inadequately described |
| DSS specific information: This data collection uses an alternate code set for this data element. Code 97 ('Not applicable') should be mapped to Code 7. Code 99 ('Not stated/inadequately described') should be mapped to Code 9. |
8 | Sibling file cluster | 525049 |
|
| |
1 | Child protection person identifier | 459397 | String
[13]
| | DSS specific information: Each child protection client (child) has a unique person identifier (ID). Each person ID is used by only one client and each client has only one ID. The person ID of the subject child in funded out-of-home care and the person ID of each known sibling (of the subject child) in a funded out-of-home care placement on the night of 30 June (regardless of whether they are in the same placement) is recorded. For each two-person relationship each person identifier will be recorded twice; once as the subject child Person ID and once as the sibling Person ID. |
2 | Sibling relationship | 529702 | Number
[2]
| 1 | Full sibling | 2 | Half sibling | 99 | Not stated/inadequately described |
| |