Person—date of birth, DDMMYYYY
Identifying and definitional attributes | |
Metadata item type:![]() | Data Element |
---|---|
Short name:![]() | Date of birth |
Synonymous names:![]() | Date of birth |
METEOR identifier:![]() | 270391 |
Registration status:![]() |
|
Definition:![]() | The date of birth of the person. |
Data Element Concept: | Person—date of birth |
Value domain attributes | ||||
Representational attributes | ||||
Representation class:![]() | Date | |||
---|---|---|---|---|
Data type:![]() | Date/Time | |||
Format:![]() | DDMMYYYY | |||
Maximum character length:![]() | 8 | |||
Data element attributes | ||||
Collection and usage attributes | ||||
Guide for use:![]() | If date of birth is not known or cannot be obtained, provision should be made to collect or estimate age. Collected or estimated age would usually be in years for adults, and to the nearest three months (or less) for children aged less than two years. Additionally, an estimated date flag should be reported in conjunction with all estimated dates of birth. For data collections concerned with children's services, it is suggested that the estimated Date of birth of children aged under 2 years should be reported to the nearest 3 month period, i.e. 0101, 0104, 0107, 0110 of the estimated year of birth. For example, a child who is thought to be aged 18 months in October of one year would have his/her estimated date of birth reported as 0104 of the previous year. Again, an estimated date flag should be reported in conjunction with all estimated dates of birth. | |||
Collection methods:![]() | Information on date of birth can be collected using the one question: What is your/(the person's) date of birth? In self-reported data collections, it is recommended that the following response format is used: Date of birth: _ _ / _ _ / _ _ _ _ This enables easy conversion to the preferred representational layout (DDMMYYYY). Estimated dates of birth should be identified by an appropriate estimated date flag to prevent inappropriate use of date of birth data for record identification and/or the derivation of other metadata items that require accurate date of birth information. | |||
Comments:![]() | Privacy issues need to be taken into account in asking persons their date of birth. Wherever possible and wherever appropriate, date of birth should be used rather than age because the actual date of birth allows a more precise calculation of age. When date of birth is an estimated or default value, national health and community services collections typically use 0101 or 0107 or 3006 as the estimate or default for DDMM. It is suggested that different rules for reporting data may apply when estimating the Date of birth of children aged under 2 years because of the rapid growth and development of children within this age group which means that a child's development can vary considerably over the course of a year. Thus, more specific reporting of estimated age is suggested. NHDD specific: DSS-Health care client identification: Any new information collection systems should allow for 0000YYYY. (Refer to Standards Australia AS5017-2002 Health Care Client Identification). | |||
Source and reference attributes | ||||
Submitting organisation:![]() | National Health Data Committee National Community Services Data Committee | |||
Relational attributes | ||||
Related metadata references:![]() | Supersedes ![]() Has been superseded by Person—date of birth, DDMMYYYY
| |||
Implementation in Data Set Specifications:![]() All attributes + |
| |||
Implementation in Indicators:![]() |
|
Downloading
The download may take a while, please wait.
Do not refresh the screen until the download is complete.