Service episode—episode end date, DDMMYYYY
Data Element Attributes
Identifying and definitional attributes | |
Metadata item type:![]() | Data Element |
---|---|
Short name:![]() | Episode end date |
Synonymous names:![]() | Service exit date; Exit date; End date; Support period end date; Date of expiry; Date of exit; Order end date; Detention end date |
METEOR identifier:![]() | 692003 |
Registration status:![]() | Disability, Standard 05/07/2019 Homelessness, Standard 10/08/2018 |
Definition:![]() | The date on which a service episode was completed, expressed as DDMMYYYY. |
Data Element Concept:![]() | Service episode—episode end date |
Value Domain:![]() | Date DDMMYYYY |
Value domain attributes | ||
Representational attributes | ||
Representation class:![]() | Date | |
---|---|---|
Data type:![]() | Date/Time | |
Format:![]() | DDMMYYYY | |
Maximum character length:![]() | 8 |
Source and reference attributes | |
Submitting organisation:![]() | Australian Institute of Health and Welfare |
---|
Data element attributes | |
Collection and usage attributes | |
Guide for use:![]() | May occur after or on the same day as date of last delivery of service. Due to the considerable variation in the types of services provided in the community services sector, it is not possible at this stage to define in generic terms what will constitute completion of a service episode. Individual collections should however define what constitutes completion for their own purposes. This metadata item should always be recorded as an 8 digit valid date comprising day, month and year. Year should always be recorded in its full 4 digit format. For days and months with a numeric value of less than 10, zeros should be used to ensure that the date contains the required 8 digits. For example if a service episode is completed on July 1 2000 the date assistance completed should be recorded as 01072000 as specified by the format. |
---|---|
Collection methods:![]() | The end date must be related to a particular service episode. For each separate service episode a separate end date should be recorded. |
Comments:![]() | This metadata item may be used in the calculation of measures of periods of support and duration of assistance. |
Source and reference attributes | |
Submitting organisation:![]() | Australian Institute of Health and Welfare |
Relational attributes | |
Related metadata references:![]() | Supersedes Service episode—episode end date, DDMMYYYY Community Services (retired), Standard 01/03/2005 Disability, Superseded 05/07/2019 Homelessness, Superseded 10/08/2018 Housing assistance, Standard 23/08/2010 |
Implementation in Data Set Specifications:![]() | Disability Services NMDS 2018–19 Disability, Standard 05/07/2019 Implementation start date: 01/07/2018 Implementation end date: 30/06/2019 Conditional obligation: In the Disability Services National Minimum Data Set (DS NMDS), this data element is only answered for service users who have stopped receiving services from the service type outlet. Otherwise it is left blank. DSS specific information: In the DS NMDS, this refers to the date on which the person ceased to be a service user of the service type outlet. It is only reported for service users who have ceased receiving services from the service type outlet, otherwise it is left blank. The service episode end date must relate to the service type outlet ID (Service type outlet—outlet identifier, XX[X(26)]) and associated service type (Service type outlet—service activity type, NDA service type code N.NN). A service user is considered to leave a service when either:
The 'Service episode—service cessation reason, NDA code' and 'Service event—last service provision date, DDMMYYYY' should also be completed for service users who have exited. Specialist Homelessness Services NMDS 2019- Homelessness, Standard 10/08/2018 Conditional obligation: In the Specialist Homelessness Services NMDS, this item is only asked of clients. DSS specific information: In the Specialist Homelessness Services NMDS this data element is the support period end date. |