NHS Connecting for Health
NHS Data Model and Dictionary Service
| Type: | Change Request |
| Reference: | 1306 |
| Version No: | 1.0 |
| Subject: | Supporting Change Request for CDS 6-2 - Removal of CDS 6-0 |
| Effective Date: | 1 November 2012 |
| Reason for Change: | Change to Data Standards |
| Publication Date: | 19 November 2012 |
Background:
Commissioning Data Set version 6-2 (ISB0092 Amd 16/2010 (Change)) is being introduced to support and enable several different requirements for different business areas of the NHS. NHS Data Model and Dictionary Change Request 1166 Commissioning Data Set version 6-2 introduces the new Commissioning Data Set tables and new data elements, attributes and business definitions supporting CDS 6-2.
This Change Request, CR1306, updates the existing Commissioning Data Set tables for CDS version 6-1, to remove references to CDS version 6-0 items. All menus, overview pages etc have also been renamed CDS V6-1 for clarity.
The Change Request also updates links to data elements which have been replaced at CDS version 6-2. This has been done separately from CR1166 to avoid confusion for users and prevent the size of CR1166 being a problem if system suppliers and submitters of CDS data use it for developing CDS 6-2.
This Change Request also formally retires two data elements which were originally introduced in Commissioning Data Set version 6-0 (see DSCN 14/2007 Introduction of Commissioning Data Set Version 6 schema) as placeholders which were intended to support Payment by Results developments in the future. The Department of Health Payment by Results team have now confirmed that these data elements will not be required, and they have been removed from the Commissioning Data Set version 6-2 tables and the corresponding CDS-XML schema version 6-2. The data elements are:
-
LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE)
- ADMINISTRATIVE CATEGORY (AT START OF EPISODE)
Note that the CDS-XML schema version 6-1-1 still retains the capability of carrying these data elements, but they should not, and should never have, been submitted to the Secondary Uses Service. The information may still be collected if required locally.
Both this Change Request (CR1306) and the main CDS 6-2 Change Request (CR1166), are published as part of the Commissioning Data Set version 6-2 standard ISB0092 Amd 16/2010 (Change).
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:
| Date: | 19 November 2012 |
| Sponsor: | Jeremy Thorp, Programme Delivery Director, NHS Information Reporting Services (NIRS), 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 Name, Description
CDS V6 Type 001 - Commissioning Data Set Interchange Header OverviewCDS V6-1 Type 001 - Commissioning Data Set Interchange Header Overview
Click CDS V6 Type 001 - Commissioning Data Set Interchange Header for a "Full Screen" view.Click CDS V6-1 Type 001 - Commissioning Data Set Interchange Header for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE SENDER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE RECEIVER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE DATE OF PREPARATION | F S8 S13 | ||
| M | 1..1 | CDS INTERCHANGE TIME OF PREPARATION | F S8 S14 | ||
| M | 1..1 | CDS INTERCHANGE APPLICATION REFERENCE | F S8 | ||
| O | 0..1 | CDS INTERCHANGE TEST INDICATOR | F | ||
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_001_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_001_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer OverviewCDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer Overview
Click CDS V6 Type 002 - Commissioning Data Set Interchange Trailer for a "Full Screen" view.Click CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL COUNT | F S8 | ||
| O | 0..1 | CDS INTERCHANGE SENDER IDENTITY | F | ||
| O | 0..1 | CDS INTERCHANGE RECEIVER IDENTITY | F | ||
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_002_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_002_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 003 - Commissioning Data Set Message Header OverviewCDS V6-1 Type 003 - Commissioning Data Set Message Header Overview
Click CDS V6 Type 003 - Commissioning Data Set Message Header for a "Full Screen" view.Click CDS V6-1 Type 003 - Commissioning Data Set Message Header for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity controls for each Commissioning Data Set Message. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS MESSAGE TYPE | V | ||
| M | 1..1 | CDS MESSAGE VERSION NUMBER | F | ||
| M | 1..1 | CDS MESSAGE REFERENCE | F | ||
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_003_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_003_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 004 - Commissioning Data Set Message Trailer OverviewCDS V6-1 Type 004 - Commissioning Data Set Message Trailer Overview
Click CDS V6 Type 004 - Commissioning Data Set Message Trailer for a "Full Screen" view.Click CDS V6-1 Type 004 - Commissioning Data Set Message Trailer for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity controls for each Commissioning Data Set Message. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS MESSAGE REFERENCE | F | ||
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_004_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_004_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol OverviewCDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Overview
Click CDS V6 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol for a "Full Screen" view.Click CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory Commissioning Data Set Submission Protocol controls for when using the Bulk Update mechanism. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS TYPE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER | V | ||
| O | 0..1 | CDS UNIQUE IDENTIFIER | F S9 | ||
| M | 1..1 | CDS BULK REPLACEMENT GROUP | V | ||
| M | 1..1 | CDS EXTRACT DATE | F S13 | ||
| M | 1..1 | CDS EXTRACT TIME | F S14 | ||
| M | 1..1 | CDS REPORT PERIOD START DATE | F S6 S13 | ||
| M | 1..1 | CDS REPORT PERIOD END DATE | F S6 S13 | ||
| M | 1..1 | CDS ACTIVITY DATE | F S6 S10 S11 S13 | ||
| M | 1..1 | CDS SENDER IDENTITY | F S5 | ||
| M | 1..1 | CDS PRIME RECIPIENT IDENTITY | F S5 S7 | ||
| O | 1..7 | CDS COPY RECIPIENT IDENTITY | F S5 S7 | ||
| X | 0..0 | CDS TEST INDICATOR | F S2 | ||
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_005B_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_005B_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol OverviewCDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol Overview
Click CDS V6 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol for a "Full Screen" view.Click CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory Commissioning Data Set Submission Protocol controls for when using the Net Change mechanism. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS TYPE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER | V | ||
| M | 1..1 | CDS UNIQUE IDENTIFIER | F S9 | ||
| M | 1..1 | CDS UPDATE TYPE | V | ||
| M | 1..1 | CDS APPLICABLE DATE | F S8 S13 | ||
| M | 1..1 | CDS APPLICABLE TIME | F S8 S14 | ||
| M | 1..1 | CDS ACTIVITY DATE | F S6 S10 S11 S13 | ||
| M | 1..1 | CDS SENDER IDENTITY | F S5 | ||
| M | 1..1 | CDS PRIME RECIPIENT IDENTITY | F S5 S7 | ||
| O | 1..7 | CDS COPY RECIPIENT IDENTITY | F S5 S7 | ||
| X | 0..0 | CDS TEST INDICATOR | F S2 | ||
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_005N_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_005N_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 010 - Accident and Emergency Commissioning Data Set OverviewCDS V6-1 Type 010 - Accident and Emergency Commissioning Data Set Overview
Click CDS V6 Type 010 - Accident and Emergency Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 010 - Accident and Emergency Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 010 - ACCIDENT AND EMERGENCY COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Accident And Emergency Attendance. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (A AND E) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient for an Accident and Emergency Attendance. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: ATTENDANCE OCCURRENCE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Accident and Emergency Attendance. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | A and E ATTENDANCE NUMBER | F | ||
| R | 0..1 | A and E ARRIVAL MODE | V | ||
| R | 0..1 | A and E ATTENDANCE CATEGORY | V | ||
| R | 0..1 | A and E ATTENDANCE DISPOSAL | V | ||
| R | 0..1 | A and E INCIDENT LOCATION TYPE | V | ||
| R | 0..1 | A and E PATIENT GROUP | V | ||
| R | 0..1 | SOURCE OF REFERRAL FOR A and E | V | ||
| R | 0..1 | A and E DEPARTMENT TYPE | V | ||
| M | 1..1 | ARRIVAL DATE | F S1 S13 | ||
| M | 1..1 | ARRIVAL TIME | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F S8 | ||
| R | 0..1 | A and E INITIAL ASSESSMENT TIME | F S14 | ||
| R | 0..1 | A and E TIME SEEN FOR TREATMENT | F S14 | ||
| R | 0..1 | A and E ATTENDANCE CONCLUSION TIME | F S14 | ||
| R | 0..1 | A and E DEPARTURE TIME | F S14 | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| O | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: ATTENDANCE OCCURRENCE - PERSON GROUP (A AND E CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Clinician. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | A and E STAFF MEMBER CODE | F | ||
| Notation | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | |
| Group Status O | 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| Notation | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CLINICAL DIAGNOSIS GROUP (A AND E) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Accident and Emergency coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | ACCIDENT AND EMERGENCY DIAGNOSIS - FIRST | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | ACCIDENT AND EMERGENCY DIAGNOSIS - SECOND | F | ||
| Notation | DATA GROUP: ATTENDANCE OCCURRENCE - CLINICAL INVESTIGATION GROUP (A AND E) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Accident and Emergency coded Investigations undertaken. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | INVESTIGATION SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY INVESTIGATION | Rules | ||
| M | 1..1 | ACCIDENT AND EMERGENCY INVESTIGATION - FIRST | F H4 | ||
| O | 0..* | DATA GROUP: SECONDARY INVESTIGATION | Rules | ||
| M | 1..1 | ACCIDENT AND EMERGENCY INVESTIGATION - SECOND | F H4 | ||
| Notation | DATA GROUP: ATTENDANCE OCCURRENCE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities and Treatments undertaken. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F | ||
| R | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: ATTENDANCE OCCURRENCE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities and Treatments undertaken. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: ATTENDANCE OCCURRENCE - CLINICAL TREATMENT GROUP (A AND E) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Accident and Emergency coded Clinical Activities and Treatments undertaken. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | ACCIDENT AND EMERGENCY TREATMENT - FIRST | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | ACCIDENT AND EMERGENCY TREATMENT - SECOND | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_010_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_010_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 020 - Outpatient Commissioning Data Set OverviewCDS V6-1 Type 020 - Outpatient Commissioning Data Set Overview
Click CDS V6 Type 020 - Outpatient Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 020 - Outpatient Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 020 - OUTPATIENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Outpatient Attendance. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED OR PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) OR PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (CARE ACTIVITY) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| Notation | DATA GROUP: CARE EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| Notation | DATA GROUP: CARE EPISODE - CLINICAL DIAGNOSIS GROUP (ICD) | |
| Group Status O | 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| Notation | DATA GROUP: CARE EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CARE ATTENDANCE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Care Attendance or Missed/Cancelled Appointment. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ATTENDANCE IDENTIFIER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY | V | ||
| R | 0..1 | ATTENDED OR DID NOT ATTEND (Called ATTENDANCE STATUS in the CDS-XML Schema version 6-1-1) | V | ||
| R | 0..1 | FIRST ATTENDANCE | V H4 | ||
| R | 0..1 | MEDICAL STAFF TYPE SEEING PATIENT | V | ||
| R | 0..1 | OPERATION STATUS | V | ||
| R | 0..1 | OUTCOME OF ATTENDANCE | V | ||
| M | 1..1 | APPOINTMENT DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP - ATTENDANCE | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location and Site Code Of Treatment. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | V N3 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: ACTIVITY CHARACTERISTICS - REFERRAL | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PRIORITY TYPE | V | ||
| R | 0..1 | SERVICE TYPE REQUESTED | V | ||
| R | 0..1 | SOURCE OF REFERRAL FOR OUT-PATIENTS | V | ||
| R | 0..1 | REFERRAL REQUEST RECEIVED DATE | F S13 | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: CARE REFERRAL - MISSED APPOINTMENT OCCURRENCE | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of a Missed Appointment. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LAST DNA OR PATIENT CANCELLED DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_020_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_020_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 021- Future Outpatient Commissioning Data Set OverviewCDS V6-1 Type 021- Future Outpatient Commissioning Data Set Overview
Click CDS V6 Type 021 - Future Outpatient Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 021 - Future Outpatient Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 021 - FUTURE OUTPATIENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Future (or Planned) Outpatient Attendance. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| 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 | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (CARE ACTIVITY) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| Notation | DATA GROUP: CARE EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V | ||
| Notation | DATA GROUP: CARE EPISODE - CLINICAL DIAGNOSIS GROUP (ICD) | |
| Group Status O | 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| Notation | DATA GROUP: CARE EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CARE ATTENDANCE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Care Attendance or Missed/Cancelled Appointment. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ATTENDANCE IDENTIFIER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY | V | ||
| R | 0..1 | ATTENDED OR DID NOT ATTEND (Called ATTENDANCE STATUS in the CDS-XML Schema version 6-1-1) | V | ||
| R | 0..1 | FIRST ATTENDANCE | V | ||
| R | 0..1 | MEDICAL STAFF TYPE SEEING PATIENT | V | ||
| R | 0..1 | OPERATION STATUS | V | ||
| R | 0..1 | OUTCOME OF ATTENDANCE | V | ||
| M | 1..1 | APPOINTMENT DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F S8 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location and Site Code Of Treatment. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: ACTIVITY CHARACTERISTICS - REFERRAL | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PRIORITY TYPE | V | ||
| R | 0..1 | SERVICE TYPE REQUESTED | V | ||
| R | 0..1 | SOURCE OF REFERRAL FOR OUT-PATIENTS | V | ||
| R | 0..1 | REFERRAL REQUEST RECEIVED DATE | F S13 | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: CARE REFERRAL - MISSED APPOINTMENT OCCURRENCE | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of a Missed Appointment. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LAST DNA OR PATIENT CANCELLED DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| M | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_021_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_021_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 030 - Elective Admission List - End Of Period Census (Standard) Commissioning Data Set OverviewCDS V6-1 Type 030 - Elective Admission List - End Of Period Census (Standard) Commissioning Data Set Overview
Click CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 030 - ELECTIVE ADMISSION LIST - END OF PERIOD CENSUS (STANDARD) COMMISSIONING DATA SET | |
| FUNCTION: To support the details of all booked, planned and waiting list admissions, consisting of records of patients waiting for Elective Admission at a specified date. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement for the Patient's planned episode. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| O | 0..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY - ACTIVITY CHARACTERISTICS | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Elective Admission List Entry Occurrence. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ELECTIVE ADMISSION LIST ENTRY NUMBER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE | V | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS | V | ||
| R | 0..1 | PRIORITY TYPE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | GUARANTEED ADMISSION DATE | F S13 | ||
| R | 0..1 | LAST DNA OR PATIENT CANCELLED DATE | F S13 | ||
| O | 0..1 | WAITING LIST ENTRY LAST REVIEWED DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V | ||
| Notation | DATA GROUP: INTENDED PROCEDURE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 1..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended READ coded Clinical Procedures. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location (the Intended Site of Treatment) of any Intended Procedures. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | INTENDED SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: OFFER OF ADMISSION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Offer Of Admission and the Outcome. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ADMISSION OFFER OUTCOME | V | ||
| R | 0..1 | OFFERED FOR ADMISSION DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: ORIGINAL EAL ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the date on which the Decision to Admit was made. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ORIGINAL DECIDED TO ADMIT DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY REMOVAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the removal from the Elective Admission List. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL REASON | V | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_030_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_030_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set OverviewCDS V6-1 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set Overview
Click CDS V6 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 040 - ELECTIVE ADMISSION LIST - END OF PERIOD CENSUS (OLD) COMMISSIONING DATA SET | |
| FUNCTION: To report to the previous (old) Commissioner that the EAL Entry is now the responsibility of another Commissioner. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Service Agreement for the Patient's planned episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| M | 1..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S1 S13 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_040_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_040_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set OverviewCDS V6-1 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set Overview
Click CDS V6 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 050 - ELECTIVE ADMISSION LIST - END OF PERIOD CENSUS (NEW) COMMISSIONING DATA SET | |
| FUNCTION: To be used to report to a new Commissioner an EAL Entry that had previously been the responsibility of another Commissioner. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | F S3 S12 | |||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Service Agreement for the Patient's planned episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| M | 1..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S1 S13 | ||
| Notation | DATA GROUP: EAL ENTRY - ACTIVITY CHARACTERISTICS | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Elective Admission List Entry Occurrence. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ELECTIVE ADMISSION LIST ENTRY NUMBER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE | V | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS | V | ||
| R | 0..1 | PRIORITY TYPE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | GUARANTEED ADMISSION DATE | F S13 | ||
| R | 0..1 | LAST DNA OR PATIENT CANCELLED DATE | F S13 | ||
| O | 0..1 | WAITING LIST ENTRY LAST REVIEWED DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V | ||
| Notation | DATA GROUP: INTENDED PROCEDURE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 1..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended READ coded Clinical Procedures. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location (the Intended Site of Treatment) of any Intended Procedures. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | INTENDED SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: OFFER OF ADMISSION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Offer Of Admission and the Outcome. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ADMISSION OFFER OUTCOME | V | ||
| R | 0..1 | OFFERED FOR ADMISSION DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: ORIGINAL EAL ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the date on which the Decision to Admit was made. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ORIGINAL DECIDED TO ADMIT DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY REMOVAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the removal from the Elective Admission List. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL REASON | V | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_050_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_050_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set OverviewCDS V6-1 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set Overview
Click CDS V6 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 060 - ELECTIVE ADMISSION LIST - EVENT DURING PERIOD (ADD) COMMISSIONING DATA SET | |
| FUNCTION: To be used to make an initial report that the Elective Admission List Entry has been added to the Provider's Elective Admission List. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED OR PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) OR PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement for the Patient's planned episode. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| O | 0..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY - ACTIVITY CHARACTERISTICS | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Elective Admission List Entry Occurrence. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ELECTIVE ADMISSION LIST ENTRY NUMBER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE | V | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS | V | ||
| R | 0..1 | PRIORITY TYPE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | GUARANTEED ADMISSION DATE | F S13 | ||
| R | 0..1 | LAST DNA OR PATIENT CANCELLED DATE | F S13 | ||
| O | 0..1 | WAITING LIST ENTRY LAST REVIEWED DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V | ||
| Notation | DATA GROUP: INTENDED PROCEDURE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 1..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended READ coded Clinical Procedures. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location (the Intended Site of Treatment) of any Intended Procedures. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | INTENDED SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: OFFER OF ADMISSION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Offer Of Admission and the Outcome. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ADMISSION OFFER OUTCOME | V | ||
| R | 0..1 | OFFERED FOR ADMISSION DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: ORIGINAL EAL ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the date on which the Decision to Admit was made. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ORIGINAL DECIDED TO ADMIT DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY REMOVAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the removal from the Elective Admission List. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL REASON | V | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_060_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_060_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set OverviewCDS V6-1 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set Overview
Click CDS V6 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 070 - ELECTIVE ADMISSION LIST - EVENT DURING PERIOD (REMOVE) COMMISSIONING DATA SET | |
| FUNCTION: To be used to report that the EAL entry has been removed from the Provider's Elective Admission List. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| DATA GROUP: EAL ENTRY REMOVAL | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Removal from the Elective Admission List. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ELECTIVE ADMISSION LIST REMOVAL REASON | V | ||
| M | 1..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S1 S13 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_070_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_070_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set OverviewCDS V6-1 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set Overview
Click CDS V6 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 080 - ELECTIVE ADMISSION LIST - EVENT DURING PERIOD (OFFER) COMMISSIONING DATA SET | |
| FUNCTION: To be used to report that an offer of admission has been made to the patient. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: EAL OFFER OF ADMISSION | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Offer Of Admission and the Outcome. |
| M | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ADMISSION OFFER OUTCOME | V | ||
| M | 1..1 | OFFERED FOR ADMISSION DATE | F S1 S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_080_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_080_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set OverviewCDS V6-1 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set Overview
Click CDS V6 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 090 - ELECTIVE ADMISSION LIST - EVENT DURING PERIOD (AVAILABLE/UNAVAILABLE) COMMISSIONING DATA SET | |
| FUNCTION: To be used to report changes in the patient's availability for treatment. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: EAL PATIENT SUSPENSION | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's unavailability for treatment (suspension). |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | SUSPENSION START DATE | F S1 S13 | ||
| R | 0..1 | SUSPENSION END DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_090_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_090_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set OverviewCDS V6-1 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set Overview
Click CDS V6 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 100- ELECTIVE ADMISSION LIST - EVENT DURING PERIOD (OLD SERVICE AGREEMENT) COMMISSIONING DATA SET | |
| FUNCTION: To be used to report to the previous (OLD) Commissioner that the EAL Entry is now the responsibility of a new Commissioner. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Service Agreement for the Patient's planned episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| M | 1..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S1 S13 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_100_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_100_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set OverviewCDS V6-1 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set Overview
Click CDS V6 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 110 - ELECTIVE ADMISSION LIST - EVENT DURING PERIOD (NEW SERVICE AGREEMENT) COMMISSIONING DATA SET | |
| FUNCTION: To be used to make an initial report to a new Commissioner of an EAL entry that had previously been the responsibility of another Commissioner. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Service Agreement for the Patient's planned episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| M | 1..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S1 S13 | ||
| Notation | DATA GROUP: EAL ENTRY - ACTIVITY CHARACTERISTICS | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Elective Admission List Entry Occurrence. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ELECTIVE ADMISSION LIST ENTRY NUMBER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE | V | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS | V | ||
| R | 0..1 | PRIORITY TYPE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | GUARANTEED ADMISSION DATE | F S13 | ||
| R | 0..1 | LAST DNA OR PATIENT CANCELLED DATE | F S13 | ||
| O | 0..1 | WAITING LIST ENTRY LAST REVIEWED DATE | F S13 | ||
| Notation | DATA GROUP: EAL ENTRY - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V | ||
| Notation | DATA GROUP: INTENDED PROCEDURE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 1..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended READ coded Clinical Procedures. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location (the Intended Site of Treatment) of any Intended Procedures. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | INTENDED SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: OFFER OF ADMISSION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Offer Of Admission and the Outcome. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | ADMISSION OFFER OUTCOME | V | ||
| R | 0..1 | OFFERED FOR ADMISSION DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: ORIGINAL EAL ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the date on which the Decision to Admit was made. |
| R | 0..1 | Data Element Components | Rules | ||
| R | 1..1 | ORIGINAL DECIDED TO ADMIT DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_110_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_110_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set OverviewCDS V6-1 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set Overview
Click CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS TYPE V6-1 120 - FINISHED BIRTH EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished Birth Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the personal details of the Patient (the Baby). See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE (Birth Episode) Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED OR PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Baby). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F H4 | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V H4 | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - DISCHARGE CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the discharge details of the Hospital Provider Spell containing the Episode. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | DISCHARGE DESTINATION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| O | 0..1 | DISCHARGE READY DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| R | 0..1 | DISCHARGE DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's Episode (the Baby). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F H4 | ||
| R | 0..1 | LAST EPISODE IN SPELL INDICATOR | V | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | OPERATION STATUS | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE | V H4 | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S13 | ||
| M | 1..1 | END DATE (EPISODE) | F H4 S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: BIRTH EPISODE- PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| Notation | DATA GROUP: BIRTH 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| Notation | DATA GROUP: BIRTH EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: BIRTH EPISODE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: BIRTH EPISODE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | I2 | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (AT WARD STAY) | |
| Group Status O | Group Repeats 0..97 | FUNCTION: To carry the details of the Location at a Ward Stay. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | END DATE | F S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the End Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: BIRTH EPISODE - NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES | V | ||
| Notation | DATA GROUP: ANTENATAL CARE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | FIRST ANTENATAL ASSESSMENT DATE | F S13 | ||
| Notation | DATA GROUP: ANTENATAL CARE - PERSON GROUP (RESPONSIBLE CLINICIAN) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the General Medical Practitioner responsible for the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | GENERAL MEDICAL PRACTITIONER (ANTENATAL CARE) | F | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER PRACTICE (ANTENATAL CARE) | F | ||
| Notation | DATA GROUP: ANTENATAL CARE - LOCATION GROUP - DELIVERY PLACE INTENDED | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON | V | ||
| R | 0..1 | DELIVERY PLACE TYPE (INTENDED) | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Labour/Delivery. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD | V | ||
| R | 0..1 | DELIVERY DATE | F S13 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Birth Occurrence. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | BIRTH ORDER | F | ||
| R | 0..1 | DELIVERY METHOD | V | ||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | ||
| R | 0..1 | RESUSCITATION METHOD | V | ||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY | V | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE PERSON IDENTITY - MOTHER | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE (MOTHER) | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (MOTHER)) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER (MOTHER) | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (MOTHER)) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER (MOTHER) | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| O | 0..1 | PATIENT USUAL ADDRESS (MOTHER) - ADDRESS STRUCTURED (Label format Postal Address) OR PATIENT USUAL ADDRESS (MOTHER) - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE TYPE (ACTUAL) | V | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_120_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_120_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set OverviewCDS V6-1 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set Overview
Click CDS V6 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 130 - FINISHED GENERAL EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished General Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | PERSON MARITAL STATUS | V N1 | ||
| R | 0..1 | LEGAL STATUS CLASSIFICATION CODE (ON ADMISSION) | V N1 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F H4 | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V H4 | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - DISCHARGE CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the discharge details of the Hospital Provider Spell containing the Episode. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | DISCHARGE DESTINATION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| O | 0..1 | DISCHARGE READY DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| R | 0..1 | DISCHARGE DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's Finished Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F H4 | ||
| R | 0..1 | LAST EPISODE IN SPELL INDICATOR | V | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | OPERATION STATUS | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE | V H4 | ||
| O | 0..1 | FIRST REGULAR DAY OR NIGHT ADMISSION | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS | V | ||
| X | 0..1 | LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE) | N1 N2 | ||
| M | 1..1 | START DATE (EPISODE) | F S13 | ||
| M | 1..1 | END DATE (EPISODE) | F H4 S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| R | 0..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| R | 0..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (AT WARD STAY) | |
| Group Status R | Group Repeats 0..97 | FUNCTION: To carry the details of one or more Ward Stays. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | END DATE | F S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the End Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Elective Admission List Entry. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | DURATION OF ELECTIVE WAIT | F | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | DECIDED TO ADMIT DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_130_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_130_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set OverviewCDS V6-1 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set Overview
Click CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 140 - FINISHED DELIVERY EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished Delivery Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient (the Mother). See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | R | 0..1 | PERSON BIRTH DATE | F S3 S12 |
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Mother). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | PERSON MARITAL STATUS | V N1 | ||
| R | 0..1 | LEGAL STATUS CLASSIFICATION CODE (ON ADMISSION) | V N1 | ||
| Notation | DATA GROUP: DELIVERY CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the delivery characteristics of the Patient (the Mother). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PREGNANCY TOTAL PREVIOUS PREGNANCIES | V | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F H4 | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V H4 | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - DISCHARGE CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the discharge details of the Hospital Provider Spell containing the Episode. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | DISCHARGE DESTINATION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| O | 0..1 | DISCHARGE READY DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| R | 0..1 | DISCHARGE DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F H4 | ||
| R | 0..1 | LAST EPISODE IN SPELL INDICATOR | V | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | OPERATION STATUS | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS | V | ||
| X | 0..1 | LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE) | N1 N2 | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S13 | ||
| M | 1..1 | END DATE (EPISODE) | F H4 S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (AT WARD STAY) | |
| Group Status O | Group Repeats 0..97 | FUNCTION: To carry the details of the Location at a Ward Stay. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | END DATE | F S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the End Of Episode. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | F N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| M | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES | V | ||
| Notation | DATA GROUP: ANTENATAL CARE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Antenatal Care. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | FIRST ANTENATAL ASSESSMENT DATE | F S13 | ||
| Notation | DATA GROUP: ANTENATAL CARE - PERSON GROUP (RESPONSIBLE CLINICIAN) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the General Medical Practitioner responsible for the Antenatal Care. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | GENERAL MEDICAL PRACTITIONER (ANTENATAL CARE) | F | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER PRACTICE (ANTENATAL CARE) | F | ||
| Notation | DATA GROUP: ANTENATAL CARE - LOCATION GROUP - DELIVERY PLACE INTENDED | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended Delivery Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON | V | ||
| R | 0..1 | DELIVERY PLACE TYPE (INTENDED) | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Labour/Delivery. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD | V | ||
| R | 0..1 | DELIVERY DATE | F S13 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE | |||||||||
| FUNCTION: To carry the details of up to 9 Birth Occurrences - one per Baby. | ||||||||||
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE - ACTIVITY CHARACTERISTICS. | Rules | |||||||
| R | 0..1 | BIRTH ORDER | F | |||||||
| R | 0..1 | DELIVERY METHOD | V | |||||||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | |||||||
| R | 0..1 | RESUSCITATION METHOD | V | |||||||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY | V | |||||||
| DATA GROUP: PERSON GROUP - BABY FUNCTION: To carry the Identity of the Baby. One of the following DATA GROUPS must be used: | ||||||||||
| M | 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR (BABY) Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | Rules | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR (BABY) Code Value = 01 (Number present and verified) | ||||||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE (BABY) | Rules | |||||||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (BABY) | F S3 | |||||||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (BABY)) | F | |||||||
| M | 1..1 | Data Element Components | Rules | |||||||
| M | 1..1 | NHS NUMBER (BABY) | F S3 | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR (BABY) NOT included in the above | ||||||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | |||||||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (BABY) | F S3 | |||||||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (BABY)) | F | |||||||
| M | 1..1 | Data Element Components | Rules | |||||||
| R | 0..1 | NHS NUMBER (BABY) | F S3 | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | Data Element Components | Rules | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| Notation | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - BABY | |
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - BABY: To carry the characteristics of the Baby. | |||||
| M | 1..1 | Data Element Components | Rules | ||||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||||
| R | 0..1 | BIRTH WEIGHT | F | ||||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Birth Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE TYPE (ACTUAL) | V | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| M | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_140_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_140_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set OverviewCDS V6-1 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set Overview
Click CDS V6 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 150 - OTHER BIRTH EVENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details for an Other Birth. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the personal details of the Patient (the Baby). See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE (Birth Episode) Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Baby). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES | V | ||
| Notation | DATA GROUP: ANTENATAL CARE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | FIRST ANTENATAL ASSESSMENT DATE | F S13 | ||
| Notation | DATA GROUP: ANTENATAL CARE - PERSON GROUP (RESPONSIBLE CLINICIAN) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the General Medical Practitioner responsible for the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | GENERAL MEDICAL PRACTITIONER (ANTENATAL CARE) | F | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER PRACTICE (ANTENATAL CARE) | F | ||
| Notation | DATA GROUP: ANTENATAL CARE - LOCATION GROUP - DELIVERY PLACE INTENDED | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON | V | ||
| R | 0..1 | DELIVERY PLACE TYPE (INTENDED) | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Labour/Delivery. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD | V | ||
| M | 1..1 | DELIVERY DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Birth Occurrence. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | BIRTH ORDER | F | ||
| R | 0..1 | DELIVERY METHOD | V | ||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | ||
| R | 0..1 | RESUSCITATION METHOD | V | ||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY | V | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE PERSON IDENTITY - MOTHER | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity details of the Baby's Mother. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE (MOTHER) | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (MOTHER)) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER (MOTHER) | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (MOTHER)) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER (MOTHER) | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| O | 0..1 | PATIENT USUAL ADDRESS (MOTHER) - ADDRESS STRUCTURED (Label format Postal Address) OR PATIENT USUAL ADDRESS (MOTHER) - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE TYPE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_150_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_150_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set OverviewCDS V6-1 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set Overview
Click CDS V6 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 160 - OTHER DELIVERY EVENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details for an Other Delivery. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient (the Mother). See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | R | 0..1 | PERSON BIRTH DATE | F S3 S12 |
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Mother). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | PERSON MARITAL STATUS | V N1 | ||
| Notation | DATA GROUP: DELIVERY CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the delivery characteristics of the Patient (the Mother). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PREGNANCY TOTAL PREVIOUS PREGNANCIES | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. | ||
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES | V | ||
| Notation | DATA GROUP: ANTENATAL CARE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | FIRST ANTENATAL ASSESSMENT DATE | F S13 | ||
| Notation | DATA GROUP: ANTENATAL CARE - PERSON GROUP (RESPONSIBLE CLINICIAN) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the General Medical Practitioner responsible for the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | GENERAL MEDICAL PRACTITIONER (ANTENATAL CARE) | F | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER PRACTICE (ANTENATAL CARE) | F | ||
| Notation | DATA GROUP: ANTENATAL CARE - LOCATION GROUP - DELIVERY PLACE INTENDED | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON | V | ||
| R | 0..1 | DELIVERY PLACE TYPE (INTENDED) | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Labour/Delivery. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD | V | ||
| M | 1..1 | DELIVERY DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: LABOUR/DELIVERY SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement for the Delivery. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - ONE FOR EACH BABY IN THE DELIVERY | |||||||||
| Group Status R | Group Repeats 0..9 | FUNCTION: To carry the details of up to 9 Birth Occurrences - one per Baby. | ||||||||
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE - ACTIVITY CHARACTERISTICS. | Rules | |||||||
| R | 0..1 | BIRTH ORDER | F | |||||||
| R | 0..1 | DELIVERY METHOD | V | |||||||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | |||||||
| R | 0..1 | RESUSCITATION METHOD | V | |||||||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY | V | |||||||
| DATA GROUP: PERSON GROUP - BABY FUNCTION: To carry the Identity of the Baby. One of the following DATA GROUPS must be used: | ||||||||||
| M | 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR (BABY) Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | Rules | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR (BABY) Code Value = 01 (Number present and verified) | ||||||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE (BABY) | Rules | |||||||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (BABY) | F S3 | |||||||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (BABY)) | F | |||||||
| M | 1..1 | Data Element Components | Rules | |||||||
| M | 1..1 | NHS NUMBER (BABY) | F S3 | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR (BABY) NOT included in the above | ||||||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | |||||||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (BABY) | F S3 | |||||||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (BABY)) | F | |||||||
| M | 1..1 | Data Element Components | Rules | |||||||
| R | 0..1 | NHS NUMBER (BABY) | F S3 | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | Data Element Components | Rules | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| Notation | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - BABY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Birth Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE TYPE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_160_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_160_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 170 - Admitted Patient Care - Detained And/Or Long Term Psychiatric Census Commissioning Data Set OverviewCDS V6-1 Type 170 - Admitted Patient Care - Detained And/Or Long Term Psychiatric Census Commissioning Data Set Overview
Click CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 170 - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Psychiatric Patient Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED OR PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) OR PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | PERSON MARITAL STATUS | V N1 | ||
| R | 0..1 | LEGAL STATUS CLASSIFICATION CODE (ON ADMISSION) | V N1 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (PSYCHIATRIC CENSUS) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the psychiatric characteristics of the Patient. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LEGAL STATUS CLASSIFICATION CODE (AT CENSUS DATE) | V S13 | ||
| R | 0..1 | DATE DETENTION COMMENCED | F S13 | ||
| M | 1..1 | AGE AT CENSUS | F | ||
| R | 0..1 | DURATION OF CARE TO PSYCHIATRIC CENSUS DATE | F S13 | ||
| R | 0..1 | DURATION OF DETENTION | F | ||
| R | 0..1 | MENTAL CATEGORY | V N5 | ||
| R | 0..1 | MENTAL HEALTH ACT 2007 MENTAL CATEGORY | V N6 | ||
| R | 0..1 | STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS | V | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| M | 1..1 | AGE ON ADMISSION | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Consultant Episode on the Census Date. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS | V | ||
| M | 1..1 | START DATE (EPISODE) | F S13 | ||
| M | 1..1 | DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE | F S1 S10 S13 | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V | ||
| 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (WARD STAY AT PSYCHIATRIC CENSUS DATE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location of the Ward Stay at the Psychiatric Census Date. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| R | 0..1 | AGE GROUP INTENDED | V | ||
| R | 0..1 | SEX OF PATIENTS | V | ||
| R | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| R | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE | F N7 S1 S10 S13 | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Elective Admission List Entry. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | DURATION OF ELECTIVE WAIT | F | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | DECIDED TO ADMIT DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| O | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_170_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_170_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set OverviewCDS V6-1 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set Overview
Click CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 180 - UNFINISHED BIRTH EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished Birth Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the personal details of the Patient (the Baby). See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE (Birth Episode) Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Baby). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F H4 | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V H4 | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - DISCHARGE CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the discharge details of the Hospital Provider Spell containing the Episode. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | DISCHARGE DESTINATION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| O | 0..1 | DISCHARGE READY DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| R | 0..1 | DISCHARGE DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's Episode (the Baby). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F H4 | ||
| R | 0..1 | LAST EPISODE IN SPELL INDICATOR | V | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | OPERATION STATUS | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE | V H4 | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S1 S13 | ||
| R | 0..1 | END DATE (EPISODE) | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| Notation | DATA GROUP: BIRTH 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| Notation | DATA GROUP: BIRTH EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: BIRTH EPISODE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: BIRTH EPISODE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (AT WARD STAY) | |
| Group Status R | Group Repeats 0..97 | FUNCTION: To carry the details of the Location at a Ward Stay. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | END DATE | F S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the End Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: BIRTH EPISODE - NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES | V | ||
| Notation | DATA GROUP: ANTENATAL CARE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | FIRST ANTENATAL ASSESSMENT DATE | F S13 | ||
| Notation | DATA GROUP: ANTENATAL CARE - PERSON GROUP (RESPONSIBLE CLINICIAN) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the General Medical Practitioner responsible for the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | GENERAL MEDICAL PRACTITIONER (ANTENATAL CARE) | F | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER PRACTICE (ANTENATAL CARE) | F | ||
| Notation | DATA GROUP: ANTENATAL CARE - LOCATION GROUP - DELIVERY PLACE INTENDED | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON | V | ||
| R | 0..1 | DELIVERY PLACE TYPE (INTENDED) | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Labour/Delivery. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD | V | ||
| R | 0..1 | DELIVERY DATE | F S13 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Delivery Occurrence. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | BIRTH ORDER | F | ||
| R | 0..1 | DELIVERY METHOD | V | ||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | ||
| R | 0..1 | RESUSCITATION METHOD | V | ||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY | V | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE PERSON IDENTITY - MOTHER | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity details of the Baby's Mother. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE (MOTHER) | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (MOTHER)) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER (MOTHER) | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (MOTHER) | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (MOTHER)) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER (MOTHER) | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (MOTHER) | V | ||
| O | 0..1 | PATIENT USUAL ADDRESS (MOTHER) - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS (MOTHER) - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE (MOTHER)) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE TYPE (ACTUAL) | V | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_180_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_180_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set OverviewCDS V6-1 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set Overview
Click CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 190 - UNFINISHED GENERAL EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished General Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. This Group must be present if the record relates to a Referral To Treatment Period Included In 18 Weeks Target. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient. See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | PERSON MARITAL STATUS | V N1 | ||
| R | 0..1 | LEGAL STATUS CLASSIFICATION CODE (ON ADMISSION) | V N1 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F H4 | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V H4 | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - DISCHARGE CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the discharge details of the Hospital Provider Spell containing the Episode. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | DISCHARGE DESTINATION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| O | 0..1 | DISCHARGE READY DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| R | 0..1 | DISCHARGE DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's Unfinished Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F H4 | ||
| R | 0..1 | LAST EPISODE IN SPELL INDICATOR | V | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | OPERATION STATUS | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE | V H4 | ||
| O | 0..1 | FIRST REGULAR DAY OR NIGHT ADMISSION | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS | V | ||
| X | 0..1 | LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE) | N1 N2 | ||
| M | 1..1 | START DATE (EPISODE) | F S1 S13 | ||
| R | 0..1 | END DATE (EPISODE) | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| R | 0..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| R | 0..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (AT WARD STAY) | |
| Group Status R | Group Repeats 0..97 | FUNCTION: To carry the details of one or more Ward Stays. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | END DATE | F S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the End Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Elective Admission List Entry. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | DURATION OF ELECTIVE WAIT | F | ||
| R | 0..1 | INTENDED MANAGEMENT | V | ||
| R | 0..1 | DECIDED TO ADMIT DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_190_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_190_Details
- Changed Description
Change to Data Set: Changed Name, Description
CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set OverviewCDS V6-1 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set Overview
Click CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set for a "Full Screen" view.Click CDS V6-1 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set for a "Full Screen" view.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6-1 TYPE 200 - UNFINISHED DELIVERY EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished Delivery Episode. |
| Notation | DATA GROUP: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT STATUS | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| X | 0..1 | Data Element Components | Rules | ||||
| X | 0..1 | LEAD CARE ACTIVITY INDICATOR | N2 | ||||
| Notation | DATA GROUP: PATIENT IDENTITY | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the Identity of the Patient (the Mother). See Note: S3 in Commissioning Data Set Business Rules. | |
| One of the following DATA GROUPS must be used: |
| 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F S3 | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F S3 | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| O | 0..1 | PATIENT USUAL ADDRESS - ADDRESS STRUCTURED (Label format Postal Address) Or PATIENT USUAL ADDRESS - ADDRESS UNSTRUCTURED (Character string) | F S3 | ||
| R | 0..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | R | 0..1 | PERSON BIRTH DATE | F S3 S12 |
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Mother). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | PERSON MARITAL STATUS | V N1 | ||
| R | 0..1 | LEGAL STATUS CLASSIFICATION CODE (ON ADMISSION) | V N1 | ||
| Notation | DATA GROUP: DELIVERY CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the delivery characteristics of the Patient (the Mother). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PREGNANCY TOTAL PREVIOUS PREGNANCIES | V | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - ADMISSION CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the admission details of the Hospital Provider Spell containing the Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HOSPITAL PROVIDER SPELL NUMBER | F H4 | ||
| R | 0..1 | ADMINISTRATIVE CATEGORY (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION | V H4 | ||
| R | 0..1 | ADMISSION METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | SOURCE OF ADMISSION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| Notation | DATA GROUP: HOSPITAL PROVIDER SPELL - DISCHARGE CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the discharge details of the Hospital Provider Spell containing the Episode. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | DISCHARGE DESTINATION (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD (HOSPITAL PROVIDER SPELL) | V H4 | ||
| O | 0..1 | DISCHARGE READY DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| R | 0..1 | DISCHARGE DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Patient's Episode. | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | EPISODE NUMBER | F H4 | ||
| R | 0..1 | LAST EPISODE IN SPELL INDICATOR | V | ||
| X | 0..1 | ADMINISTRATIVE CATEGORY (AT START OF EPISODE) | N2 | ||
| R | 0..1 | OPERATION STATUS | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS | V | ||
| X | 0..1 | LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE) | N1 N2 | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S1 S13 | ||
| R | O..1 | END DATE (EPISODE) | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Service Agreement. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | COMMISSIONING SERIAL NUMBER | F | ||
| O | 0..1 | NHS SERVICE AGREEMENT LINE NUMBER | F | ||
| O | 0..1 | PROVIDER REFERENCE NUMBER | F | ||
| R | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| R | 0..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 S8 | ||
| R | 0..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F S8 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | TREATMENT FUNCTION CODE | V H4 | ||
| 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 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Diagnoses. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | DIAGNOSIS SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (READ) | F | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (READ) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (OPCS) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the OPCS coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (OPCS) | F H4 | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F H4 | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL ACTIVITY GROUP (READ) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the READ coded Clinical Activities. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY PROCEDURE | Rules | ||
| M | 1..1 | PRIMARY PROCEDURE (READ) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (READ) | F | ||
| M | 1..1 | PROCEDURE DATE | F I1 S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the Start Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: LOCATION GROUP (AT WARD STAY) | |
| Group Status O | Group Repeats 0..97 | FUNCTION: To carry the details of the Location at a Ward Stay. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | END DATE | F S13 | ||
| Notation | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Location at the End Of Episode. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY | V | ||
| O | 0..1 | AGE GROUP INTENDED | V | ||
| O | 0..1 | SEX OF PATIENTS | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY | V | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | F N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES | V | ||
| Notation | DATA GROUP: ANTENATAL CARE - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | FIRST ANTENATAL ASSESSMENT DATE | F S13 | ||
| Notation | DATA GROUP: ANTENATAL CARE - PERSON GROUP (RESPONSIBLE CLINICIAN) | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the General Medical Practitioner responsible for the Antenatal Care. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | GENERAL MEDICAL PRACTITIONER (ANTENATAL CARE) | F | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER PRACTICE (ANTENATAL CARE) | F | ||
| Notation | DATA GROUP: ANTENATAL CARE - LOCATION GROUP - DELIVERY PLACE INTENDED | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Intended Delivery Location. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON | V | ||
| R | 0..1 | DELIVERY PLACE TYPE (INTENDED) | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Labour/Delivery. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD | V | ||
| R | 0..1 | DELIVERY DATE | F S13 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - ONE FOR EACH BABY IN THE DELIVERY | |||||||||
| FUNCTION: To carry the details of up to 9 Birth Occurrences - one per Baby. | ||||||||||
| R | 0..1 | DATA GROUP: DELIVERY OCCURRENCE - ACTIVITY CHARACTERISTICS. | Rules | |||||||
| R | 0..1 | BIRTH ORDER | F | |||||||
| R | 0..1 | DELIVERY METHOD | V | |||||||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | |||||||
| R | 0..1 | RESUSCITATION METHOD | V | |||||||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY | V | |||||||
| DATA GROUP: PERSON GROUP - BABY FUNCTION: To carry the Identity of the Baby. One of the following DATA GROUPS must be used: | ||||||||||
| M | 1..1 | DATA GROUP: WITHHELD IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR (BABY) Code Value = 90 (Patient identity withheld from submission) NOTE - NHS NUMBER STATUS INDICATOR 90 IS NOT APPROVED BY THE INFORMATION STANDARDS BOARD FOR HEALTH AND SOCIAL CARE AND THEREFORE THIS STRUCTURE SHOULD NOT BE USED | Rules | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR (BABY) Code Value = 01 (Number present and verified) | ||||||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE (BABY) | Rules | |||||||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (BABY) | F S3 | |||||||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (BABY)) | F | |||||||
| M | 1..1 | Data Element Components | Rules | |||||||
| M | 1..1 | NHS NUMBER (BABY) | F S3 | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR (BABY) NOT included in the above | ||||||||
| O | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | |||||||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (BABY) | F S3 | |||||||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER (BABY)) | F | |||||||
| M | 1..1 | Data Element Components | Rules | |||||||
| R | 0..1 | NHS NUMBER (BABY) | F S3 | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR (BABY) | V | |||||||
| R | 0..1 | Data Element Components | Rules | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
Status
R
Repeats
0..1
| R | 0..1 | FUNCTION: To carry the characteristics of the Baby. | |||||||||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Birth Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| X | 0..1 | LOCATION TYPE | N3 | ||
| R | 0..1 | DELIVERY PLACE TYPE (ACTUAL) | V | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Healthcare Resource Group. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE | F I3 | ||
| R | 0..1 | HEALTHCARE RESOURCE GROUP CODE-VERSION NUMBER | F I3 | ||
| Notation | DATA GROUP: HEALTHCARE RESOURCE GROUP - CLINICAL ACTIVITY | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the HRG Dominant Grouping Variable Procedure. Note that this will not apply when no operation was carried out. In this case, the Data Group referring to HRG Dominant Grouping Variable - Procedure should be omitted. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | PROCEDURE SCHEME IN USE | V I3 | ||
| O | 0..1 | HRG DOMINANT GROUPING VARIABLE-PROCEDURE | F I3 | ||
| Notation | DATA GROUP: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: CDS V6-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Data_Sets.CDS_V6_Type_200_Details to Data_Dictionary.Messages.CDS_V6-1.Data_Sets.CDS_V6-1_Type_200_Details
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS TYPES.The CDS V6-1 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS TYPES.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
CDS V6 Type 001 - Commissioning Data Set Interchange Header- Mandatory - One per Commissioning Data Set InterchangeCDS V6 Type 003 - Commissioning Data Set Message Header- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS TYPE - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
CDS V6 Type 004 - Commissioning Data Set Message Trailer- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer- Mandatory - One per Commissioning Data Set Interchange- CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 001 - Commissioning Data Set Interchange Header is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 001 - Commissioning Data Set Interchange Header is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set Interchange submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Commissioning Data Set Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_001_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_001_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS TYPES.The CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS TYPES.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
CDS V6 Type 001 - Commissioning Data Set Interchange Header- Mandatory - One per Commissioning Data Set InterchangeCDS V6 Type 003 - Commissioning Data Set Message Header- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS TYPE - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
CDS V6 Type 004 - Commissioning Data Set Message Trailer- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer- Mandatory - One per Commissioning Data Set Interchange- CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 002 - Commissioning Data Set Interchange Trailer is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 002 - CDS INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_002_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_002_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS TYPES.The CDS V6-1 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS TYPES.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
CDS V6 Type 001 - Commissioning Data Set Interchange Header- Mandatory - One per Commissioning Data Set InterchangeCDS V6 Type 003 - Commissioning Data Set Message Header- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS TYPE - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
CDS V6 Type 004 - Commissioning Data Set Message Trailer- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer- Mandatory - One per Commissioning Data Set Interchange- CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 003 - Commissioning Data Set Message Header is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 003 - Commissioning Data Set Message Header is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 003 - CDS MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_003_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_003_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS TYPES.The CDS V6-1 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS TYPES.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
CDS V6 Type 001 - Commissioning Data Set Interchange Header- Mandatory - One per Commissioning Data Set InterchangeCDS V6 Type 003 - Commissioning Data Set Message Header- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS TYPE - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
CDS V6 Type 004 - Commissioning Data Set Message Trailer- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer- Mandatory - One per Commissioning Data Set Interchange- CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 004 - Commissioning Data Set Message Trailer is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 004 - Commissioning Data Set Message Trailer is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_004_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_004_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS TYPES.The CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS TYPES.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS TYPES using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
CDS V6 Type 001 - Commissioning Data Set Interchange Header- Mandatory - One per Commissioning Data Set InterchangeCDS V6 Type 003 - Commissioning Data Set Message Header- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS TYPE - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
CDS V6 Type 004 - Commissioning Data Set Message Trailer- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer- Mandatory - One per Commissioning Data Set Interchange- CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 005B - TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Update Mechanisms of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_005B_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_005B_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS TYPES.The CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS TYPES.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS TYPES using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
CDS V6 Type 001 - Commissioning Data Set Interchange Header- Mandatory - One per Commissioning Data Set InterchangeCDS V6 Type 003 - Commissioning Data Set Message Header- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS TYPE - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
CDS V6 Type 004 - Commissioning Data Set Message Trailer- Mandatory - One per Commissioning Data Set Message- CDS V6-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer- Mandatory - One per Commissioning Data Set Interchange- CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 005N - CDS TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Update Mechanisms of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_005N_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_005N_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 010 - Accident and Emergency Commissioning Data Set carries the data for an Accident and Emergency Attendance.CDS V6-1 Type 010 - Accident and Emergency Commissioning Data Set carries the data for an Accident and Emergency Attendance.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 010 - Accident and Emergency Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 010 - Accident and Emergency Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 010 - ACCIDENT AND EMERGENCY COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of an Accident and Emergency Attendance. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: COMMISSIONING DATA SET TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS (A AND E) | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| M | 1..1 | DATA GROUP: ATTENDANCE OCCURRENCE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (A AND E CONSULTANT) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (A AND E) | ||
| R | 0..1 | DATA GROUP: CLINICAL INVESTIGATION GROUP (A AND E) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (A AND E) | ||
| R | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_010_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_010_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 020 - Outpatient Commissioning Data Set carries the data for an Outpatient Attendance or a cancelled/missed APPOINTMENT.The CDS V6-1 Type 020 - Outpatient Commissioning Data Set carries the data for an Outpatient Attendance or a cancelled/missed APPOINTMENT.
It covers all NHS and private Outpatient ACTIVITY taking place in any:
- acute, community or mental health NHS Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.This CDS TYPE may also be used to submit Referral To Treatment Clock Stop Administrative Events.
This CDS TYPE must not be used for "Future Outpatients" - for this the CDS V6 Type 021 - Future Outpatient Commissioning Data Set must be used.This CDS TYPE must not be used for "Future Outpatients" - for this the CDS V6-1 Type 021 - Future Outpatient Commissioning Data Set must be used.
Note: CDS V6 Type 020 - Outpatient Commissioning Data Set is called Care Activity in the Commissioning Data Set XML Message Schema.Note: CDS V6-1 Type 020 - Outpatient Commissioning Data Set is called Care Activity in the Commissioning Data Set XML Message Schema version 6-1-1.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 020 - Outpatient Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 020 - Outpatient Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 020 - OUTPATIENT COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of an Outpatient Attendance, or a missed Appointment. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS (CARE ACTIVITY) | ||
| R | 0..1 | DATA GROUP: CARE EPISODE | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| M | 1..1 | DATA GROUP: CARE ATTENDANCE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP-ATTENDANCE | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: CARE ACTIVITY REFERRAL | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS - REFERRAL | ||
| O | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: MISSED APPOINTMENT OCCURRENCE | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_020_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_020_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
The CDS V6 Type 021 - Future Outpatient Commissioning Data Set carries the data for a Future Outpatient Attendance or a future cancelled APPOINTMENT.The CDS V6-1 Type 021 - Future Outpatient Commissioning Data Set carries the data for a Future Outpatient Attendance or a future cancelled APPOINTMENT.
This CDS TYPE has not been approved by the Information Standards Board for Health and Social Care and submissions to support local activities and commissioning will be supported for piloting purposes only.
It covers all NHS and private Outpatient ACTIVITY taking place in any:
- acute, community or mental health NHS Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
This CDS TYPE must not be used for "Outpatients" - for this the CDS V6 Type 020 - Outpatient Commissioning Data Set must be used.This CDS TYPE must not be used for "Outpatients" - for this the CDS V6-1 Type 020 - Outpatient Commissioning Data Set must be used.
Note: CDS V6 Type 021 - Future Outpatient Commissioning Data Set is called Future Care Activity in the Commissioning Data Set XML Message Schema.Note: CDS V6-1 Type 021 - Future Outpatient Commissioning Data Set is called Future Care Activity in the Commissioning Data Set XML Message Schema version 6-1-1.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 021 - Future Outpatient Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 021 - Future Outpatient Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 021 - FUTURE OUTPATIENT COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Future or Planned Outpatient Attendance (Care Attendance). | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS (CARE ACTIVITY) | ||
| R | 0..1 | DATA GROUP: CARE EPISODE | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| M | 1..1 | DATA GROUP: CARE ATTENDANCE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP-ATTENDANCE | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: CARE ACTIVITY REFERRAL | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS - REFERRAL | ||
| O | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: MISSED APPOINTMENT OCCURRENCE | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_021_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_021_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set carries the data for all booked, planned and waiting list admissions.CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set carries the data for all booked, planned and waiting list admissions.
This consists of records for PATIENTS waiting for Elective Admission at a specified date and should be sent to the Secondary Uses Service within one month of the end of the period to which they relate unless a shorter time-scale has been agreed with the recipient.
Some Health Care Providers also send a final CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set after the PATIENT has been removed from the WAITING LIST to identify when and why this took place.Some Health Care Providers also send a final CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set after the PATIENT has been removed from the WAITING LIST to identify when and why this took place. Commissioners who do not wish to use such final Elective Admission List-End Of Period Census Commissioning Data Sets should ignore them.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 030 - ELECTIVE ADMISSION LIST - END OF PERIOD CENSUS (STANDARD) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of all booked, planned and waiting list admissions for a specified date. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| O | 0..1 | DATA GROUP: EAL SERVICE AGREEMENT DETAILS |
| M | 1..1 | DATA GROUP: EAL ENTRY | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: INTENDED PROCEDURES (OPCS) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES (READ) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| O | 0..1 | DATA GROUP: EAL ENTRY REMOVAL | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_030_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_030_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set is used to report to the previous (old) Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of another Commissioner.CDS V6-1 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set is used to report to the previous (old) Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of another Commissioner.
This CDS TYPE should be sent within one month of the end of the period to which it relates unless a shorter time-scale has been agreed with the recipient.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 040 - ELECTIVE ADMISSION LIST END OF PERIOD CENSUS (OLD) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To report to the previous (old) Commissioner that the EAL Entry is now the responsibility of another Commissioner. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: EAL SERVICE AGREEMENT CHANGE DETAILS |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_040_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_040_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set is used to report to a new Commissioner an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.CDS V6-1 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set is used to report to a new Commissioner an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.
This CDS TYPE should be sent within one month of the end of the period to which it relates unless a shorter time-scale has been agreed with the recipient.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 050 - ELECTIVE ADMISSION LIST - END OF PERIOD CENSUS (NEW) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to report to a new Commissioner an EAL Entry that had previously been the responsibility of another Commissioner. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: EAL SERVICE AGREEMENT DETAILS |
| R | 0..1 | DATA GROUP: EAL ENTRY | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: INTENDED PROCEDURES (OPCS) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES (READ) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| O | 0..1 | DATA GROUP: EAL ENTRY REMOVAL | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_050_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_050_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is used to make an initial report that an ELECTIVE ADMISSION LIST ENTRY has been added to the Health Care Provider's ELECTIVE ADMISSION LIST.CDS V6-1 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is used to make an initial report that an ELECTIVE ADMISSION LIST ENTRY has been added to the Health Care Provider's ELECTIVE ADMISSION LIST.
Elective Admission List Event During Period CDS TYPES are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
Note: for Elective Admission List Event During Period CDS TYPES, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 060 - ELECTIVE ADMISSION LIST EVENT DURING PERIOD (ADD) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to make an initial report that the Elective Admission List Entry has been added to the Provider's Elective Admission List. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: EAL SERVICE AGREEMENT DETAILS |
| M | 1..1 | DATA GROUP: EAL ENTRY | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: INTENDED PROCEDURES (OPCS) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES (READ) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_060_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_060_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is used to report that the ELECTIVE ADMISSION LIST ENTRY has been removed from the Health Care Provider's ELECTIVE ADMISSION LIST.CDS V6-1 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is used to report that the ELECTIVE ADMISSION LIST ENTRY has been removed from the Health Care Provider's ELECTIVE ADMISSION LIST.
Elective Admission List Event During Period CDS TYPES are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
Note: for Elective Admission List Event During Period CDS TYPES, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 070 - ELECTIVE ADMISSION LIST EVENT DURING PERIOD (REMOVE) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to report that the EAL entry has been removed from the Provider's Elective Admission List. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: EAL ENTRY REMOVAL |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_070_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_070_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is used to report that an OFFER OF ADMISSION has been made to the PATIENT.CDS V6-1 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is used to report that an OFFER OF ADMISSION has been made to the PATIENT.
Elective Admission List Event During Period CDS TYPES are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
Note: for Elective Admission List Event During Period CDS TYPES, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 080 - ELECTIVE ADMISSION LIST- EVENT DURING PERIOD (OFFER) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to report that an offer of admission has been made to the patient. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: EAL OFFER OF ADMISSION |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_080_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_080_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set is used to report changes in the PATIENT's availability for treatment.CDS V6-1 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set is used to report changes in the PATIENT's availability for treatment.
Elective Admission List Event During Period CDS TYPES are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Note: for Elective Admission List Event During Period CDS TYPES, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 090 - ELECTIVE ADMISSION LIST- EVENT DURING PERIOD (AVAILABLE/UNAVAILABLE ) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to report changes in the patient's availability for treatment. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: EAL PATIENT SUSPENSION |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_090_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_090_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is used to report to the previous Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of a new Commissioner.CDS V6-1 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is used to report to the previous Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of a new Commissioner.
Elective Admission List Event During Period CDS TYPES are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Note: for Elective Admission List Event During Period CDS TYPES, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 100 - ELECTIVE ADMISSION LIST- EVENT DURING PERIOD (OLD SERVICE AGREEMENT)) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to report to the previous (OLD) Commissioner that the EAL Entry is now the responsibility of a new Commissioner. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: EAL SERVICE AGREEMENT |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_100_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_100_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set is used to make an initial report to a new Commissioner of an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.CDS V6-1 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set is used to make an initial report to a new Commissioner of an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.
Elective Admission List Event During Period CDS TYPES are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-1 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Note: for Elective Admission List Event During Period CDS TYPES, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 110 - ELECTIVE ADMISSION LIST- EVENT DURING PERIOD (NEW SERVICE AGREEMENT) COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To be used to make an initial report to a new Commissioner of an EAL entry that had previously been the responsibility of another Commissioner. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| M | 1.1 | DATA GROUP: EAL SERVICE AGREEMENT DETAILS |
| R | 0..1 | DATA GROUP: EAL ENTRY | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: INTENDED PROCEDURES (OPCS) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES (READ) | ||
| O | 0..1 | DATA GROUP: INTENDED PROCEDURES - LOCATION GROUP | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_110_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_110_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set carries the data for a Finished Birth Episode.CDS V6-1 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set carries the data for a Finished Birth Episode.
This is required when a delivery has resulted in a REGISTRABLE BIRTH which has taken place in either an NHS Hospital or in an non-NHS ORGANISATION funded by the NHS.
The information is taken from the birth notification for each baby born.
In addition to Finished Birth Episodes, Unfinished Birth Episode Commissioning Data Set records are required for all Unfinished Birth Episodes as at midnight on 31st March each year.
CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set should be used for the submission of this Unfinished Birth Episode Commissioning Data Set.CDS V6-1 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set should be used for the submission of this Unfinished Birth Episode Commissioning Data Set.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 120 - APC-FINISHED BIRTH EPISODE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished Birth Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DISCHARGE CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: BIRTH EPISODE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| O | 0..97 | DATA GROUP: LOCATION GROUP (AT WARD STAY) | ||
| O | 0..1 | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | ||
| R | 0..1 | DATA GROUP: CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: ADULT CRITICAL CARE PERIOD | ||
| R | 0.1 | DATA GROUP: GP REGISTRATION |
| R | 0.1 | DATA GROUP: REFERRER |
| R | 0.1 | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: ANTENATAL CARE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (RESPONSIBLE CLINICIAN) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE INTENDED) | ||
| R | 0..1 | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON IDENTITY (MOTHER) | ||
| R | 0..1 | DATA GROUP: PERSON CHARACTERISTICS (MOTHER) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE ACTUAL) | ||
| R | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_120_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_120_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set carries the data for a Finished General Episode.CDS V6-1 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set carries the data for a Finished General Episode.
It covers all NHS and private Admitted Patient Care (day case and inpatient) ACTIVITY taking place in any:
- acute, community or mental health NHS Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
An Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes as at midnight on 31 March each year and for all unfinished short-stay informal psychiatric PATIENTS who are resident in hospital or on leave of absence (Home Leave) on 31 March and who have been in hospital for less than 12 months.
CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set should be used for the submission of this Unfinished General Episode Commissioning Data Set.CDS V6-1 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set should be used for the submission of this Unfinished General Episode Commissioning Data Set.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 130 - APC FINISHED GENERAL EPISODE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished General Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DISCHARGE CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: CONSULTANT EPISODE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| R | 0..97 | DATA GROUP: LOCATION GROUP (AT WARD STAY) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | ||
| R | 0..1 | DATA GROUP: CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: ADULT CRITICAL CARE PERIOD | ||
| R | 0.1 | DATA GROUP: GP REGISTRATION |
| R | 0.1 | DATA GROUP: REFERRER |
| R | 0.1 | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY |
| R | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_130_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_130_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set carries the data for a Finished Delivery Episode which is required when a delivery has resulted in a REGISTRABLE BIRTH.CDS V6-1 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set 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.
In addition to Finished Delivery Episodes, Unfinished Delivery Episode Commissioning Data Set records are required for all Unfinished Delivery Episodes as at midnight on 31 March each year.
CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set should be used for the submission of this Unfinished Delivery Episode Commissioning Data Set.CDS V6-1 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set should be used for the submission of this Unfinished Delivery Episode Commissioning Data Set.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 140 - APC-FINISHED DELIVERY EPISODE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished Delivery Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DELIVERY CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DISCHARGE CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: CONSULTANT EPISODE | ||
| M | 1..1 | DATA GROUP: CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| O | 0..97 | DATA GROUP: LOCATION GROUP (AT WARD STAY) | ||
| O | 0..1 | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | ||
| R | 0..1 | DATA GROUP: CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: ADULT CRITICAL CARE PERIOD | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: ANTENATAL CARE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (RESPONSIBLE CLINICIAN) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE INTENDED) | ||
| R | 0..1 | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS |
| R | 0..9 | DATA GROUP: BIRTH OCCURRENCE (one for each Baby in the delivery) | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON IDENTITY (BABY) | ||
| R | 0..1 | DATA GROUP: PERSON CHARACTERISTICS (BABY) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE ACTUAL) | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_140_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_140_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
This CDS TYPE applies to:
- NHS funded home births and
- all other birth events which are not NHS-funded, either directly or under an NHS SERVICE AGREEMENT.
The data in these records originates from birth notification records and requires only a limited data set to be completed.
Maternity events, taking place in either NHS hospitals or in non-NHS ORGANISATIONS funded by the NHS, will be recorded using CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set and CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set.Maternity events, taking place in either NHS hospitals or in non-NHS ORGANISATIONS funded by the NHS, will be recorded using CDS V6-1 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set and CDS V6-1 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 150 - OTHER BIRTH EVENT COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished General Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: ANTENATAL CARE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (RESPONSIBLE CLINICIAN) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - DELIVERY PLACE INTENDED | ||
| M | 1..1 | DATA GROUP: LABOUR/DELIVERY | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON IDENTITY (MOTHER) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - DELIVERY PLACE ACTUAL | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_150_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_150_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set carries the data for an Other Delivery.CDS V6-1 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set carries the data for an Other Delivery.
This CDS TYPE applies to:
- NHS funded home deliveries and
- all other delivery events which are not NHS-funded, either directly or under an NHS SERVICE AGREEMENT.
The data in these records originates from birth notification records and requires only a limited data set to be completed.
Maternity events, taking place in either NHS hospitals or in non-NHS ORGANISATIONS funded by the NHS, will be recorded using CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set and CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set.Maternity events, taking place in either NHS hospitals or in non-NHS ORGANISATIONS funded by the NHS, will be recorded using CDS V6-1 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set and CDS V6-1 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 160 - OTHER DELIVERY EVENT COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished General Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DELIVERY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: ANTENATAL CARE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (RESPONSIBLE CLINICIAN) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - DELIVERY PLACE INTENDED | ||
| M | 1..1 | DATA GROUP: LABOUR/DELIVERY | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..9 | DATA GROUP: BIRTH OCCURRENCE (One for each Baby in the delivery) | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON IDENTITY (BABY) | ||
| R | 0..1 | DATA GROUP: PERSON CHARACTERISTICS (BABY) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - DELIVERY PLACE ACTUAL | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_160_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_160_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set carries the data for the Psychiatric Census.CDS V6-1 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set carries the data for the Psychiatric Census.
The Health and Social Care Information Centre 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.
In the case of NHS 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.
ORGANISATIONS may, by local agreement make submissions of the Psychiatric Census other than at 31st March each year. Care must be taken to ensure that the CDS ACTIVITY DATE chosen is compatible with the Commissioning Data Set Submission Protocol used.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 170 - APC-DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished General Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS (PSYCHIATRIC CENSUS) | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: CONSULTANT EPISODE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (WARD STAY AT PSYCHIATRIC CENSUS DATE) | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_170_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_170_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set carries the data for an Unfinished Birth Episode.CDS V6-1 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set carries the data for an Unfinished Birth Episode.
This is required when a delivery has resulted in a REGISTRABLE BIRTH which has taken place in either an NHS Hospital or in an non-NHS ORGANISATION funded by the NHS.
The information is taken from the birth notification for each baby born.
Unfinished Birth Episode Commissioning Data Set records are required for all Unfinished Birth Episodes as at midnight on 31st March each year.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 180 - APC-UNFINISHED BIRTH EPISODE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of an Unfinished Birth Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DISCHARGE CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: CONSULTANT EPISODE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| O | 0..97 | DATA GROUP: LOCATION GROUP (AT WARD STAY) | ||
| O | 0..1 | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | ||
| R | 0..1 | DATA GROUP: CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: ADULT CRITICAL CARE PERIOD | ||
| R | 0.1 | DATA GROUP: GP REGISTRATION |
| R | 0.1 | DATA GROUP: REFERRER |
| R | 0.1 | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: ANTENATAL CARE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (RESPONSIBLE CLINICIAN) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE INTENDED) | ||
| R | 0..1 | DATA GROUP: LABOUR/DELIVERY | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON IDENTITY (MOTHER) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE ACTUAL) | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_180_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_180_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set carries the data for an Unfinished General Episode.CDS V6-1 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set carries the data for an Unfinished General Episode.
It covers all NHS and private Admitted Patient Care (day case and inpatient) ACTIVITY taking place in any:
- acute, community or mental health NHS Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
An Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes as at midnight on 31 March each year and for all unfinished short-stay informal psychiatric PATIENTS who are resident in hospital or on leave of absence (Home Leave) on 31 March and who have been in hospital for less than 12 months.
CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set may optionally be sent more regularly, usually monthly.CDS V6-1 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set may optionally be sent more regularly, usually monthly.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-1 TYPE 190 - APC UNFINISHED DELIVERY EPISODE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of a Finished Delivery Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DISCHARGE CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: CONSULTANT EPISODE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| O | 0..97 | DATA GROUP: LOCATION GROUP (AT WARD STAY) | ||
| O | 0..1 | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | ||
| R | 0..1 | DATA GROUP: CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: ADULT CRITICAL CARE PERIOD | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY |
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_190_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_190_Overview
- Changed Description
Change to Supporting Information: Changed Name, Description
CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set carries the data for an Unfinished Delivery Episode.CDS V6-1 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set 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.
Unfinished Birth and Delivery Episode Commissioning Data Set records are required for all Unfinished Birth and Delivery Episodes as at midnight on 31 March each year.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried in the CDS V6-1 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW CDS V6-1 TYPE 200 - APC UNFINISHED DELIVERY EPISODE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of an Unfinished Delivery Episode. | |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: CDS TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PERSON GROUP (PATIENT) | ||
| M | 1..1 | DATA GROUP: PATIENT IDENTITY | ||
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DELIVERY CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: HOSPITAL PROVIDER SPELL | ||
| M | 1..1 | DATA GROUP: ADMISSION CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: DISCHARGE CHARACTERISTICS | ||
| M | 1..1 | DATA GROUP: CONSULTANT EPISODE | ||
| M | 1..1 | DATA GROUP: EPISODE CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (CONSULTANT) | ||
| R | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (ICD) | ||
| O | 0..1 | DATA GROUP: CLINICAL DIAGNOSIS GROUP (READ) | ||
| R | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (OPCS) | ||
| O | 0..1 | DATA GROUP: CLINICAL ACTIVITY GROUP (READ) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (AT START OF EPISODE) | ||
| O | 0..97 | DATA GROUP: LOCATION GROUP (AT WARD STAY) | ||
| O | 0..1 | DATA GROUP: LOCATION GROUP (AT END OF EPISODE) | ||
| R | 0..1 | DATA GROUP: CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | ||
| R | 0..9 | DATA GROUP: ADULT CRITICAL CARE PERIOD | ||
| R | 0..1 | DATA GROUP: GP REGISTRATION | ||
| R | 0..1 | DATA GROUP: REFERRER | ||
| R | 0..1 | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: ANTENATAL CARE | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON GROUP (RESPONSIBLE CLINICIAN) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE INTENDED) | ||
| R | 0..1 | DATA GROUP: LABOUR/DELIVERY - ACTIVITY CHARACTERISTICS |
| R | 0..9 | DATA GROUP: BIRTH OCCURRENCE (one for each Baby in the delivery) | ||
| R | 0..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| R | 0..1 | DATA GROUP: PERSON IDENTITY (BABY) | ||
| R | 0..1 | DATA GROUP: PERSON CHARACTERISTICS (BABY) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE ACTUAL) | ||
| R | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP |
| M | 1..* | DATA GROUP: CDS V6-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Name, Description
- Changed Name from Data_Dictionary.Messages.CDS_V6.Overviews.CDS_V6_Type_200_Overview to Data_Dictionary.Messages.CDS_V6-1.Overviews.CDS_V6-1_Type_200_Overview
- Changed Description
Change to Supporting Information: Changed Name
- Changed Name from Web_Site_Content.Navigation.CDS_Version_6_Details_List_Navigation_Menu to Web_Site_Content.Navigation.CDS_Version_6-1_Details_List_Navigation_Menu
Change to Supporting Information: Changed Name, Description
Includes Commissioning Data Set 6-0 and 6-1
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 Name, Description
- Changed Name from Web_Site_Content.CDS_Supporting_Information.CDS_Version_CDS006_Type_List to Web_Site_Content.CDS_Supporting_Information.CDS_Version_6-1_Type_List
- Changed Description
Change to Supporting Information: Changed Description
A Clinic Attendance Midwife is a CARE CONTACT.
A Clinic Attendance Midwife is a Clinic Attendance Non-Consultant.
A Clinic Attendance Midwife is an APPOINTMENT and/or attendance at a Midwife Clinic or an APPOINTMENT and/or contact with a Midwife Clinic.
The total number of attendances or contacts in a period is required for central returns.
Where both mother and baby attend a Postnatal clinic together this is to count as one attendance.
Information recorded for a Clinic Attendance Midwife includes:
Change to Supporting Information: Changed Description
A Clinic Attendance Nurse is a CARE CONTACT.
A Clinic Attendance Nurse is a Clinic Attendance Non-Consultant.
A Clinic Attendance Nurse is an attendance at or contact with a Nurse Clinic.
Note: Local arrangements for apportioning attendances or contacts to the relevant TREATMENT FUNCTION CODE may be made instead of recording this for each attendance.
Information recorded for a Clinic Attendance Nurse includes:
Change to Supporting Information: Changed Description
The NHS Data Model and Dictionary contains current and previous versions of the Commissioning Data Sets. The list below contains the Commissioning Data Sets since 2001.
Current versions
The tables listing the elements in each data set are available in the following type lists.
December 2007:CDS Version CDS006 Type List(incorporates Version CDS 6-1)- November 2008: CDS Version 6-1 Type List
- November 2012: CDS Version 6-2 Type List
Retired versions
- December 2007 to November 2012: CDS Version 6-0
- April 2005 to March 2008: CDS Version NHS005 Type List
- April 2001 to March 2005: CDS Version NHS003 and 4 Type List
The message schema are listed in Commissioning Data Set Message Schema Versions
Change to Supporting Information: Changed Description
A Consultant Episode (Hospital Provider) is an ACTIVITY GROUP.
A Consultant Episode (Hospital Provider) is the time a PATIENT spends in the continuous care of one CONSULTANT using Hospital Site or Care Home bed(s) of one Health Care Provider or, in the case of shared care, in the care of two or more CONSULTANTS. Where care is provided by two or more CONSULTANTS within the same episode, one CONSULTANT will take overriding responsibility for the PATIENT and only one Consultant Episode (Hospital Provider) is recorded. Additional CONSULTANTS participating in the care of PATIENTS are defined as Shared Care Consultants. A Consultant Episode (Hospital Provider) includes those episodes for which a GENERAL MEDICAL PRACTITIONER is acting as a CONSULTANT.
A PATIENT going on Home Leave, or Mental Health Leave Of Absence for 28 days or less, or has a current period of Mental Health Absence Without Leave of 28 days or less, does not interrupt the Consultant Episode (Hospital Provider).
A PATIENT may not have concurrent Consultant Episodes (Hospital Provider) but can have Consultant Out-Patient Episodes overlapping with a Consultant Episode (Hospital Provider). A Consultant Episode (Hospital Provider) must not overlap with a Nursing Episode for the same PATIENT.
Any time spent as a LODGED PATIENT before being admitted to a WARD is included in the first Consultant Episode (Hospital Provider).
A CONSULTANT transfer occurs when the responsibility for a PATIENT transfers from one CONSULTANT (or GENERAL MEDICAL PRACTITIONER acting as a CONSULTANT) to another within a Hospital Provider Spell. In this case one Consultant Episode (Hospital Provider) will end and another one begin.
A transfer of responsibility may occur from a CONSULTANT to the PATIENT's own GENERAL MEDICAL PRACTITIONER (not acting as CONSULTANT) with the PATIENT still in a WARD or Care Home to receive nursing care. In this case the Consultant Episode (Hospital Provider) will end and a Nursing Episode will begin.
A transfer of responsibility from the PATIENT's own GENERAL MEDICAL PRACTITIONER to a CONSULTANT while the PATIENT is in a WARD or Care Home for nursing care will end the Nursing Episode and begin a Consultant Episode (Hospital Provider).
During the Consultant Episode (Hospital Provider) a number of Patient Procedures and PATIENT DIAGNOSES may be recorded.
If this is the first episode under a CONSULTANT in one of the psychiatric specialties within the Hospital Provider Spell, the appropriate PSYCHIATRIC PATIENT STATUS should be recorded.
There may be one or more Mental Health Delayed Discharge Periods recorded during a Consultant Episode (Hospital Provider) under a CONSULTANT in one of the psychiatric specialties (see MAIN SPECIALTY CODE (MENTAL HEALTH).
Information recorded for a Consultant Episode (Hospital Provider) includes:
Change to Supporting Information: Changed Description
The following table is effective from 3rd November 2008 onwards after the relevant section of the Mental Health Act 2007 comes into force, and sets out the relationship between Parts and Sections of the Mental Health Act 1983 (amended by the Crime (Sentences) Act 1997 and the Mental Health Act 2007), and specifies how the codes in CATEGORY OF PATIENT, MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE, STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS and MENTAL HEALTH ACT 2007 MENTAL CATEGORY interrelate.The following table is effective from 3rd November 2008 onwards after the relevant section of the Mental Health Act 2007 comes into force, and sets out the relationship between Parts and Sections of the Mental Health Act 1983 (amended by the Crime (Sentences) Act 1997 and the Mental Health Act 2007), and specifies how the codes in CATEGORY OF PATIENT, MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE, STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS CODE and MENTAL HEALTH ACT 2007 MENTAL CATEGORY interrelate.
The underlying MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE of an Adult Mental Health Care Spell will be carried through a period of Supervised Community Treatment although the MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION will be suspended during that period.
|
|
|
|
|
PART | SECTIONS | MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE | Status of Patient In Psychiatric Census | MENTAL HEALTH ACT 2007 MENTAL CATEGORY |
| Part II | 2 - 34 | 02 - 06 | 1 or 3 | A, B, 9 |
| Part III | 35 - 55 | 07 - 18, 34 | 1 or 3 | A, B, 9 |
| Part IV | 56 - 64 | Not listed, not relevant | ||
| Part V | 65 - 79 | Not listed, not relevant | ||
| Part VI | 80 - 92 | Not listed, not relevant | ||
| Part VII | 93 - 113 | Not listed, not relevant | ||
| Part VIII | 114 - 125 | Not listed, not relevant | ||
| Part IX | 126 - 130 | Not listed, not relevant | ||
| Part X | 131 - 149 | 19 - 20 | 1 or 3 | A, B, 9 |
| Previous legislation (other acts) | 30 - 32 | 1 or 3 | A, B, 9 | |
| Not detained | 01, 35, 36 | 2 | 8 | |
The following table is effective prior to 3rd November 2008 when the relevant section of the Mental Health Act 2007 comes into force, and sets out the relationship between Parts and Sections of the Mental Health Act 1983 (amended by the Crime (Sentences) Act 1997), and specifies how the codes in CATEGORY OF PATIENT, MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE, STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS and MENTAL CATEGORY interrelate.The following table is effective prior to 3rd November 2008 when the relevant section of the Mental Health Act 2007 comes into force, and sets out the relationship between Parts and Sections of the Mental Health Act 1983 (amended by the Crime (Sentences) Act 1997), and specifies how the codes in CATEGORY OF PATIENT, MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE, STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS CODE and MENTAL CATEGORY interrelate.
PART | SECTIONS | MENTAL HEALTH ACT LEGAL STATUS CLASSIFICATION CODE | Status of Patient In Psychiatric Census | MENTAL CATEGORY |
| Part II | 2 - 34 | 02 - 06 | 1 or 3 | 1 - 5, 9 |
| Part III | 35 - 55 | 07 - 18, 34 | 1 or 3 | 1 - 5, 9 |
| Part IV | 56 - 64 | Not listed, not relevant | ||
| Part V | 65 - 79 | Not listed, not relevant | ||
| Part VI | 80 - 92 | Not listed, not relevant | ||
| Part VII | 93 - 113 | Not listed, not relevant | ||
| Part VIII | 114 - 125 | Not listed, not relevant | ||
| Part IX | 126 - 130 | Not listed, not relevant | ||
| Part X | 131 - 149 | 19 - 20 | 1 or 3 | 1 - 5, 9 |
| Previous legislation (other acts) | 30 - 32 | 1 or 3 | 1 - 5, 9 | |
| Not detained/ Supervised Discharge under Section 25 | 01, 33, 35, 36 | 2 | 8 | |
Change to Supporting Information: Changed Description
An Out-Patient Attendance Consultant is a CARE CONTACT.
An Out-Patient Attendance Consultant is an attendance at which a PATIENT is seen by or has contact with (face to face or via telephone/telemedicine) a CONSULTANT, in respect of one referral, that is not a visit to the home of a PATIENT for which a fee is payable under paragraph 140 of the Terms and Conditions of Service.
For an Out-Patient Attendance Consultant, a CONSULTANT includes a member of the CONSULTANT's firm or locum for such a member.
An Out-Patient Attendance Consultant will be part of a Consultant Out-Patient Episode.
If a PATIENT is seen by a CONSULTANT at a Consultant Clinic then this will be a Clinic Attendance Consultant. An attendance may involve more than one PERSON (e.g. a family). The number of attendances to be recorded should be the number of PATIENTS for whom the particular CONSULTANT has identifiable individual records and which will be maintained as a result of the attendance.
A visit to the home of a PATIENT made at the instance of a hospital or specialist to review the urgency of a proposed admission to hospital, or to continue to supervise treatment initiated or prescribed at a hospital or clinic is covered by this definition.
Out-Patient Attendance Consultant also includes a PATIENT being seen by a CONSULTANT from a different MAIN SPECIALTY CODE during a Consultant Episode (Hospital Provider) in circumstances where there is no transfer of responsibility for the care of the PATIENT.
If the PATIENT is currently subject to a Mental Health Care Spell and the CONSULTANT they are in contact with during attendance is their allocated Care Programme Approach care coordinator then a Face To Face Contact CPA Care Coordinator should also be recorded.
During the Out-Patient Attendance Consultant, a number of PATIENT DIAGNOSES and Patient Procedures may be recorded.
A series of Out-Patient Attendance Consultant will form a Consultant Out-Patient Episode, generated from a single referral. Note that it is possible to have two Consultant Out-Patient Episodes with the same CONSULTANT for different clinical conditions, if two referrals are made. An attendance may involve more than one PERSON - for example, a family. Out-Patient Attendance Consultant can take place outside a clinic session, and can take place at the PATIENT's normal place of residence.
A PATIENT attending a WARD for examination or care will be counted as an Out-Patient Attendance Consultant if he/she is seen by a doctor. If they are only seen by a NURSE, they are a Ward Attendance.
An Out-Patient Attendance Consultant should also be recorded where a PATIENT is seen by a CONSULTANT from a different MAIN SPECIALTY CODE during a Consultant Episode (Hospital Provider) where there is no transfer of responsibility for the care of the PATIENT. For example, a PATIENT who is admitted to hospital under a Gastroenterology specialty following an overdose may be seen while still in hospital by a psychiatrist who has been asked to assess their mental condition. The assessment by the psychiatrist should be recorded as an Out-Patient Attendance Consultant.
Information recorded for an Out-Patient Attendance Consultant includes:
Change to Supporting Information: Changed Description
A Ward Attendance is a CARE CONTACT.
A Ward Attendance is an attendance at a WARD by a PATIENT for nursing care, where the PATIENT is not currently admitted to that Health Care Provider. A Ward Attendance should be recorded for only one Nurse or Midwife Contact. If the attendance is primarily for the purpose of examination or treatment by a doctor it is an Out-Patient Attendance Consultant and not a Ward Attendance. The care is for the prevention, cure, relief or investigation because of a disease, injury, health problem or other factor affecting their health status and may include one or more Patient Procedures. This includes:-
| a. | Disease (physical or mental) confirmed or suspected - inclusive of undiagnosed signs or symptoms. | |
| b. | Injury - inclusive of poisoning - confirmed or suspected. | |
| c. | Health problem e.g. prostheses or graft in situ | |
| d. | Other factors influencing the health status of non-sick PERSONS e.g | |
| i. | pregnancy | |
| ii. | sexual and reproductive health (formerly known as family planning) | |
| iii. | potential donor (organ or tissue) | |
| iv. | potential problem requiring prophylactic (preventative) care | |
| v. | bereavement or other problem requiring health professional counselling | |
| vi. | cosmetic surgery | |
| vii. | other | |
The ADMINISTRATIVE CATEGORY of the PATIENT can be recorded for the Ward Attendance.
The PATIENT's FIRST ATTENDANCE whether the first in a series or the only attendance should be recorded.The PATIENT's FIRST ATTENDANCE CODE whether the first in a series or the only attendance should be recorded.
If the PATIENT is currently subject to a Mental Health Care Spell and during attendance is in contact with the NURSE who is their allocated care programme approach care coordinator then a Face To Face Contact CPA Care Coordinator should also be recorded.
Change to Data Element: Changed Name, status to Retired, Description
The PATIENT's ADMINISTRATIVE CATEGORY may change during a spell, for example, the PATIENT may opt to change from NHS to private health care.The category on admission is recorded as ADMINISTRATIVE CATEGORY (ON ADMISSION) and is used to derive the 'Category of Patient' for HES.The Data Element ADMINISTRATIVE CATEGORY (AT START OF EPISODE) has been retired from the NHS Data Model and Dictionary as at 01 November 2012 as the item was not approved for use in the Commissioning Data Sets by the Information Standards Board for Health and Social Care. The XML data element for this item was removed at Commissioning Data Set XML schema version 6-2; although the placeholder remains in Commissioning Data Set XML Schema version 6-1-1, this should not be populated in Commissioning Data Set submissions.
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 Element: Changed Name, status to Retired, Description
- Changed Name from Data_Dictionary.Data_Field_Notes.A.Ad.ADMINISTRATIVE_CATEGORY_(AT_START_OF_EPISODE) to Retired.Data_Dictionary.Data_Field_Notes.A.ADMINISTRATIVE_CATEGORY_(AT_START_OF_EPISODE)
- Retired ADMINISTRATIVE CATEGORY (AT START OF EPISODE)
- Changed Description
Change to Data Element: Changed Name, status to Retired, Description
The last live version of LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE) is available in the September 2012 release of the NHS Data Model and Dictionary.
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 Element: Changed Name, status to Retired, Description
- Changed Name from Data_Dictionary.Data_Field_Notes.L.LEGAL_STATUS_CLASSIFICATION_CODE_(AT_START_OF_EPISODE) to Retired.Data_Dictionary.Data_Field_Notes.L.LEGAL_STATUS_CLASSIFICATION_CODE_(AT_START_OF_EPISODE)
- Retired LEGAL STATUS CLASSIFICATION CODE (AT START OF EPISODE)
- Changed Description
Change to Data Element: Changed Description
| Format/Length: | n1 |
| HES Item: | CENSAT |
| National Codes: | |
| Default Codes: |
Notes:
See Mental Health Act Table for details of how this data item relates to Parts and Sections of the Act.
Permitted National Codes:
| 1 | Detained PATIENT |
| 2 | Long term PATIENT |
| 3 | Detained and long term PATIENT |
STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS will be replaced with STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS CODE, which should be used for all new and developing data sets and for XML messages.
Change to Data Element: Changed Description
| Format/length: | n7 |
| HES item: | CENWARD |
| National Codes: | |
| Default Codes: |
Notes:
Data Set Change Notice07/2000 implemented a change to replace this composite data element within Commissioning Data Set by the constituent components listed below. This description has been retained for information purposes only and this data element should not be used in any current or future message.
This is a composite data item required to be recorded within a Hospital Episode Statistics Psychiatric Census Record: Additional Data Field and is a description of the characteristics of a ward which covers resources available to intended users. It is derived from several constituent components each of which although based upon NHS Data Model and Dictionary attribute classifications, are not the same; for example, Home Leave has been added to each classification list.
The derived value has six constituent component parts, AABCDEF. The value is derived as follows:
| AA | Clinical Care Intensity, see INTENDED CLINICAL CARE INTENSITY CODE |
| B | Age, see INTENDED AGE GROUP |
| C | Sex, see SEX OF PATIENTS CODE |
| D | Hospital provider |
| E | Number of days open only during the day, see WARD DAY PERIOD AVAILABILITY CODE |
| F | Number of days open at night, see WARD NIGHT PERIOD AVAILABILITY CODE |
Thus Home Leave on Psychiatric Census Date would be:
| 7199999 | Home Leave (non-psychiatric) |
| 7299999 | Home Leave (psychiatric) |
Change to Package: Changed Name
- Changed Name from Data_Dictionary.Messages.CDS_V6 to Data_Dictionary.Messages.CDS_V6-1
For enquiries about this Change Request, please email datastandards@nhs.net