CDS UNIQUE IDENTIFIER

Format/Length:an35
National Codes: 
Default Codes: 

Notes:
See the supporting information in the Commissioning Data Set Submission Protocol.

A Commissioning Data Set data element providing a unique identity for the life-time of an episode carried in a Commissioning Data Set message.

Once assigned, a Commissioning Data Set record must retain its CDS UNIQUE IDENTIFIER otherwise duplicate Commissioning Data Set records may be generated and stored in the Secondary Uses Service database.

The CDS UNIQUE IDENTIFIER has three components. The recommended constructs are given below.

For All CDS Types EXCEPT the EAL CDS Types:

REFUIDFORMATCODES / VALUESCOMMENT
1NHS Organisation Code Type an1A = Pre 1996 Organisation Code
B = Post 1996 NHS Organisation Code
Mandatory For all CDS Types 
2Provider Code an5The NHS Organisation Code of the Provider at the time of, or at the start of, the period covered by the activity reported by the CDS Message.Mandatory for all CDS Types 
3aApplication Specific CDS Identity an29A code of up to 29 alpha-numeric characters generated by the Sender's application to uniquely identify the CDS within its CDS Type or family of CDS TypesMandatory for all CDS Types
Except for EAL CDS Types 

For EAL End Of Period (EOP) CDS Types only:

REFUIDFORMATCODES / VALUESCOMMENT
1NHS Organisation Code Type an1A = Pre 1996 Organisation Code
B = Post 1996 NHS Organisation Code
Mandatory For all CDS Types 
2Provider Code an5The NHS Organisation Code of the Provider at the time of, or at the start of, the period covered by the activity reported by the CDS Message.Mandatory for all CDS Types 
3bApplication Specific CDS Identity an9A code of up to 9 alpha-numeric characters generated by the Sender's application to uniquely identify the EAL End Of period census CDS Types with the same Admission List Entry. Additional data positions must be left blank.Mandatory for all EAL EOP CDS Types 
3cFiller an20Additional data positions must be left blank. 

For EAL Event During Period (EDP) CDS Types only:

REFUIDFORMATCODES / VALUESCOMMENT
1NHS Organisation Code Type an1A = Pre 1996 Organisation Code
B = Post 1996 NHS Organisation Code
Mandatory For all CDS Types 
2Provider Code an5The NHS Organisation Code of the Provider at the time of, or at the start of, the period covered by the activity reported by the CDS Message.Mandatory for all CDS Types 
3dApplication Specific CDS Identity an9A code of up to 5 alpha-numeric characters padded with 4 trailing spaces to 9 characters. Generated by the Sender's application to uniquely identify the EAL Event During Period Census CDS Types with the same Admission List Entry.Mandatory for all EAL EDP CDS Types 
3eFiller an3A code of 3 alpha-numeric characters generated by the Sender's application to identify the event within the EAL Entry. Even if the events are of different types, they must have different identifiers. .Mandatory for all EAL EDP CDS Types 
3fFiller an17Additional data positions must be left blank. 

Usage:
See the supporting information in the Commissioning Data Set Submission Protocol for detailed information.

This is a mandatory data item when the Net Change Update Mechanism is used and strongly recommended for use with the Bulk Replacement Update Mechanism.

However it is strongly advised that users of the Bulk Replacement Mechanism maintain a correctly generated CDS UNIQUE IDENTIFIER within the Commissioning data. This will establish a migration path towards the use of the Net Change Mechanism and will also then minimise the risk of creating duplicate Commissioning Data Set data in the Secondary Uses Service database.

1. Note that senders of Commissioning Data Set data remain directly responsible for the integrity of the CDS UNIQUE IDENTIFIER.
2. The first two components, the ORGANISATION CODE TYPE and the ORGANISATION CODE (CODE OF PROVIDER), are required for all CDS Types.
3. It is a mandatory requirement for all submissions using the Net Change Update Mechanism that these two components are constructed correctly to ensure uniqueness of CDS UNIQUE IDENTIFIERS across the NHS.
4. The structure of 3b and 3c allows the EAL End of Period Census and the EAL Event During Period Census for the same EAL Entry to be linked.

There are circumstances in patient care application systems where the control of the UID key integrity may be suspect. These issues include:

a) Episode deletion (not resulting in a Commissioning Data Set deletion of previously submitted data sent to the original Commissioner);
b) Episode re-sequencing (not resulting in a corresponding Commissioning Data Set records being sent);
c) Service agreement alterations not resulting in correct adjustments - Old Service Agreement deletion / New Service Agreement addition
d) Re-admissions causing duplicate keys on the Secondary Uses Service database.

 

This data element is also known by these names:
ContextAlias
pluralCDS UNIQUE IDENTIFIERS