NHS Connecting for Health
NHS Data Model and Dictionary Service
Reference: | Change Request 1295 |
Version No: | 1.0 |
Subject: | Retirement of old Commissioning Data Set messages |
Effective Date: | Immediate |
Reason for Change: | Retirement of old Commissioning Data Set layout |
Publication Date: | 2 March 2012 |
Background:
In the May 2010 Release of the NHS Data Model and Dictionary a new layout of the Commissioning Data Set pages was introduced and users were advised that:
-
There would be a period of dual running of both the new and old views of the Commissioning Data Set pages, to allow users to become familiar with the new layout and notation used and
- The Commissioning Data Set Validation Table had been updated in line with the redesigned Commissioning Data Set pages, but would not be made available as an excel file or appear in the NHS Data Model and Dictionary after the period of dual running of the old and new Commissioning Data Set pages, as all the information is available on the new pages.
This Change Request retires the old style Commissioning Data Set messages and Commissioning Data Set Validation Table from the NHS Data Model and Dictionary.
To view a demonstration on "How to Read an NHS Data Model and Dictionary Change Request", visit the NHS Data Model and Dictionary help pages at: http://www.datadictionary.nhs.uk/Flash_Files/changerequest.htm.
Note: if the web page does not open, please copy the link and paste into the web browser.
Summary of changes:
Data Set | |
CDS V6 TYPE 001 (RETIRED) renamed from CDS V6 TYPE 001 | Changed Description, status to Retired, Name |
CDS V6 TYPE 002 (RETIRED) renamed from CDS V6 TYPE 002 | Changed Description, status to Retired, Name |
CDS V6 TYPE 003 (RETIRED) renamed from CDS V6 TYPE 003 | Changed Description, status to Retired, Name |
CDS V6 TYPE 004 (RETIRED) renamed from CDS V6 TYPE 004 | Changed Description, status to Retired, Name |
CDS V6 TYPE 005B (RETIRED) renamed from CDS V6 TYPE 005B | Changed Description, status to Retired, Name |
CDS V6 TYPE 005N (RETIRED) renamed from CDS V6 TYPE 005N | Changed Description, status to Retired, Name |
CDS V6 TYPE 010 (RETIRED) renamed from CDS V6 TYPE 010 | Changed Description, status to Retired, Name |
CDS V6 TYPE 020 (RETIRED) renamed from CDS V6 TYPE 020 | Changed Description, status to Retired, Name |
CDS V6 TYPE 021 (RETIRED) renamed from CDS V6 TYPE 021 | Changed Description, status to Retired, Name |
CDS V6 TYPE 030 (RETIRED) renamed from CDS V6 TYPE 030 | Changed Description, status to Retired, Name |
CDS V6 TYPE 040 (RETIRED) renamed from CDS V6 TYPE 040 | Changed Description, status to Retired, Name |
CDS V6 TYPE 050 (RETIRED) renamed from CDS V6 TYPE 050 | Changed Description, status to Retired, Name |
CDS V6 TYPE 060 (RETIRED) renamed from CDS V6 TYPE 060 | Changed Description, status to Retired, Name |
CDS V6 TYPE 070 (RETIRED) renamed from CDS V6 TYPE 070 | Changed Description, status to Retired, Name |
CDS V6 TYPE 080 (RETIRED) renamed from CDS V6 TYPE 080 | Changed Description, status to Retired, Name |
CDS V6 TYPE 090 (RETIRED) renamed from CDS V6 TYPE 090 | Changed Description, status to Retired, Name |
CDS V6 TYPE 100 (RETIRED) renamed from CDS V6 TYPE 100 | Changed Description, status to Retired, Name |
CDS V6 TYPE 110 (RETIRED) renamed from CDS V6 TYPE 110 | Changed Description, status to Retired, Name |
CDS V6 TYPE 120 (RETIRED) renamed from CDS V6 TYPE 120 | Changed Description, status to Retired, Name |
CDS V6 TYPE 130 (RETIRED) renamed from CDS V6 TYPE 130 | Changed Description, status to Retired, Name |
CDS V6 TYPE 140 (RETIRED) renamed from CDS V6 TYPE 140 | Changed Description, status to Retired, Name |
CDS V6 TYPE 150 (RETIRED) renamed from CDS V6 TYPE 150 | Changed Description, status to Retired, Name |
CDS V6 TYPE 160 (RETIRED) renamed from CDS V6 TYPE 160 | Changed Description, status to Retired, Name |
CDS V6 TYPE 170 (RETIRED) renamed from CDS V6 TYPE 170 | Changed Description, status to Retired, Name |
CDS V6 TYPE 180 (RETIRED) renamed from CDS V6 TYPE 180 | Changed Description, status to Retired, Name |
CDS V6 TYPE 190 (RETIRED) renamed from CDS V6 TYPE 190 | Changed Description, status to Retired, Name |
CDS V6 TYPE 200 (RETIRED) renamed from CDS V6 TYPE 200 | Changed Description, status to Retired, Name |
CRITICAL CARE MINIMUM DATA SET | Changed Description |
NEONATAL CRITICAL CARE MINIMUM DATA SET | Changed Description |
PAEDIATRIC CRITICAL CARE MINIMUM DATA SET | Changed Description |
Supporting Information | |
CDS MANDATED DATA FLOWS | Changed Description |
CDS NOTATION | Changed Description |
CDS SUBMISSION PROTOCOL | Changed Description |
CDS VERSION 6 TYPE LIST NAVIGATION MENU (RETIRED) renamed from CDS VERSION 6 TYPE LIST NAVIGATION MENU | Changed Description, status to Retired, Name |
CDS VERSION CDS006 TYPE LIST | Changed Description |
COMMISSIONING DATA SET OVERVIEW | Changed Description |
COMMISSIONING DATA SETS INTRODUCTION | Changed Description |
COMMISSIONING DATA SETS MENU | Changed Description |
COMMISSIONING DATA SET VALIDATION TABLE (RETIRED) renamed from COMMISSIONING DATA SET VALIDATION TABLE | Changed Description, status to Retired, Name |
REFERRAL TO TREATMENT CLOCK STOP ADMINISTRATIVE EVENT | Changed Description |
Attribute Definitions | |
FIRST ATTENDANCE | Changed Description |
Data Elements | |
APPOINTMENT DATE | Changed Description |
CDS ACTIVITY DATE | Changed Description |
DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE | Changed Description |
EARLIEST REASONABLE OFFER DATE | Changed Description |
FIRST ATTENDANCE | Changed Description |
FIRST ATTENDANCE CODE | Changed Description |
MENTAL CATEGORY | Changed Description |
MENTAL CATEGORY CODE | Changed Description |
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | Changed Description |
REFERRAL TO TREATMENT PERIOD END DATE | Changed Description |
REFERRAL TO TREATMENT PERIOD START DATE | Changed Description |
REFERRAL TO TREATMENT PERIOD STATUS | Changed Description |
REFERRAL TO TREATMENT STATUS | Changed Description |
UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) | Changed Description |
Date: | 2 March 2012 |
Sponsor: | Nicholas Oughtibridge, Acting Director of Data Standards and Products, Technology Office, Department of Health Informatics Directorate |
Note: New text is shown with a blue background. Deleted text is crossed out. Retired text is shown in grey. Within the Diagrams deleted classes and relationships are red, changed items are blue and new items are green.
Click here for a printer friendly view of this page.
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 001 - CDS INTERCHANGE HEADER
CDS Interchanges and Messages submitted to the SUS must use the CDS Header and Trailer Controls to provide the correct addressing and identification of data flows.This item has been retired from the NHS Data Model and Dictionary.
The CDS Interchange Header defines mandatory identity and addressing information for the CDS submission.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Every CDS Interchange must consist of:CDS INTERCHANGE HEADER - Mandatory - One per CDS InterchangeCDS MESSAGE HEADER - Mandatory - One per CDS MessageCDS MESSAGE DATA - As defined for the specific CDS TypeCDS MESSAGE TRAILER - Mandatory - One per CDS MessageCDS INTERCHANGE TRAILER - Mandatory - One per CDS Interchange
Multiple CDS messages are usually sent in a single CDS Interchange.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 001
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_001 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_001
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 002 - CDS INTERCHANGE TRAILER
CDS Interchanges and Messages submitted to the SUS must use the CDS Header and Trailer Controls to provide the correct addressing and identification of data flows.This item has been retired from the NHS Data Model and Dictionary.
The CDS Interchange Trailer signifies the end of a CDS Interchange and contains control information for the Interchange.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Every CDS Interchange must consist of:CDS INTERCHANGE HEADER - Mandatory - One per CDS InterchangeCDS MESSAGE HEADER - Mandatory - One per CDS MessageCDS MESSAGE DATA - As defined for the specific CDS TypeCDS MESSAGE TRAILER - Mandatory - One per CDS MessageCDS INTERCHANGE TRAILER - Mandatory - One per CDS Interchange
Multiple CDS messages are usually sent in a single CDS Interchange.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data should be included whenever availableO = Optional - data need not be included
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 002
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_002 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_002
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 003 - CDS MESSAGE HEADER
CDS Interchanges and Messages submitted to the SUS must use the CDS Header and Trailer Controls to provide the correct addressing and identification of data flows.This item has been retired from the NHS Data Model and Dictionary.
The CDS MESSAGE HEADER signifies the start of each CDS Message and contains control information for the Message.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Every CDS Interchange must consist of:CDS INTERCHANGE HEADER - Mandatory - One per CDS InterchangeCDS MESSAGE HEADER - Mandatory - One per CDS MessageCDS MESSAGE DATA - As defined for the specific CDS TypeCDS MESSAGE TRAILER - Mandatory - One per CDS MessageCDS INTERCHANGE TRAILER - Mandatory - One per CDS Interchange
Multiple CDS messages are usually sent in a single CDS Interchange.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data should be included whenever availableO = Optional - data need not be included
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 003
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_003 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_003
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 004 - CDS MESSAGE TRAILER
CDS Interchanges and Messages submitted to the SUS must use the CDS Header and Trailer Controls to provide the correct addressing and identification of data flows.This item has been retired from the NHS Data Model and Dictionary.
The CDS MESSAGE TRAILER signifies the end of each CDS Message and contains control information for the Message.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Every CDS Interchange must consist of:CDS INTERCHANGE HEADER - Mandatory - One per CDS InterchangeCDS MESSAGE HEADER - Mandatory - One per CDS MessageCDS MESSAGE DATA - As defined for the specific CDS TypeCDS MESSAGE TRAILER - Mandatory - One per CDS MessageCDS INTERCHANGE TRAILER - Mandatory - One per CDS Interchange
Multiple CDS messages are usually sent in a single CDS Interchange.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data should be included whenever availableO = Optional - data need not be included
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 004
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_004 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_004
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 005B - CDS TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL
Every CDS submitted or received must include a CDS Transaction Header Group which is used to carry CDS identification and addressing data and the data indicating the specific use of one of the Update Mechanisms of the CDS Exchange Protocol.This item has been retired from the NHS Data Model and Dictionary.
All CDS Types using the CDS Bulk Replacement Update Mechanism of the CDS Exchange Protocol must begin with this Mandatory Data Group.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Note:1. The CDS UNIQUE IDENTIFIER may be provided as an optional data item when using the Bulk Update Protocol. In all cases, care must be taken to ensure that the value generated for the CDS UNIQUE IDENTIFIER is unique across all NHS organisations by prefixing the locally maintained value with an NHS Organisation Code, usually that of the originator of the data.2. The mandatory CDS ACTIVITY DATE must be present and valid for all CDS Types from Version 6 onwards. For CDS Type 170 the CDS ACTIVITY DATE contains the CDS CENSUS DATE which is also the DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE.3. For the following CDS Types the CDS ACTIVITY DATE must contain the DATE OF ELECTIVE ADMISSION LIST CENSUS which is usually the end of the Period being reported:CDS Type 030 Elective Admission List End of Period Census (Standard)CDS Type 040 Elective Admission List End of Period Census (Old)CDS Type 050 Elective Admission List End of Period Census (New)4. The mandatory CDS ACTIVITY DATE must be present and valid for all CDS Types. In addition, the "Originating Date" which is used to derive the CDS ACTIVITY DATE and held elsewhere in the CDS must also be valid and compatible with the specific CDS EXCHANGE PROTOCOL being used.5. There may be up to 7 CDS COPY RECIPIENT IDENTITY occurrences specifiedAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data should be included whenever availableO = Optional - data need not be included
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 005B
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_005B to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_005B
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 005N - CDS TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL
Every CDS submitted or received must include a CDS Transaction Header Group which is used to carry CDS identification and addressing data and the data indicating the specific use of one of the Update Mechanisms of the CDS Exchange Protocol.This item has been retired from the NHS Data Model and Dictionary.
All CDS TYPES using the CDS Net Change Update Mechanism of the CDS Exchange Protocol must begin with this Mandatory Data Group.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Note:1. The CDS UNIQUE IDENTIFIER must be provided as a mandatory data item when using the Net Change Protocol. In all cases, care must be taken to ensure that the value generated for the CDS UNIQUE IDENTIFIER is unique across all NHS organisations by prefixing the locally maintained value with an NHS ORGANISATION CODE, usually that of the originator of the data.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.2. The mandatory CDS ACTIVITY DATE must be present and valid for all CDS Types from Version 6 onwards. For CDS Type 170 the CDS ACTIVITY DATE contains the CDS CENSUS DATE which is also the CDS CENSUS DATE.3. For the following CDS Types the CDS ACTIVITY DATE must contain the DATE OF ELECTIVE ADMISSION LIST CENSUS which is usually the end of the Period being reported:
CDS Type 030 Elective Admission List End of Period Census (Standard)CDS Type 040 Elective Admission List End of Period Census (Old)CDS Type 050 Elective Admission List End of Period Census (New)
4. The mandatory CDS ACTIVITY DATE must be present and valid for all CDS TYPES. In addition, the "Originating Date" which is used to derive the CDS ACTIVITY DATE and held elsewhere in the CDS must also be valid and compatible with the specific CDS PROTOCOL IDENTIFIER being used.5. There may be up to 7 CDS COPY RECIPIENT IDENTITY occurrences specified
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data should be included whenever availableO = Optional - data need not be included
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 005N
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_005N to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_005N
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 010 - ACCIDENT AND EMERGENCY CDS
This Commissioning Data Set carries the data for an Accident and Emergency Attendance Episode and consists of the following Commissioning Data Set Data Groups:This item has been retired from the NHS Data Model and Dictionary.
INTERCHANGE, MESSAGE and COMMISSIONING DATA SET TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSGENERAL PRACTITIONER REGISTRATIONATTENDANCE OCCURRENCE - Activity CharacteristicsATTENDANCE OCCURRENCE - Service Agreement DetailsATTENDANCE OCCURRENCE - Person Group (A And E Consultant)ATTENDANCE OCCURRENCE - Clinical Information (Diagnosis)ATTENDANCE OCCURRENCE - Clinical Information (Investigation)ATTENDANCE OCCURRENCE - Clinical Information (Treatment)HEALTHCARE RESOURCE GROUPThe last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 010
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_010 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_010
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 020 - OUTPATIENT CDS
The Outpatient CDS carries the data for a Care Activity or a cancelled / missed Care Appointment. The data set applies for Consultant, Nurse, Midwife, and other CARE PROFESSIONALS attendances and appointments, including Ward Attendances for nursing care.This item has been retired from the NHS Data Model and Dictionary.
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.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
This CDS Type must not be used for "Future Outpatients" - for this CDS TYPE 021 must be used.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
This Commissioning Data Set Type may also be used to submit Referral To Treatment Clock Stop Administrative Events.
The CDS consists of the following CDS Data Groups:
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
|
| ||
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 020
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_020 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_020
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 021 - FUTURE OUTPATIENT CDS
The Future Outpatient CDS carries the data for a forthcoming Care Activity, future or planned Care Appointment. The data set applies for Consultant, Nurse and Midwife attendances and appointments including Ward Attendances for nursing care.This item has been retired from the NHS Data Model and Dictionary.
The CDS TYPE 021 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSCARE EPISODEATTENDANCE OCCURRENCEGP REGISTRATIONREFERRALHEALTHCARE RESOURCE GROUP
Note: Each Commissioning Data Set must contain a valid CDS ACTIVITY DATE and when using the CDS BULK REPLACEMENT UPDATE MECHANISM this date must also be compatible with the CDS REPORT PERIOD START DATE and the CDS REPORT PERIOD END DATE specified as part of the CDS EXCHANGE PROTOCOL.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The CDS ACTIVITY DATE has an "originating date" held within the Commissioning Data Set data and for the Future Outpatient CDS Type this is the APPOINTMENT DATE held in the Attendance Occurrence-Activity Characteristics data structure.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Where the source application system cannot provide a valid date, the default value may be applied, see APPOINTMENT DATE.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
|
| ||
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 021
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_021 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_021
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDS
The Elective Admission List CDSs consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The End Of Period Census Commissioning Data Sets carry details for all booked, planned and waiting list admissions consisting of records of patients waiting for elective admission at a specified date. These should be sent within one month of the end of the period to which they relate unless a shorter time-scale has been agreed with the recipient.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Three derivations are permitted:1) CDS Type 030 - The End Of Period Census (STANDARD)2) CDS Type 040 - The End Of Period Census (OLD)3) CDS Type 050 - The End Of Period Census (NEW)
This derivation, CDS Type = 030 - The End Of Period Census (STANDARD), is the simplest variation and, with one exception detailed below, all Providers must be able to create it as defined and all Commissioners must be able to process it.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The exception as identified above is for an Elective Admission List Removal. Some providers send a final EAL-End Of Period Census CDS after the patient has been removed from the list to identify when and why this took place. Commissioners who do not wish to receive such final EAL-End Of Period Census Commissioning Data Sets should ignore them.
Where the Elective Admission List 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.
The CDS TYPE 030 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSCOMMISSIONING OCCURRENCEEAL ENTRYGP REGISTRATIONOFFER OF ADMISSIONORIGINAL EAL ENTRYREFERRALEAL ENTRY REMOVALHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 030
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_030 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_030
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 040 - EAL - END OF PERIOD CENSUS OLD CDS
The Elective Admission List CDSs consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The End Of Period Census Commissioning Data Sets carry details for all booked, planned and waiting list admissions consisting of records of patients waiting for elective admission at a specified date. These should be sent within one month of the end of the period to which they relate unless a shorter time-scale has been agreed with the recipient.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Three derivations are permitted:1) CDS Type 030 - The End Of Period Census (STANDARD)2) CDS Type 040 - The End Of Period Census (OLD)3) CDS Type 050 - The End Of Period Census (NEW)
This derivation, CDS Type = 040 - The End Of Period Census (OLD), is used to report to the previous (old) Commissioner that the EAL Entry is now the responsibility of another Commissioner.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The CDS TYPE 040 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYCOMMISSIONING OCCURRENCE
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 040
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_040 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_040
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 050 - EAL - END OF PERIOD CENSUS NEW CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The End Of Period Census Commissioning Data Sets carry details for all booked, planned and waiting list admissions consisting of records of patients waiting for elective admission at a specified date. These should be sent within one month of the end of the period to which they relate unless a shorter time-scale has been agreed with the recipient.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Three derivations are permitted:1) CDS Type 030 - The End Of Period Census (STANDARD)2) CDS Type 040 - The End Of Period Census (OLD)3) CDS Type 050 - The End Of Period Census (NEW)
This derivation, CDS Type = 050 - The End Of Period Census (NEW), may be used to report to a new Commissioner an EAL Entry that had previously been the responsibility of another Commissioner.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The CDS TYPE 050 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSCOMMISSIONING OCCURRENCEEAL ENTRYGP REGISTRATIONOFFER OF ADMISSIONORIGINAL EAL ENTRYREFERRALEAL ENTRY REMOVALHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 050
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_050 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_050
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The Event During Period Commissioning Data Set Types carry details for all events - patients added or removed from the Elective Admission List - that have taken place during the period.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
These Commissioning Data Sets are intended for those Providers and Commissioners who have the capability to implement transaction-based processing. They should be supplemented where required by an annual EAL End Of Period Census.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Six EAL Event During Period derivations are permitted:1) CDS Type 060 - The Event During Period (ADD)2) CDS Type 070 - The Event During Period (REMOVE)3) CDS Type 080 - The Event During Period (OFFER)4) CDS Type 090 - The Event During Period (AVAILABLE / UNAVAILABLE)5) CDS Type 100 - The Event During Period (OLD SERVICE AGREEMENT)6) CDS Type 110 - The Event During Period (NEW SERVICE AGREEMENT)
This derivation, CDS TYPE = 060, is the Event During Period (ADD) and is used to make an initial report that the EAL entry has been added to the Provider's Elective Admission List.
Note that for EAL Event During Period Commissioning Data Set Types, the Unique CDS Identifier, as held in the CDS Transaction Header Group, must be completed in order to provide the EAL identity.
Where the Elective Admission List 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.
The CDS TYPE 060 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSCOMMISSIONING OCCURRENCEEAL ENTRYGP REGISTRATIONOFFER OF ADMISSIONORIGINAL EAL ENTRYREFERRALHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 060
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_060 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_060
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The Event During Period Commissioning Data Set Types carry details for all events - patients added or removed from the Elective Admission List - that have taken place during the period.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
These Commissioning Data Sets are intended for those Providers and Commissioners who have the capability to implement transaction-based processing. They should be supplemented where required by an annual EAL End Of Period Census.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Six EAL Event During Period derivations are permitted:1) CDS Type 060 - The Event During Period (ADD)2) CDS Type 070 - The Event During Period (REMOVE)3) CDS Type 080 - The Event During Period (OFFER)4) CDS Type 090 - The Event During Period (AVAILABLE / UNAVAILABLE)5) CDS Type 100 - The Event During Period (OLD SERVICE AGREEMENT)6) CDS Type 110 - The Event During Period (NEW SERVICE AGREEMENT)
This derivation, CDS Type = 070, is the Event During Period (REMOVE) and is used to report that the EAL entry has been removed from the Provider's Elective Admission List.
Note that for EAL Event During Period CDS Types, the Unique CDS Identifier, as held in the CDS Transaction Header Group, must be completed in order to provide the EAL identity.
Where the Elective Admission List 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.
The CDS TYPE 070 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYEAL ENTRY REMOVAL
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 070
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_070 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_070
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The Event During Period Commissioning Data Set Types carry details for all events - patients added or removed from the Elective Admission List - that have taken place during the period.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
These Commissioning Data Sets are intended for those Providers and Commissioners who have the capability to implement transaction-based processing. They should be supplemented where required by an annual EAL End Of Period Census.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Six EAL Event During Period derivations are permitted:1) CDS Type 060 - The Event During Period (ADD)2) CDS Type 070 - The Event During Period (REMOVE)3) CDS Type 080 - The Event During Period (OFFER)4) CDS Type 090 - The Event During Period (AVAILABLE / UNAVAILABLE)5) CDS Type 100 - The Event During Period (OLD SERVICE AGREEMENT)6) CDS Type 110 - The Event During Period (NEW SERVICE AGREEMENT)
This derivation, CDS Type = 080, is the Event During Period (OFFER) and is used to report that an offer of admission has been made to the patient.
Note that for EAL Event During Period CDS Types, the Unique CDS Identifier, as held in the CDS Transaction Header Group, must be completed in order to provide the EAL identity.
Where the Elective Admission List 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.
The CDS TYPE 080 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYEAL OFFER OF ADMISSION
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 080
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_080 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_080
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 090 - EAL - EVENT DURING PERIOD - AVAILABLE / UNAVAILABLE CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The Event During Period Commissioning Data Set Types carry details for all events - patients added or removed from the Elective Admission List - that have taken place during the period.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
These Commissioning Data Sets are intended for those Providers and Commissioners who have the capability to implement transaction-based processing. They should be supplemented where required by an annual EAL End Of Period Census.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Six EAL Event During Period derivations are permitted:1) CDS Type 060 - The Event During Period (ADD)2) CDS Type 070 - The Event During Period (REMOVE)3) CDS Type 080 - The Event During Period (OFFER)4) CDS Type 090 - The Event During Period (AVAILABLE / UNAVAILABLE)5) CDS Type 100 - The Event During Period (OLD SERVICE AGREEMENT)6) CDS Type 110 - The Event During Period (NEW SERVICE AGREEMENT)
This derivation, CDS Type = 090, is the Event During Period (AVAILABLE / UNAVAILABLE) and is used to report changes in the patient's availability for treatment.
Note that for EAL Event During Period CDS Types, the Unique CDS Identifier, as held in the CDS Transaction Header Group, must be completed in order to provide the EAL identity.
The CDS TYPE 090 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYEAL PATIENT SUSPENSION
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 090
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_090 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_090
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 100 - EAL - EVENT DURING PERIOD - OLD SERVICE AGREEMENT CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The Event During Period Commissioning Data Set Types carry details for all events - patients added or removed from the Elective Admission List - that have taken place during the period.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
These Commissioning Data Sets are intended for those Providers and Commissioners who have the capability to implement transaction-based processing. They should be supplemented where required by an annual EAL End Of Period Census.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Six EAL Event During Period derivations are permitted:1) CDS Type 060 - The Event During Period (ADD)2) CDS Type 070 - The Event During Period (REMOVE)3) CDS Type 080 - The Event During Period (OFFER)4) CDS Type 090 - The Event During Period (AVAILABLE / UNAVAILABLE)5) CDS Type 100 - The Event During Period (OLD SERVICE AGREEMENT)6) CDS Type 110 - The Event During Period (NEW SERVICE AGREEMENT)
This derivation, CDS Type = 100, is the Event During Period (OLD SERVICE AGREEMENT) and is used to report to the previous (OLD) Commissioner that the EAL Entry is now the responsibility of a new Commissioner.
Note that for EAL Event During Period CDS Types, the Unique CDS Identifier, as held in the CDS Transaction Header Group, must be completed in order to provide the EAL identity.
The CDS TYPE 100 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYCOMMISSIONING OCCURRENCE
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 100
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_100 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_100
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 110 - EAL - EVENT DURING PERIOD - NEW SERVICE AGREEMENT CDS
The Elective Admission List Commissioning Data Sets consist of two distinct types of data sets:EAL - End Of Period Census CDS Types, andEAL - Event During Period CDS Types.This item has been retired from the NHS Data Model and Dictionary.
The Event During Period Commissioning Data Set Types carry details for all events - patients added or removed from the Elective Admission List - that have taken place during the period.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
These Commissioning Data Sets are intended for those Providers and Commissioners who have the capability to implement transaction-based processing. They should be supplemented where required by an annual EAL End Of Period Census.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
Six EAL Event During Period derivations are permitted:1) CDS Type 060 - The Event During Period (ADD)2) CDS Type 070 - The Event During Period (REMOVE)3) CDS Type 080 - The Event During Period (OFFER)4) CDS Type 090 - The Event During Period (AVAILABLE / UNAVAILABLE)5) CDS Type 100 - The Event During Period (OLD SERVICE AGREEMENT)6) CDS Type 110 - The Event During Period (NEW SERVICE AGREEMENT)
This derivation, CDS TYPE = 110, is the Event During Period (NEW SERVICE AGREEMENT) and is used to make an initial report to a new Commissioner of an EAL entry that had previously been the responsibility of another Commissioner.
Note that for EAL Event During Period CDS Types, the Unique CDS Identifier, as held in the CDS Transaction Header Group, must be completed in order to provide the EAL identity.
The CDS TYPE 110 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSCOMMISSIONING OCCURRENCEEAL ENTRYGP REGISTRATIONOFFER OF ADMISSIONORIGINAL EAL ENTRYREFERRALHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be Used
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 110
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_110 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_110
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 120 - ADMITTED PATIENT CARE - FINISHED BIRTH EPISODE CDS
The Finished Birth Episode Commissioning Data Set Type carries the data for a Finished Birth Episode which is required when a delivery has resulted in a registrable birth. This may take place in either NHS Hospitals or in non-NHS organisations funded by the NHS. The information is taken from the birth notification for each baby born.This item has been retired from the NHS Data Model and Dictionary.
In addition to Finished Birth Episodes an Unfinished Birth Episode Commissioning Data Set record is required for all Unfinished Birth Episodes at midnight on 31 March each year.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The CDS TYPE 120 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODECRITICAL CARE PERIODGP REGISTRATIONREFERRALPREGNANCYANTENATAL CAREHOSPITAL LABOUR / DELIVERYBIRTH OCCURRENCEHEALTHCARE RESOURCE GROUPAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
| |||
|
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 120
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_120 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_120
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDS
The Admitted Patient Care Finished General Episode Commissioning Data Set Type carries the data for a Finished General Episode.This item has been retired from the NHS Data Model and Dictionary.
It covers all NHS and private Admitted Patient Care (day case and inpatient) activity taking place in any acute, community, psychiatric NHS Trust or Primary Care Trust or other NHS hospital under the care of a consultant, midwife or nurse. Additionally, NHS funded Admitted Patient Care taking place in non-NHS hospitals and institutions is required.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Where the Admitted Patient Care 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.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
In addition to Finished General Episodes an Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes at midnight on 31 March each year. Unfinished General Episode Commissioning Data Set records are also required for 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.
The CDS TYPE 130 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (shown independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODECRITICAL CARE PERIODGP REGISTRATIONREFERRALEAL ENTRYHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
| |||
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 130
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_130 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_130
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 140 - ADMITTED PATIENT CARE - FINISHED DELIVERY EPISODE CDS
The Admitted Patient Care Finished Delivery Episode Commissioning Data Set Type carries the data for a Finished Delivery Episode which is required when a delivery has resulted in a registrable birth. This may take place in either NHS Hospitals or in non-NHS organisations funded by the NHS. The information is taken from the birth notification for each baby born.This item has been retired from the NHS Data Model and Dictionary.
In addition to Finished Delivery Episodes an Unfinished Delivery Episode Commissioning Data Set record is required for all Unfinished Birth Episodes at midnight on 31 March each year.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The CDS TYPE 140 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODECRITICAL CARE PERIODGP REGISTRATIONREFERRALPREGNANCYANTENATAL CAREHOSPITAL LABOUR / DELIVERYBIRTH OCCURRENCEHEALTHCARE RESOURCE GROUPAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
| |||
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 140
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_140 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_140
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 150 - ADMITTED PATIENT CARE - OTHER BIRTH EVENT CDS
The Admitted Patient Care Other Birth CDS Type carries the data for an Other Birth.This item has been retired from the NHS Data Model and Dictionary.
This Commissioning Data Set Type applies to:(i) NHS funded home births, and(ii) all other birth events which are not NHS-funded, either directly or under an NHS service agreement.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Maternity events, taking place in either NHS hospitals or in non-NHS hospitals funded by the NHS, will be recorded as ordinary Delivery and Birth episodes. The data in these records come from birth notification records and require only a limited data set to be completed.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The CDS TYPE 150 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSGP REGISTRATIONPREGNANCYANTENATAL CAREOTHER LABOUR / DELIVERYBIRTH OCCURRENCE
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross reference Tables show these derivations.
|
| | ||
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 150
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_150 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_150
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 160 - ADMITTED PATIENT CARE - OTHER DELIVERY EVENT CDS
This Commissioning Data Set Type applies to:(i) NHS funded home deliveries, and(ii) all other delivery events which are not NHS-funded, either directly or under an NHS service agreement.This item has been retired from the NHS Data Model and Dictionary.
Maternity events, taking place in either NHS hospitals or in non-NHS hospitals funded by the NHS, will be recorded as ordinary Delivery and Birth episodes. The data in these records come from birth notification records and require only a limited data set to be completed.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The CDS TYPE 160 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSGP REGISTRATIONPREGNANCYANTENATAL CAREOTHER LABOUR / DELIVERYBIRTH OCCURRENCE (max of 9 Babies)Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
| | ||
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 160
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_160 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_160
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 170 - ADMITTED PATIENT CARE - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS CDS
The Detained and/or Long Term Psychiatric Commissioning Data Set Type carries the data for the Psychiatric Census.This item has been retired from the NHS Data Model and Dictionary.
The NHS Information Centre for health and social care require a record for every patient admitted as at 31 March each year for which the patient is detained or the Episode is part of a Hospital Provider Spell which has lasted longer then one year and for which the majority of time has been spent under the care of a Consultant in one of the psychiatric specialties.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
In the case of Trust mergers and demergers occurring, where the Hospital provider Spell would have lasted longer then one year except for the merger / demerger, patients should be included. The Organisation Code (Code of Provider) will be that of the organisation in existence as at the 31 March Census Date.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The CDS TYPE 170 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (shown independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSPATIENT PSYCHIATRIC CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODEGP REGISTRATIONREFERRALEAL ENTRYHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode records and in End of Year Census records.An entry in the column headed HES indicates that the data element is extracted from the Secondary Uses Service database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The Hospital Episode Statistics Cross Reference Tables show these derivations.
|
|
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 170
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_170 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_170
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 180 - ADMITTED PATIENT CARE - UNFINISHED BIRTH EPISODE CDS
The Unfinished Birth Episode Commissioning Data Set carries the data for an Unfinished Birth Episode which is required when a delivery has resulted in a registrable birth. This may take place in either NHS Hospitals or in non-NHS organisations funded by the NHS. The information is taken from the birth notification for each baby born.This item has been retired from the NHS Data Model and Dictionary.
An Unfinished Birth Episode Commissioning Data Set record is required for all Unfinished Birth Episodes at midnight on 31 March each year.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The CDS TYPE 180 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODECRITICAL CARE PERIODGP REGISTRATIONREFERRALPREGNANCYANTENATAL CAREHOSPITAL LABOUR / DELIVERYBIRTH OCCURRENCEHEALTHCARE RESOURCE GROUPAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
|
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 180
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_180 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_180
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDS
The Admitted Patient Care Unfinished General Episode Commissioning Data Set Type carries the data for an Unfinished General Consultant/ Midwife/ Nurse Episode.This item has been retired from the NHS Data Model and Dictionary.
It covers all NHS and private Admitted Patient Care (day case and inpatient) activity taking place in any acute, community, psychiatric NHS Trust or Primary Care Trust or other NHS hospital under the care of a consultant, midwife or nurse. Additionally, NHS funded Admitted Patient Care taking place in non-NHS hospitals and institutions is required.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Where the Admitted Patient Care 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.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
An Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes at midnight on 31 March each year. Unfinished General Episode Commissioning Data Set records are also required for 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.
The CDS TYPE 190 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (shown independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODECRITICAL CARE PERIODGP REGISTRATIONREFERRALEAL ENTRYHEALTHCARE RESOURCE GROUP
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 190
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_190 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_190
Change to Data Set: Changed Description, status to Retired, Name
CDS V6 TYPE 200 - ADMITTED PATIENT CARE - UNFINISHED DELIVERY EPISODE CDS
The Admitted Patient Care Unfinished Delivery Episode Commissioning Data Set Type carries the data for an Unfinished Delivery Episode. This may take place in either NHS Hospitals or in non-NHS organisations funded by the NHS. The information is taken from the birth notification for each baby born.This item has been retired from the NHS Data Model and Dictionary.
An Unfinished Delivery Episode Commissioning Data Set record is required for all Unfinished Birth Episodes at midnight on 31 March each year.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
The CDS TYPE 200 consists of the following CDS Data Groups:INTERCHANGE, MESSAGE and CDS TRANSACTION HEADERS and TRAILERS (defined independently)PATIENT PATHWAYPATIENT IDENTITYPATIENT CHARACTERISTICSPATIENT DELIVERY CHARACTERISTICSHOSPITAL PROVIDER SPELLCONSULTANT EPISODECRITICAL CARE PERIODGP REGISTRATIONREFERRALPREGNANCYANTENATAL CAREHOSPITAL LABOUR / DELIVERYBIRTH OCCURRENCEHEALTHCARE RESOURCE GROUPAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
The markers in the columns "OPT, U/A and HES" indicate the NHS recommendations for the inclusion of data:M = Mandatory - data must be included where availableO = Optional - data need not be included* = Must Not Be UsedR in the column headed U/A indicates the data is required in the Unfinished Episode / Annual Census of Unfinished Episode record and on an End of Year Census record.An entry in the column headed HES indicates that the data element is extracted from the SUS database for Hospital Episode Statistics. Data extracted for Hospital Episode Statistics purposes contains some derived items. The CDS/HES Cross Reference Tables show these derivations.
|
|
|
|
Change to Data Set: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS V6 TYPE 200
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_TYPE_200 to Retired.Data_Dictionary.Messages.CDS_V6_Old_Layout.CDS_V6_TYPE_200
Change to Data Set: Changed Description
Critical Care Minimum Data Set Overview
Critical Care Minimum Data Set excludes neonatal critical care. A subset of this minimum data set is used to derive Adult Critical Care HRGs. The subset is sent in the following Commissioning Data Set messages:
CDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 200 - ADMITTED PATIENT CARE - UNFINISHED DELIVERY EPISODE CDS- CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode CDS
- CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode CDS
Change to Data Set: Changed Description
Neonatal Critical Care Minimum Data Set Overview
The Neonatal Critical Care Minimum Data Set is sent as a subset in the following Commissioning Data Set messages:
CDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDS- CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
Data Set Data Elements |
---|
Person Group (Patient): To carry the personal details of the Patient (the baby). One occurrence of this Group is permitted. |
PERSON BIRTH DATE |
DISCHARGE DATE (HOSPITAL PROVIDER SPELL) |
DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) |
Neonatal Critical Care Group: To carry the details of the Neonatal Critical Care Period. One occurrence of this Group is permitted. |
CRITICAL CARE LOCAL IDENTIFIER |
CRITICAL CARE START DATE |
CRITICAL CARE START TIME |
CRITICAL CARE DISCHARGE DATE |
CRITICAL CARE DISCHARGE TIME |
CRITICAL CARE UNIT FUNCTION |
GESTATION LENGTH (AT DELIVERY) |
Neonatal Critical Care Daily Activity Group: To carry the daily activity data for each day of the Neonatal Critical Care Period. 999 occurrences of this Group are permitted. |
ACTIVITY DATE (CRITICAL CARE) |
PERSON WEIGHT |
20 occurrences of Critical Care Activity Codes are permitted within the Neonatal Critical Care Daily Activity Group. All codes relate to care provided on the ACTIVITY DATE (CRITICAL CARE). |
CRITICAL CARE ACTIVITY CODE |
20 occurrences of High Cost Drugs OPCS codes are permitted within the Neonatal Critical Care Daily Activity Group. All codes relate to drugs provided on the ACTIVITY DATE (CRITICAL CARE). |
HIGH COST DRUGS (OPCS) |
Change to Data Set: Changed Description
Paediatric Critical Care Minimum Data Set Overview
The Paediatric Critical Care Minimum Data Set is sent as a subset in the following Commissioning Data Set messages:
CDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 200 - ADMITTED PATIENT CARE - UNFINISHED DELIVERY EPISODE CDS- CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode CDS
- CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode CDS
Data Set Data Elements |
---|
Person Group (Patient): To carry the personal details of the Patient. One occurrence of this Group is permitted. |
PERSON BIRTH DATE |
DISCHARGE DATE (HOSPITAL PROVIDER SPELL) |
DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) |
Paediatric Critical Care Group: To carry the details of the Paediatric Critical Care Period. |
CRITICAL CARE LOCAL IDENTIFIER |
CRITICAL CARE START DATE |
CRITICAL CARE START TIME |
CRITICAL CARE DISCHARGE DATE |
CRITICAL CARE DISCHARGE TIME |
CRITICAL CARE UNIT FUNCTION |
Paediatric Critical Care Daily Activity Group: To carry the daily activity data for each day of the Paediatric Critical Care Period. 999 occurrences of this Group are permitted. |
ACTIVITY DATE (CRITICAL CARE) |
20 occurrences of Critical Care Activity Codes are permitted within the Paediatric Critical Care Daily Activity Group. All codes relate to care provided on the CRITICAL CARE START DATE. |
CRITICAL CARE ACTIVITY CODE |
2 HIGH COST DRUGS (OPCS) codes are permitted but there is the capacity for 20 codes within the Paediatric Critical Care Daily Activity Group, to allow future refinement. All codes relate to drugs provided on the CRITICAL CARE LOCAL IDENTIFIER. |
HIGH COST DRUGS (OPCS) |
Change to Supporting Information: Changed Description
The minimum Commissioning Data Set information flow requirement to enable Hospital Episode Statistics, 18 Weeks ACTIVITY reporting, and Payment by Results to be supported by the Secondary Uses Service is shown in the table below.
The Secondary Uses Service supports every CDS TYPE but only a subset is mandated to flow.
Commissioning Data Sets may flow to the Secondary Uses Service using either Net Change or Bulk Replacement Commissioning Data Set Submission Protocols. Many Standard NHS Contracts between Health Care Providers and the commissioners of their SERVICES, now specify weekly submission of initially-coded data sets to the Secondary Uses Service. The use of Net Change Commissioning Data Set Submission Protocols is recommended for submissions of this frequency.
CDS TYPE | DESCRIPTION | MIN FREQ | DIRECTIVE | DATA FLOW |
CDS 010 | Accident And Emergency | Monthly | Accident and Emergency Attendances were mandated to flow nationally from 1st April 2005, see Data Set Change Notice 32/2004 | All Accident and Emergency Attendances occurring during the time period being reported and defined by the Commissioning Data Set Submission Protocol being used. |
CDS 020 | Out-Patient | Monthly | Out-Patient Attendance Commissioning Data Sets (including Ward Attenders) were mandated to be submitted to the Secondary Uses Service from 1st October 2001, see Data Set Change Notice 05/2001. Out-Patient Attendance Commissioning Data Set records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | Due to the high volumes involved, these are often submitted on a weekly basis. |
CDS 021 | Future Out-Patients | As Required for piloting | From 01/01/2008, submissions to support local activities and commissioning will be supported for piloting purposes only. | |
CDS 030 | Elective Admission List End of Period (Standard) | Monthly if used | All Providers should endeavour to support this data flow. Elective Admission List End of Period Census (Standard) Commissioning Data Set records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | All entries where at the end of the time period being reported and defined by the Commissioning Data Set Submission Protocol, the PATIENT remains on the ELECTIVE ADMISSION LIST. Optionally and by local agreement with commissioners, entries relating to the PATIENTS that have been removed from the ELECTIVE ADMISSION LIST may be included. |
CDS 040 | Elective Admission List End of Period (New) | Monthly if used | Optional | May be submitted where the Commissioner has been changed during the time period reported. |
CDS 050 | Elective Admission List End of Period (Old) | Monthly if used | Optional | May be submitted where the Commissioner has been changed during the time period reported. |
CDS 060 | Elective Admission List Event During Period (Add) | Monthly if used | Optional Elective Admission List Event During Period (Add) Commissioning Data Set records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | May be submitted where an entry has been added to the ELECTIVE ADMISSION LIST during the time period reported. |
CDS 070 | Elective Admission List Event During Period (Remove) | Monthly if used | Optional Elective Admission List Event During Period (Remove) Commissioning Data Set records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | May be submitted where an entry has been removed from the ELECTIVE ADMISSION LIST during the time period reported. |
CDS 080 | Elective Admission List Event During Period (Offer) | Monthly if used | Optional Elective Admission List Event During Period (Offer) CDS records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | May be submitted where an offer has been made during the time period reported. |
CDS 090 | Elective Admission List Event During Period (Available / Unavailable) | Monthly if used | Optional | May be submitted where a patient becomes Available or Unavailable during the time period reported. |
CDS 100 | Elective Admission List Event During Period (Old Service Agreement) | Monthly if used | Optional | May be submitted where the Commissioner has been changed during the time period reported. |
CDS 110 | Elective Admission List Event During Period (New Service Agreement) | Monthly if used | Optional | May be submitted where the Commissioner has been changed during the time period reported. |
CDS 120 | Finished Birth Episode | Monthly | All finished Admitted Patient Care data must be submitted "at least monthly" (EL - Dec 1995). This includes Non-Contract Activity. | All Episodes that have finished relevant to the time period defined by the Commissioning Data Set Submission Protocol being used. |
CDS 130 | Finished General Episode | Monthly | All finished Admitted Patient Care data must be submitted "at least monthly" (EL - Dec 1995). Finished General Episode Commissioning Data Set records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | All Episodes that have finished relevant to the time period defined by the Commissioning Data Set Submission Protocol being used. |
CDS 140 | Finished Delivery Episode | Monthly | All finished Admitted Patient Care data must be submitted at least monthly (EL - Dec 1995). This includes Non-Contract Activity. | All Episodes that have finished relevant to the time period defined by the Commissioning Data Set Submission Protocol being used. |
CDS 150 | Other Birth | Monthly | This includes Home Birth. | All Episodes that have finished relevant to the time period defined by the Commissioning Data Set Submission Protocol being used. |
CDS 160 | Other Delivery | Monthly | This includes Home Delivery. | All Episodes that have finished relevant to the time period defined by the Commissioning Data Set Submission Protocol being used. |
CDS 170 | The Detained and/or Long Term Psychiatric Census | Annually | Required by The NHS Information Centre for health and social care. May optionally be sent more regularly, usually monthly. | Reflects data as at the 31st March each year. All Episodes that are relevant to the time period defined by the Commissioning Data Set Submission Protocol being used. |
CDS 180 | Unfinished Birth Episode | Annually | The Annual Census / Unfinished Census. Required by The NHS Information Centre for health and social care. | Data relating to episodes that were unfinished as at midnight on 31st March and have not been included in the Detained and/or Long Term Psychiatric Census, and have not been submitted to the Secondary Uses Service in either Finished or Unfinished Commissioning Data Set data, must be submitted to the Secondary Uses Service. |
CDS 190 | Unfinished General Episode | Annually | The Annual Census / Unfinished Census. Required by The NHS Information Centre for health and social care. May optionally be sent more regularly, usually monthly. Unfinished General Episode Commissioning Data Set records where the activity relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement must include the PATIENT PATHWAY data group items, from 1st October 2009. | Data relating to episodes that were unfinished as at midnight on 31st March and have not been included in the Detained and/or Long Term Psychiatric Census, and have not been submitted to the Secondary Uses Service in either Finished or Unfinished Commissioning Data Set data, must be submitted to the Secondary Uses Service. |
CDS 200 | Unfinished Delivery Episode | Annually | The Annual Census / Unfinished Census. Required by The NHS Information Centre for health and social care. May optionally be sent more regularly, usually monthly. | Data relating to episodes that were unfinished as at midnight on 31st March and have not been included in the Detained and/or Long Term Psychiatric Census, and have not been submitted to the Secondary Uses Service in either Finished or Unfinished Commissioning Data Set data, must be submitted to the Secondary Uses Service. |
In the above data flows, the validation criteria for each data element is shown in the Commissioning Data Set Validation Table.
Change to Supporting Information: Changed Description
The Commissioning Data Set is the basic structure used for the submission of commissioning data to the Secondary Uses Service and is designed to be capable of individually conveying many different Commissioning Data Set structures, encompassing Accident and Emergency Attendances, Out-Patient Attendances, Admitted Patient Care and Elective Admission List.
Commissioning Data Set Messages have been defined in specific components known as a CDS TYPE.
Specific notation is used to indicate the requirements of the CDS-XML Message Schema Design conditions for submission of data in the Commissioning Data Sets.
The structure of the Commissioning Data Set message is shown by the use of Data Groups and Sub Groups within those Data Groups. For each Data Group, Sub Group and individual Data Element, the allowed cardinality at each level is also shown in the "Status" and "Repeats" columns.
The CDS TYPE specifications must therefore be read in this hierarchy, using the Status and Repeat conditions within the Data Groups and Sub Groups, to determine the requirements for the individual Data Elements.
Status Column Notation
The Notation used for the "STATUS" column is as follows:
STATUS | MEANING | DESCRIPTION |
M | MANDATORY | This signifies that the collection and submission of this Commissioning Data Set data is deemed MANDATORY and its presence is necessary for the CDS TYPE to be correctly validated and accepted for processing by the Secondary Uses Service. If a data item is shown as MANDATORY, this should also be regarded as REQUIRED by the Department of Health. In most instances, data marked as MANDATORY in a Sub Group will result in its parent Data Group also being marked as mandatory, but this is not always the case. For instance, although the Consultant Episode - Clinical Diagnosis Group (ICD) is marked as R=REQUIRED (and therefore need not actually be populated), if it is used then both the DIAGNOSIS SCHEME IN USE and the PRIMARY DIAGNOSIS (ICD) are marked as M=MANDATORY and must both be present. |
| ||
R | REQUIRED | This signifies that the collection and submission of this Commissioning Data Set data is deemed REQUIRED by the Department of Health to comply with authorised NHS Standards, Policies and Directives. Therefore whenever a Commissioning Data Set is collected and subsequently submitted to the Secondary Uses Service, this data must be supported and populated into the relevant data sets if the data is available. Note that "temporal" conditions may mean that there are instances where this directive cannot be fulfilled. For instance in a CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS, ICD and OPCS data elements are marked as "Required" indicating that this data should be included. However, if at the time of submission to the Secondary Uses Service this data remains incomplete (perhaps awaiting coding in the ORGANISATION), the remaining data in the CDS record should still be submitted. Once the ORGANISATION has updated its systems with the data, the CDS TYPE relating to that ACTIVITY should then be resubmitted to the Secondary Uses Service. |
O | OPTIONAL | This signifies that the collection and submission of this Commissioning Data Set data is OPTIONAL. Its inclusion in the Commissioning Data Set is therefore determined by "local agreement" between the ORGANISATIONS exchanging the data. Note that even if marked O=OPTIONAL, any data included in a Commissioning Data Set submission to the Secondary Uses Service must comply with its specification published in the NHS Data Model and Dictionary otherwise the data may be deemed invalid and rejected. |
X | X | This is used where the Data Element has been included in the Commissioning Data Set design, usually for pilot use, but is not yet authorised for transmission by the wider NHS. The Data Element will be in italics and not linked to the Data Element where one exists. |
Repeats Column Notation
The Notation used for the "REPEATS" column is as follows:
REPEATS | DESCRIPTION | |
0..1 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to a maximum of 1. | |
0..9 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to a maximum of 9. | |
0..* | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to an unlimited maximum. | |
1..1 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to a maximum of 1. | |
1..97 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to a maximum of 97. | |
1..* | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to an unlimited maximum. |
Rules Column Notation
An entry in the "Rules" column shows that a specific Rule applies to submission of an individual Data Element. These meaning of these Rules can be found in Commissioning Data Set Business Rules.
Notation Examples
The following are examples of some common scenarios.
EXAMPLE 1: A MANDATORY Data Group with differing Sub-Groups and component data status conditions. |
The following example shows a MANDATORY Data Group - therefore the Data Group must be present for the CDS TYPE to be validated and accepted for processing by the Secondary Uses Service. When a Data Group is used:
The following data structure is one of three options when completing the Patient Identity Data Group: |
1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 = Verified | Rules | |||
R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | |||
M | 1..1 | LOCAL PATIENT IDENTIFIER | F | ||
M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
M | 1..1 | Data Element Components | Rules | ||
M | 1..1 | NHS NUMBER | F | ||
M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
M | 1..1 | POSTCODE OF USUAL ADDRESS | S3 | ||
M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
R | 0..1 | PERSON BIRTH DATE (Introduced in Commissioning Data Set V6-1) | F S3 |
EXPLANATION: The parent Data Group has a "Status" of M=MANDATORY which indicates that this Data Group must be present in the Commissioning Data Set to ensure correct validation and acceptance when submitted to the Secondary Uses Service. The parent Data Group "Repeats" = 1..1 indicates that only one occurrence of this Data Group must flow in this particular Commissioning Data Set record. |
EXAMPLE 2: A REQUIRED Data Group with differing component data status conditions. |
The following example shows a REQUIRED Data Group. This data must be present in the relevant Commissioning Data Set if available. However, if submitted to the Secondary Uses Service, omission of this REQUIRED Data Group will not cause rejection. When the Data Group is used:
|
Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (ICD) | ||||
Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the ICD coded Clinical Diagnoses. |
M | 1..1 | Data Element Components | Rules | ||
M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
O | 0..* | DATA GROUP: SECONDARY DIAGNOSIS | Rules | ||
M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 |
EXPLANATION: The Data Group "Status" = R = Required indicates that this Data Group must be populated in the relevant Commissioning Data Set if the data is available. The Data Group "Repeats" = 0..1 indicates that population of this Data Group is not necessary to enable the Commissioning Data Set to be sent to the Secondary Uses Service. If it is sent, then only one occurrence of this Data Group may flow in this particular Commissioning Data Set record. |
Change to Supporting Information: Changed Description
The Commissioning Data Set messages 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.
Two Update Mechanisms are available:
- Net Change - to support the management of an individual CDS TYPE in the Secondary Uses Service database and enables Commissioning data to be inserted/ updated or deleted.
CDS Senders are expected to use the Net Change Update Mechanism wherever possible. - Bulk Replacement - to support the management of bulk commissioning data for an identified CDS BULK REPLACEMENT GROUP of data for a specified time period and for a specified CDS PRIME RECIPIENT IDENTITY.
CDS Senders should only use the Bulk Replacement Update Mechanism in exceptional circumstances.
It is strongly advised that all NHS Trusts should, as a minimum process, commence migration to use the CDS-XML Version 6 Message for weekly Net Change submissions by March 2009 as this is the date mandated by the "NHS Operating Framework".
Net Change:Net Change processes are managed by specific data settings as defined in the CDS V6 TYPE 005N option of the CDS Transaction Header Group.Net Change processes are managed by specific data settings as defined in the CDS V6 Type 005N - CDS 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:
Each CDS TYPE must have a CDS UNIQUE IDENTIFIER which must be uniquely maintained for the life of that Commissioning Data Set record. This is a particular consideration where mergers and/or healthcare systems are changed or upgraded, see CDS Submission and PCT 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.
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 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 Primary Care Trust or NHS Trust.
Bulk ReplacementBulk Replacement processes are managed by specific data settings as defined in the CDS V6 TYPE 005B option of the CDS Transaction Header Group.Bulk Replacement processes are managed by specific data settings as defined in the CDS V6 Type 005B - CDS 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
- CDS BULK REPLACEMENT GROUP
- CDS EXTRACT DATE
- CDS EXTRACT TIME
- CDS REPORT PERIOD START DATE
- CDS REPORT PERIOD END DATE
- CDS PRIME RECIPIENT IDENTITY
Every CDS TYPE must be submitted using the correct CDS BULK REPLACEMENT GROUP.
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 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 Primary Care Trust or NHS Trust.
The CDS PRIME RECIPIENT IDENTITY must be identified in each Commissioning Data Set and must not be changed during the lifetime of the Commissioning Data Set record otherwise the data stored in the Secondary Uses Service database may lose its integrity (e.g. duplicate Commissioning data may be stored).
For this reason it is advised that the ORGANISATION CODE (PCT OF RESIDENCE) should always be used to determine the CDS PRIME RECIPIENT IDENTITY as detailed in the Commissioning Data Set Addressing Grid. Senders must also be aware that if the ORGANISATION CODE (PCT OF RESIDENCE) is itself derived from the PATIENT's POSTCODE OF USUAL ADDRESS then great care must be taken to manage all elements of this relationship.
If it is necessary to change any of this data during the lifetime of a Commissioning Data Set record, then the Secondary Uses Service help desk should be contacted for advice.
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 Provider sub-contracts healthcare provision and its associated Commissioning Data Set submission to a second Provider, arrangements to submit the Commissioning Data Set data must be made locally to ensure that only one Provider sends the Commissioning Data Set data to the Secondary Uses Service.
If the second Provider wishes to add other Commissioning data to the Secondary Uses Service database to that already submitted by the first Provider, both parties need to ensure that a different CDS SENDER IDENTITY is used. Often this is done by changing the last 2 digits of the 5 digit code (the Site element of the Organisation Code).
Note: Data sent using the same CDS SENDER IDENTITY 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 helpdesk.
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 Provider Code in order to change the CDS INTERCHANGE SENDER IDENTITY should this becomes necessary.
Change to Supporting Information: Changed Description, status to Retired, Name
THE COMMISSIONING DATA SET - VERSION CDS006: CDS TYPE LISTThis item has been retired from the NHS Data Model and Dictionary.
CDS DATA FLOW CONTROLS - (Mandatory for every CDS Interchange):CDS V6 TYPE 001 - CDS INTERCHANGE HEADERCDS V6 TYPE 002 - CDS INTERCHANGE TRAILERCDS V6 TYPE 003 - CDS MESSAGE HEADERCDS V6 TYPE 004 - CDS MESSAGE TRAILERThe last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
CDS Transaction Header Group -(Mandatory for every CDS TYPE):CDS V6 TYPE 005B - CDS TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOLorCDS V6 TYPE 005N - CDS TRANSACTION HEADER GROUP - NET CHANGE PROTOCOLAccess to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line.
CDS TYPES:Accident and Emergency CDS Type:CDS V6 TYPE 010 - ACCIDENT AND EMERGENCY CDS
Care Activity CDS Types:CDS V6 TYPE 020 - OUTPATIENT CDS (known in the Schema as Care Activity CDS)CDS V6 TYPE 021 - FUTURE OUTPATIENT CDS (known in the Schema as Future Care Activity CDS)
Admitted Patient Care CDS Types:CDS V6 TYPE 120 - ADMITTED PATIENT CARE - FINISHED BIRTH EPISODE CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 140 - ADMITTED PATIENT CARE - FINISHED DELIVERY EPISODE CDSCDS V6 TYPE 150 - ADMITTED PATIENT CARE - OTHER BIRTH EVENT CDSCDS V6 TYPE 160 - ADMITTED PATIENT CARE - OTHER DELIVERY EVENT CDSCDS V6 TYPE 170 - ADMITTED PATIENT CARE - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS CDSCDS V6 TYPE 180 - ADMITTED PATIENT CARE - UNFINISHED BIRTH EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 200 - ADMITTED PATIENT CARE - UNFINISHED DELIVERY EPISODE CDS
Elective Admission List CDS Types - End Of Period Census Types:CDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 040 - EAL - END OF PERIOD CENSUS OLD CDSCDS V6 TYPE 050 - EAL - END OF PERIOD CENSUS NEW CDS
Elective Admission List CDS Types - Event During Period Types:CDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDSCDS V6 TYPE 090 - EAL - EVENT DURING PERIOD - AVAILABLE / UNAVAILABLE CDSCDS V6 TYPE 100 - EAL - EVENT DURING PERIOD - OLD SERVICE AGREEMENT CDSCDS V6 TYPE 110 - EAL - EVENT DURING PERIOD - NEW SERVICE AGREEMENT CDS
Change to Supporting Information: Changed Description, status to Retired, Name
- Changed Description
- Retired CDS Version 6 Type List Navigation Menu
- Changed Name from Web_Site_Content.Navigation.CDS_Version_6_Type_List_Navigation_Menu to Retired.Web_Site_Content.Navigation.CDS_Version_6_Type_List_Navigation_Menu
Change to Supporting Information: Changed Description
Includes Commissioning Data Set 6-0 and 6-1
For guidance on the new Commissioning Data Set Layout, see the Commissioning Data Set Redesign Guidance Notes on the NHS Data Model and Dictionary website.For guidance on the Commissioning Data Set Layout, see the Commissioning Data Set Redesign Guidance Notes on the NHS Data Model and Dictionary website.
Change to Supporting Information: Changed Description
The primary purpose of national data sets is to enable conformant health information to be generated across the country, independent of the ORGANISATION or system that maintains it. In achieving this, The NHS Information Centre for health and social care will enable healthcare professionals to measure and compare the delivery and quality of care provided and to support them in sharing information with other health professionals and ORGANISATIONS.
Information Requirements
- monitor and manage NHS SERVICE AGREEMENTS;
- develop commissioning plans;
- support the Payment by Results processes;
- support NHS Comparators;
- monitor Health Improvement Programmes;
- underpin clinical governance;
- understand the health needs of the population.
- support reporting against 18 week wait targets
Information on care provided for all PATIENTS by NHS Hospitals and Primary Care Trusts and Independent Sector Providers (for NHS PATIENTS only) is specified in the Commissioning Data Sets and must be submitted to the Secondary Uses Service according to issued guidelines.
Commissioners need access to data to monitor Non-Contract Activity as part of the management of their NHS SERVICE AGREEMENTS. Primary Care Trusts also need to monitor in-year referrals to investigate the sources and reasons for Non-Contract Activity.Independent Sector Treatment Centres (TC) are responsible for providing Admitted Patient Care and Out-Patient Attendance Commissioning Data Sets and may submit this data on their own behalf or via a third party. Other Independent Sector activity for NHS PATIENTS is the responsibility of the NHS commissioning body for the provision of the appropriate central returns and data sets.
The Department of Health requires accurate data of all PATIENTS admitted to or treated as out-patients, or treated as an Accident And Emergency Attendance by NHS Hospital Providers and Primary Care Trusts, including PATIENTS receiving private treatment.The Department of Health requires accurate data of all PATIENTS admitted to or treated as out-patients, or treated as an Accident and Emergency Attendance by NHS Hospital Providers and Primary Care Trusts, including PATIENTS receiving private treatment. The data also includes NHS PATIENTS treated electively in the independent sector and overseas. These Hospital Episode Statistics (HES) are derived from the Admitted Patient Care, Out-Patient Attendance and Accident and Emergency Attendance Commissioning Data Sets as stored in the Secondary Uses Service. This data provides information about hospital and PATIENT management, epidemiological data on PATIENT DIAGNOSES and OPERATIVE PROCEDURES.
Referral To Treatment Clock Stop Administrative Events may also flow using the CDS V6 TYPE 020 - OUTPATIENT CDS.Referral To Treatment Clock Stop Administrative Events may also flow using the CDS V6 Type 020 - Outpatient CDS. This allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity.
Commissioning Data Set Data Flow Definitions
CDS TYPES
The Commissioning Data Set is the basic structure used for the submission of commissioning data to the Secondary Uses Service and is designed to be capable of individually conveying many different Commissioning Data Set structures encompassing Accident and Emergency Attendances, Out-Patient Attendances, Future Attendances, Admitted Patient Care and Elective Admission List data etc.
Commissioning Data Set Messages have been defined in specific components known as a CDS TYPE. Each Commissioning Data Set Type as configured into the Commissioning Data Set Message carries only one specific Commissioning Data Set Type, an examples being the Finished Consultant Episode Commissioning Data Set Type etc.
Change to Supporting Information: Changed Description
Information on care provided for all PATIENTS by NHS Hospital Providers, Primary Care Trusts and Independent Sector Providers (for NHS PATIENTS only) is specified in the Commissioning Data Sets and must be submitted to the Secondary Uses Service according to issued guidelines.
Use the following links to access more detailed information.
The Commissioning Data Sets
- Commissioning Data Set Overview
- Commissioning Data Set Versions
- Commissioning Data Set Notation
- Commissioning Data Set Business Rules
- Commissioning Data Set Mandated Data Flows
- Commissioning Data Set Submission Protocol
- Commissioning Data Set Addressing Grid
Commissioning Data Set Validation Table- Security Issues and Patient Confidentiality
- Commissioning Data Set Submission and Primary Care Trust Mergers
- Commissioning Data Set Data Duplication
- Hospital Episode Statistics
- Hospital Episode Statistics Cross Reference Tables
The CDS-XML Message
Change to Supporting Information: Changed Description
- CDS Overview
- CDS Version 6 Type List
- CDS Versions
- CDS Addressing Grid
- CDS Business Rules
- CDS Data Duplication
- CDS Mandated Data Flows
- CDS Notation
- CDS Submission and PCT Mergers
- CDS Submission Protocol
CDS Validation Table- Hospital Episode Statistics
- Hospital Episode Statistics Cross Reference Tables
- Referral To Treatment Clock Stop Administrative Event
- Security Issues and Patient Confidentiality
- CDS-XML Message
- CDS-XML Message Schema Overview
- CDS-XML Message Schema Versions
- CDS-XML Message Schema Design
- CDS-XML Schema Version Numbering
- CDS-XML Message Schema Documentation
Change to Supporting Information: Changed Description, status to Retired, Name
This table details the Data Elements used in the different versions of the Commissioning Data Sets and the validation applied in each CDS TYPE.This item has been retired from the NHS Data Model and Dictionary.
This table is also available to download in Excel format from the CDS Supporting Information section of the NHS Data Model and Dictionary website.The last live version of this item is available in the January 2012 release of the NHS Data Model and Dictionary.
Commissioning Data Set Versions
Table Structure
This table is structured with separate rows for each Data Element and separate columns for each CDS TYPE. Where the rules have changed between versions, each set of rules has its own sub-row. The cells within the body of the table show the validation applied to a Data Element for a specific CDS TYPE.
Commissioning Data Set VersionsThe following notation is used in the "Version" column to identify the version or versions of the Commissioning Data Sets that the validation rule applies to.
V6-1 -CDS Version CDS006 Type List(incorporates Version CDS 6-1)V5 -CDS Version NHS005 Type List
Where the same rules apply to several Commissioning Data Sets the first and last version are identified.
V5:6-1 Commissioning Data Set Version 5 through to Version 6-1
Where a Data Element is no longer available in a Commissioning Data Set the version number is suffixed with =R
Notation used in each table cell
Blank cell - the CDS TYPE does not include the Data Element.Access to this version can be obtained by emailing datastandards@nhs.net with "NHS Data Model and Dictionary - Archive Request" in the email subject line. Populated cell - the CDS TYPE includes the Data Element. The notation includes the content validation, optional population validation and optional additional use cases for the Data Element.
Content validationThe content validation falls into one of the following two types:
F - The format is validated, for example the format of aDATEmust comply with the XML standardV - TheData Elementis validated against an explicit list of permitted values
Population validationWhere a Data Element is required, the content validation is suffixed with a population validation code:
Technical constraintsM - ThisData Elementis mandatory in the XML schema.Submissions will not flow if thisData Elementis absentC - There are conditions where theData Elementmust be populated.In these conditions, messages will not flow if thisData Elementis absentBusiness constraintsR - Data required as part of NHS business rules to meet NHS business requirements.Organisations are obliged to provide thisData Elementfor activity provided or commissioned by the NHS.*- There are conditions where theData Elementmust not be populated.Business rules for the anonymisation of data should be applied as per the guidance issued inSecurity Issues and Patient Confidentiality.
Additional use cases
Secondary Uses Service business rules:
S1This mandatory CDS DATE is used as the originating date to determine the mandatoryCDS ACTIVITY DATE.S2TheSecondary Uses ServiceDOES NOT support the use of theCDS TEST INDICATORTherefore thisData Elementmust not be used.S3ForSecurity Issues and Patient Confidentialityfor further information.S4Used to ensure the correct sequencing of multiple and/or subsequent Commissioning Data Set submissions.S5These Organisation Codes must be present and registered with theSecondary Uses Service.The Commissioning Data Set Schema does not logically validate the content value of this data.S6AllCDS REPORT PERIOD START DATESandCDS REPORT PERIOD END DATESmust be consistent in allCommissioning Data Setscontained in a BULK Interchange submission.TheCDS REPORT PERIOD START DATEmust be on or before theCDS REPORT PERIOD END DATE.TheCDS ACTIVITY DATEis a mandatoryData Elementand must fall within the period defined.See the Commissioning Data Set Submission Protocol.S7See the Commissioning Data Set Addressing GridS8These Data Elements are required for correct processing by theSecondary Uses Service.If omitted, theSecondary Uses Servicewill reject the Commissioning Data Set data.S9The CDS UNIQUE IDENTIFIER is a mandatory data item when using the Net Change Protocol.When using the Bulk Update Protocol this data item is optional but it is strongly advised that where it can be correctly generated and maintained it should be used.See the Commissioning Data Set Submission Protocol.S10For CDS V6 TYPE 170 - ADMITTED PATIENT CARE - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS COMMISSIONING DATA SET, the CDS ACTIVITY DATE contains the CDS CENSUS DATE which is also the DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE.S11For the following CDS TYPES, the CDS ACTIVITY DATE must contain the DATE OF ELECTIVE ADMISSION LIST CENSUS which is usually the end of the Period being reported:CDS V6 TYPE 030 - ELECTIVE ADMISSION LIST - END OR PERIOD CENSUS (STANDARD) COMMISSIONING DATA SETCDS V6 TYPE 040 - ELECTIVE ADMISSION LIST - END OR PERIOD CENSUS (OLD) COMMISSIONING DATA SETCDS V6 TYPE 050 - ELECTIVE ADMISSION LIST - END OR PERIOD CENSUS (NEW) COMMISSIONING DATA SETS12These PERSON BIRTH DATE Data Elements must use dates between 01/01/1880 and 31/12/2999 in order to pass validation.S13Data Elements reporting a DATE (which is not PERSON BIRTH DATE Data Element) must use dates between 01/01/1900 and 31/12/2999 in order to pass validation.S14For Data Elements reporting a TIME, the hour portion must be between 00 and 23 inclusive in order to pass validation.
Healthcare Resource Groups:
H4ThisData Elementis used by theSecondary Uses Serviceto derive Healthcare Resource Group 4.Failure to correctly populate thisData Elementis likely to result in an incorrect Healthcare Resource Group, usually associated with lower levels of healthcare resource.
Additional notation† - This notation has been applied to the following items:CDS TYPE 021 Future Out-Patient Commissioning Data Set - Following consultation, piloting and proof that all items are appropriate, this Commissioning Data Set will be available for referrals without appointments, future scheduled appointments and cancelled appointments where the appointment date is in the future. In the interim it is recommended this CDS TYPE is only used for piloting.Lead Care Activity Indicator - this Data Element is undefined, must not be submitted and should not flow in the Commissioning Data Sets.LOCATION TYPE - the definition and value list for this Data Element is under review. Dependent on the review findings changes may be piloted and then approved. Until that time, this Data Element should not flow in the Commissioning Data Sets.ADMINISTRATIVE CATEGORY (AT START OF EPISODE) and LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE) - these Data Elements have not been piloted and therefore should not flow in the Commissioning Data Sets.
The Standard Contract
The Standard Contract Schedule 5 requires Health Care Providers to ensure that the following Commissioning Data Sets are submitted to the Commissioners on a monthly basis within 5 Operational Days of the end of the month to which the data sets relate, so that the data sets are completed by the applicable Reconciliation Point:
Admitted Patient Care General Episode Commissioning Data Set;Out-patient Attendance Commissioning Data Set;Accident and Emergency Attendance Commissioning Data Set;Elective Admission List Commissioning Data Set - End of Period Census (Standard);from April 2007Admitted Patient Care Delivery Episode Commissioning Data Set;Admitted Patient Care Birth Episode Commissioning Data Set;Admitted Patient Care Detained / Long Term Psychiatric Census Commissioning Data Set;Admitted Patient Care Other Delivery Commissioning Data Set;Admitted Patient Care Other Birth Event Commissioning Data Set
Change to Supporting Information: Changed Description, status to Retired, Name
- Changed Description
- Retired Commissioning Data Set Validation Table
- Changed Name from Web_Site_Content.CDS_Supporting_Information.Commissioning_Data_Set_Validation_Table to Retired.Web_Site_Content.CDS_Supporting_Information.Commissioning_Data_Set_Validation_Table
Change to Supporting Information: Changed Description
Data Set Change Notice 18/2006 published in December 2006, defined essential new data items required to support the measurement of 18 week REFERRAL TO TREATMENT PERIODS (monitoring of DH PSA target 13 - "By 2008, no one will have to wait longer than 18 weeks from GP referral to hospital treatment"). In particular, the Data Set Change Notice 18/2006 introduced the following new data items.
Strategic reporting of 18 weeks will be undertaken by the Secondary Uses Service using data obtained via the Commissioning Data Sets . The new data items defined in Data Set Change Notice 18/2006 are enabled to flow in Commissioning Data Set version 6-0, 6-1, and will continue to flow in subsequent versions.
However, an event which results in an update to the REFERRAL TO TREATMENT PERIOD STATUS may occur outside the events that are defined in the Commissioning Data Sets (typically Outpatient or Inpatient encounters) and will therefore not flow to the Secondary Uses Service. These types of events have been termed as "administrative events". They can be defined as any communication event between the Health Care Provider and the PATIENT that occurs outside of an outpatient attendance or inpatient admission and that results in the PATIENT's REFERRAL TO TREATMENT PERIOD STATUS being changed to stop the 18 week clock. These events are not face to face consultations and do not necessarily involve clinical staff.
These Referral To Treatment Clock Stop Administrative Events may be carried using the Commissioning Data Set Type 020 Outpatient record type. They are differentiated from PATIENT contact ACTIVITY by the FIRST ATTENDANCE value carried within them. FIRST ATTENDANCE national code 5 "Referral to treatment clock stop administrative event" signifies that an ACTIVITY has taken place which has ended the REFERRAL TO TREATMENT PERIOD and changed the REFERRAL TO TREATMENT PERIOD STATUS to one of the following:
- 30 Start of First Definitive Treatment
- 31 Start of Active Monitoring initiated by the PATIENT
- 32 Start of Active Monitoring initiated by the CARE PROFESSIONAL
- 34 Decision not to treat - decision not to treat made or no further contact required
- 35 PATIENT declined offered treatment
30 Start of First Definitive Treatment
31 Start of Active Monitoring initiated by the PATIENT
32 Start of Active Monitoring initiated by the CARE PROFESSIONAL
34 Decision not to treat - decision not to treat made or no further contact required
35 PATIENT declined offered treatment
36 PATIENT died before treatment
When to Use Referral To Treatment Clock Stop Administrative Events
These events may happen because:
- The ACTIVITY occurred in a setting where IT systems cannot produce REFERRAL TO TREATMENT PERIOD data items, or
- The ACTIVITY would be carried in a Commissioning Data Set record type not currently processed by the Secondary Uses Service
Secondary Uses Service Processing
The Secondary Uses Service currently processes the following Commissioning Data Set record types in order to build Referral To Treatment pathways.
CDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
All other types are not currently processed and so if they carry the REFERRAL TO TREATMENT PERIOD END DATE for a REFERRAL TO TREATMENT PERIOD, a Referral To Treatment Clock Stop Administrative Event must also be sent in order to inform the Secondary Uses Service of the clock stop.
Note that future versions of the Secondary Uses Service will also process:
CDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDS- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
The dates when ORGANISATIONS submitting REFERRAL TO TREATMENT PERIOD data to the Secondary Uses Service can cease having to also send a Referral To Treatment Clock Stop Administrative Event when a clock stop is carried in one of the Elective Admission List Commissioning Data Set Types, will be notified as part of the Secondary Uses Service release documentation. It is also anticipated that CDS V6 TYPE 021 - FUTURE OUTPATIENT CDS will be processed once piloting is complete and its use is approved by the Information Standards Board for Health and Social Care. It is also anticipated that CDS V6 Type 021 - Future Outpatient CDS will be processed once piloting is complete and its use is approved by the Information Standards Board for Health and Social Care. A cancelled future APPOINTMENT record could carry a REFERRAL TO TREATMENT PERIOD Clock Stop. Again the timescales will be notified as part of the Secondary Uses Service release documentation.
There are no current plans for the Secondary Uses Service to process the remaining Commissioning Data Set Types:
CDS V6 TYPE 040 - EAL - END OF PERIOD CENSUS OLD CDSCDS V6 TYPE 090 - EAL - EVENT DURING PERIOD - AVAILABLE / UNAVAILABLE CDSCDS V6 TYPE 100 - EAL - EVENT DURING PERIOD - OLD SERVICE AGREEMENT CDSCDS V6 TYPE 120 - ADMITTED PATIENT CARE - FINISHED BIRTH EPISODE CDSCDS V6 TYPE 140 - ADMITTED PATIENT CARE - FINISHED DELIVERY EPISODE CDSCDS V6 TYPE 160 - ADMITTED PATIENT CARE - OTHER DELIVERY EVENT CDSCDS V6 TYPE 180 - ADMITTED PATIENT CARE - UNFINISHED BIRTH EPISODE CDSCDS V6 TYPE 200 - ADMITTED PATIENT CARE - UNFINISHED DELIVERY EPISODE CDS- CDS V6 Type 010 - Accident and Emergency CDS
- CDS V6 Type 040 - EAL - End of Period Census Old CDS
- CDS V6 Type 050 - EAL - End of Period Census New CDS
- CDS V6 Type 090 - EAL - Event During Period - Available / Unavailable CDS
- CDS V6 Type 100 - EAL - Event During Period - Old Service Agreement CDS
- CDS V6 Type 110 - EAL - Event During Period - New Service Agreement CDS
- CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode CDS
- CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode CDS
- CDS V6 Type 150 - Admitted Patient Care - Other Birth Event CDS
- CDS V6 Type 160 - Admitted Patient Care – Other Delivery Event CDS
- CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census CDS
- CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode CDS
- CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode CDS
This is the because a Referral To Treatment Clock Stop Administrative Event occurring in the scenarios where these record types are generated, would be rare. However this will be reviewed as part of the ongoing maintenance of the Referral To Treatment Clock Stop Administrative Event, and the requirements for the Secondary Uses Service.
When NOT to Use a Referral To Treatment Clock Stop Administrative Event
The Referral To Treatment Clock Stop Administrative Event should NOT be used to correct previously submitted records where a REFERRAL TO TREATMENT PERIOD END DATE was submitted incorrectly to the Secondary Uses Service.
For example, if an Out-Patient Appointment took place where First Definitive Treatment was started, but the REFERRAL TO TREATMENT PERIOD END DATE was not sent in the corresponding CDS V6 TYPE 020 - OUTPATIENT CDS record as it was not entered on the Patient Administration System until later; then the CDS V6 TYPE 020 - OUTPATIENT CDS record should be resubmitted with the correct data.For example, if an Out-Patient Appointment took place where First Definitive Treatment was started, but the REFERRAL TO TREATMENT PERIOD END DATE was not sent in the corresponding CDS V6 Type 020 - Outpatient CDS record as it was not entered on the Patient Administration System until later; then the CDS V6 Type 020 - Outpatient CDS record should be resubmitted with the correct data. A Referral To Treatment Clock Stop Administrative Event should NOT be used.
Where an ORGANISATION's Patient Administration System supports the submission of cancelled and Did Not Attend appointments in the CDS V6 TYPE 020 - OUTPATIENT CDS, the Referral To Treatment Clock Stop Administrative Event should NOT be used when a PATIENT has a booked Out-Patient Appointment, which is then cancelled because, for example, the PATIENT dies. In these cases the CDS V6 TYPE 020 - OUTPATIENT CDS can carry the details of a cancelled CARE ACTIVITY, including the REFERRAL TO TREATMENT PERIOD END DATE and update to the REFERRAL TO TREATMENT STATUS.Where an ORGANISATION's Patient Administration System supports the submission of cancelled and Did Not Attend appointments in the CDS V6 Type 020 - Outpatient CDS, the Referral To Treatment Clock Stop Administrative Event should NOT be used when a PATIENT has a booked Out-Patient Appointment, which is then cancelled because, for example, the PATIENT dies. In these cases the CDS V6 Type 020 - Outpatient CDS can carry the details of a cancelled CARE ACTIVITY, including the REFERRAL TO TREATMENT PERIOD END DATE and update to the REFERRAL TO TREATMENT STATUS. (Note - not all Patient Administration Systems provide functionality to create and submit Commissioning Data Set records for cancellations/Did Not Attend's as this is not yet mandated - you should contact your Patient Administration System support team to ascertain whether your Patient Administration System supports this. If not, then it is permissible to send a Referral To Treatment Clock Stop Administrative Event in order to stop the clock in the Secondary Uses Service instead).
Referral To Treatment Clock Stop Administrative Events only require a sub-set of the data elements contained in the CDS V6 TYPE 020 - OUTPATIENT CDS record, to be submitted to the Secondary Uses Service. All other data elements not listed should be omitted from the XML submission of the CDS V6 TYPE 020 - OUTPATIENT CDS record to the Secondary Uses Service.Referral To Treatment Clock Stop Administrative Events only require a sub-set of the data elements contained in the CDS V6 Type 020 - Outpatient CDS record, to be submitted to the Secondary Uses Service. All other data elements not listed should be omitted from the XML submission of the CDS V6 Type 020 - Outpatient CDS record to the Secondary Uses Service. The submission of a Referral To Treatment Clock Stop Administrative Event is not reliant on the use of the Net Changes Commissioning Data Set Submission Protocol to the Secondary Uses Service
The required data elements making up a Referral To Treatment Clock Stop Administrative Event are:
Data Element Required | Notes |
UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) or PATIENT PATHWAY IDENTIFIER | The Commissioning Data Set Schema version 6-1 requires EITHER the PATIENT PATHWAY IDENTIFIER, or the UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) to be populated. |
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | If the UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) is used, the ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) should contain X09 (which relates to the Choose and Book system) |
REFERRAL TO TREATMENT STATUS | This should contain only one of the following codes to signify that the REFERRAL TO TREATMENT PERIOD has ended: 30 Start of First Definitive Treatment 31 Start of Active Monitoring initiated by the PATIENT 32 Start of Active Monitoring initiated CARE PROFESSIONAL 34 Decision not to treat - decision not to treat made or no further contact required 35 PATIENT declined offered treatment 36 PATIENT died before treatment |
REFERRAL TO TREATMENT PERIOD START DATE | |
REFERRAL TO TREATMENT PERIOD END DATE | |
NHS NUMBER | |
NHS NUMBER STATUS INDICATOR | |
POSTCODE OF USUAL ADDRESS | |
ORGANISATION CODE (PCT OF RESIDENCE) | |
FIRST ATTENDANCE | This should always hold the National code 5 - "Referral to Treatment Period Clock Stop Administrative Event" |
APPOINTMENT DATE | This field is XML mandatory in Commissioning Data Set Schema version 6-1 for Type 020 Outpatients, and for the purposes of the Referral To Treatment Clock Stop Administrative Event, should hold the same date as the REFERRAL TO TREATMENT PERIOD END DATE |
AGE AT CDS ACTIVITY DATE | This field is XML mandatory in the Commissioning Data Set Schema version 6-1 for Type 020 Outpatients, and should hold the PATIENTS age at REFERRAL TO TREATMENT PERIOD END DATE |
ORGANISATION CODE (CODE OF PROVIDER) | This field is not XML mandatory in the Commissioning Data Set version 6-1 schema but is required by the Secondary Uses Service for processing of all records |
ORGANISATION CODE (CODE OF COMMISSIONER) | This field is not XML mandatory in the Commissioning Data Set version 6-1 schema but is required by the Secondary Uses Service for processing of all records |
Change to Attribute: Changed Description
This indicates whether a PATIENT is making a first attendance or contact; or a follow-up attendance or contact.
National Codes:
1 | First attendance face to face |
2 | Follow-up attendance face to face |
3 | First telephone or telemedicine consultation |
4 | Follow-up telephone or telemedicine consultation |
5 | Referral To Treatment Clock Stop Administrative Event* |
*Referral to Treatment Clock Stop Administrative Event allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity. It flows through the CDS V6 TYPE 020 - OUTPATIENT CDS structure. It flows through the CDS V6 Type 020 - Outpatient CDS structure. See Referral To Treatment Clock Stop Administrative Event.
Change to Data Element: Changed Description
Format/Length: | See DATE |
HES Item: | |
National Codes: | |
Default Codes: |
Notes:
APPOINTMENT DATE is the same as attribute APPOINTMENT DATE.
Usage in the CDS:
The Outpatient and Future Outpatient CDS Types use the APPOINTMENT DATE as the "CDS ORIGINATING DATE" as a mandatory requirement of the CDS Exchange Protocol, see CDS ACTIVITY DATE.
For the Future Outpatient CDS where no APPOINTMENT DATE is available from the healthcare system, a default date value of 2999-12-31 may be applied.
Care must be taken to generate the correct CDS Exchange Protocol when using this default value.
When submitting a Referral To Treatment Clock Stop Administrative Event via the CDS V6 TYPE 020 - OUTPATIENT CDS, APPOINTMENT DATE is equivalent to the REFERRAL TO TREATMENT PERIOD END DATE carried in the record.When submitting a Referral To Treatment Clock Stop Administrative Event via the CDS V6 Type 020 - Outpatient CDS, APPOINTMENT DATE is equivalent to the REFERRAL TO TREATMENT PERIOD END DATE carried in the record.
Change to Data Element: Changed Description
Format/Length: | See DATE |
HES Item: | |
National Codes: | |
Default Codes: |
Notes:Used in the NHS standard format which is the e-Government Interoperability Framework (e-GIF) compliant format of CCYY-MM-DD.
Definition:
For Commissioning data, every CDS TYPE has a "CDS Originating Date" contained within the Commissioning Data Set data that must be used to populate the CDS ACTIVITY DATE.
The CDS ACTIVITY DATE is held in the Commissioning Data Set Transaction Header Group and is a mandatory data element for all uses of the Commissioning Data Set for both Bulk Update and Net Change Protocols, see the Commissioning Data Set Submission Protocol supporting information.For Bulk Update use, see: CDS V6 TYPE 005BFor Bulk Update use, see: CDS V6 Type 005B - CDS Transaction Header Group - Bulk Update ProtocolFor Net Change Use, see: CDS V6 TYPE 005NFor Net Change Use, see: CDS V6 Type 005N - CDS Transaction Header Group - Net Change Protocol
The CDS ACTIVITY DATE has an associated "CDS Originating Date" specifically identified for each CDS TYPE as follows:
CDS TYPE | DESCRIPTION | CDS ORIGINATING DATE (used to populate the CDS ACTIVITY DATE) |
010 | Accident and Emergency Attendance | ARRIVAL DATE , ARRIVAL TIME |
020 | Outpatient (known in the Schema as Care Activity) | APPOINTMENT DATE |
021 | Future Outpatient (known in the Schema as Future Care Activity) | APPOINTMENT DATE |
030 | EAL End Of Period Census - STANDARD | DECIDED TO ADMIT DATE |
040 | EAL End Of Period Census - OLD | NHS SERVICE AGREEMENT CHANGE DATE |
050 | EAL End Of Period Census - NEW | NHS SERVICE AGREEMENT CHANGE DATE |
060 | EAL Event During Period - ADD | DECIDED TO ADMIT DATE |
070 | EAL Event During Period - REMOVE | ELECTIVE ADMISSION LIST REMOVAL DATE |
080 | EAL Event During Period - OFFER | OFFERED FOR ADMISSION DATE |
090 | EAL Event During Period - AVAILABLE / UNAVAILABLE | SUSPENSION START DATE |
100 | EAL Event During Period - OLD SERVICE AGREEMENT | NHS SERVICE AGREEMENT CHANGE DATE |
110 | EAL Event During Period - NEW SERVICE AGREEMENT | NHS SERVICE AGREEMENT CHANGE DATE |
120 | Finished Birth Episode | END DATE (EPISODE) |
130 | Finished General Episode | END DATE (EPISODE) |
140 | Finished Delivery Episode | END DATE (EPISODE) |
150 | Other Birth | DELIVERY DATE |
160 | Other Delivery | DELIVERY DATE |
170 | Detained and/or Long-Term Psychiatric Census | DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE (CDS V6 - located in the Consultant Episode Activity Characteristics data group) (CDS V5 - located in the LOCATION GROUP: Ward Stay data group) |
180 | Unfinished Birth Episode | START DATE (EPISODE) |
190 | Unfinished General Episode | START DATE (EPISODE) |
200 | Unfinished Delivery Episode | START DATE (EPISODE) |
Usage:
The CDS ACTIVITY DATE is validated by the Secondary Uses Service and Commissioning Data Set Interchanges are rejected if the date is not present, invalid or not compatible with the Commissioning Data Set Submission Protocol controls being used.
In particular, when using the Commissioning Data Set Bulk Replacement Update Mechanism, the CDS ACTIVITY DATE and its "CDS Originating Date" are used by the Secondary Uses Service to validate that the CDS TYPE date applicability falls within the CDS REPORT PERIOD START DATE and the CDS REPORT PERIOD END DATE.
Change to Data Element: Changed Description
Format/Length: | See DATE |
HES Item: | CENDATE |
National Codes: | |
Default Codes: |
Notes:
The CDS V6 TYPE 170 - the Detained and/or Long Term Psychiatric Census must be submitted annually to the Secondary Uses Service using a date of 31 March for the year of the census.The CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census CDS must be submitted annually to the Secondary Uses Service using a date of 31 March for the year of the census.
See the CDS Mandated Data Flows .See the CDS Mandated Data Flows for further information.
By local agreement, other submissions may be made and where this is undertaken, the date chosen must also be compatible with the CDS Submission Protocol used.
Change to Data Element: Changed Description
Format/Length: | See DATE |
National Codes: | |
Default Codes: |
Notes:It is the date of the earliest of the Reasonable Offers made to a PATIENT for an APPOINTMENT or Elective Admission.EARLIEST REASONABLE OFFER DATE is the date of the earliest of the Reasonable Offers made to a PATIENT for an APPOINTMENT or Elective Admission. It should only be included on the Commissioning Data Sets where the PATIENT has declined at least two Reasonable Offers, and a Patient Pause is to be applied to the length of wait calculation performed by the Secondary Uses Service.
For an APPOINTMENT this is the earliest of the APPOINTMENT DATES OFFERED where the REASONABLE OFFER INDICATOR of the APPOINTMENT OFFER is National code 1 - Reasonable Offer.
For an OFFER OF ADMISSION this is the earliest of the OFFERED FOR ADMISSION DATES where the REASONABLE OFFER INDICATOR of the OFFER OF ADMISSION is National code 1 - Reasonable Offer.
Patient Cancellations
Where, for any reason, a PATIENT cancels or does not attend an APPOINTMENT or an OFFER OF ADMISSION the EARLIEST REASONABLE OFFER DATE for the rearranged APPOINTMENT or OFFER OF ADMISSION will be the EARLIEST REASONABLE OFFER DATE of the cancelled APPOINTMENT or OFFER OF ADMISSION.
Provider Cancellations
Where, for any reason, any Health Care Provider cancels and re-arranges an APPOINTMENT or an OFFER OF ADMISSION, the EARLIEST REASONABLE OFFER DATE for the re-arranged APPOINTMENT or OFFER OF ADMISSION will be the date of the earliest Reasonable Offer made following the cancellation.
Patients who are unavailable
Where a PATIENT makes themself unavailable for a longer period of time, for example a PATIENT who is a teacher who wishes to delay their admission until the summer holidays, making a Reasonable Offer may be inappropriate.
In these circumstances, so long as the Health Care Provider could have made at least two Reasonable Offers, the EARLIEST REASONABLE OFFER DATE will be the date of the earliest Reasonable Offer that the provider could have offered the PATIENT. This must be communicated to the PATIENT.
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record:
relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement
and
includes the REFERRAL TO TREATMENT PERIOD END DATE of the REFERRAL TO TREATMENT PERIOD
and
is of the following Commissioning Data Set Types:
CDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDS- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
then EARLIEST REASONABLE OFFER DATE must be populated in the Commissioning Data Set record if a Patient Pause (the PATIENT is paused on the ELECTIVE ADMISSION LIST because they have made themselves unavailable for treatment for a specified period (for non-clinical reasons)) is to be applied to a REFERRAL TO TREATMENT PERIOD by the Secondary Uses Service.
Failure to include EARLIEST REASONABLE OFFER DATE in the Admitted Patient Care General Episode Commissioning Data Set record carrying the REFERRAL TO TREATMENT PERIOD END DATE, will mean no Patient Pause is applied to the duration of wait calculation for the REFERRAL TO TREATMENT PERIOD performed by the Secondary Uses Service.
Use in the Community Information Data Set For Secondary Uses:
For the Community Information Data Set the EARLIEST REASONABLE OFFER DATE may be used locally to inform waiting time calculations for Allied Health Professional Referral To Treatment Measurement. It can be used to account for periods of time where the PATIENT has not accepted the first available APPOINTMENT OFFER and this has extended the Allied Health Professional Referral To Treatment Measurement waiting time, for example:
- where a PATIENT who is a child has been offered an APPOINTMENT but their parent/carer states that they wish to wait until the school holidays commence. The Community Health Service cannot commence planned treatment until the PATIENT is available.
- where the PATIENT works away and cannot attend for a period of time, but it is not appropriate to discharge the PATIENT from the Community Health Service.
Change to Data Element: Changed Description
Format/Length: | n1 |
HES Item: | |
National Codes: | See FIRST ATTENDANCE |
Default Codes: |
Notes:This indicates whether a PATIENT is making a FIRST ATTENDANCE or follow-up attendance or contact and whether the CONSULTATION MEDIUM USED national code was 'Face to face communication', 'Telephone' or 'Telemedicine web camera'.FIRST ATTENDANCE indicates whether a PATIENT is making a FIRST ATTENDANCE or follow-up attendance or contact and whether the CONSULTATION MEDIUM USED national code was 'Face to face communication', 'Telephone' or 'Telemedicine web camera'.
A FIRST ATTENDANCE is the first in a series, or only attendance of an APPOINTMENT which took place regardless of how many previous APPOINTMENTS were made which did not take place for whatever reason. All subsequent attendances in the series which take place should be recorded as follow-up.
FIRST ATTENDANCE National Code 5 - "Referral to Treatment Clock Stop Administrative Event" allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity. It flows through the CDS V6 TYPE 020 - OUTPATIENT CDS structure. It flows through the CDS V6 Type 020 - Outpatient CDS structure. See Referral To Treatment Clock Stop Administrative Event.
FIRST ATTENDANCE will be replaced with FIRST ATTENDANCE CODE, which should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
Format/Length: | an1 |
HES Item: | |
National Codes: | See FIRST ATTENDANCE |
Default Codes: |
This item is being used for development purposes and has not yet been assured by the Information Standards Board for Health and Social Care.
Notes:
FIRST ATTENDANCE CODE is the same as attribute FIRST ATTENDANCE.
FIRST ATTENDANCE CODE indicates whether a PATIENT is making a FIRST ATTENDANCE or follow-up attendance or contact and whether the CONSULTATION MEDIUM USED national code was 'Face to face communication', 'Telephone' or 'Telemedicine web camera'.
A FIRST ATTENDANCE is the first in a series, or only attendance of an APPOINTMENT which took place regardless of how many previous APPOINTMENTS were made which did not take place for whatever reason. All subsequent attendances in the series which take place should be recorded as follow-up.
FIRST ATTENDANCE National Code 5 - "Referral to Treatment Clock Stop Administrative Event" allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity. It flows through the CDS V6 TYPE 020 - OUTPATIENT CDS structure. It flows through the CDS V6 Type 020 - Outpatient CDS structure. See Referral To Treatment Clock Stop Administrative Event.
FIRST ATTENDANCE CODE replaces FIRST ATTENDANCE, and should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
Format/Length: | n1 |
HES Item: | MENTCAT |
National Codes: | See MENTAL CATEGORY |
Default Codes: | 8 - Not applicable (i.e. not detained) |
9 - Not known: a validation error |
Notes:
See Mental Health Act Table for details of how MENTAL CATEGORIES relates to Parts and Sections of the Act.
This data element is effective for PATIENTS detained prior to 3rd November 2008 when the relevant section of the Mental Health Act 2007 comes into force, which abolishes the Mental Health Act 1983 MENTAL CATEGORIES. For PATIENTS detained from 3rd November 2008, the MENTAL HEALTH ACT 2007 MENTAL CATEGORY data element should be used.
MENTAL CATEGORY may continue to be used for historical purposes for any PATIENT last detained prior to 3rd November 2008 when the relevant section of the Mental Health Act 2007 comes into force. In these circumstances MENTAL CATEGORY will flow in the CDS V6 TYPE 170 - ADMITTED PATIENT CARE - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS CDS, and the Mental Health Minimum Data Set. In these circumstances MENTAL CATEGORY will flow in the CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census CDS, and the Mental Health Minimum Data Set.
MENTAL CATEGORY will be replaced with MENTAL CATEGORY CODE, which should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
Format/Length: | an1 |
HES Item: | MENTCAT |
National Codes: | See MENTAL CATEGORY |
Default Codes: | 8 - Not applicable (i.e. not detained) |
9 - Not known: a validation error |
This item is being used for development purposes and has not yet been assured by the Information Standards Board for Health and Social Care.
Notes:
See Mental Health Act Table for details of how MENTAL CATEGORY CODES relate to Parts and Sections of the Act.
This data element is effective for PATIENTS detained prior to 3rd November 2008 when the relevant section of the Mental Health Act 2007 comes into force, which abolishes the Mental Health Act 1983 MENTAL CATEGORIES. For PATIENTS detained from 3rd November 2008, the MENTAL HEALTH ACT 2007 MENTAL CATEGORY data element should be used.
MENTAL CATEGORY CODE may continue to be used for historical purposes for any PATIENT last detained prior to 3rd November 2008 when the relevant section of the Mental Health Act 2007 comes into force. In these circumstances MENTAL CATEGORY CODE will flow in the CDS V6 TYPE 170 - ADMITTED PATIENT CARE - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS CDS, and the Mental Health Minimum Data Set. In these circumstances MENTAL CATEGORY CODE will flow in the CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census CDS, and the Mental Health Minimum Data Set.
MENTAL CATEGORY CODE replaces MENTAL CATEGORY and should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
Format/Length: | max an5 |
National Codes: | |
Default Codes: |
Notes:
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) is the same as attribute ORGANISATION CODE.
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) is the ORGANISATION CODE of the ORGANISATION issuing the PATIENT PATHWAY IDENTIFIER.
Where Choose and Book has been used, the ORGANISATION CODE for NHS Connecting For Health (X09) should be used.
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:
CDS V6 TYPE 020 - OUTPATIENT CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
then ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) must be present in the Commissioning Data Set PATIENT PATHWAY Data Group.
Change to Data Element: Changed Description
Format/Length: | See DATE |
HES Item: | |
National Codes: | |
Default Codes: |
Notes:This is the same as attribute REFERRAL TO TREATMENT PERIOD END DATE.
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:
CDS V6 TYPE 020 - OUTPATIENT CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
then REFERRAL TO TREATMENT PERIOD END DATE must be present in the Commissioning Data Set PATIENT PATHWAY Data Group, where the REFERRAL TO TREATMENT PERIOD has ended.
Change to Data Element: Changed Description
Format/Length: | See DATE |
HES Item: | |
National Codes: | |
Default Codes: |
Notes:
REFERRAL TO TREATMENT PERIOD START DATE is the same as attribute REFERRAL TO TREATMENT PERIOD START DATE.
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:
CDS V6 TYPE 020 - OUTPATIENT CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
then REFERRAL TO TREATMENT PERIOD START DATE must be present in the Commissioning Data Set PATIENT PATHWAY Data Group.
Change to Data Element: Changed Description
Format/Length: | an2 |
HES Item: | |
National Codes: | See REFERRAL TO TREATMENT PERIOD STATUS |
Default Codes: |
Notes:
REFERRAL TO TREATMENT PERIOD STATUS is the same as attribute REFERRAL TO TREATMENT PERIOD STATUS.
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:
CDS V6 TYPE 020 - OUTPATIENT CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
then REFERRAL TO TREATMENT PERIOD STATUS must be present in the Commissioning Data Set PATIENT PATHWAY Data Group.
REFERRAL TO TREATMENT PERIOD STATUS replaces REFERRAL TO TREATMENT STATUS and should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
Format/Length: | n2 |
HES Item: | |
National Codes: | See REFERRAL TO TREATMENT PERIOD STATUS |
Default Codes: |
Notes:This is the same as attribute REFERRAL TO TREATMENT PERIOD STATUS.
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:
CDS V6 TYPE 020 - OUTPATIENT CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
then REFERRAL TO TREATMENT STATUS must be present in the Commissioning Data Set PATIENT PATHWAY Data Group.
REFERRAL TO TREATMENT STATUS will be replaced with REFERRAL TO TREATMENT PERIOD STATUS, which should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
Format/Length: | n12 |
HES Item: | |
National Codes: | |
Default Codes: |
Notes:
UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) is the same as attribute UNIQUE BOOKING REFERENCE NUMBER (CONVERTED).
Use in Commissioning Data Set version 6-0 onwards
If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:
CDS V6 TYPE 020 - OUTPATIENT CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDS- CDS V6 Type 020 - Outpatient CDS
- CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS
- CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS
- CDS V6 Type 030 - EAL - End of Period Census Standard CDS
- CDS V6 Type 060 - EAL - Event During Period - Add CDS
- CDS V6 Type 070 - EAL - Event During Period - Remove CDS
- CDS V6 Type 080 - EAL - Event During Period - Offer CDS
then either UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) or PATIENT PATHWAY IDENTIFIER must be present in the Commissioning Data Set PATIENT PATHWAY Data Group.
For enquiries about this Change Request, please email datastandards@nhs.net