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

Health care provider identification DSS

Identifying and definitional attributes

Metadata item type:Help on this termData Set Specification
METEOR identifier:Help on this term374199
Registration status:Help on this term
  • Health, Retired 20/03/2013
DSS type:Help on this termData Set Specification (DSS)
Scope:Help on this term

The scope of these data elements includes identification of individual and organisation health care providers. The data elements also allow for identification of an individual in a health care organisation. The definition of health care provider is:

'any person or organisation who is involved in or associated with the delivery of healthcare to a client, or caring for client wellbeing'.

The data elements have been defined to enable a common, best practice approach to the way data are captured and stored, to ensure that records relating to a provider will be associated with that individual and/or organisation and no other. The definitions are proposed for clinical and administrative data management purposes.

The ability to positively identify health care providers and locate their relevant details is an important support to the provision of speedy, safe, high quality, comprehensive and efficient health care. Unambiguous identification of individual health care providers is necessary for:

  • Requesting and reporting of orders, tests and results (e.g. pathology, diagnostic imaging)
  • Other communications and referrals between health care providers regarding ongoing care of patients (e.g. a referral from a GP to a specialist, a hospital discharge plan)
  • Reporting on health care provision to statutory authorities (e.g. reporting of hospital patient administration systems data to State/Territory government health agencies)
  • Payments to providers
  • Registration of providers
  • Directories or lists of providers and their service locations for consumer information.

Collection and usage attributes

Collection methods:Help on this termCollected at point of entry to health care for the purposes of the identification of the provider of that health care.
Comments:Help on this termThere are many barriers to successfully identifying individuals in health care settings, including variable data quality; differing data capture requirements and mechanisms; and varying data matching methods. This data set specification provides a framework for improving the confidence that the data being associated with any given individual or organisation, is appropriately associated.

Source and reference attributes

Submitting organisation:Help on this termStandards Australia Inc Health Informatics Committee (IT-014)
Reference documents:Help on this term

Health care client identification DSS

The Australian Standard AS4846 Health Care Provider Identification identifies other data that should be collected. These data are collections of free text information and as such are not capable of standardisation as a national health data standard. Within AS4846 however they form part of the data collection necessary for the complete identification of a heath care provider.

These data elements are identified in the section Standardised elsewhere section below.

If these data elements are collected in conjunction with those of the Data set specification they form a collection equivalent to that of the Australian Standard AS4846.

Relational attributes

Related metadata references:Help on this term
Supersedes Health care provider identification DSS
  • Health, Superseded 03/12/2008
See also Person and provider identification in healthcare National Best Practice Data Set
  • Health, Standard 05/10/2016

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
-Date—accuracy indicator, code AAAMandatory1
-Individual service provider—occupation (self-identified), code (ANZSCO 1st edition) N[NNN]{NN}Mandatory1
-Individual service provider—occupation end date, DDMMYYYY

DSS specific information:

This date must:

  • be greater than or equal to the provider occupation start date;
  • be a valid date;
  • be collected for each provider occupation recorded.

If the date is estimated in some way, it is recommended that the metadata item Date accuracy indicator also be recorded at the time of record creation to flag the accuracy of the data.

For data integrity, data exchange, future data analysis and/or manipulation of data from diverse sources the Date accuracy indicator must be used in conjunction with the provider occupation end date in all instances to ensure accuracy.

Mandatory1
-Individual service provider—occupation start date, DDMMYYYY

DSS specific information:

This date must:

  • be greater than or equal to the provider occupation start date;
  • be a valid date;
  • be collected for each provider occupation recorded.

If the date is estimated in some way, it is recommended that the metadata item Date accuracy indicator also be recorded at the time of record creation to flag the accuracy of the data.

For data integrity, data exchange, future data analysis and/or manipulation of data from diverse sources the Date accuracy indicator must be used in conjunction with the provider occupation start date in all instances to ensure accuracy.

Mandatory1
-Person (address)—address line, text X[X(179)]Mandatory1
-Person (address)—address type, code NMandatory1
-Person (address)—Australian postcode, code (Postcode datafile) {NNNN}Mandatory1
-Person (address)—building/complex sub-unit identifier, [X(7)]Mandatory1
-Person (address)—building/complex sub-unit type, code A[AAA]Mandatory1
-Person (address)—building/property name, text X[X(29)]Mandatory1
-Person (address)—country identifier, code (SACC 2008) NNNNMandatory1
-Person (address)—electronic communication address, text [X(250)]Mandatory1
-Person (address)—electronic communication medium, code N

DSS specific information:

Multiple electronic communication addresses (for example, multiple phone numbers, fax numbers and e-mail) may be recorded as required. Each instance should have an appropriate Electronic communication medium and Electronic communication usage code assigned.
Mandatory1
-Person (address)—electronic communication usage, code N

DSS specific information:

Multiple electronic communication addresses (for example, multiple phone numbers, fax numbers and e-mail) may be recorded as required. Each instance should have an appropriate Electronic communication medium and Electronic communication usage code assigned.
Mandatory1
-Person (address)—floor/level identifier, [NNNA]Mandatory1
-Person (address)—floor/level type, code A[A]Mandatory1
-Person (address)—house/property identifier, text X[X(11)]Mandatory1
-Person (address)—international postcode, text X[X(9)]Mandatory1
-Person (address)—lot/section identifier, N[X(14)]Mandatory1
-Person (address)—non-Australian state/province, text [X(40)]

DSS specific information:

When used for identification purposes record this data element as part of an address.
Mandatory1
-Person (address)—postal delivery point identifier, {N(8)}Mandatory1
-Person (address)—street name, text A[A(29)]Mandatory1
-Person (address)—street suffix, code A[A]Mandatory1
-Person (address)—street type, code A[AAA]Mandatory1
-Person (address)—suburb/town/locality name, text A[A(49)]

DSS specific information:

This data should be verified against the Australia Post Postcode File (see
www.auspost.com.au/postcodes). Alternatively, contact State or Territory
Health Authorities for Postcode files.
Mandatory1
-Person (name)—family name, text X[X(39)]

DSS specific information:

When used for the purpose of positive identification or contact, agencies or establishments that collect Family name should also collect Person name type.
Mandatory1
-Person (name)—given name sequence number, code NMandatory1
-Person (name)—given name, text X[X(39)]Mandatory1
-Person (name)—name conditional use flag, code NMandatory1
-Person (name)—name suffix sequence number, code NMandatory1
-Person (name)—name suffix, text A[A(11)]Mandatory1
-Person (name)—name title sequence number, code NMandatory1
-Person (name)—name title, text A[A(11)]

DSS specific information:

For the purpose of positive identification of a person, each name title should be associated with a Name title sequence number.

Name title should not be confused with job title. An example of Name title is 'Mr' for Mister.

Mandatory1
-Person (name)—name type, code NMandatory1
-Person—Australian state/territory identifier, code NMandatory1
-Person—date of birth, DDMMYYYY

DSS specific information:

Date of birth must be less than or equal to the date of death.
Mandatory1
-Person—date of death, DDMMYYYYMandatory1
-Person—person identifier, XXXXXX[X(14)]

DSS specific information:

Field cannot be blank.
Mandatory1
-Person—sex, code NMandatory1
-Service provider organisation (address)—address line, text X[X(179)]Mandatory1
-Service provider organisation (address)—address type, code NMandatory1
-Service provider organisation (address)—Australian postcode, code (Postcode datafile) {NNNN}Mandatory1
-Service provider organisation (address)—building/complex sub-unit identifier, [X(7)]Mandatory1
-Service provider organisation (address)—building/complex sub-unit type, code A[AAA]Mandatory1
-Service provider organisation (address)—building/property name, text X[X(29)]Mandatory1
-Service provider organisation (address)—electronic communication address, text [X(250)]Mandatory1
-Service provider organisation (address)—electronic communication medium, code N

DSS specific information:

Multiple electronic communication addresses (for example, multiple phone numbers, fax numbers and e-mail) may be recorded as required. Each instance should have an appropriate Electronic communication medium and Electronic communication usage code assigned.
Mandatory1
-Service provider organisation (address)—floor/level identifier, [NNNA]Mandatory1
-Service provider organisation (address)—floor/level type, code A[A]Mandatory1
-Service provider organisation (address)—house/property identifier, text X[X(11)]Mandatory1
-Service provider organisation (address)—international postcode, text X[X(9)]Mandatory1
-Service provider organisation (address)—lot/section identifier, N[X(14)]Mandatory1
-Service provider organisation (address)—non-Australian state/province, text X[X(39)]

DSS specific information:

When used for identification purposes record this data element as part of an address.
Mandatory1
-Service provider organisation (address)—postal delivery point identifier, {N(8)}Mandatory1
-Service provider organisation (address)—street name, text A[A(29)]Mandatory1
-Service provider organisation (address)—street suffix, code A[A]Mandatory1
-Service provider organisation (address)—street type, code A[AAA]Mandatory1
-Service provider organisation (address)—suburb/town/locality name, text A[A(49)]

DSS specific information:

This data should be verified against the Australia Post Postcode File (see www.auspost.com.au/postcodes). Alternatively, contact State or Territory Health Authorities for Postcode files.
Mandatory1
-Service provider organisation (name)—name type, code NMandatory1
-Service provider organisation (name)—organisation name, text X[X(199)]Mandatory1
-Service provider organisation—Australian state/territory identifier, code N

DSS specific information:

When used specifically in the collection of address information for a client, the following local implementation rules may be applied:

NULL may be used to signify an unknown address State; and Code 0 may be used to signify an overseas address.

Mandatory1
-Service provider organisation—organisation end date, DDMMYYYYMandatory1
-Service provider organisation—organisation start date, DDMMYYYY

DSS specific information:

If the date is estimated in some way, it is recommended that the metadata item Date accuracy indicator also be recorded at the time of record creation to flag the accuracy of the data.

For data exchange and /or manipulation of data from diverse sources the Date accuracy indicator metadata item must be used in conjunction with the Organisation start date in all instances to ensure data integrity and accuracy of analysis.

Mandatory1
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+20220809.3