Record—identifier, X[X(79)]

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.

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.

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.

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.

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.

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.

Implementation start date: 01/07/2022

Implementation end date: 30/06/2023

Implementation start date: 01/07/2018

Implementation end date: 30/06/2019

Implementation start date: 01/07/2019

Implementation end date: 30/06/2020

Implementation start date: 01/07/2018

Implementation end date: 30/06/2019

Implementation start date: 01/07/2019

Implementation end date: 30/06/2020

Implementation start date: 01/07/2020

Implementation end date: 30/06/2021

Implementation start date: 01/07/2021

Implementation end date: 30/06/2022

Implementation start date: 01/07/2022

Implementation end date: 30/06/2023

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.

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.

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.

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.

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.