Service episode—episode end date, DDMMYYYY

DSS specific information:

A date of expiry is when the order the child is under is no longer applicable. It should be recorded for each separate care and protection order episode. This can be for a number of reasons including:

The child is placed on a higher level order than the one they are currently on
The order expires
The child turns 18 years
The child moves interstate
The child dies
The child returns home and is no longer considered by the child protection authority to be in need of care.
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.

DSS specific information:

A date of expiry is when the order the child is under is no longer applicable. It should be recorded for each separate care and protection order episode. This can be for a number of reasons including:

The child is placed on a higher level order than the one they are currently on
The order expires
The child turns 18 years
The child moves interstate
The child dies
The child returns home and is no longer considered by the child protection authority to be in need of care.
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.

DSS specific information:

An end date is recorded for each separate out-of-home care episode of the client.

An end date is recorded when:

• the child is moved from one placement to another placement; it is part of the case plan for the child to formally leave the out-of-home care system; or
• the child is no longer a client of the community services department. This includes clients who turn 18 years and children who are no longer are in need of care.
  An unapproved break greater than 7 days (such as the child absconds) is counted as an exit.

The date is recorded when it is part of an agreed case plan for the child to no longer reside in the placement.

Where the child has absconded and does not return to the placement, the date is where the department deems that the placement has ceased. 

If the child does not exit this placement during the year, a data of 11111111 is used to indicate this.

If the date is unknown, the date 01011900 is provided.

This metadata item is used to determine the length of time in out-of-home care and the number of different carers.

DSS specific information:

An end date is recorded for each separate out-of-home care episode of the client.

An end date is recorded when:

• the child is moved from one placement to another placement; it is part of the case plan for the child to formally leave the out-of-home care system; or
• the child is no longer a client of the community services department. This includes clients who turn 18 years and children who are no longer are in need of care.
  An unapproved break greater than 7 days (such as the child absconds) is counted as an exit.

The date is recorded when it is part of an agreed case plan for the child to no longer reside in the placement.

Where the child has absconded and does not return to the placement, the date is where the department deems that the placement has ceased. 

If the child does not exit this placement during the year, a data of 11111111 is used to indicate this.

If the date is unknown, the date 01011900 is provided.

This metadata item is used to determine the length of time in out-of-home care and the number of different carers.

DSS specific information:

This data element should only be reported for CSTDA service users who have ceased receiving CSTDA-funded services from the service type outlet.

A service user is considered to leave a service when either:

• the service user ends the support relationship with the service outlet; or
• the service outlet ends the support relationship with the service user.

DSS specific information:

This data element should only be reported for CSTDA service users who have ceased receiving CSTDA-funded services from the service type outlet.

A service user is considered to leave a service when either:

• the service user ends the support relationship with the service outlet; or
• the service outlet ends the support relationship with the service user.

Implementation start date: 01/07/2009

DSS specific information:

This data element should only be reported for NDA service users who have ceased receiving NDA-funded services from the service type outlet.

A service user is considered to leave a service when either:

• the service user ends the support relationship with the service outlet; or
• the service outlet ends the support relationship with the service user.

Implementation start date: 01/07/2010

DSS specific information:

This data element should only be reported for NDA service users who have ceased receiving NDA-funded services from the service type outlet.

A service user is considered to leave a service when either:

• the service user ends the support relationship with the service outlet; or
• the service outlet ends the support relationship with the service user.

Implementation start date: 01/07/2011

DSS specific information:

This data element should only be reported for NDA service users who have ceased receiving NDA-funded services from the service type outlet.

A service user is considered to leave a service when either:

• the service user ends the support relationship with the service outlet; or
• the service outlet ends the support relationship with the service user.

Implementation start date: 01/07/2012

Implementation end date: 30/06/2013

DSS specific information:

In the DS NMDS this refers to the date on which the person ceased to be a service user of the NDA-funded service type outlet. It is only reported for service users who have ceased receiving NDA-funded disability support services from the service type outlet.

A service user is considered to leave a service when either:

• the service user ends the support relationship with the service outlet; or
• the service outlet ends the support relationship with the service user.

Implementation start date: 24/09/2009

DSS specific information:

A detention period is the period spent in a particular detention centre for a particular type of detention (pre-court detention, pre-sentence detention, sentenced detention). A detention period ends when:

•        the young person is released from detention

•        the young person is transferred to another detention centre

•        the young person is transferred to the custody of another jurisdiction (e.g. adult corrective services, police custody, interstate)

•        the type of detention changes (pre-court detention, pre-sentence detention, sentenced detention)

•        the young person escapes from detention or absconds

•        the young person dies.

Implementation start date: 01/07/2005

DSS specific information:

For the purposes of the Juvenile Justice NMDS, the episode's 'end date' is the 'exit date'-the date on which supervision or case management of the juvenile justice client, by the juvenile justice department under a specific legal arrangement, ends, or where there is a change in the type of supervision provided and/or the specific juvenile justice agency responsible.

An exit date should be recorded for each separate juvenile justice episode of the client.
An episode will end and an exit date recorded on discharge of the client from an episode of supervision or case management by the juvenile justice department under one of the types of intervention listed in the data domain of juvenile justice episode type. An Exit date should be recorded when:

• the client completes their supervision or case management and exits the juvenile justice system;
• the client completes their supervision or case management under one juvenile justice episode type but is then placed on another supervision or case management with a different juvenile justice episode type (for example, if a client completes remand and enters detention then an exit date would be recorded on discharge from remand);
• the client breaches resulting in a change in juvenile justice episode type (for example, if a juvenile on immediate release breaches their order and is returned to detention, then an exit date will be recorded for the immediate release and an entry date for detention). The date recorded should be the date the client was breached;
• If, for an existing client, another juvenile justice episode type which is ranked more highly on the ranking scale outlined under the description of juvenile justice episode begins;
• If the client dies;
• If a client is transferred from the juvenile justice system to the adult justice system;
• If a client is transferred from the jurisdiction to another State or Territory;
• If a client escapes an exit date should be recorded as at the time of escape.
• If a client on a custodial order (remand or detention) is transferred to a different place of custody within a jurisdiction (for example from a detention centre in Sydney to one in Wagga). This constitutes a change in episode and an exit date should be recorded for an episode in Sydney and an entry to an episode in Wagga.

In some circumstances an exit date will be the same as an entry date for a following juvenile justice episode (for example where a juvenile moves directly from detention to parole or supervised release).
A client can be recorded as being on only ONE juvenile justice episode at any point in time (i.e. they cannot have concurrent juvenile justice episodes). Therefore an Entry date must be followed by an Exit date for that episode, before another Entry date can be recorded. If a client is on 2 or more orders at a particular time in a jurisdiction, then the one considered the most serious should be recorded in the juvenile justice NMDS (with ranking as described in the juvenile justice episode data concept, with 1 being most serious and 12 being least serious).
If a client on a juvenile justice episode receives another order that is more highly ranked than the type of order for the original episode, then that original episode should be ended (and an Exit date recorded as the date the new more highly ranked type of order began). A new episode should be commenced (with an Entry date recorded as the date the new more highly ranked order began). The juvenile justice episode type of the second episode will be that of the more highly ranked type of order.
If the second order is of a lower ranking there will be no change in episode and no Exit date or Entry date recorded at the time the new order commences.
However, if the first order is completed by the juvenile, and the second order still applies and is the highest ranked order that is current at the time, then it should be recorded at that point. The Exit date for the second more highly ranked order will be when the client has been deemed to have completed the order. The Entry date for the lower ranked order will be the same date as the Exit date from the higher order, as that is the date when it becomes the most highly ranked order applying to the juvenile.
Approved leave does not constitute a discharge or new admission and so no exit date should be recorded on return from leave.
Escape, if the juvenile is absent for less than 2 days, does not constitute a discharge or new admission and so no exit date should be recorded on return.
Only those breaches resulting in a change in the juvenile justice episode type or a change in the place of custody will signal the end of an episode.
A return to court does not necessarily signal the end of an episode. If it results in no change in juvenile justice episode type of the client, or (if on a custodial intervention) in their place of custody, then a return to court will not constitute a discharge and new episode. For example, a youth on remand may return to court several times (for hearings, outcome, sentencing etc). During this time the type of intervention has not changed or the place of remand. In this case the returns to court would not constitute the end of an episode. However, under this scenario, if the court changed the place of remand of the juvenile, then this would constitute a new episode. If the juvenile is found guilty the commencement of the sentence imposed by the court would also mark the end of the episode of remand and the beginning of a new episode.

Implementation start date: 24/09/2009

DSS 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.

DSS specific information:

Implementation start date: 01/07/2011

Implementation start date: 01/07/2012

Implementation end date: 30/06/2013

Implementation start date: 01/07/2013

Implementation end date: 30/06/2014

Conditional obligation:

DSS specific information: