AIHW logo
METEOR logo
Our sites
AIHW GEN Aged Care Data Aboriginal and Torres Strait Islander
Health Performance Framework
Indigenous Mental Health and
Suicide Prevention Clearinghouse
Australian Mesothelioma Registry Housing data Regional Insights for Indigenous Communities
Contact FAQs
  • Find metadata
    • Find metadata
    • Getting started
    • Data set specifications
    • Indicator sets
    • Data quality statements
    • Data dictionary archives
  • Metadata management
    • Metadata management
    • Data standards
    • Registration authorities
    • Registration statuses
  • How to use METEOR
    • How to use METEOR
    • First steps
    • Using My Page
    • Downloading and printing
    • FAQs
    • About METEOR
  • Learn about metadata
    • Learn about metadata
    • Metadata explained
    • How to create metadata
    • Metadata development resources

Individual name cluster

Identifying and definitional attributes

Metadata item type:Help on this termData Set Specification
METEOR identifier:Help on this term528153
Registration status:Help on this term
  • Health, Standard 05/10/2016
DSS type:Help on this termData Element Cluster
Scope:Help on this term

The Individual name cluster includes data elements that in combination define an individual's name. An individual’s name consists of the following components: name title, given name, family name, family name prefix and name suffix.

Collection and usage attributes

Guide for use:Help on this term

Each name component has an associated sequence number data element that describes the sequence by which each name component should be combined. It should be noted that a person can have multiples of a single name component.

It is acknowledged that some people use more than one name (for example formal name, birth name, married/maiden name and tribal name), depending on the circumstances. In healthcare, name is used not only as an identifier but also as a major means of communication and trust, and name is also a matter of privacy. For this reason, it shall be recognised that people use different names for different purposes.

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 parents so that the minor’s records can be retrieved and continuity of care can be maintained, regardless of which parent accompanies the minor to the agency or establishment.

A person should generally be registered using their preferred name as it is more likely to be used in common usage and on subsequent visits to an agency or establishment. The person's preferred name may in fact be their legal name.

Collection methods:Help on this term

This data element cluster represents one full name for an individual. A full name must include at least one family name, and can include name titles, given names, family name prefixes and name suffixes.

There can be more than one full name recorded for an individual; in that situation, the data element cluster should be recorded for each full name. At least one name must be recorded, and the preferred name should always be sought.

Source and reference attributes

Submitting organisation:Help on this term

Australian Institute of Health and Welfare

Reference documents:Help on this term

Standards Australia 2014. AS 4846:2014 Person and provider identification in healthcare. Sydney: Standards Australia.

Relational attributes

Implementation in Data Set Specifications:Help on this term
All attributes +

Person and provider identification in healthcare National Best Practice Data SetHealth, Standard 05/10/2016

DSS specific attributes +

DSS specific information:

This data element cluster should be recorded every time a full name is provided by an individual. A full name must include at least one family name, and can include name titles, given names, family name prefixes and name suffixes.

There can be more than one full name recorded for an individual; in that situation, the data element cluster should be recorded for each full name. At least one name must be recorded, and the preferred name should always be sought.


Metadata items in this Data Set SpecificationHelp on this term

Show more detail
Seq No.Help on this termMetadata itemHelp on this termObligationHelp on this termMax occursHelp on this term
1Person—name title, text X[X(11)]Optional99
2Person—name title sequence number, code N[N]

Conditional obligation:

Conditional upon Person—name title, text X[X(11)] being recorded.

Conditional99
3Person—given name, text X[X(39)]

DSS specific information:

The response to Person—single name only flag, yes/no code N must be 'no'.

Optional99
4Person—given name sequence number, code N[N]

Conditional obligation:

Conditional upon Person—given name, text X[X(39)] being recorded.

Conditional99
5Person—family name prefix, text A[A(29)]Mandatory99
6Person—family name prefix sequence number, code N[N]

Conditional obligation:

Conditional upon Person—family name prefix, text A[A(29)] being recorded.

Conditional99
7Person—family name, text X[X(39)]

DSS specific information:

Any person shall have at least one family name.

Mandatory99
8Person—family name sequence number, code N[N]

DSS specific information:

Recorded in conjunction with Person—family name, text X[X(39)].

Mandatory99
9Person—name suffix, text X[X(4)]Optional99
10Person—name suffix sequence number, code N[N]

Conditional obligation:

Conditional upon Person—name suffix, text X[XXXX] being recorded.

Conditional99
11Person—name usage type, code XOptional1
12Person—name usage type start date, DDMMYYYY

Conditional obligation:

Conditional on Person—name usage type, code N being recorded.

Conditional1
13Person—name usage type end date, DDMMYYYY

Conditional obligation:

Conditional on Person—name usage type, code N being recorded. Only recorded when an end date is identified.

Conditional1
14Date—accuracy indicator, code AAA

DSS specific information:

Recorded in conjunction with the data elements within this cluster that are used to record a date.

Mandatory2
15Identifier—identifier usage, code NNNOptional1
16Person—preferred name indicator, yes/no code XOptional1
17Person—single name only flag, code A

DSS specific information:

If given name is blank when registration occurs, this field should be asked.

Mandatory1
18Restricted name usage cluster

DSS specific information:

A single full name may have multiple conditional use flags associated with it. This data element cluster should be recorded as many times as applicable.

Optional1
Help
Downloading

The download may take a while, please wait.

Do not refresh the screen until the download is complete.

<Title>

<body>
<footer>
  • View
  • Show more
  • Print view
  • Download
  • Word™
  • Pdf
  • Advanced Download
  • Review
  • Compare items
© Australian Institute of Health and Welfare
Version 1.0.0+20220531.2