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

Site Navigation

  • 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
Your session is about to end!
Your session will expire at [TIME]
Select Extend at the top right corner or you will be logged out

Record—identifier, X[X(79)]

Data Element Attributes

Identifying and definitional attributes

Metadata item type:Help on this termData Element
Short name:Help on this termRecord identifier (80 character maximum)
Synonymous names:Help on this termState record identifier
METEOR identifier:Help on this term679557
Registration status:Help on this term

Health, Standard 25/01/2018

Definition:Help on this term

A logical combination of alphanumeric characters that uniquely identifies a record.

Data Element Concept:Help on this termRecord—identifier
Value Domain:Help on this termIdentifier X[X(79)]

Value domain attributes

Representational attributes

Representation class:Help on this termIdentifier
Data type:Help on this termString
Format:Help on this termX[X(79)]
Maximum character length:Help on this term80

Data element attributes Help on this term

Source and reference attributes

Submitting organisation:Help on this term

Australian Institute of Health and Welfare

Relational attributes

Related metadata references:Help on this term
Supersedes Record—identifier, X[X(79)]

        Health, Superseded 25/01/2018

Implementation in Data Set Specifications:Help on this term
All attributes +
Activity based funding: Non-admitted patient NBEDS 2018-19

        Independent Hospital Pricing Authority, Superseded 30/06/2019

DSS specific attributes +
Implementation start date: 01/07/2018
Implementation end date: 30/06/2019
DSS specific information:

In the context of the ABF NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2018-19

        Health, Superseded 12/12/2018

DSS specific attributes +
Implementation start date: 01/07/2018
Implementation end date: 30/06/2019
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2019-20

        Health, Superseded 18/12/2019

DSS specific attributes +
Implementation start date: 01/07/2019
Implementation end date: 30/06/2020
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2020–21

        Health, Superseded 05/02/2021

DSS specific attributes +
Implementation start date: 01/07/2020
Implementation end date: 30/06/2021
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2021–22

        Health, Superseded 20/10/2021

DSS specific attributes +
Implementation start date: 01/07/2021
Implementation end date: 30/06/2022
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2022–23

        Health, Superseded 20/12/2022

DSS specific attributes +
Implementation start date: 01/07/2022
Implementation end date: 30/06/2023
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2023–24

        Health, Standard 20/12/2022

DSS specific attributes +
Implementation start date: 01/07/2023
Implementation end date: 30/06/2024
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Admitted patient care NMDS 2024–25

        Health, Qualified 08/09/2023

DSS specific attributes +
Implementation start date: 01/07/2024
Implementation end date: 30/06/2025
DSS specific information:

In the context of the Admitted patient care NMDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data specification, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Emergency service care NBEDS 2022–23

        Health, Superseded 07/02/2023

DSS specific attributes +
Implementation start date: 01/07/2022
Implementation end date: 30/06/2023

Emergency service care NBEDS 2023–24

        Health, Standard 07/02/2023

DSS specific attributes +
Implementation start date: 01/07/2023
Implementation end date: 30/06/2024

Emergency service care NBEDS 2024–25

        Health, Qualified 08/09/2023

DSS specific attributes +
Implementation start date: 01/07/2024
Implementation end date: 30/06/2025

Leave and hospital-in-the-home care NBEDS 2024-25

        Health, Qualified 19/09/2023

DSS specific attributes +
Implementation start date: 01/07/2024
Implementation end date: 30/06/2025
DSS specific information:

In the LHITH NBEDS this data element collects the State Record Identifier (SRI), which identifies the episode of admitted patient care. It should be a stable and unique identifier consistent with the Admitted Patient Care collection.


Non-admitted patient emergency department care NBEDS 2018-19

        Health, Superseded 12/12/2018

DSS specific attributes +
Implementation start date: 01/07/2018
Implementation end date: 30/06/2019

Non-admitted patient emergency department care NBEDS 2019–20

        Health, Retired 19/11/2019

DSS specific attributes +
Implementation start date: 01/07/2019
Implementation end date: 30/06/2020

Non-admitted patient emergency department care NMDS 2018-19

        Health, Superseded 12/12/2018

DSS specific attributes +
Implementation start date: 01/07/2018
Implementation end date: 30/06/2019

Non-admitted patient emergency department care NMDS 2019–20

        Health, Superseded 18/12/2019

DSS specific attributes +
Implementation start date: 01/07/2019
Implementation end date: 30/06/2020

Non-admitted patient emergency department care NMDS 2020–21

        Health, Superseded 05/02/2021

DSS specific attributes +
Implementation start date: 01/07/2020
Implementation end date: 30/06/2021

Non-admitted patient emergency department care NMDS 2021–22

        Health, Superseded 20/10/2021

DSS specific attributes +
Implementation start date: 01/07/2021
Implementation end date: 30/06/2022

Non-admitted patient emergency department care NMDS 2022–23

        Health, Superseded 07/02/2023

DSS specific attributes +
Implementation start date: 01/07/2022
Implementation end date: 30/06/2023

Non-admitted patient emergency department care NMDS 2023–24

        Health, Standard 07/02/2023

DSS specific attributes +
Implementation start date: 01/07/2023
Implementation end date: 30/06/2024

Non-admitted patient emergency department care NMDS 2024–25

        Health, Qualified 08/09/2023

DSS specific attributes +
Implementation start date: 01/07/2024
Implementation end date: 30/06/2025

Non-admitted patient NBEDS 2018-19

        Health, Superseded 12/12/2018

DSS specific attributes +
Implementation start date: 01/07/2018
Implementation end date: 30/06/2019
DSS specific information:

In the context of the Non-admitted patient NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Non-admitted patient NBEDS 2019-20

        Health, Superseded 18/12/2019

        Independent Hospital Pricing Authority, Standard 01/07/2019

DSS specific attributes +
Implementation start date: 01/07/2019
Implementation end date: 30/06/2020
DSS specific information:

In the context of the NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Non-admitted patient NBEDS 2020–21

        Health, Superseded 05/02/2021

DSS specific attributes +
Implementation start date: 01/07/2020
Implementation end date: 30/06/2021
DSS specific information:

In the context of the NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Non-admitted patient NBEDS 2021–22

        Health, Superseded 20/10/2021

DSS specific attributes +
Implementation start date: 01/07/2021
Implementation end date: 30/06/2022
DSS specific information:

In the context of the NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Non-admitted patient NBEDS 2022–23

        Health, Superseded 20/12/2022

DSS specific attributes +
Implementation start date: 01/07/2022
Implementation end date: 30/06/2023
DSS specific information:

In the context of the NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Non-admitted patient NBEDS 2023–24

        Health, Standard 20/12/2022

DSS specific attributes +
Implementation start date: 01/07/2023
Implementation end date: 30/06/2024
DSS specific information:

In the context of the NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


Non-admitted patient NBEDS 2024–25

        Health, Qualified 08/09/2023

DSS specific attributes +
Implementation start date: 01/07/2024
Implementation end date: 30/06/2025
DSS specific information:

In the context of the NAP NBEDS, the Record identifier data element exists to aid with data processing. This data element is generated for inclusion in data submissions to facilitate referencing of specific records in discussions between the receiving agency and the reporting body. It is to be used solely for this purpose.

When stipulated in a data set, each record in a data submission will be assigned a unique numeric or alphanumeric record identifier to permit easy referencing of individual records in discussions between the receiving agency and the reporting body. The unique record identifier assigned by the reporting body should be generated in a fashion that allows the associated data record to be traced to its original form in the reporting body's source database.

Reporting jurisdictions may use their own alphabetic, numeric or alphanumeric coding system.

This field cannot be left blank.


<Title>

<body>
<footer>

View

  • Show more
  • Print view

Download

  • Word
  • PDF
  • Advanced options

Review

  • Compare items
Help
Downloading

The download may take a while, please wait.

Do not refresh the screen until the download is complete.

Terms & Conditions
Do you agree with the Terms and Conditions?

<Title>

<body>
<footer>
Loading...

Navigation

  • Find metadata
  • Metadata management
  • How to use METEOR
  • Learn about metadata

Resources

  • Accessibility
  • Copyright
  • Disclaimer
  • Freedom of Information
  • Privacy policy
  • Vulnerability and disclosure policy

Quick Links

  • Contact
  • FAQs
  • Search
AIHW logo
© Australian Insitute of Health and Welfware, 2023