Identifying and definitional attributes | |
Metadata item type: | Data Element |
---|---|
Short name: | Date accuracy indicator |
METEOR identifier: | 294429 |
Registration status: | Health, Standard 04/05/2005 Community Services (retired), Standard 30/09/2005 Early Childhood, Standard 21/05/2010 Housing assistance, Standard 23/08/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 |
Definition: | An indicator of the accuracy of the components of a reported date, as represented by a code. |
Data element concept attributes | |
Identifying and definitional attributes | |
Data element concept: | Date—accuracy indicator |
---|---|
METEOR identifier: | 294418 |
Registration status: | Health, Standard 04/05/2005 Community Services (retired), Standard 30/09/2005 Early Childhood, Standard 21/05/2010 Housing assistance, Standard 23/08/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 |
Definition: | An indicator of the accuracy of the components of a reported date. |
Context: | This data element is designed to flag whether each component in a date is accurate, estimated or unknown. |
Object class: | Date |
Property: | Accuracy indicator |
Value domain attributes | |
Identifying and definitional attributes | |
Value domain: | Date accuracy indicator code AAA |
---|---|
METEOR identifier: | 289952 |
Registration status: | Health, Standard 04/05/2005 Community Services (retired), Standard 30/09/2005 Early Childhood, Standard 21/05/2010 Housing assistance, Standard 23/08/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 |
Definition: | A code set representing the accuracy of the components of a date. |
Data element attributes | |
Collection and usage attributes | |
Collection methods: | Collection constraints: If constraints for the collection of the date are imposed, such as ‘a valid date must be input in an information system for unknown date components’, the Date accuracy indicator should be used along with the date as a way of avoiding the contamination of the valid dates with the same value on the respective date components. Example: Some jurisdictions use 0107YYYY and some use 0101YYYY when only the year is known. When month and year are known some use the 15th day as the date i.e. 15MMYYYY. Where this occurs in a data collection that is used for reporting or analysis purposes there will be dates in the collection with the attributes 0107YYYY etc., that are accurate and some that are not accurate. Without a corresponding flag to determine this accuracy the analysis or report will be contaminated by those estimated dates. |
---|---|
Comments: | Provision of a date is often a mandatory requirement in data collections. Most computer systems require a valid date to be recorded in a date field i.e. the month part must be an integer between 1 and 12, the day part must be an integer between 1 and 31 with rules about the months with less than 31 days, and the year part should include the century. Also in many systems, significant dates (e.g. date of birth) are mandatory requirements. However, in actual practice, the date or date components are often not known (e.g. date of birth, date of injury) but, as stated above, computer systems require a valid date. This means that a date MUST be included and it MUST follow the rules for a valid date. It therefore follows that, while such a date will contain valid values according to the rules for a date, the date is in fact an ‘unknown’ or ‘estimated’ date. For future users of the data, it is essential to know that a date is accurate, unknown or estimated and which components of the date are accurate, unknown or estimated. |
Source and reference attributes | |
Submitting organisation: | Standards Australia |
Reference documents: | Standards Australia 2002. AS5017—2002 Health Care Client Identification. Sydney: Standards Australia |
Relational attributes | |
Related metadata references: | See also Health-care incident—date health-care incident occurred, DDMMYYYY Health, Standard 07/12/2011 See also Individual service provider—occupation end date, DDMMYYYY Community Services (retired), Standard 30/09/2005 Health, Standard 04/05/2005 See also Individual service provider—occupation start date, DDMMYYYY Community Services (retired), Standard 30/09/2005 Health, Superseded 05/10/2016 See also Medical indemnity claim management episode—medical indemnity claim finalisation date, DDMMYYYY Health, Standard 21/11/2013 See also Medical indemnity claim management episode—medical indemnity claim finalisation date, DDMMYYYY Health, Superseded 21/11/2013 See also Medical indemnity claim management episode—reserve placement date, DDMMYYYY Health, Standard 07/12/2011 See also Medical indemnity claim—medical indemnity claim commencement date, DDMMYYYY Health, Standard 07/12/2011 See also Person—date of birth, DDMMYYYY Aged Care, Standard 30/06/2023 Australian Institute of Health and Welfare, Recorded 09/08/2023 Australian Teacher Workforce Data Oversight Board, Standard 30/08/2022 Children and Families, Standard 22/11/2016 Commonwealth Department of Health, Retired 19/08/2023 Community Services (retired), Standard 25/08/2005 Disability, Standard 07/10/2014 Early Childhood, Standard 21/05/2010 Health, Standard 04/05/2005 Homelessness, Standard 23/08/2010 Housing assistance, Standard 20/06/2005 Independent Hospital Pricing Authority, Standard 01/11/2012 Indigenous, Standard 11/08/2014 National Health Performance Authority (retired), Retired 01/07/2016 Tasmanian Health, Standard 31/08/2016 WA Health, Standard 19/03/2015 Youth Justice, Standard 15/02/2022 See also Person—date of birth, MMYYYY Commonwealth Department of Social Services (retired), Standard 20/06/2018 Health, Standard 10/12/2009 National Health Performance Authority (retired), Retired 01/07/2016 Tasmanian Health, Standard 06/05/2021 See also Person—date of birth, MMYYYY Tasmanian Health, Superseded 06/05/2021 See also Person—date of birth, YYYY Australian Teacher Workforce Data Oversight Board, Recorded 27/10/2022 Health, Qualified 18/07/2024 Tasmanian Health, Standard 06/05/2021 See also Record—linkage key, code 581 XXXXXDDMMYYYYN Community Services (retired), Standard 21/05/2010 Disability, Standard 07/10/2014 Early Childhood, Standard 21/05/2010 Health, Superseded 25/01/2018 Homelessness, Superseded 10/08/2018 Housing assistance, Standard 23/08/2010 See also Record—linkage key, code 581 XXXXXDDMMYYYYX Health, Standard 25/01/2018 Homelessness, Standard 10/08/2018 See also Statistical linkage key 581 cluster Community Services (retired), Standard 21/05/2010 Disability, Standard 07/10/2014 Early Childhood, Standard 21/05/2010 Health, Superseded 25/01/2018 Homelessness, Superseded 10/08/2018 Housing assistance, Standard 23/08/2010 See also Statistical linkage key 581 cluster Health, Superseded 17/12/2021 Homelessness, Standard 10/08/2018 See also Statistical linkage key 581 cluster Health, Standard 17/12/2021 |
Implementation in Data Set Specifications: | Address communication suppression cluster Health, Standard 05/10/2016 DSS specific information: This data element should be used in conjunction with a date field. Address status cluster Health, Standard 05/10/2016 DSS specific information: This data element should be collected in conjunction with the Address—address start date, DDMMYYYY and Address—address end date, DDMMYYYY data elements to indicate the accuracy of the components of the start and end dates. Cancer (clinical) DSS Health, Superseded 08/05/2014 Cancer (clinical) DSS Health, Superseded 14/05/2015 Cancer (clinical) NBPDS Health, Standard 14/05/2015 Dementia NBPDS Health, Standard 05/10/2022 Duplicate record cluster Health, Standard 05/10/2016 Health care client identification DSS Health, Superseded 03/12/2008 Health care client identification DSS Health, Retired 20/03/2013 Health care provider identification DSS Health, Superseded 04/07/2007 Health care provider identification DSS Health, Superseded 03/12/2008 Health care provider identification DSS Health, Retired 20/03/2013 Healthcare identification occupation cluster Health, Standard 05/10/2016 Healthcare provider organisation cluster Health, Standard 05/10/2016 Conditional obligation: Required for Organisation—name usage start date, DDMMYYYY, and for Organisation—name usage end date, DDMMYYYY when provided. Identification in healthcare cluster Health, Standard 05/10/2016 DSS specific information: Recorded in conjunction with the data elements within this cluster that are used to record a date. Individual demographic identifiers cluster Health, Standard 05/10/2016 Individual name cluster Health, Standard 05/10/2016 DSS specific information: Recorded in conjunction with the data elements within this cluster that are used to record a date. Intertwined record cluster Health, Standard 05/10/2016 DSS specific information: Recorded in conjunction with the data elements within this cluster that are used to record a date. Medical indemnity DSS 2012-14 Health, Superseded 21/11/2013 Implementation start date: 01/07/2012 Implementation end date: 30/06/2014 DSS specific information: This data element is to be used in conjunction with the following data elements: Health-care incident—date incident occurred, date DDMMYYYY; Medical indemnity claim—medical indemnity claim commencement date, DDMMYYYY; Medical indemnity claim management episode—medical indemnity claim finalisation date, DDMMYYYY; Medical indemnity claim management episode—reserve placement date, DDMMYYYY; and Person—date of birth, DDMMYYYY. Medical indemnity NBPDS 2014- Health, Standard 21/11/2013 Implementation start date: 01/07/2014 DSS specific information: This data element is to be used in conjunction with the following data elements: Health-care incident—date incident occurred, date DDMMYYYY; Medical indemnity claim—medical indemnity claim commencement date, DDMMYYYY; Medical indemnity claim management episode—medical indemnity claim finalisation date, DDMMYYYY; Medical indemnity claim management episode—reserve placement date, DDMMYYYY; and Person—date of birth, DDMMYYYY. Provider extensions or restrictions to practice cluster Health, Standard 05/10/2016 Provider registration cluster Health, Standard 05/10/2016 Public Housing and State Owned and Managed Indigenous housing (PH & SOMIH) DSS 2018- Housing assistance, Standard 10/05/2019 Implementation start date: 01/07/2018 Restricted name usage cluster Health, Standard 05/10/2016 Conditional obligation: Recorded in conjunction with the data elements within this cluster that are used to record a date. SAAP Client Collection National Minimum Data Set Community Services (retired), Retired 01/07/2011 DSS specific information: This data element should be collected for the client and for each accompanying child. It should be collected in conjunction with the client/accompanying children date of birth. Similar but different entity cluster Health, Standard 05/10/2016 DSS specific information: Recorded in conjunction with the data elements within this cluster that are used to record a date. Specialist Homelessness Services NMDS 2011 Homelessness, Superseded 01/05/2013 Housing assistance, Superseded 01/05/2013 Implementation start date: 01/07/2011 Specialist Homelessness Services NMDS 2012-13 Homelessness, Superseded 01/05/2013 Housing assistance, Superseded 01/05/2013 Implementation start date: 01/07/2012 Implementation end date: 30/06/2013 Statistical linkage key 581 cluster Community Services (retired), Standard 21/05/2010 Disability, Standard 07/10/2014 Early Childhood, Standard 21/05/2010 Health, Superseded 25/01/2018 Homelessness, Superseded 10/08/2018 Housing assistance, Standard 23/08/2010 Conditional obligation: Where a date of birth is estimated the date accuracy indicator should be used Statistical linkage key 581 cluster Health, Standard 17/12/2021 Implementation start date: 01/07/2018 Conditional obligation: Where a date of birth is estimated the date accuracy indicator should be used. Statistical linkage key 581 cluster Health, Superseded 17/12/2021 Homelessness, Standard 10/08/2018 Implementation start date: 01/07/2018 Conditional obligation: Where a date of birth is estimated the date accuracy indicator should be used. |