Record—identifier, X[X(79)]

Identifying and definitional attributes
Metadata item type:	Data Element
Short name:	Record identifier (80 character maximum)
Synonymous names:	State record identifier
METEOR identifier:	679557
Registration status:	Health, Standard 25/01/2018
Definition:	A logical combination of alphanumeric characters that uniquely identifies a record.
Data Element Concept:	Record—identifier
Value Domain:	Identifier X[X(79)]

Value domain attributes
Representational attributes
Representation class:	Identifier
Data type:	String
Format:	X[X(79)]
Maximum character length:	80

Data element attributes
Source and reference attributes
Submitting organisation:	Australian Institute of Health and Welfare
Relational attributes
Related metadata references:	Supersedes Record—identifier, X[X(79)] Health, Superseded 25/01/2018
Implementation in Data Set Specifications: 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.