Identifying and definitional attributes | |
Metadata item type: | Data Element |
---|---|
Short name: | Record identifier (80 character maximum) |
Synonymous names: | State record identifier |
METEOR identifier: | 555463 |
Registration status: | Health, Superseded 25/01/2018 |
Definition: | A record identifier that is unique to the reporting body, as represented by a code. |
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: | Has been superseded by Record—identifier, X[X(79)] Health, Standard 25/01/2018 |
Implementation in Data Set Specifications: | Admitted patient care NMDS 2014-15 Health, Superseded 13/11/2014 Implementation start date: 01/07/2014 Implementation end date: 30/06/2015 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 2015-16 Health, Superseded 10/11/2015 Implementation start date: 01/07/2015 Implementation end date: 30/06/2016 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 2016-17 Health, Superseded 05/10/2016 Implementation start date: 01/07/2016 Implementation end date: 30/06/2017 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 2017-18 Health, Superseded 25/01/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 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. Non-admitted patient DSS 2014-15 Health, Superseded 13/11/2014 Implementation start date: 01/07/2014 Implementation end date: 30/06/2015 DSS specific information: In the context of the Non-admitted patient DSS, 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. Non-admitted patient DSS 2015-16 Health, Superseded 19/11/2015 Implementation start date: 01/07/2015 Implementation end date: 30/06/2016 DSS specific information: In the context of the Non-admitted patient DSS, 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. Non-admitted patient emergency department care DSS 2014-15 Health, Superseded 04/02/2015 Implementation start date: 01/07/2014 Implementation end date: 30/06/2015 Non-admitted patient emergency department care DSS 2015-16 Health, Superseded 02/12/2015 Implementation start date: 01/07/2015 Implementation end date: 30/06/2016 Non-admitted patient emergency department care NBEDS 2016-17 Health, Superseded 05/10/2016 Implementation start date: 01/07/2016 Implementation end date: 30/06/2017 Non-admitted patient emergency department care NBEDS 2017-18 Health, Superseded 12/12/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 Non-admitted patient emergency department care NMDS 2014-15 Health, Superseded 13/11/2014 Implementation start date: 01/07/2014 Implementation end date: 30/06/2015 Non-admitted patient emergency department care NMDS 2015-16 Health, Superseded 19/11/2015 Implementation start date: 01/07/2015 Implementation end date: 30/06/2016 Non-admitted patient emergency department care NMDS 2016-17 Health, Superseded 05/10/2016 Implementation start date: 01/07/2016 Implementation end date: 30/06/2017 Non-admitted patient emergency department care NMDS 2017-18 Health, Superseded 25/01/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 Non-admitted patient NBEDS 2016-17 Health, Superseded 05/10/2016 Implementation start date: 01/07/2016 Implementation end date: 30/06/2017 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 2017-18 Health, Superseded 25/01/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 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. |