ID
16745
Beskrivning
Health sector data set specifications from METeOR, Australia's repository for national metadata standards, developed by the Australian Institute of Health and Welfare (http://meteor.aihw.gov.au/content/index.phtml/itemId/345165) Statistical linkage key 581 Statistical data linkage refers to the bringing together of data from different sources to gain a greater understanding of a situation or individual from the combined (or linked) dataset. This facilitates a better understanding of the patterns of service use by groups of clients for research, statistical or policy analysis, planning and evaluation purposes. Its form is: XXXXXDDMMYYYYN The sequence in which the linkage key is completed is as follows: Family name (the first 3 Xs) Given name (the 4th and 5th X) Date of birth by day, month and four-digit year Sex XXX 2nd, 3rd and 5th letters of the family name. In the first three spaces the agency should record the 2nd, 3rd and 5th letters of the client’s family name. For example: If the client’s family name is Smith the reported value should be MIH. If the client’s family name is Jones the reported value should be ONS. Regardless of the length of a person’s name, the reported value should always be three characters long. If the legal family name is not long enough to supply the requested letters (i.e. a legal family name of less than five letters) then agencies should substitute the number ‘2’ to reflect the missing letters. The placement of a number ‘2’ should always correspond to the same space that the missing letter would have within the 3-digit field. A number (rather than a letter) is used for such a substitution in order to clearly indicate that an appropriate corresponding letter from the person’s name is not available. Cases where the family name has less than 5 letters: If a person’s family name is Farr, then value reported would be AR2 because the 2 is substituting for a missing 5th letter of the family name. Similarly, if the person’s family name was Hua, then the value reported would be UA2 because the 2 is substituting for the missing 5th letter of the family name. If a client’s family name is missing altogether the agency should record the number 999 for all three spaces associated with the family name, (not the number 2). In some cultures it is traditional to state the family name first. To overcome discrepancies in recording/reporting that may arise as a result of this practice, agencies should always ask the person to specify their legal first given name and their legal family name separately. These should then be recorded as first given name and family name as appropriate, regardless of the order in which they may be traditionally given. If the client’s family name includes non-alphabetic characters—for example hyphens (as in Lee-Archer), apostrophes (as in O’Mara) or blank spaces (as in De Vries)—these non-alphabetic characters should be ignored when counting the position of each character. XX 2nd and 3rd letters of given name In the fourth and fifth spaces the agency should record the 2nd and 3rd letters of the client’s given name. For example: If the client’s given name is Elizabeth the reported value should be LI. If the client’s given name is Robert the reported value should be OB. If the client’s given name includes non-alphabetic characters—for example hyphens (as in Jo-Anne) or apostrophes (as in D'Arcy), these non-alphabetic characters should be ignored when counting the position of each character. Regardless of the length of a person’s given name, the reported value should always be two characters long. If the given name of the person is not long enough to supply the requested letters (i.e. a name of less than three letters) then agencies should substitute the number ‘2’ to reflect the missing letters. The placement of a number ‘2’ should always correspond to the same space that the missing letter would have within the 2-digit field. A number (rather than a letter) is used for such substitutions in order to clearly indicate that an appropriate corresponding letter from the person’s name is not available. For example: If the person’s legal name was Jo then the value reported would be O2 because the 2 is substituting for the missing 3rd letter of the given name. If the person’s given name is missing altogether the agency should record 99 for the two spaces associated with the given name. In some cultures it is traditional to state the family name first. To overcome discrepancies in recording/reporting that may arise as a result of this practice, agencies should always ask the person to specify their given name and their family name separately. These should then be recorded as first given name and family name as appropriate, regardless of the order in which they may be traditionally given. Date of Birth DD represents the day in the month a person was born MM represents the month in the year a person was born YYYY represents the year a person was born 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 or a date accuracy indicator 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 or date accuracy indicator http://meteor.aihw.gov.au/content/index.phtml/ itemId/294429 should be reported in conjunction with all estimated dates of birth. Sex N represents whether or not the person is a 1. Male or 2. Female. Operationally, sex is the distinction between male and female, as reported by a person or as determined by an interviewer. When collecting data on sex by personal interview, asking the sex of the respondent is usually unnecessary and may be inappropriate, or even offensive. It is usually a simple matter to infer the sex of the respondent through observation, or from other cues such as the relationship of the person(s) accompanying the respondent, or first name. The interviewer may ask whether persons not present at the interview are male or female. A person's sex may change during their lifetime as a result of procedures known alternatively as sex change, gender reassignment, transsexual surgery, transgender reassignment or sexual reassignment. Throughout this process, which may be over a considerable period of time, the person's sex could be recorded as either Male or Female. In data collections that use the ICD-10-AM classification, where sex change is the reason for admission, diagnoses should include the appropriate ICD-10-AM code(s) that clearly identify that the person is undergoing such a process. This code(s) would also be applicable after the person has completed such a process, if they have a procedure involving an organ(s) specific to their previous sex (e.g. where the patient has prostate or ovarian cancer). Code 3 Intersex or indeterminate Is normally used for babies for whom sex has not been determined for whatever reason. Should not generally be used on data collection forms completed by the respondent. Should only be used if the person or respondent volunteers that the person is intersex or where it otherwise becomes clear during the collection process that the individual is neither male nor female. Code 9 Not stated/inadequately described Is not to be used on primary collection forms. It is primarily for use in administrative collections when transferring data from data sets where the item has not been collected. Data that has been produced by linkage for statistical and research purposes should not be used subsequently for client management purposes. This data cluster contains a set of specific data elements to be reported on in a predetermined combination. © Australian Institute of Health and Welfare 2015 Metadata and Classifications Unit Australian Institute of Health and Welfare GPO Box 570 Canberra ACT 2601
Länk
http://meteor.aihw.gov.au/content/index.phtml/itemId/345165
Nyckelord
Versioner (1)
- 2016-08-03 2016-08-03 -
Uppladdad den
3 augusti 2016
DOI
För en begäran logga in.
Licens
Creative Commons BY-NC 3.0
Modellkommentarer :
Här kan du kommentera modellen. Med hjälp av pratbubblor i Item-grupperna och Item kan du lägga in specifika kommentarer.
Itemgroup-kommentar för :
Item-kommentar för :
Du måste vara inloggad för att kunna ladda ner formulär. Var vänlig logga in eller registrera dig utan kostnad.
Alcohol and other drug treatment services NMDS 2015- Statistical linkage key 581 cluster Metadata Online Registry (METeOR)
Alcohol and other drug treatment services NMDS 2015- Statistical linkage key 581 cluster Metadata Online Registry (METeOR)
Beskrivning
Record
Beskrivning
Record—linkage key, code 581 XXXXXDDMMYYYYN Identifying and definitional attributes Short name: Statistical linkage key 581 METeOR identifier: 349895 Registration status: Housing assistance, Standard 23/08/2010 Health, Standard 07/12/2011 Early Childhood, Standard 21/05/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 Community Services (retired), Standard 21/05/2010 Definition: A key that enables two or more records belonging to the same individual to be brought together. It is represented by a code consisting of the second, third and fifth characters of a person’s family name, the second and third letters of the person’s given name, the day, month and year when the person was born and the sex of the person, concatenated in that order. Data Element Concept: Record—linkage key Value domain attributes Representational attributes Representation class: Code Data type: String Format: XXXXXDDMMYYYYN Maximum character length: 14 Data element attributes Collection and usage attributes Collection methods: Information about whether or not the person's date of birth is accurate should be noted. By knowing that date of birth is accurate it is possible to reduce underestimation of total service user numbers and overestimation of service users' ages. Comments: The linkage key is designed to make it possible to count number of clients and services they received, without counting the same client more than once. It can also be used for linking to other related data collections. It is for statistical linkage purposes only, not for case management or the tracking of individual persons. This may be done using a range of identifiers and/or keys. Source and reference attributes Submitting organisation: Australian Institute of Health and Welfare. Steward: Australian Institute of Health and Welfare Relational attributes Related metadata references: See also Date—accuracy indicator, code AAA Housing assistance, Standard 23/08/2010, Health, Standard 04/05/2005, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Disability, Standard 07/10/2014, Community Services (retired), Standard 30/09/2005 See also Date—estimate indicator, code N Tasmanian Health, Draft 23/07/2012, Community Services (retired), Standard 27/04/2007 See also National Indigenous Reform Agreement: PI 10-The proportion of Indigenous children aged 4 and 5 years who are enrolled in, and attending, a preschool program in the year before full-time schooling, by remoteness, 2013 Indigenous, Archived 13/12/2013 Is formed using Person—date of birth, DDMMYYYY Housing assistance, Standard 20/06/2005, Health, Standard 04/05/2005, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Tasmanian Health, Final 30/06/2014, WA Health, Endorsed 19/03/2015, Independent Hospital Pricing Authority, Standard 01/11/2012, Indigenous, Endorsed 11/08/2014, National Health Performance Authority, Standard 07/11/2013, Commonwealth Department of Health, Candidate 25/05/2015, Disability, Standard 07/10/2014, Community Services (retired), Standard 25/08/2005 Is formed using Person—letters of family name, text XXX Housing assistance, Standard 23/08/2010, Health, Standard 07/12/2011, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Disability, Standard 07/10/2014, Community Services (retired), Standard 27/03/2007 Is formed using Person—letters of given name, text XX Housing assistance, Standard 23/08/2010, Health, Standard 07/12/2011, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Disability, Standard 07/10/2014, Community Services (retired), Standard 27/03/2007 Is formed using Person—sex, code N Housing assistance, Standard 10/02/2006, Health, Standard 04/05/2005, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, WA Health, Draft 23/08/2012, Independent Hospital Pricing Authority, Standard 01/11/2012, Indigenous, Endorsed 11/08/2014, National Health Performance Authority, Standard 07/11/2013, Commonwealth Department of Health, Candidate 16/07/2015, Disability, Standard 07/10/2014, Community Services (retired), Standard 25/08/2005 Implementation in Data Set Specifications: Early Childhood Education and Care DSS 2015 Early Childhood, Standard 01/06/2015 Early Childhood Education and Care: Unit Record Level NMDS 2015 Early Childhood, Standard 01/06/2015 Statistical linkage key 581 cluster Housing assistance, Standard 23/08/2010 Health, Standard 07/12/2011 Early Childhood, Standard 21/05/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 Community Services (retired), Standard 21/05/2010 Implementation in Indicators: Used as numerator National Affordability Housing Agreement: 4: Proportion of people experiencing repeat periods of homelessness, 2010 Homelessness, Standard 16/02/2011 Used as denominator National Affordability Housing Agreement: 4: Proportion of people experiencing repeat periods of homelessness, 2010 Homelessness, Standard 16/02/2011
Datatyp
text
Beskrivning
Date
Beskrivning
Date—accuracy indicator, code AAA Obligation: Conditional Identifying and definitional attributes Short name: Date accuracy indicator METeOR identifier: 294429 Registration status: Housing assistance, Standard 23/08/2010 Health, Standard 04/05/2005 Early Childhood, Standard 21/05/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 Community Services (retired), Standard 30/09/2005 Definition: An indicator of the accuracy of the components of a reported date, as represented by a code. Data Element Concept: Date—accuracy indicator Value domain attributes Representational attributes Representation class: Code Data type: String Format: AAA Maximum character length: 3 Permissible values: Value Meaning AAA Day, month and year are accurate AAE Day and month are accurate, year is estimated AAU Day and month are accurate, year is unknown AEA Day is accurate, month is estimated, year is accurate AEE Day is accurate, month and year are estimated AEU Day is accurate, month is estimated, year is unknown AUA Day is accurate, month is unknown, year is accurate AUE Day is accurate, month is unknown, year is estimated AUU Day is accurate, month and year are unknown 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 set specification specific attributes Statistical linkage key 581 cluster Conditional obligation: Where a date of birth is estimated the date accuracy indicator should be used 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 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 Health, Standard 04/05/2005, Community Services (retired), Standard 30/09/2005 See also Individual service provider—occupation start date, DDMMYYYY Health, Standard 04/05/2005, Community Services (retired), Standard 30/09/2005 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—medical indemnity claim finalisation date, DDMMYYYY Health, Standard 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 Housing assistance, Standard 20/06/2005, Health, Standard 04/05/2005, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Tasmanian Health, Final 30/06/2014, WA Health, Endorsed 19/03/2015, Independent Hospital Pricing Authority, Standard 01/11/2012, Indigenous, Endorsed 11/08/2014, National Health Performance Authority, Standard 07/11/2013, Commonwealth Department of Health, Candidate 25/05/2015, Disability, Standard 07/10/2014, Community Services (retired), Standard 25/08/2005 See also Person—date of birth, MMYYYY Health, Standard 10/12/2009, National Health Performance Authority, Standard 12/12/2013 See also Record—linkage key, code 581 XXXXXDDMMYYYYN Housing assistance, Standard 23/08/2010, Health, Standard 07/12/2011, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Disability, Standard 07/10/2014, Community Services (retired), Standard 21/05/2010 See also Statistical linkage key 581 cluster Housing assistance, Standard 23/08/2010, Health, Standard 07/12/2011, Early Childhood, Standard 21/05/2010, Homelessness, Standard 23/08/2010, Disability, Standard 07/10/2014, Community Services (retired), Standard 21/05/2010 Implementation in Data Set Specifications: Cancer (clinical) DSS Health, Standard 14/05/2015 Medical indemnity DSS 2014- Health, Standard 21/11/2013 Statistical linkage key 581 cluster Housing assistance, Standard 23/08/2010 Health, Standard 07/12/2011 Early Childhood, Standard 21/05/2010 Homelessness, Standard 23/08/2010 Disability, Standard 07/10/2014 Community Services (retired), Standard 21/05/2010
Datatyp
text