Introduction

The CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-1 Type 005N - CDS Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-1 Type 005N - CDS Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-1 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-1 Type 003 - Commissioning Data Set Message Header should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Net Change Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set carries the data for an Emergency Care Attendance.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-2 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-2 Type 003 - Commissioning Data Set Message Header should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

Note that the CDS V6-2-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.

Note that the CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Net Change Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
  CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set carries the data for an Emergency Care Attendance.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
  CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.

Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.

Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:

• CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
• CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message

Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:

• CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS Type
• CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type

Followed by:

• The CDS Type - As required to carry the specific Commissioning Data Set data records

Each Commissioning Data Set message ends with:

• CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message

Each Commissioning Data Set Interchange ends with:

• CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 010 - Accident and Emergency Commissioning Data Set carries the data for an Accident and Emergency Attendance.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 020 - Outpatient Commissioning Data Set carries the data for an Outpatient Attendance or a cancelled/missed APPOINTMENT.

It covers all NHS and private Outpatient ACTIVITY taking place in any:

• acute, community, mental health NHS Trust or NHS Foundation Trust
• other NHS hospital
• non-NHS hospitals or institutions where the care delivered is NHS-funded.

under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow, unless the ACTIVITY falls under the Allied Health Professional Referral To Treatment Measurement standard.  In this case, an out-patient record for the Allied Health Professional ACTIVITY must be submitted, with the CDS DATA GROUP : PATIENT PATHWAY data elements completed as necessary.

This CDS Type may also be used to submit Referral To Treatment Clock Stop Administrative Events.

This CDS Type must not be used for "Future Outpatients" - for this the CDS V6-2 Type 021 - Future Outpatient Commissioning Data Set must be used.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

The CDS V6-2 Type 021 - Future Outpatient Commissioning Data Set carries the data for a Future Outpatient Attendance or a future cancelled APPOINTMENT.

This CDS Type was not approved by the Information Standards Board for Health and Social Care and submissions to support local activities and commissioning will be supported for piloting purposes only.

It covers all NHS and private Outpatient ACTIVITY taking place in any:

• acute, community, mental health NHS Trust or NHS Foundation Trust
• other NHS hospital
• non-NHS hospitals or institutions where the care delivered is NHS-funded.

under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

This CDS Type must not be used for "Outpatients" - for this the CDS V6-2 Type 020 - Outpatient Commissioning Data Set must be used.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set carries the data for all booked, planned and waiting list admissions.

This consists of records for PATIENTS waiting for Elective Admission at a specified date and should be sent to the Secondary Uses Service within one month of the end of the period to which they relate unless a shorter time-scale has been agreed with the recipient.

Some Health Care Providers also send a final CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set after the PATIENT has been removed from the WAITING LIST to identify when and why this took place. Commissioners who do not wish to use such final Elective Admission List-End Of Period Census Commissioning Data Sets should ignore them.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 040 - Elective Admission List - End of Period Census (Old) Commissioning Data Set is used to report to the previous (old) Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of another Commissioner.

This CDS Type should be sent within one month of the end of the period to which it relates unless a shorter time-scale has been agreed with the recipient.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 050 - Elective Admission List - End of Period Census (New) Commissioning Data Set is used to report to a new Commissioner an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.

This CDS Type should be sent within one month of the end of the period to which it relates unless a shorter time-scale has been agreed with the recipient.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.Notation 

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business RulesBusiness Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is used to make an initial report that an ELECTIVE ADMISSION LIST ENTRY has been added to the Health Care Provider's ELECTIVE ADMISSION LIST.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol.  They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. 
 

Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.

Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is used to report that the ELECTIVE ADMISSION LIST ENTRY has been removed from the Health Care Provider's ELECTIVE ADMISSION LIST.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists. 

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol.  They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.

Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is used to report that an OFFER OF ADMISSION has been made to the PATIENT.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists. 

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol.  They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.

Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.

Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 090 - Elective Admission List - Event During Period (Available or Unavailable) Commissioning Data Set is used to report changes in the PATIENT's availability for treatment.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow. 

Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol.  They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.

Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is used to report to the previous Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of a new Commissioner.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol.  They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. 

Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set used to make an initial report to a new Commissioner of an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.

It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol.  They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.

Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set carries the data for a Finished Birth Episode.

This is required when a delivery has resulted in a REGISTRABLE BIRTH which has taken place in either an NHS Hospital or in an non-NHS ORGANISATION funded by the NHS.

The information is taken from the birth notification for each baby born.

In addition to Finished Birth Episodes, Unfinished Birth Episode Commissioning Data Set records are required for all Unfinished Birth Episodes as at midnight on 31st March each year.

CDS V6-2 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set should be used for the submission of this Unfinished Birth Episode Commissioning Data Set.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats. 

Business Rules

See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.

XML Schema

For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.

For guidance on downloading the XML Schema, see XML Schema TRUD Download.

Introduction

CDS V6-2 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set carries the data for a Finished General Episode.

It covers all NHS and private Admitted Patient Care (day case and inpatient) ACTIVITY taking place in any:

• acute, community, mental health NHS Trust or NHS Foundation Trust
• other NHS hospital
• non-NHS hospitals or institutions where the care delivered is NHS-funded.

under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.

ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.

Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.

An Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes as at midnight on 31 March each year and for all unfinished short-stay informal psychiatric PATIENTS who are resident in hospital or on leave of absence (Home Leave) on 31 March and who have been in hospital for less than 12 months.

CDS V6-2 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set should be used for the submission of this Unfinished General Episode Commissioning Data Set.

To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.

Data Group Overview

A high-level view of the Data Groups carried is shown below.Notation

See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.