Person (name)—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:||Indigenous, Endorsed 05/09/2014|
Disability, Standard 13/08/2015
Community Services (retired), Standard 06/02/2012
That part of a name a person usually has in common with some other members of his/her family, as distinguished from his/her given names, as represented by text.
|Data Element Concept:||Person (name)—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 cannot be a repeated data element.
There are no universal verification rules for a person's Family Name.
This metadata item should be recorded for all persons who receive services from or are of interest to an organisation. For the purposes of positive identification, it may also be recorded for providers of those services who are individuals.
Mixed case should be used.
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.
A person is able to change his or her name by usage in all States and Territories of Australia with the exception of Western Australia, where a person may only change his or her name under the Change of Name Act. Care should be taken when recording a change of name for a minor. Ideally, the name recorded for the minor should be known to both of his/her parents, so the minor's records can be retrieved and continuity of care maintained, regardless of which parent accompanies the minor to the agency or establishment.
The following format may assist with data collection:
What is your family name? _______________________________________
If special characters form part of the family name they should be included, e.g. hyphenated names should be entered with a hyphen.
- hyphen, e.g. Wilson-Phillips
Do not leave a space before or after a hyphen, i.e. between the last letter of 'Wilson' and the hyphen, nor a space between the hyphen and the first letter of 'Phillips'.
- apostrophe, e.g. O'Brien, D'Agostino
Do not leave a space before or after the apostrophe, i.e. between the 'O' and the apostrophe, or a space between the apostrophe and 'Brien'.
- full stop, e.g. St. John, St. George
Do not leave a space before a full stop, i.e. between 'St' and the full stop. Do leave a space between the full stop and 'John'.
- space, e.g. van der Humm, Le Brun, Mc Donald
If the client 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.
Registered unnamed newborn babies:
When registering a newborn, use the mother's family name as the baby's family name unless instructed otherwise by the mother. Record unnamed babies under the newborn identification name Name type.
Persons with only one name:
Some people do not have a family name and a given name, they have only one name by which they are known. If the person has only one name, record it in the 'Family name' field and leave the 'Given name' field blank.
Registering an unidentified person:
The default for unknown family name should be unknown in all instances and the name recorded as an alias name. Don't create a 'fictitious' family name such as 'Doe' as this is an actual family name. When the person's name becomes known, record it as the preferred family name and do not overwrite the alias name of unknown.
Registering clients from disaster sites:
Persons treated from disaster sites should be recorded under the alias Name Type. Local business rules should be developed for consistent recording of disaster site person details.
Care should be taken not to use identical dummy data (family name, given name, date of birth, sex) for two or more persons from a disaster site.
If the family name needs to be shortened:
If the length of the family name exceeds the length of the field, truncate the family name from the right (that is, dropping the final letters). Also, the last character of the name should be a hash (#) to identify that the name has been truncated.
Use of incomplete names or fictitious names:
Some organisations permit persons to use a pseudonym (fictitious or partial name) in lieu of their full or actual name. It is recommended that the person be asked to record both the pseudonym (Alias name) in addition to the person's legal name.
Baby for adoption:
The word adoption should not be used as the family name, given name or alias for a newborn baby. A newborn baby that is for adoption should be registered in the same way that other newborn babies are registered. However, if a baby born in the hospital is subsequently adopted, and is admitted for treatment as a child, the baby is registered under their adopted (current) name, and the record should not be linked to the birth record. This should be the current practice. Any old references to adoption in client registers (for names) should also be changed to unknown. Contact your State or Territory adoption information service for further information.
Where a family name contains a prefix, such as one to indicate that the person is a widow, this must be entered as part of the 'Family name' field. When widowed, some Hungarian women add 'Ozvegy' (abbreviation is 'Ozy') before their married family name, e.g. 'Mrs Szabo' would become 'Mrs Ozy Szabo'.
A useful resource when capturing ethnic names is the referenced Naming Systems of Ethnic Groups produced by Centrelink, Canberra, AGPS.
Misspelled family name:
If the person's family name has been misspelled in error, update the family name with the correct spelling. The misspelled name should not be deleted as recording misspelled names is important for filing documents that may be issued with previous versions of the person's name. Discretion should be used regarding the degree of recording that is maintained.
Often people use a variety of names, including legal names, married/maiden names, nicknames, assumed names, traditional names, etc. 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 names 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 2006. AS 4590—2006 Interchange of client information. 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 (name)—given name, text X[X(39)] WA Health, Draft 23/08/2012, Indigenous, Endorsed 05/09/2014, Disability, Standard 13/08/2015, Community Services (retired), Standard 06/02/2012
See also Person—name usage type, code AAA Health, Proposed 11/04/2013, Disability, Standard 13/08/2015, Community Services (retired), Standard 06/02/2012
|Implementation in Data Set Specifications:|
All attributes +
Closing the Gap/Child Health Check Initiative: Ear, nose and throat operation summary form DSS Indigenous, Endorsed 05/12/2017
Ear nose and throat services patient cluster Indigenous, Endorsed 05/09/2014
Ear operation details cluster Indigenous, Endorsed 05/12/2017
OATSIH Services Reporting (OSR) certification cluster Indigenous, Endorsed 07/12/2017
OATSIH Services Reporting (OSR) service details cluster Indigenous, Archived 07/12/2017
OATSIH Services Reporting (OSR) service details cluster Indigenous, Endorsed 16/09/2014
OATSIH Services Reporting (OSR) service details cluster Indigenous, Archived 07/12/2017
Person details data dictionary Disability, Standard 13/08/2015
Service provider organisation contact information cluster Indigenous, Archived 07/12/2017
Service provider organisation contact information cluster Indigenous, Endorsed 07/12/2017
Service provider organisational contact cluster Indigenous, Endorsed 07/12/2017