Day is accurate, month is estimated, year is unknown
AUU
Day is accurate, month and year are unknown
AUA
Day is accurate, month is unknown, year is accurate
AUE
Day is accurate, month is unknown, year is estimated
AEA
Day is accurate, month is estimated, year is accurate
EAA
Day is estimated, month and year are accurate
EAE
Day is estimated, month is accurate, year is estimated
EAU
Day is estimated, month is accurate, year is unknown
EEA
Day and month are estimated, year is accurate
EEE
Day, month and year are estimated
EEU
Day and month are estimated, year is unknown
EUA
Day is estimated, month is unknown, year is accurate
EUE
Day is estimated, month is unknown, year is estimated
EUU
Day is estimated, month and year are unknown
UAA
Day is unknown, month and year are accurate
UAE
Day is unknown, month is accurate, year is estimated
UAU
Day is unknown, month is accurate, year is unknown
UEA
Day is unknown, month is estimated, year is accurate
UEE
Day is unknown, month and year are estimated
UEU
Day is unknown, month is estimated, year is unknown
UUA
Day and month are unknown, year is accurate
UUE
Day and month are unknown, year is estimated
UUU
Day, month and year are unknown
Collection and usage attributes
Guide for use:
Any combination of the values A, E, U representing the corresponding level of accuracy of each date component of the reported date.
This data element consists of a combination of three codes, each of which denotes the accuracy of one date component:
A – the referred date component is accurate
E – the referred date component is not known but is estimated
U – the referred date component is not known and not estimated.
This data element contains positional fields (DMY) that reflects the order of the date components in the format (DDMMYYYY) of the reported date:
Field 1 (D) – refers to the accuracy of the day component;
Field 2 (M) – refers to the accuracy of the month component;
Field 3 (Y) – refers to the accuracy of the year component.
Data domain
Date component (for a format DDMMYYYY)
(D)ay
(M)onth
(Y)ear
Accurate
A
A
A
Estimated
E
E
E
Unknown
U
U
U
This data element is valid only for use with dates that are reported/exchanged in the format (DDMMYYYY).
Example 1: A date has been sourced from a reliable source and is known as accurate then the Date accuracy indicator should be informed as (AAA).
Example 2: If only the age of the person is known and there is no certainty of the accuracy of this, then the Date accuracy indicator should be informed as (UUE). That is the day and month are “unknown” and the year is “estimated”.
Example 3: If a person was brought in unconscious to an emergency department of a hospital and the only information available was from a relative who was certain of the age and the birthday’s 'month' then the Date accuracy indicator should be informed as (UAA). A year derived from an accurate month and accurate age is always an accurate year.
The Date accuracy indicator can be useful for operational purposes to indicate the level of accuracy that a date has been collected at any point in time. It can indicate whether the stored date needs to be followed up until it reaches the intended minimal required accuracy. For example, if a person was brought in unconscious to an emergency department of a hospital the level of accuracy of the date collected at that point may not be satisfactory. It is likely that the correct date of birth can be obtained at a later date. The Date accuracy indicator provides information on the accuracy of the entered dates that may require further action.
For future users of the data it may also be essential they know the accuracy of the date components of a reported 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 they 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:
AS5017 Health Care Client Identification, 2002, Sydney: Standards Australia
