Commissioning Data Set Submission Protocol

The Commissioning Data Sets submitted by providers carry information to determine the update method to be used by the Secondary Uses Service in order to update the national database.

These update rules are known as the Commissioning Data Set Submission Protocol  and the set of data controls used to indicate this are carried in the Commissioning Data Set Transaction Header Group which must be present and correct in every CDS Type submitted to the Secondary Uses Service.

Net Change: Net Change processes are managed by specific data settings as defined in the  CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol  / CDS V6-3 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol  option of the CDS Transaction Header Group. The Secondary Uses Service uses the following data to manage the database:

• CDS SENDER IDENTITY

  / ORGANISATION IDENTIFIER (CDS SENDER)

• CDS UNIQUE IDENTIFIER
• CDS APPLICABLE DATE
• CDS APPLICABLE TIME

Note that CDS SENDER IDENTITY is used for CDS V6-2 and CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set. ORGANISATION IDENTIFIER (CDS SENDER) is used for CDS V6-2-3 Type 011 - Emergency Care Commissioning Data Set and  CDS Version 6-3 onwards. 

Each CDS Type must have a CDS UNIQUE IDENTIFIER which must be uniquely maintained throughout the life of that Commissioning Data Set record. This is a particular consideration where mergers and/or healthcare systems are changed or upgraded, see Commissioning Data Set Submission and Organisation Mergers. Any change to the CDS UNIQUE IDENTIFIER during the "lifetime" of a Commissioning Data Set record will almost certainly result in a duplicate record being lodged in the Secondary Uses Service database.

A Commissioning Data Set record delete transaction must be sent to the Secondary Uses Service database when any previously sent Commissioning Data Set record requires deletion/removal, for example to reflect Commissioner changes etc. 

Where CDS UPDATE TYPE  1 is required (delete/cancellation), an empty XML element called 'Delete Transaction' can be used instead of submitting he original CDS Type  record, after the CDS V6-2 Type 005N - CDS Transaction Header Group - Net Change Protocol/ CDS V6-3 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol. See the CDS V6-2 or CDS V6-3 XML Schema Release Notes which can be downloaded via the XML Schema TRUD Download  page.

The CDS APPLICABLE DATE and CDS APPLICABLE TIME must be used to ensure that all Commissioning data is updated in the Secondary Uses Service database in the correct chronological order.

The CDS SENDER IDENTITY/ ORGANISATION IDENTIFIER (CDS SENDER) must not change during the lifetime of the CDS data.  This is particularly significant for multiple and/or merged ORGANISATIONS, and for those services who submit data on behalf of another  NHS Trust,  NHS Foundation Trust  or  Independent Sector Healthcare Provider.

Bulk Replacement Bulk Replacement processes are managed by specific data settings as defined in the  CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol/ CDS V6-3 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol option of the CDS Transaction Header Group. The Secondary Uses Service uses the following data to manage the database:

• CDS SENDER IDENTITY

  / ORGANISATION IDENTIFIER (CDS SENDER)

• CDS BULK REPLACEMENT GROUP CODE
• CDS EXTRACT DATE
• CDS EXTRACT TIME
• CDS REPORT PERIOD START DATE
• CDS REPORT PERIOD END DATE

Note that CDS SENDER IDENTITY is used for CDS V6-2 and CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set. ORGANISATION IDENTIFIER (CDS SENDER) is used for CDS V6-2-3 Type 011 - Emergency Care Commissioning Data Set and  CDS V6-3 onwards.

Every CDS Type must be submitted using the correct CDS BULK REPLACEMENT GROUP CODE.

The CDS REPORT PERIOD START DATE and the CDS REPORT PERIOD END DATE, (i.e. the effective date period), must be valid and consistent, and reflect the dates relevant to the Commissioning data contained in the interchange.

The CDS SENDER IDENTITY/ ORGANISATION IDENTIFIER (CDS SENDER) must not change during the lifetime of the Commissioning Data Set record. This is particularly significant for multiple and/or merged ORGANISATIONS, and for those services who submit data on behalf of another  ORGANISATION.

For submissions of CDS V6-2 and CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set, the CDS PRIME RECIPIENT IDENTITY is Mandatory for submission in the CDS Type 005B (CDS Transaction Header Group - Bulk Update Protocol) and CDS Type 005N (CDS Transaction Header Group - Net Change Protocol). However, it no longer forms part of the key for the process of determining duplicate records within the Secondary Uses Service. Note that the CDS PRIME RECIPIENT IDENTITY continues to be used to determine data access requirements within the Secondary Uses Service  for Commissioning Data Set  version 6-2 submissions.  For Commissioning Data Set  version 6-3 and CDS V6-2-3 Type 011 - Emergency Care Commissioning Data Set, data element ORGANISATION IDENTIFIER (CDS RECIPIENT)  is used for this purpose.

If it is necessary to change any of this data during the lifetime of a Commissioning Data Set record, then the Secondary Uses Service (SUS) Service Desk should be contacted for advice. See the NHS England website at: Secondary Uses Service (SUS).

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.

Sub contracting If a Health Care Provider sub-contracts healthcare provision and its associated Commissioning Data Set submission to a second ORGANISATION  (eg a different Health Care Provider  or a Shared Services Organisation), arrangements to submit the Commissioning Data Set data must be made locally to ensure that only one ORGANISATION  sends the Commissioning Data Set data to the Secondary Uses Service.

If the second ORGANISATION  wishes to add other Commissioning data to the Secondary Uses Service database to that already submitted by the first ORGANISATION, both parties need to ensure that a different CDS SENDER IDENTITY/ ORGANISATION IDENTIFIER (CDS SENDER) is used.

Note: Data sent using the same CDS SENDER IDENTITY/ ORGANISATION IDENTIFIER (CDS SENDER) by two different parties will most likely overwrite each other's data in the Secondary Uses Service database. Further advice can be obtained from the Secondary Uses Service (SUS) Service Desk, see the  NHS England  website at: Secondary Uses Service (SUS) Guidance.

Users should be aware of how the 15 character code of their CDS INTERCHANGE SENDER IDENTITY (also known as the EDI Address) is created. This may depend on how their XML interface solution has been set up. It may not be possible to rely on a change to the ORGANISATION CODE (CODE OF PROVIDER)/ ORGANISATION IDENTIFIER (CODE OF PROVIDER)  in order to change the CDS INTERCHANGE SENDER IDENTITY should this become necessary.