NHS Connecting for Health
NHS Data Model and Dictionary Service
| Reference: | Change Request 1069 |
| Version No: | 1.0 |
| Subject: | Commissioning Data Set Pages Redesign in the NHS Data Model and Dictionary |
| Effective Date: | Immediate |
| Reason for Change: | Change to Layout |
| Publication Date: | 24 May 2010 |
Background:
The NHS Data Model and Dictionary Service receive help desk queries relating to issues surrounding the submission of Commissioning Data Sets and the Commissioning Data Set information held in the NHS Data Model and Dictionary. This information is currently held on the Commissioning Data Set table pages, Commissioning Data Set Supporting Information pages and the schema (for codes used in Commissioning Data Sets).
This Information Standards Notice updates the NHS Data Model and Dictionary as follows:
- improves the layout of the Commissioning Data Set tables;
- incorporates elements of other approved data standards into the Commissioning Data Set table pages (i.e. Commissioning Data Set Validation Table, CDS-XML Schema).
This Information Standards Notice does not change the meaning of any item currently within the Commissioning Data Set table pages. It is a change of layout only to make the Commissioning Data Set information clearer for the user.
Summary of changes:
| Date: | 24 May 2010 |
| Sponsor: | Ken Lunn, Director of Data Standards and Products, NHS Connecting for Health |
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: New Data Set
CDS V6 Type 001 - Commissioning Data Set Interchange Header Overview
Click CDS V6 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 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: New Data Set
CDS V6 Type 002 - Commissioning Data Set Interchange Trailer Overview
Click CDS V6 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 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: New Data Set
CDS V6 Type 003 - Commissioning Data Set Message Header Overview
Click CDS V6 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 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: New Data Set
CDS V6 Type 004 - Commissioning Data Set Message Trailer Overview
Click CDS V6 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| Notation | DATA GROUP: CDS V6 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 010 - ACCIDENT AND EMERGENCY COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Accident And Emergency Attendance. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY (From Commissioning Data Set Version 6-1 onwards) | 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 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 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 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 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: New Data Set
CDS V6 Type 020 - Outpatient Commissioning Data Set Overview
Click CDS V6 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 TYPE 020 - OUTPATIENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Outpatient Attendance. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| R | 0..1 | PERSON GENDER CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY (From Commissioning Data Set Version 6-1 onwards) | 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) | 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 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 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 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 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: New Data Set
CDS V6 Type 021- Future Outpatient Commissioning Data Set Overview
Click CDS V6 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 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| R | 0..1 | PERSON GENDER CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY (From Commissioning Data Set Version 6-1 onwards) | 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) | 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS TYPE V6 120 - FINISHED BIRTH EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished Birth Episode. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 | ||
| 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - PERSON CHARACTERISTICS - MOTHER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby's Mother (Commissioning Data Set Version 6-0 only) |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) (Commissioning Data Set Version 6-0 only) | 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 130 - FINISHED GENERAL EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished General Episode. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 | ||
| 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 140 - FINISHED DELIVERY EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished Delivery Episode. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 | ||
| 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | F S3 S12 | ||||||||
| 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 BIRTH DATE (BABY) (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||||||||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||||||||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||||||||
| R | 0..1 | BIRTH WEIGHT | F | ||||||||
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL: 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 150 - OTHER BIRTH EVENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details for an Other Birth. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | F S3 S12 | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - MOTHER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby's Mother (Commissioning Data Set Version 6-0 only) |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) (Commissioning Data Set Version 6-0 only) | 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 160 - OTHER DELIVERY EVENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details for an Other Delivery. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | F S3 S12 | ||||||||
| 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 BIRTH DATE (BABY) (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||||||||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||||||||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||||||||
| R | 0..1 | BIRTH WEIGHT | F | ||||||||
| R | 0..1 | DATA GROUP: DELIVERY OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL: To carry the details of the Actual 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 TYPE (ACTUAL) | V | ||||||||
| Notation | DATA GROUP: CDS V6 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 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 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 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: New Data Set
Click CDS V6 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 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 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 180 - UNFINISHED BIRTH EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished Birth Episode. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 | ||
| 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - PERSON CHARACTERISTICS - MOTHER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby's Mother (Commissioning Data Set Version 6-0 only) |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) (Commissioning Data Set Version 6-0 only) | 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 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 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 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 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: New Data Set
CDS V6 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.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
| CDS V6 TYPE 190 - UNFINISHED GENERAL EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished General Episode. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 | ||
| 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 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 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 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 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: New Data Set
Click CDS V6 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 TYPE 200 - UNFINISHED DELIVERY EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished Delivery Episode. |
| Notation | DATA GROUP: CDS V6 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 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 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 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 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 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 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 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 (From Commissioning Data Set Version 6-1 onwards) | 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 (From Commissioning Data Set Version 6-1 onwards) | 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 BIRTH DATE (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||
| 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 | ||
| 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | 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) (From Commissioning Data Set Version 6-1 onwards) | F S3 S12 | ||||||||
| 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 BIRTH DATE (BABY) (Commissioning Data Set Version 6-0 only) | F S3 S12 | ||||||||
| R | 0..1 | PERSON GENDER CURRENT (BABY) | V | ||||||||
| R | 0..1 | LIVE OR STILL BIRTH | V | ||||||||
| R | 0..1 | BIRTH WEIGHT | F | ||||||||
| R | 0..1 | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL: 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 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 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 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 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: New Supporting Information
The Commissioning Data Sets have notation to identify the business and/or processing rules which apply to individual Data Elements. This notation appears in the Rules column of the Commissioning Data Set details page.
Population Validation
All Data Elements are subject to length validation. Some Data Elements are also subject to format and content validation against a list of permitted values defined in the NHS Data Model and Dictionary. The value lists are held on the Attribute which the Data Element is based on, plus default codes which are held on the Data Element itself.
| RULE | POPULATION VALIDATION |
| F | The format is validated, for example the format of a DATE must comply with the XML standard. |
| V | The Data Element is validated against an explicit list of permitted values as defined in the NHS Data Model and Dictionary. |
Business Rules
Some Data Elements are subject to additional Business Rules as indicated below:
- Prefix I = CDS-XML Schema anomalies and issues.
- Prefix N = NHS Data Standards and Policy Rules
| PREFIX | BUSINESS RULES: H - Healthcare Resource Group Business Rules |
| H4 | This Data Element is used by the Secondary Uses Service to derive the Healthcare Resource Group 4. Failure to correctly populate this data element is likely to result in an incorrect Healthcare Resource Group, usually associated with lower levels of healthcare resource. |
| PREFIX | BUSINESS RULES: I - CDS-XML Schema Anomalies and Issues |
| I1 | This is a known schema anomaly and has been registered for future resolution. |
| I2 | See the specifications in the NHS Data Model and Dictionary for the specific format characteristics of this Data Element. |
| I3 | There is no national requirement to flow Healthcare Resource Group 4 (HRG4) through the Commissioning Data Sets, see DSCN 17/2008. |
| PREFIX | BUSINESS RULES: N - NHS Data Standards and Policy Rules |
| N1 | Psychiatric PATIENTS only. |
| N2 | Not defined or approved by the Information Standards Board for Health and Social Care. |
| N3 | The definition and value list for this data is under review. |
| N4 | Up to 20 codes per daily activity occurrence may be recorded. |
| N5 | This data should only flow in Commissioning Data Set versions 6-0 and 6-1 for PATIENTS detained under the Mental Health Act prior to the Mental Health Act 2007. |
| N6 | This data should only flow in Commissioning Data Set version 6-1 for PATIENTS detained under the Mental Health Act 2007. |
| N7 | From Commissioning Data Set version 6-0 onwards, the use of the DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE in the location group is optional as it must be carried in the Episode Characteristics. |
| PREFIX | BUSINESS RULES: S - Secondary Uses Service Business Rules |
| S1 | This mandatory Commissioning Data Set date is used as the originating date to determine the mandatory CDS ACTIVITY DATE. |
| S2 | The Secondary Uses Service DOES NOT support the use of the CDS TEST INDICATOR. Therefore this Data Element must not be used. |
| S3 | See Security Issues and Patient Confidentiality, for further information. |
| S4 | Used to ensure the correct sequencing of multiple and/or subsequent Commissioning Data Set submissions. |
| S5 | These ORGANISATION CODES must be present and registered with the Secondary Uses Service. The Commissioning Data Set Schema does not validate the content value of this data. |
| S6 | All CDS REPORT PERIOD START DATES and CDS REPORT PERIOD END DATES must be consistent in all Commissioning Data Set records contained in a BULK Interchange submission. The CDS REPORT PERIOD START DATE must be on or before the CDS REPORT PERIOD END DATE. The CDS ACTIVITY DATE is a mandatory data element and must fall within the period defined. See the Commissioning Data Set Submission Protocol. |
| S7 | See the Commissioning Data Set Addressing Grid. |
| S8 | These Data Elements are required for correct processing by the Secondary Uses Service. If omitted, the Secondary Uses Service will reject the Commissioning Data Set data. |
| S9 | The CDS UNIQUE IDENTIFIER is a mandatory data item when using the Net Change Protocol. When using the Bulk Update Protocol this data item is optional but it is strongly advised that where it can be correctly generated and maintained it should be used. See the Commissioning Data Set Submission Protocol. |
| S10 | For CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set, the CDS ACTIVITY DATE contains the CDS CENSUS DATE which is also the DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE. |
| S11 | For the following CDS TYPES, the CDS ACTIVITY DATE must contain the DATE OF ELECTIVE ADMISSION LIST CENSUS which is usually the end of the Period being reported: CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set CDS V6 Type 040 - Elective Admission List - End Of Period Census (Old) Commissioning Data Set CDS V6 Type 050 - Elective Admission List - End Of Period Census (New) Commissioning Data Set |
| S12 | These PERSON BIRTH DATE Data Elements must use DATES between 01/01/1880 and 31/12/2999 in order to pass validation |
| S13 | Data Elements reporting a DATE (which is not a PERSON BIRTH DATE Data Element) must use dates between 01/01/1900 and 31/12/2999 in order to pass validation |
| S14 | For Data Elements reporting a TIME, the hour portion must be between 00 and 23 inclusive in order to pass validation |
Change to Supporting Information: New Supporting Information
The Commissioning Data Set is the basic structure used for the submission of commissioning data to the Secondary Uses Service and is designed to be capable of individually conveying many different Commissioning Data Set structures, encompassing Accident and Emergency Attendances, Out-Patient Attendances, Admitted Patient Care and Elective Admission List.
Commissioning Data Set Messages have been defined in specific components known as a CDS TYPE.
Specific notation is used to indicate the requirements of the CDS-XML Message Schema Design conditions for submission of data in the Commissioning Data Sets.
The structure of the Commissioning Data Set message is shown by the use of Data Groups and Sub Groups within those Data Groups. For each Data Group, Sub Group and individual Data Element, the allowed cardinality at each level is also shown in the "Status" and "Repeats" columns.
The CDS TYPE specifications must therefore be read in this hierarchy, using the Status and Repeat conditions within the Data Groups and Sub Groups, to determine the requirements for the individual Data Elements.
Status Column Notation
The Notation used for the "STATUS" column is as follows:
| STATUS | MEANING | DESCRIPTION |
| M | MANDATORY | This signifies that the collection and submission of this Commissioning Data Set data is deemed MANDATORY and its presence is necessary for the CDS TYPE to be correctly validated and accepted for processing by the Secondary Uses Service. If a data item is shown as MANDATORY, this should also be regarded as REQUIRED by the Department of Health. In most instances, data marked as MANDATORY in a Sub Group will result in its parent Data Group also being marked as mandatory, but this is not always the case. For instance, although the Consultant Episode - Clinical Diagnosis Group (ICD) is marked as R=REQUIRED (and therefore need not actually be populated), if it is used then both the DIAGNOSIS SCHEME IN USE and the PRIMARY DIAGNOSIS (ICD) are marked as M=MANDATORY and must both be present. |
| R | REQUIRED | This signifies that the collection and submission of this Commissioning Data Set data is deemed REQUIRED by the Department of Health to comply with authorised NHS Standards, Policies and Directives. Therefore whenever a Commissioning Data Set is collected and subsequently submitted to the Secondary Uses Service, this data must be supported and populated into the relevant data sets if the data is available. Note that "temporal" conditions may mean that there are instances where this directive cannot be fulfilled. For instance in a CDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDS, ICD and OPCS data elements are marked as "Required" indicating that this data should be included. However, if at the time of submission to the Secondary Uses Service this data remains incomplete (perhaps awaiting coding in the ORGANISATION), the remaining data in the CDS record should still be submitted. Once the ORGANISATION has updated its systems with the data, the CDS TYPE relating to that ACTIVITY should then be resubmitted to the Secondary Uses Service. |
| O | OPTIONAL | This signifies that the collection and submission of this Commissioning Data Set data is OPTIONAL. Its inclusion in the Commissioning Data Set is therefore determined by "local agreement" between the ORGANISATIONS exchanging the data. Note that even if marked O=OPTIONAL, any data included in a Commissioning Data Set submission to the Secondary Uses Service must comply with its specification published in the NHS Data Model and Dictionary otherwise the data may be deemed invalid and rejected. |
| X | X | This is used where the Data Element has been included in the Commissioning Data Set design, usually for pilot use, but is not yet authorised for transmission by the wider NHS. The Data Element will be in italics and not linked to the Data Element where one exists. |
Repeats Column Notation
The Notation used for the "REPEATS" column is as follows:
| REPEATS | DESCRIPTION | |
| 0..1 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to a maximum of 1. | |
| 0..9 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to a maximum of 9. | |
| 0..* | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to an unlimited maximum. | |
| 1..1 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to a maximum of 1. | |
| 1..97 | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to a maximum of 97. | |
| 1..* | This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to an unlimited maximum. | |
Rules Column Notation
An entry in the "Rules" column shows that a specific Rule applies to submission of an individual Data Element. These meaning of these Rules can be found in Commissioning Data Set Business Rules.
Notation Examples
The following are examples of some common scenarios.
| EXAMPLE 1: A MANDATORY Data Group with differing Sub-Groups and component data status conditions. |
The following example shows a MANDATORY Data Group - therefore the Data Group must be present for the CDS TYPE to be validated and accepted for processing by the Secondary Uses Service. When a Data Group is used:
The following data structure is one of three options when completing the Patient Identity Data Group: |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR Code Value = 01 = Verified | Rules | |||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | |||
| M | 1..1 | LOCAL PATIENT IDENTIFIER | F | ||
| M | 1..1 | ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER | F | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | S3 | ||
| M | 1..1 | ORGANISATION CODE (PCT OF RESIDENCE) | F | ||
| R | 0..1 | PERSON BIRTH DATE (Introduced in Commissioning Data Set V6-1) | F S3 | ||
EXPLANATION: The parent Data Group has a "Status" of M=MANDATORY which indicates that this Data Group must be present in the Commissioning Data Set to ensure correct validation and acceptance when submitted to the Secondary Uses Service. The parent Data Group "Repeats" = 1..1 indicates that only one occurrence of this Data Group must flow in this particular Commissioning Data Set record. |
| EXAMPLE 2: A REQUIRED Data Group with differing component data status conditions. |
The following example shows a REQUIRED Data Group. This data must be present in the relevant Commissioning Data Set if available. However, if submitted to the Secondary Uses Service, omission of this REQUIRED Data Group will not cause rejection. When the Data Group is used:
|
| Notation | DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (ICD) | ||||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the ICD coded Clinical Diagnoses. | |||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | PROCEDURE SCHEME IN USE | V | ||
| M | 1..1 | DATA GROUP: PRIMARY DIAGNOSIS | Rules | ||
| M | 1..1 | PRIMARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSIS | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
EXPLANATION: The Data Group "Status" = R = Required indicates that this Data Group must be populated in the relevant Commissioning Data Set if the data is available. The Data Group "Repeats" = 0..1 indicates that population of this Data Group is not necessary to enable the Commissioning Data Set to be sent to the Secondary Uses Service. If it is sent, then only one occurrence of this Data Group may flow in this particular Commissioning Data Set record. |
Change to Supporting Information: New Supporting Information
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.
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
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TYPESCDS V6 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS TYPES
Followed by:
Each Commissioning Data Set message ends with:
- CDS V6 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
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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: New Supporting Information
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.
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 Interchange
- CDS V6 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:
Each Commissioning Data Set message ends with:
- CDS V6 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
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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: New Supporting Information
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.
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 Interchange
- CDS V6 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:
Each Commissioning Data Set message ends with:
- CDS V6 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
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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: New Supporting Information
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.
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 Interchange
- CDS V6 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:
Each Commissioning Data Set message ends with:
- CDS V6 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
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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: New Supporting Information
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.
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 Interchange
- CDS V6 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:
Each Commissioning Data Set message ends with:
- CDS V6 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
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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: New Supporting Information
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.
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 Interchange
- CDS V6 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:
Each Commissioning Data Set message ends with:
- CDS V6 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
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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: New Supporting Information
CDS V6 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
The CDS V6 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 18 Weeks Target, 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.
Note: CDS V6 Type 020 - Outpatient Commissioning Data Set is called Care Activity in the Commissioning Data Set XML Message Schema.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
The CDS V6 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.
Note: CDS V6 Type 021 - Future Outpatient Commissioning Data Set is called Future Care Activity in the Commissioning Data Set XML Message Schema.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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. 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 18 Weeks Target, 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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 18 Weeks Target, 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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 18 Weeks Target, 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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 18 Weeks Target, 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
CDS V6 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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
CDS V6 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 18 Weeks Target, 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 CDS 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: Details is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
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.
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.
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 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 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
CDS V6 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set carries the data for an Other Birth.
This CDS TYPE applies to:
This CDS TYPE applies to:
- NHS funded home births and
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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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: PERSON CHARACTERISTICS (MOTHER) (Commissioning Data Set Version 6-0 only) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - DELIVERY PLACE ACTUAL | ||
| M | 1..* | DATA GROUP: CDS V6 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 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: New Supporting Information
CDS V6 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.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set carries the data for the Psychiatric Census.
The NHS Information Centre for health and social care require a record for every PATIENT admitted as at 31 March each year for which the PATIENT is detained or the Episode is part of a Hospital Provider Spell which has lasted longer then one year and for which the majority of time has been spent under the care of a CONSULTANT in one of the psychiatric specialties.
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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
CDS V6 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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: PERSON CHARACTERISTICS (MOTHER) (Commissioning Data Set Version 6-0 only) | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE ACTUAL) | ||
| O | 0..1 | DATA GROUP: HEALTHCARE RESOURCE GROUP | ||
| M | 1..* | DATA GROUP: CDS V6 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 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: New Supporting Information
CDS V6 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 18 Weeks Target, 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.
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 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 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
CDS V6 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.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW CDS V6 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 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 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 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6 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 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 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: New Supporting Information
Commissioning Data Set Business Rules
Commissioning Data Set Notation
CDS DATA FLOW CONTROLS - (Mandatory for every CDS Interchange):
CDS V6 Type 001 - CDS Interchange Header: Details
CDS V6 Type 002 - CDS Interchange Trailer: Details
CDS V6 Type 003 - CDS Message Header: Details
CDS V6 Type 004 - CDS Message Trailer: Details
CDS Transaction Header Group -(Mandatory for every CDS TYPE):
CDS V6 Type 005B - CDS Transaction Header Group - Bulk Update Protocol: Details or
CDS V6 Type 005N - CDS Transaction Header Group - Net Change Protocol: Details
CDS TYPES:
Accident and Emergency CDS Type:
CDS V6 Type 010 - Accident and Emergency CDS: Details
Care Activity CDS Types:
CDS V6 Type 020 - Outpatient CDS: Details
CDS V6 Type 021 - Future Outpatient CDS: Details
Admitted Patient Care CDS Types:
CDS V6 Type 120 - Admitted Patient Care - Finished Birth Episode CDS: Details
CDS V6 Type 130 - Admitted Patient Care - Finished General Episode CDS: Details
CDS V6 Type 140 - Admitted Patient Care - Finished Delivery Episode CDS: Details
CDS V6 Type 150 - Admitted Patient Care - Other Birth Event CDS: Details
CDS V6 Type 160 - Admitted Patient Care - Other Delivery Event CDS: Details
CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census CDS: Details
CDS V6 Type 180 - Admitted Patient Care - Unfinished Birth Episode CDS: Details
CDS V6 Type 190 - Admitted Patient Care - Unfinished General Episode CDS: Details
CDS V6 Type 200 - Admitted Patient Care - Unfinished Delivery Episode CDS: Details
Elective Admission List CDS Types - End Of Period Census Types:
CDS V6 Type 030 - Elective Admission List - End of Period Census (Standard) CDS: Details
CDS V6 Type 040 - Elective Admission List - End Of Period Census (Old) CDS: Details
CDS V6 Type 050 - Elective Admission List - End Of Period Census (New) CDS: Details
Elective Admission List CDS Types - Event During Period Types:
CDS V6 Type 060 - Elective Admission List - Event During Period (Add) CDS: Details
CDS V6 Type 070 - Elective Admission List - Event During Period (Remove) CDS: Details
CDS V6 Type 080 - Elective Admission List - Event During Period (Offer) CDS: Details
CDS V6 Type 090 - Elective Admission List - Event During Period (Available / Unavailable) CDS: Details
CDS V6 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) CDS: Details
CDS V6 Type 110 - Elective Admission List - Event During Period (New Service Agreement) CDS: Details
Change to Supporting Information: Changed Description
COMMISSIONING DATA SET VERSION CDS006 TYPE LIST
Includes Commissioning Data Set versions 6-0 and 6-1Includes Commissioning Data Set 6-0 and 6-1
Accident and Emergency Commissioning Data Set Type:CDS V6 TYPE 010 - ACCIDENT AND EMERGENCY CDSCare Activity Commissioning Data Set Types:CDS V6 TYPE 020 - OUTPATIENT CDS (Known as Care Activity Commissioning Data Set in the Schema)CDS V6 TYPE 021 - FUTURE OUTPATIENT CDS (Known as Future Care Activity Commissioning Data Set in the Schema)
Admitted Patient Care Commissioning Data Set Types:CDS V6 TYPE 120 - ADMITTED PATIENT CARE - FINISHED BIRTH EPISODE CDSCDS V6 TYPE 130 - ADMITTED PATIENT CARE - FINISHED GENERAL EPISODE CDSCDS V6 TYPE 140 - ADMITTED PATIENT CARE - FINISHED DELIVERY EPISODE CDSCDS V6 TYPE 150 - ADMITTED PATIENT CARE - OTHER BIRTH EVENT CDSCDS V6 TYPE 160 - ADMITTED PATIENT CARE - OTHER DELIVERY EVENT CDSCDS V6 TYPE 170 - ADMITTED PATIENT CARE - DETAINED AND/OR LONG TERM PSYCHIATRIC CENSUS CDSCDS V6 TYPE 180 - ADMITTED PATIENT CARE - UNFINISHED BIRTH EPISODE CDSCDS V6 TYPE 190 - ADMITTED PATIENT CARE - UNFINISHED GENERAL EPISODE CDSCDS V6 TYPE 200 - ADMITTED PATIENT CARE - UNFINISHED DELIVERY EPISODE CDS
Elective Admission List Commissioning Data Set Types - End Of Period Census Types:CDS V6 TYPE 030 - EAL - END OF PERIOD CENSUS STANDARD CDSCDS V6 TYPE 040 - EAL - END OF PERIOD CENSUS OLD CDSCDS V6 TYPE 050 - EAL - END OF PERIOD CENSUS NEW CDSElective Admission List Commissioning Data Set Types - Event During Period Types:CDS V6 TYPE 060 - EAL - EVENT DURING PERIOD - ADD CDSCDS V6 TYPE 070 - EAL - EVENT DURING PERIOD - REMOVE CDSCDS V6 TYPE 080 - EAL - EVENT DURING PERIOD - OFFER CDSCDS V6 TYPE 090 - EAL - EVENT DURING PERIOD - AVAILABLE / UNAVAILABLE CDSCDS V6 TYPE 100 - EAL - EVENT DURING PERIOD - OLD SERVICE AGREEMENT CDSCDS V6 TYPE 110 - EAL - EVENT DURING PERIOD - NEW SERVICE AGREEMENT CDS
Commissioning Data Set Interchange and Message Controls - Mandatory for every Interchange:CDS V6 TYPE 001 - CDS INTERCHANGE HEADERCDS V6 TYPE 002 - CDS INTERCHANGE TRAILERCDS V6 TYPE 003 - CDS MESSAGE HEADERCDS V6 TYPE 004 - CDS MESSAGE TRAILER
Commissioning Data Set Transaction Header Group - Mandatory for every Commissioning Data Set:CDS V6 TYPE 005B - CDS TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOLorCDS V6 TYPE 005N - CDS TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL
Change to Supporting Information: Changed Description
Information on care provided for all PATIENTS by NHS Hospital Providers, Primary Care Trusts and Independent Sector Providers (for NHS PATIENTS only) is specified in the Commissioning Data Sets and must be submitted to the Secondary Uses Service according to issued guidelines.
Use the following links to access more detailed information.
The Commissioning Data Sets
- Commissioning Data Set Overview
- Commissioning Data Set Versions
- Commissioning Data Set Notation
- Commissioning Data Set Business Rules
- Commissioning Data Set Mandated Data Flows
- Commissioning Data Set Submission Protocol
- Commissioning Data Set Addressing Grid
- Commissioning Data Set Validation Table
- Security Issues and Patient Confidentiality
- Commissioning Data Set Submission and Primary Care Trust Mergers
- Commissioning Data Set Data Duplication
- Hospital Episode Statistics
- Hospital Episode Statistics Cross Reference Tables
The CDS-XML Message
Change to Supporting Information: Changed Description
- Commissioning Data Set Overview
- Commissioning Data Set Versions
- CDS Notation
- CDS Business Rules
- CDS Mandated Data Flows
- CDS Submission Protocol
- CDS Addressing Grid
- Commissioning Data Set Validation Table
- Security Issues and Patient Confidentiality
- CDS Submission and PCT Mergers
- CDS Data Duplication
- Hospital Episode Statistics
- Hospital Episode Statistics Cross Reference Tables
- Referral To Treatment Clock Stop Administrative Event
The CDS-XML Message
For enquiries about this Information Standards Notice, please email datastandards@nhs.net