[WWW - 2023.07.31]
Identifying and Definitional Attributes
QH 042424 v2
Data Element
Data Element
Draft
15-Mar-2019
Current
16-Jul-2019
Standard
Information Management Strategic Governance Committee (IMSGC), Queensland Health
01-Jul-2018
The part of a name a person usually has in common with some other members of his/her family, as distinguished from his/her given name.
Family name (QHAPDC, QPDC)
Surname; Last name; Mother's family name (QPDC)
Representational Attributes
Character
Text
X[X(23)]
1
24
Permissible Values

Permissible_values

-
Supplementary Values

Supplemenary_values

CodeDescription
NOVALUNKNOWN
Collection and Usage Attributes
A person's family name is one of the following:
- the hereditary or tribal name of a person's family
- acquired by a person in accordance with a due process defined in a state or territory Act relating to the registration of births, deaths, marriages and changes of name and sex, and for related purposes
- any other name distinguished from a person's given name.

A person's full family name shall be recorded. A history of family names shall be retained.

All parts of a family name are to be displayed and printed in CAPITAL letters to clearly differentiate it from other parts of a name.

Consideration shall be given to the unnecessary use of non-alphanumeric characters and symbols, which should be avoided wherever possible due to implications on system functionality.
Queensland Hospital Admitted Patient Data Collection (QHAPDC) and Queensland Perinatal Data Collection (QPDC):
Must not contain unidentified characters/symbols.
Left adjusted and space filled to 24 characters.
Must not be blank.
Record up to the first 24 characters of the patient's full family name.

Consideration shall be given to the unnecessary use of non-alphanumeric characters and symbols, which should be avoided wherever possible due to implications on system functionality.

If family name is not known or cannot be established, record UNKNOWN.
Some people do not have a family name and a given name. They have only one name by which they are known. If the patient has only one name, record it as the family name.

The family name indicated by the 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 family name indicated by the 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.

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 the 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 the minor to the facility.

Whenever a person informs the facility of a change of family name (e.g. following marriage or divorce) the former family name should be recorded as an alias name. A full history of names should be retained. E.g. Mary Georgina SMITH informs the hospital that she has been married, changed her family name and wishes to be known as Mary Georgina JONES. Record JONES, as her preferred family name and record SMITH as an alias name.

Punctuation
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. WILSON-PHILLIPS
If the person has a hyphenated family name it should be recorded with a hyphen, for example 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.

Sometimes people with hyphenated family names use only one of the two hyphenated names for example WILSON-PHILLIPS. Record the family name indicated by the person as the preferred name, for example WILSON and record each of the family names as an alias.
E.g. WILSON PHILLIPS and WILSON-PHILLIPS

Apostrophe e.g. O'BRIEN
If a person has an apostrophe in their family name, 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.
E.g. O'BRIEN, D'AGOSTINO.

Full stop e.g. ST. JOHN
If a person has a full stop in their family name, 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.
E.g. ST. JOHN, ST. GEORGE.

Spaces e.g. VAN DER HUMM
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.
E.g. VAN DER HUMM, LE BRUN, MC DONALD.

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.

Registering an unidentified client
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 client's family name becomes known, record it as the family name and make every attempt to identify whether it is the preferred and / or Medicare card family name. Keep the UNKNOWN as an alias name.

Registering people from disaster sites
Clients treated from disaster sites should be recorded under the alias name usage type. Local business rules should be developed for consistent recording of disaster site client details. Care should be taken not to use identical dummy data (family name, given names, date of birth, sex) for two or more clients from a disaster site.

Use of aliases and pseudonyms
It is recognised that some people may prefer to use an alias when they present to receive a health service.

If an alias name is recorded for the family name, it is recommended that a person be asked to also record their Medicare card family name.

Baby for adoption
A newborn baby that is for adoption should be registered in the same way that other newborn babies are registered. Refer to the Department of Health Managing the clinical records of children available for adoption Standard and Guideline.

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 family name that they had previously registered. Record their current name as the family and record the discontinued name as an alias.

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

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

Baby for adoption
The word 'adoption' should not be used as the family name, given names 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 with a new UR number, and the record should not be linked to the birth record. This should be the current practice. Any old references to adoption in patient registers (for names) should also be changed to UNKNOWN. Refer to the Queensland Health Managing the Clinical Records of Children Available for Adoption Policy and Managing the Clinical Records of Children for Adoption Guideline for further information.

Queensland Perinatal Data Collection (QPDC):
Record the family name of of the mother.

Operating theatre operations data supply requirement 2019-2020
The family name of the consultant assigned to the operation/ surgical consultant family name (SurgiNet)
Relational Attributes
Related Metadata References

Related Metadata References_IR

  • 1 - 4
ViewRelationshipMetadata Item TypeMetadata Item SubtypeNameIdentifier & VersionApproval Status
SupersedesData ElementData ElementPerson (name)-family name (QHAPDC, QPDC)QH 042424 Version 1Superseded
Relates toData ElementData ElementPerson (name)-family nameQH 040002 Version 5Current
Relates toData ElementData ElementPerson (name)-first given name (QHAPDC, QPDC)QH 042425 Version 2Current
Relates toData ElementData ElementPerson (name)-second given name (QHAPDC, QHNAPDC, QPDC)QH 042426 Version 2Current
Implementation in Metadata Sets

Implemented

  • 1 - 15
ViewMetadata Item TypeMetadata Item SubtypeNameIdentifer & VersionObligationApproval StatusEffective FromEffective To
Information AssetData CollectionQueensland Hospital Admitted Patient Data Collection (QHAPDC)QH 020001 Version 2MandatoryCurrent01-Jul-2019
Information AssetData CollectionQueensland Hospital Admitted Patient Data Collection (QHAPDC)QH 020001 Version 1MandatorySuperseded01-Jul-201830-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Private Facility Data Supply Requirement (DSR) 2018-2019QH 020503 Version 1MandatorySuperseded01-Jul-201830-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Private Facility Data Supply Requirement (DSR) 2019-2020QH 020581 Version 1MandatorySuperseded01-Jul-201930-Jun-2020
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Private Facility Data Supply Requirement (DSR) 2020-2021QH 020692 Version 1MandatorySuperseded01-Jul-202030-Jun-2021
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Private Facility Data Supply Requirement (DSR) 2021-2022QH 020780 Version 1MandatorySuperseded01-Jul-202130-Jun-2022
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Private Facility Data Supply Requirement (DSR) 2022-2023QH 0139401 Version 1MandatoryCurrent01-Jul-202230-Jun-2023
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Public Hospital Services Data Supply Requirement (DSR) 2018-2019QH 020504 Version 1MandatorySuperseded01-Jul-201830-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Public Hospital Services Data Supply Requirement (DSR) 2019-2020QH 020582 Version 1MandatorySuperseded01-Jul-201930-Jun-2020
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Public Hospital Services Data Supply Requirement (DSR) 2020-2021QH 020693 Version 1MandatorySuperseded01-Jul-202030-Jun-2021
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Public Hospital Services Data Supply Requirement (DSR) 2021-2022QH 020781 Version 1MandatorySuperseded01-Jul-202130-Jun-2022
Data Supply RequirementHHS Service AgreementQueensland Hospital Admitted Patient Data Collection (QHAPDC) Public Hospital Services Data Supply Requirement (DSR) 2022-2023QH 0140697 Version 1MandatoryCurrent01-Jul-202230-Jun-2023
Information AssetData CollectionQueensland Perinatal Data Collection (QPDC)QH 020003 Version 2MandatoryCurrent01-Jul-2019
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2018-2019QH 020448 Version 1MandatorySuperseded01-Jul-201830-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2019-2020QH 020569 Version 1MandatorySuperseded01-Jul-201930-Jun-2020
Source and Reference Attributes