[WWW - 2023.07.31]
Identifying and Definitional Attributes
QH 040003 v4
Data Element
Data Element
The person's identifying name(s) within the family group or by which the person is uniquely socially identified.
Clinical and administrative purposes and individual identification
Given name
First name, Middle name, Second name
Representational Attributes
Permissible Values


Supplementary Values


Collection and Usage Attributes
A person may have more than one given name, record all the given name(s) used by a person.
Display: The given name(s) is displayed or printed in mixed case.

The first given name would have a sequence number of 1, the second given name a sequence number of 2 and so on. It is essential that the Person (name)-given name sequence number be recorded for the first three recorded given names of a person. It is desirable if a Person (name)-given name sequence number could be recorded for the fourth and subsequent given names.

A full history of given names is to be retained.
May be null where One name indicator is code 1 - person has only one name.

The Oral Health Data Supply Requirement (DSR):
Must not be null.
A person should generally be registered using their preferred name as it is more likely in common usage and more likely to be used on subsequent visits to the health care facility. The given name by which the person wants to be identified should be indicated by the Person (name)-preferred name indicator data element as their preferred given name. This given name may be different from the given name on the person's Medicare card, or other given names the person may be identified by and should be recorded and indicated by the Person (name)-name usage type data element.

If given name is not known or cannot be established, record Unknown.

The given name indicated by the Person (name)-preferred name indicator should be recorded in the format preferred by the person. For example this may be the same as that indicated by the person on a form. Where appropriate, the given name indicated by the Person (name)-name usage type data element should be the same format as that printed on the relevant identification card (e.g. Medicare card) to ensure consistent collection of name data.

It is acknowledged that some people use more than one given name (e.g. formal name, birth name, nickname or shortened name, or tribal name) depending on the circumstances. In Queensland a person is able to change his or her name for usage. Care should be taken when recording a change of name for a minor, all relevant legal documentation should be obtained and diligently managed. Ideally, the name recorded for a minor should be known to both of his/her parents or guardian/carer, so the minor's records can be retrieved and continuity of care maintained, regardless of which parent accompanies a minor to a facility.

Whenever a person informs the facility of a change of given name (e.g. now prefers to be known by their second given name), the former given name should be recorded according to the appropriate Person (name)-name usage type. Do not delete or overwrite a previous given name.

e.g. Mary Georgina SMITH informs the hospital that she now prefers to be known as Georgina record Georgina as her given name, and indicate as preferred and record Mary according to the Person (name)-name usage type data element.

e.g. The facility is informed that B/O Louise JONES has been named Mary JONES. Retain B/O Louise as the newborn name using the Person (name)-name usage type where this option is available, or record it as an alias name in the case of older or legacy systems that may only have this field available. Record Mary as the given name, and indicate as preferred and also as the Medicare name if appropriate.

Multiple given names (e.g. first, second, third names)
All of the person's given names should be recorded against the relevant given name sequence number.

For example, Oscar Peter would be recorded with Oscar as the First Given Name (Code 1) and Peter as the Second Given Name (Code 2). The Given name sequence number data element provides more information about allocation of sequence numbers.

Registering an unidentified health care client
If the client's given name is not known record Unknown in the given name field and use the alias name usage type. When the client's name becomes known, add the actual name as the given name and make every attempt to identify whether it is the preferred and / or Medicare card name and retain the alias name of Unknown.

Use of aliases and pseudonyms (incomplete names or fictitious names):
The Department of Health recognises that some people may prefer to use an alias when they present to receive a health service. This may particularly be the case in sexual health.

If an alias given name is provided, it is recommended that a person be asked to also record their Medicare card given name. The given name that the person wishes to be identified by is indicated by the Person (name)-preferred name indicator.

Use of first initial
If the person's given name is not known, but the first letter (initial) of the given name is known, record the first letter as the given name and indicate as preferred. Do not record a full stop following the initial.

Person with only one name
Some people do not have a family name and a given name and 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 populate the Person (name)-one name indicator data element.

Shortened or alternate first given name
If the person uses a shortened version or an alternate version of their first given name, record this as their given name and indicate as preferred and also record their Medicare card name or alias name whichever applies.

E.g. The person's given name is Jennifer but she prefers to be called Jenny. Record Jenny as the given name and indicate as preferred and Jennifer as her Medicare card name or an alias whichever applies.

If non alphanumeric characters form part of the family name, consideration should be given to a system's capability to collect and interpret such characters. This is particularly relevant to older or legacy systems.

Hyphen e.g. Anne-Maree or Mary-Jane
Do not leave a space before or after the hyphen, i.e. between last letter of Anne and the hyphen, or a space between the hyphen and the first letter of Maree.

Spaces e.g. Jean Claude
If the person has recorded their given name as more than one word, displaying spaces in between the words, record their given names in data collection systems in the same way.

Registering an unnamed newborn baby
An unnamed (newborn) baby is to be registered using the mother's given name in conjunction with the prefix B/O. For example, if the given name of the baby's mother is Fiona, then record B/O Fiona in the given name field for the baby. B/O maps to Baby of in the national standards.

The unnamed newborn name is recorded under the newborn name, name usage type. If a name is subsequently given, record the new given name and indicate as preferred and/or Medicare card name and retain B/O Fiona as the newborn name or as an alias (older or legacy systems may only have this field available).

Registering unnamed multiple births
An unnamed (newborn) baby from a multiple birth regardless of if stillbirth (providing this meets the Queensland Births, Deaths and Marriages Registration Act) or live birth should use their mother's given name plus a reference to the multiple birth. For example, if the baby's mother's given name is Fiona and a set of twins is to be registered, then record Twin1 of Fiona in the Given Name field for the first born baby, and Twin2 of Fiona in the Given Name field of the second born baby.

The following terms should be used for recording multiple births:

Twin Use Twin i.e. Twin1 of Fiona
Triplet Use Trip i.e. Trip1 of Fiona
Quadruplet Use Quad i.e. Quad1 of Fiona
Quintuplet Use Quin i.e. Quin1 of Fiona
Sextuplet Use Sext i.e. Sext1 of Fiona
Septuplet Use Sept i.e. Sept1 of Fiona

Numbers (1, 2, 3 ...) are used, not roman numerals (I, II, III ...). Also note there should not be a space between twin and the number.

These names should be recorded under the newborn name usage type. When the babies are named, the name indicated as preferred and / or Medicare card name should be updated. The newborn name should be retained or recorded as an alias in the case of old or legacy systems that may only have this field available.

Aboriginal/Torres Strait Islander names not for continued use
For cultural reasons, an Aboriginal or Torres Strait Islander may advise a facility that they are no longer using the given name that they had previously registered and are now using an alternative given name. Indicate the given name the person wishes to be identified by as the preferred and record other given names as Medicare card name or alias name as appropriate.

Indigenous people traditionally name family members the same given name and family name for example Senior John Smith and Junior John Smith. Indicate the given name the person wishes to be identified by as the preferred and record other given names as Medicare card name or alias names as appropriate.

Ethnic Names
The Centrelink publication A Guide to Ethnic Naming Practices, provides information on the naming practices of people from culturally diverse backgrounds.

Misspelled given names
If the person's given name has been misspelled in error, update the given name field with the correct spelling and record the misspelled given name as an alias name. 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.

The Oral Health Data Supply Requirement (DSR):
External provider given name - Provide the given names of the person registered as a health service provider in an outsourced dental care.
Must not be null if care was provided.
Names registered in Australia use the Latin character set and are governed in Queensland by the Births Deaths and Marriages Registration Act 2003. In Queensland, prohibited names are proscribed in the Births, Deaths and Marriages Registration Act 2003.
Relational Attributes
Related Metadata References

Related Metadata References_IR

  • 1 - 3
ViewRelationshipMetadata Item TypeMetadata Item SubtypeNameIdentifier & VersionApproval Status
SupersedesData ElementData ElementHealth care client (name)-given nameQH 040003 Version 3Superseded
Has been superseded byData ElementData ElementPerson (name)-given nameQH 040003 Version 5Superseded
Relates toData ElementData ElementPerson (name)-family nameQH 040002 Version 4Superseded
Implementation in Metadata Sets


  • 1 - 5
ViewMetadata Item TypeMetadata Item SubtypeNameIdentifer & VersionObligationApproval StatusEffective FromEffective To
Data Supply RequirementQld LegislationLegionella Periodic (Quarterly) Reporting Data Supply Requirement (DSR)QH 020294 Version 1MandatoryCurrent01-Jul-201719-Mar-2018
Data Supply RequirementQld LegislationNotifying a Detection of Legionella Data Supply Requirement (DSR)QH 020295 Version 1MandatoryCurrent01-Jul-201719-Mar-2018
Data Supply RequirementHHS Service AgreementOral Health Data Supply Requirement (DSR)QH 020579 Version 1MandatoryCurrent01-Jul-201719-Mar-2018
Information AssetData CollectionQueensland Cancer Registry (QCR) Data CollectionQH 020002 Version 1Superseded29-May-201419-Mar-2018
Information AssetData CollectionQueensland Health Non-Admitted Patient Data Collection (QHNAPDC)QH 020262 Version 1ConditionalSuperseded01-Jul-201419-Mar-2018
Source and Reference Attributes
AS 4846-2014 Person and provider identification in healthcare, Sydney: Standards Australia