Person—family name, text X[X(39)]
Identifying and definitional attributes
|Metadata item type:||Data Element|
|Short name:||Family name|
|Synonymous names:||Surname; Last name|
|Registration status:||Health, Standard 05/10/2016|
Tasmanian Health, Endorsed 27/06/2017
Indigenous, Final 30/05/2018
ACT Health, Final 02/01/2019
The name a person has in common with some other members of their family, as represented by text.
It is often hereditary, and is distinguished from that person's first given name.
|Data Element Concept:||Person—family name|
Value domain attributes
|Maximum character length:||40|
Data element attributes
Collection and usage attributes
|Guide for use:|
A person’s family name is one of the following:
The agency or establishment should record the person's full family name on their information systems.
Family name should be recorded in the format preferred by the person. The format should be the same as that written by the person on a (pre) registration form or in the same format as that printed on an identification card, such as a Medicare card, to ensure consistent collection of name data.
If special characters (such as hyphens, umlauts or commas) form part of the family name they should be included without spaces. For example, hyphenated names should be entered with a hyphen without spaces.
Hyphenated family names should only be recorded using this data element, and not Person—family name prefix, text A[A(29)].
Apostrophe–for example O’Brien, D’Agostino
No space should be left before or after the apostrophe; for example, for the name ‘O’Brien’, there should not be a space between the ‘O’ and the apostrophe, or between the apostrophe and ‘Brien’.
Family names with apostrophes should only be recorded using this data element, and not Person—family name prefix, text A[A(29)].
Full stop–for example, St. John or St. George.
No space should be left before a full stop; for example, for the name ‘St. John’ there should not be a space between ‘St’ and the full stop. A space should be left between the full stop and the next name; for example, for the name ‘St. John’ there should be a space between the full stop and ‘John’. In this example, it would be incorrect to enter ‘St .John’ or ‘St . John’.
Space–for example, Van Der Humm, Le Brun (examples which should be entered using the provision for family name prefix).
If the person has recorded their family name as more than one word, displaying spaces in between the words, record their family name in the same way leaving one space between each word. When it is displayed there should be a space between each family name in the same sequence as collected.
Person with only a single name
Some people do not have a family name and a given name, but have only a single name by which they are known. For such individuals the name should be recorded in the Family name field and the Given name field left blank.
Registering a pseudonym
This process may be required in order to mask the identity of an individual—for example, in the case of HIV testing—where the subject of care has the right of anonymity in many jurisdictions. In this case a pseudonym (fictitious or partial name) will be entered in lieu of the person’s full or actual name. It is recommended that the subject be asked to record both the pseudonym (other name) as well as a legally known name (for example, identity card name).
Registering a pseudonym requires the local system to be able to identify which name is to be used or displayed as the preferred name for the purpose of the test. This might require the temporary change of the pseudonym name to preferred name, which is then changed back to the normal preferred name after the pseudonym use is over.
This issue also arises when those working in health care are being treated. It is a common requirement in relation to staff of an organisation or people in a comparatively small community.
Registered unnamed newborn babies
When registering a newborn, the mother’s family name should be used as the baby’s family name unless instructed otherwise by the mother. Unnamed babies should be recorded with a name usage value of Newborn name. This is a name that is not expected to persist but, unlike most temporary names, no follow-up is required during the birth episode of care to find the correct longer term name.
Registering an unidentified person
The default for unknown family name should be ‘unknown’ in all instances, and the name recorded as a name usage type of Other name (note: the name conditional use flag should be used to indicate that this is not a reliable name). A ‘fictitious’ family name such as ‘Doe’ shall not be created, as this is an actual family name. When the subject’s name becomes known, it shall be recorded as the ‘preferred’ name and the other name of ‘unknown’ shall not be overwritten.
Registering individuals from disaster sites
People from disaster sites being treated should be recorded with a name usage of ‘other name’. Local business rules should be developed for consistent recording of disaster site patient details. Care should be taken not to use identical dummy data (family name, given name, date of birth, sex) for two or more subjects from a disaster site. For example, use of the surname ‘Unknown1’, ‘Unknown2’ in the family name can clearly differentiate between individuals. Some organisations use an injury description in the given name field to assist in identification. The use of a standard start to the name supports the use of search strategies to assist in finding individuals, especially when a large number of people need to be managed in a disaster. These names have restricted use as they are relevant only for the current episode of care and purpose and should be updated with the individual’s real name as soon as possible.
Often people use a variety of names, including legal names, married/maiden names, nicknames, assumed names, traditional names, and so forth. Even small differences in recording–such as the difference between MacIntosh and McIntosh–can make record linkage impossible.
To minimise discrepancies in the recording and reporting of name information, agencies or establishments should ask the person for their full (formal) 'Given name' and 'Family name'. These may be different from the name that the person may prefer the agency or establishment workers to use in personal dealings. Agencies or establishments may choose to separately record the preferred name that the person wishes to be used by agency or establishment workers.
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 or establishments should always ask the person to specify their first given name and their family name or surname separately. These should then be recorded as 'Given name' and 'Family name' as appropriate, regardless of the order in which they may be traditionally given.
Source and reference attributes
Australian Institute of Health and Welfare
Standards Australia 2014. AS 4846:2014 Person and provider identification in healthcare. Sydney: Standards Australia.
|Related metadata references:|
Supersedes Person (name)—family name, text X[X(39)] Housing assistance, Standard 20/06/2005, Health, Superseded 05/10/2016, Tasmanian Health, Endorsed 01/09/2016, Community Services (retired), Superseded 06/02/2012
See also Person—family name prefix, text A[A(29)] Health, Standard 05/10/2016
See also Person—family name sequence number, code N[N] Health, Standard 05/10/2016
See also Person—given name, text X[X(39)] Health, Standard 05/10/2016, Tasmanian Health, Endorsed 27/06/2017, Indigenous, Final 30/05/2018, ACT Health, Final 02/01/2019
See also Person—mother’s original family name, text X[X(39)] Health, Standard 05/10/2016
See also Person—name usage type end date, DDMMYYYY Health, Not progressed 28/07/2016, Disability, Standard 13/08/2015, Community Services (retired), Standard 06/02/2012
See also Person—name usage type start date, DDMMYYYY Health, Not progressed 28/07/2016, Disability, Standard 13/08/2015, Community Services (retired), Standard 06/02/2012
See also Person—name usage type, code X Health, Standard 05/10/2016
See also Person—preferred name indicator, yes/no code X Health, Standard 05/10/2016
See also Person—single name only flag, code A Health, Standard 05/10/2016
|Implementation in Data Set Specifications:|
All attributes +
Individual name cluster Health, Standard 05/10/2016
Name cluster (Tasmania) - 2017 Tasmanian Health, Endorsed 27/06/2017
National Bowel Cancer Screening Program NBEDS 2018–19 Health, Superseded 12/12/2018
National Bowel Cancer Screening Program NBEDS 2019–20 Health, Standard 12/12/2018
National Bowel Cancer Screening Program NBEDS 2020–21 Health, Standardisation pending 15/11/2019