| Type: | Patch |
| Reference: | 1792 |
| Version No: | 1.0 |
| Subject: | Commissioning Data Set Overviews Update |
| Effective Date: | Immediate |
| Reason for Change: | Patch |
| Publication Date: | 7 September 2020 |
Background:
Versions of the Data Dictionary from 3+ onwards will not have 3 frames for data sets. The current information on the overview page will display at the top of each data set.
To ensure the new data set page contains the correct mandation, XML Schema download and constraints information, the information will be added to the overview page.
This patch:- Ensures that each overview page has an "Introduction" heading
- Adds the mandation, XML Schema download and constraints information to the end of each overview page
- Removes the information from the top of each data set.
Note: the remaining Data Sets will be updated in CR1789.
To view a demonstration on "How to Read an NHS Data Model and Dictionary Change Request", visit the NHS Data Model and Dictionary help pages at: https://www.datadictionary.nhs.uk/Flash_Files/changerequest.htm.
Note: if the web page does not open, please copy the link and paste into the web browser.
Summary of changes:
| Date: | 7 September 2020 |
| Sponsor: | Nicholas Oughtibridge, Head of Clinical Data Architecture, NHS Digital |
Note: New text is shown with a blue background. Deleted text is crossed out. Retired text is shown in grey. Within the Diagrams deleted classes and relationships are red, changed items are blue and new items are green.
Click here for a printer friendly view of this page.
Change to Data Set: Changed Description
CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header Overview
For a "Full Screen" view, click CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE SENDER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE RECEIVER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE DATE OF PREPARATION | F S8 S13 | ||
| M | 1..1 | CDS INTERCHANGE TIME OF PREPARATION | F S8 S14 | ||
| M | 1..1 | CDS INTERCHANGE APPLICATION REFERENCE | F S8 | ||
| O | 0..1 | CDS INTERCHANGE TEST INDICATOR | F | ||
Change to Data Set: Changed Description
CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer Overview
For a "Full Screen" view, click CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL COUNT | F S8 | ||
| O | 0..1 | CDS INTERCHANGE SENDER IDENTITY | F | ||
| O | 0..1 | CDS INTERCHANGE RECEIVER IDENTITY | F | ||
Change to Data Set: Changed Description
CDS V6-2-1 Type 003 - Commissioning Data Set Message Header Overview
For a "Full Screen" view, click CDS V6-2-1 Type 003 - CDS Message Header.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity controls for each Commissioning Data Set Message. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS MESSAGE TYPE | V | ||
| M | 1..1 | CDS MESSAGE VERSION NUMBER | F | ||
| M | 1..1 | CDS MESSAGE REFERENCE | F | ||
| O | 0..1 | CDS RECORD IDENTIFIER | F | ||
Change to Data Set: Changed Description
CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer Overview
For a "Full Screen" view, click CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity controls for each Commissioning Data Set Message. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS MESSAGE REFERENCE | F | ||
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory Commissioning Data Set Submission Protocol controls for when using the Bulk Update mechanism. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS TYPE CODE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER CODE | V | ||
| O | 0..1 | CDS UNIQUE IDENTIFIER | F S9 | ||
| M | 1..1 | CDS BULK REPLACEMENT GROUP CODE | 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 | ||
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2-1 Type 005N - CDS Transaction Header Group - Net Change Protocol.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory Commissioning Data Set Submission Protocol controls for when using the Net Change mechanism. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS TYPE CODE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER CODE | 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 S15 | ||
| O | 1..7 | CDS COPY RECIPIENT IDENTITY | F S5 S7 | ||
Change to Data Set: Changed Description
CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
| CDS V6-2-1 TYPE 011 - EMERGENCY CARE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Emergency Care Attendance. |
| Notation | DATA GROUP: CDS V6-2-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| Notation | DATA GROUP: CDS V6-2 -1 TYPE 003 - COMMISSIONING DATA SET MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| ONE OF THE FOLLOWING TWO OPTIONS MUST BE USED |
| Notation | DATA GROUP: CDS V6-2-1 TYPE 005B - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| OR |
| Notation | DATA GROUP: CDS V6-2-1 TYPE 005N - COMMISSIONING DATA SET TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | |
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of the Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| Notation | DATA GROUP: PATIENT PATHWAY | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Patient Pathway. | |
| M | 1..1 | DATA GROUP: PATIENT PATHWAY IDENTITY | Rules | |||
| M Or M | 1..1 1..1 | UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or PATIENT PATHWAY IDENTIFIER | F F I2 | |||
| M | 1..1 | ORGANISATION IDENTIFIER (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION IDENTIFIER (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (EXTENDED) | F S3 | ||
| M | 1..1 | ORGANISATION IDENTIFIER (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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION IDENTIFIER (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (EXTENDED) | F S3 | ||
| M | 1..1 | ORGANISATION IDENTIFIER (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | 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 IDENTIFIER (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (EMERGENCY CARE) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient for an Emergency Care Attendance. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON STATED GENDER CODE | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | ACCOMMODATION STATUS (SNOMED CT) | F | ||
| R | 0..1 | PREFERRED SPOKEN LANGUAGE (SNOMED CT) | F | ||
| R | 0..1 | ACCESSIBLE INFORMATION PROFESSIONAL REQUIRED CODE (SNOMED CT) | F | ||
| R | 0..1 | INTERPRETER LANGUAGE (SNOMED CT) | F | ||
| R | 0..1 | OVERSEAS VISITOR CHARGING CATEGORY AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: MENTAL HEALTH ACT LEGAL STATUS | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the patients Mental Health Act Legal Status. | |
| 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 | 0..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: EMERGENCY CARE ATTENDANCE LOCATION | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Emergency Care Attendance location. | |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | ORGANISATION SITE IDENTIFIER (OF TREATMENT) | F | ||
| M | 1..1 | EMERGENCY CARE DEPARTMENT TYPE | F | ||
| Notation | DATA GROUP: AMBULANCE DETAILS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry ambulance details relating to the patients arrival at Emergency Care. |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | AMBULANCE INCIDENT NUMBER | F | ||
| R | 0..1 | ORGANISATION IDENTIFIER (CONVEYING AMBULANCE TRUST) | F | ||
| Notation | DATA GROUP: EMERGENCY CARE ATTENDANCE ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Emergency Care Attendance. | |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE ATTENDANCE IDENTIFIER | F | ||
| R | 0..1 | EMERGENCY CARE ARRIVAL MODE (SNOMED CT) | F | ||
| R | 0..1 | EMERGENCY CARE ATTENDANCE CATEGORY | V | ||
| R | 0..1 | EMERGENCY CARE ATTENDANCE SOURCE (SNOMED CT) | F | ||
| R | 0..1 | ORGANISATION SITE IDENTIFIER (EMERGENCY CARE ATTENDANCE SOURCE) | F | ||
| M | 1..1 | EMERGENCY CARE ARRIVAL DATE | F S1 S13 | ||
| M | 1..1 | EMERGENCY CARE ARRIVAL TIME | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F S8 | ||
| R | 0..1 | EMERGENCY CARE INITIAL ASSESSMENT DATE | F S13 | ||
| R | 0..1 | EMERGENCY CARE INITIAL ASSESSMENT TIME | F S14 | ||
| R | 0..1 | EMERGENCY CARE ACUITY (SNOMED CT) | F | ||
| R | 0..1 | EMERGENCY CARE CHIEF COMPLAINT (SNOMED CT) | F | ||
| R | 0..1 | EMERGENCY CARE DATE SEEN FOR TREATMENT | F S13 | ||
| R | 0..1 | EMERGENCY CARE TIME SEEN FOR TREATMENT | F S14 | ||
| Notation | DATA GROUP: INJURY CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of injuries. | |
| Notation | DATA GROUP: PATIENT CLINICAL HISTORY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry patient clinical history details. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..* | COMORBIDITY (SNOMED CT) | F | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| O | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| M | 1..1 | ORGANISATION IDENTIFIER (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION IDENTIFIER (CODE OF COMMISSIONER) | F | ||
| Notation | DATA GROUP: CARE PROFESSIONALS (EMERGENCY CARE) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of the Care Professionals active during the Emergency Care Attendance. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER | F | ||
| M | 1..1 | CARE PROFESSIONAL TIER (EMERGENCY CARE) | V | ||
| M | 1..1 | CARE PROFESSIONAL DISCHARGE RESPONSIBILITY INDICATOR (EMERGENCY CARE) | V | ||
| Notation | DATA GROUP: EMERGENCY CARE DIAGNOSES (SNOMED CT) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of SNOMED CT coded Clinical Diagnoses. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE DIAGNOSIS (SNOMED CT) | F H4 | ||
| M | 1..1 | CODED CLINICAL ENTRY SEQUENCE NUMBER | F | ||
| M | 1..1 | EMERGENCY CARE DIAGNOSIS QUALIFIER (SNOMED CT) | F | ||
| Notation | DATA GROUP: EMERGENCY CARE INVESTIGATIONS (SNOMED CT) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of SNOMED CT coded Clinical Investigations. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE CLINICAL INVESTIGATION (SNOMED CT) | F H4 | ||
| R | 0..1 | PROCEDURE DATE (EMERGENCY CARE CLINICAL INVESTIGATION) | F S13 | ||
| R | 0..1 | PROCEDURE TIME (EMERGENCY CARE CLINICAL INVESTIGATION) | F S14 | ||
| Notation | DATA GROUP: EMERGENCY CARE TREATMENTS (SNOMED CT) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of SNOMED CT coded Procedures. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE PROCEDURE (SNOMED CT) | F H4 | ||
| R | 0..1 | PROCEDURE DATE (EMERGENCY CARE PROCEDURE) | F S13 | ||
| R | 0..1 | PROCEDURE TIME (EMERGENCY CARE PROCEDURE) | F S14 | ||
| Notation | DATA GROUP: REFERRALS TO OTHER SERVICES | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of referrals to other services. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRED TO SERVICE (SNOMED CT) | F | ||
| M | 1..1 | ACTIVITY SERVICE REQUEST DATE (EMERGENCY CARE) | F S13 | ||
| M | 1..1 | ACTIVITY SERVICE REQUEST TIME (EMERGENCY CARE) | F S14 | ||
| R | 0..1 | REFERRED TO SERVICE ASSESSMENT DATE | F S13 | ||
| R | 0..1 | REFERRED TO SERVICE ASSESSMENT TIME | F S14 | ||
| Notation | DATA GROUP: DISCHARGE FROM EMERGENCY CARE | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of discharge from Emergency Care. | |
| Notation | DATA GROUP: RESEARCH AND DISEASE OUTBREAK NOTIFICATION | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry details of any Research and/or Disease Outbreak Notifications. |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | CLINICAL TRIAL IDENTIFIER | F | ||
| O | 0..1 | DISEASE OUTBREAK NOTIFICATION | F | ||
| Notation | DATA GROUP: CDS V6-2-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
| Notation | DATA GROUP: CDS V6-2-1 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
Change to Data Set: Changed Description
CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header Overview
For a "Full Screen" view, click CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-2 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE SENDER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE RECEIVER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE DATE OF PREPARATION | F S8 S13 | ||
| M | 1..1 | CDS INTERCHANGE TIME OF PREPARATION | F S8 S14 | ||
| M | 1..1 | CDS INTERCHANGE APPLICATION REFERENCE | F S8 | ||
| O | 0..1 | CDS INTERCHANGE TEST INDICATOR | F | ||
Change to Data Set: Changed Description
CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer Overview
For a "Full Screen" view, click CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-2 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL COUNT | F S8 | ||
| O | 0..1 | CDS INTERCHANGE SENDER IDENTITY | F | ||
| O | 0..1 | CDS INTERCHANGE RECEIVER IDENTITY | F | ||
Change to Data Set: Changed Description
CDS V6-2-2 Type 003 - Commissioning Data Set Message Header Overview
For a "Full Screen" view, click CDS V6-2-2 Type 003 - Commissioning Data Set Message Header.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-2 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 | ||
| O | 0..1 | CDS RECORD IDENTIFIER | F | ||
Change to Data Set: Changed Description
CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer Overview
For a "Full Screen" view, click CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-2 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity controls for each Commissioning Data Set Message. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS MESSAGE REFERENCE | F | ||
Change to Data Set: Changed Description
CDS V6-2-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol Overview
For a "Full Screen" view, click CDS V6-2-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2-2 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 CODE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER CODE | V | ||
| O | 0..1 | CDS UNIQUE IDENTIFIER | F S9 | ||
| M | 1..1 | CDS BULK REPLACEMENT GROUP CODE | 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 | ||
Change to Data Set: Changed Description
CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol
For a "Full Screen" view, click CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints
| Notation | DATA GROUP: CDS V6-2-2 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 CODE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER CODE | 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 S15 | ||
| O | 1..7 | CDS COPY RECIPIENT IDENTITY | F S5 S7 | ||
Change to Data Set: Changed Description
CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set Overview.
For a "Full Screen" view, click CDS V6-2-2 Type 011 - Emergency Care CDS.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
| CDS V6-2-2 TYPE 011 - EMERGENCY CARE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Emergency Care Attendance. |
| Notation | DATA GROUP: CDS V6-2-2 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-2-2 Type 001 - CDS 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-2-2 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-2-2 Type 003 - CDS 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-2-2 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-2-2 Type 005B - CDS 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-2-2 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-2-2 Type 005N - CDS 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 IDENTIFIER (PATIENT PATHWAY IDENTIFIER ISSUER) | F I2 | |||
| M | 1..1 | DATA GROUP: REFERRAL TO TREATMENT PERIOD CHARACTERISTICS | Rules | |||
| M | 1..1 | REFERRAL TO TREATMENT PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION IDENTIFIER (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 01 (Number present and verified) | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (EXTENDED) | F S3 | ||
| M | 1..1 | ORGANISATION IDENTIFIER (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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION IDENTIFIER (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE NOT included in the above | ||||
| R | 0..1 | DATA GROUP: LOCAL IDENTIFIER STRUCTURE | Rules | ||
| M | 1..1 | LOCAL PATIENT IDENTIFIER (EXTENDED) | F S3 | ||
| M | 1..1 | ORGANISATION IDENTIFIER (LOCAL PATIENT IDENTIFIER) | F | ||
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NHS NUMBER | F | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | 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 IDENTIFIER (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (EMERGENCY CARE) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient for an Emergency Care Attendance. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON STATED GENDER CODE | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | ACCOMMODATION STATUS (SNOMED CT) | F | ||
| R | 0..1 | PREFERRED SPOKEN LANGUAGE (SNOMED CT) | F | ||
| R | 0..1 | ACCESSIBLE INFORMATION PROFESSIONAL REQUIRED CODE (SNOMED CT) | F | ||
| R | 0..1 | INTERPRETER LANGUAGE (SNOMED CT) | F | ||
| R | 0..1 | OVERSEAS VISITOR CHARGING CATEGORY AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: MENTAL HEALTH ACT LEGAL STATUS | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the patients Mental Health Act Legal Status. | |
| 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 | 0..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: EMERGENCY CARE ATTENDANCE LOCATION | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Emergency Care Attendance location. | |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | ORGANISATION SITE IDENTIFIER (OF TREATMENT) | F | ||
| M | 1..1 | EMERGENCY CARE DEPARTMENT TYPE | V | ||
| Notation | DATA GROUP: AMBULANCE DETAILS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry ambulance details relating to the patients arrival at Emergency Care. |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | AMBULANCE INCIDENT NUMBER | F | ||
| R | 0..1 | ORGANISATION IDENTIFIER (CONVEYING AMBULANCE TRUST) | F | ||
| Notation | DATA GROUP: EMERGENCY CARE ATTENDANCE ACTIVITY CHARACTERISTICS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the characteristics of the Emergency Care Attendance. | |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE ATTENDANCE IDENTIFIER | F | ||
| R | 0..1 | EMERGENCY CARE ARRIVAL MODE (SNOMED CT) | F | ||
| R | 0..1 | EMERGENCY CARE ATTENDANCE CATEGORY | V | ||
| R | 0..1 | EMERGENCY CARE ATTENDANCE SOURCE (SNOMED CT) | F | ||
| R | 0..1 | ORGANISATION SITE IDENTIFIER (EMERGENCY CARE ATTENDANCE SOURCE) | F | ||
| M | 1..1 | EMERGENCY CARE ARRIVAL DATE | F S1 S13 | ||
| M | 1..1 | EMERGENCY CARE ARRIVAL TIME | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F S8 | ||
| R | 0..1 | EMERGENCY CARE INITIAL ASSESSMENT DATE | F S13 | ||
| R | 0..1 | EMERGENCY CARE INITIAL ASSESSMENT TIME | F S14 | ||
| R | 0..1 | EMERGENCY CARE ACUITY (SNOMED CT) | F | ||
| R | 0..1 | EMERGENCY CARE CHIEF COMPLAINT (SNOMED CT) | F | ||
| R | 0..1 | EMERGENCY CARE DATE SEEN FOR TREATMENT | F S13 | ||
| R | 0..1 | EMERGENCY CARE TIME SEEN FOR TREATMENT | F S14 | ||
| Notation | DATA GROUP: INJURY CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of injuries. | |
| Notation | DATA GROUP: PATIENT CLINICAL HISTORY | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry patient clinical history details. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..* | COMORBIDITY (SNOMED CT) | F | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| O | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| M | 1..1 | ORGANISATION IDENTIFIER (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION IDENTIFIER (CODE OF COMMISSIONER) | F | ||
| Notation | DATA GROUP: CARE PROFESSIONALS (EMERGENCY CARE) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of the Care Professionals active during the Emergency Care Attendance. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | F | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER | F | ||
| M | 1..1 | CARE PROFESSIONAL TIER (EMERGENCY CARE) | V | ||
| M | 1..1 | CARE PROFESSIONAL DISCHARGE RESPONSIBILITY INDICATOR (EMERGENCY CARE) | V | ||
| Notation | DATA GROUP: EMERGENCY CARE DIAGNOSES (SNOMED CT) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of SNOMED CT coded Clinical Diagnoses. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE DIAGNOSIS (SNOMED CT) | F H4 | ||
| M | 1..1 | CODED CLINICAL ENTRY SEQUENCE NUMBER | F | ||
| M | 1..1 | EMERGENCY CARE DIAGNOSIS QUALIFIER (SNOMED CT) | F | ||
| Notation | DATA GROUP: EMERGENCY CARE INVESTIGATIONS (SNOMED CT) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of SNOMED CT coded Clinical Investigations. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE CLINICAL INVESTIGATION (SNOMED CT) | F H4 | ||
| R | 0..1 | PROCEDURE DATE (EMERGENCY CARE CLINICAL INVESTIGATION) | F S13 | ||
| R | 0..1 | PROCEDURE TIME (EMERGENCY CARE CLINICAL INVESTIGATION) | F S14 | ||
| Notation | DATA GROUP: EMERGENCY CARE TREATMENTS (SNOMED CT) | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of SNOMED CT coded Procedures. | |
| R | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | EMERGENCY CARE PROCEDURE (SNOMED CT) | F H4 | ||
| R | 0..1 | PROCEDURE DATE (EMERGENCY CARE PROCEDURE) | F S13 | ||
| R | 0..1 | PROCEDURE TIME (EMERGENCY CARE PROCEDURE) | F S14 | ||
| Notation | DATA GROUP: REFERRALS TO OTHER SERVICES | ||
| Group Status R | Group Repeats 0..* | FUNCTION: To carry the details of referrals to other services. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRED TO SERVICE (SNOMED CT) | F | ||
| M | 1..1 | ACTIVITY SERVICE REQUEST DATE (EMERGENCY CARE) | F S13 | ||
| M | 1..1 | ACTIVITY SERVICE REQUEST TIME (EMERGENCY CARE) | F S14 | ||
| R | 0..1 | REFERRED TO SERVICE ASSESSMENT DATE | F S13 | ||
| R | 0..1 | REFERRED TO SERVICE ASSESSMENT TIME | F S14 | ||
| Notation | DATA GROUP: DISCHARGE FROM EMERGENCY CARE | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of discharge from Emergency Care. | |
| Notation | DATA GROUP: RESEARCH AND DISEASE OUTBREAK NOTIFICATION | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry details of any Research and/or Disease Outbreak Notifications. |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | CLINICAL TRIAL IDENTIFIER | F | ||
| O | 0..1 | DISEASE OUTBREAK NOTIFICATION | F | ||
| Notation | DATA GROUP: CDS V6-2-2 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-2-2 Type 004 - CDS 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-2-2 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-2-2 Type 002 - CDS Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
Change to Data Set: Changed Description
CDS V6-2 Type 001 - Commissioning Data Set Interchange Header Overview
For a "Full Screen" view, click CDS V6-2 Type 001 - Commissioning Data Set Interchange Header.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE SENDER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE RECEIVER IDENTITY | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE DATE OF PREPARATION | F S8 S13 | ||
| M | 1..1 | CDS INTERCHANGE TIME OF PREPARATION | F S8 S14 | ||
| M | 1..1 | CDS INTERCHANGE APPLICATION REFERENCE | F S8 | ||
| O | 0..1 | CDS INTERCHANGE TEST INDICATOR | F | ||
Change to Data Set: Changed Description
CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer Overview
For a "Full Screen" view, click CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity and addressing information for the Commissioning Data Set submission. One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS INTERCHANGE CONTROL REFERENCE | F S8 | ||
| M | 1..1 | CDS INTERCHANGE CONTROL COUNT | F S8 | ||
| O | 0..1 | CDS INTERCHANGE SENDER IDENTITY | F | ||
| O | 0..1 | CDS INTERCHANGE RECEIVER IDENTITY | F | ||
Change to Data Set: Changed Description
CDS V6-2 Type 003 - Commissioning Data Set Message Header Overview
For a "Full Screen" view, click CDS V6-2 Type 003 - Commissioning Data Set Message Header.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2 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 | ||
| O | 0..1 | CDS RECORD IDENTIFIER | F | ||
Change to Data Set: Changed Description
CDS V6-2 Type 004 - Commissioning Data Set Message Trailer Overview
For a "Full Screen" view, click CDS V6-2 Type 004 - Commissioning Data Set Message Trailer.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | |
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the mandatory identity controls for each Commissioning Data Set Message. One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | CDS MESSAGE REFERENCE | F | ||
Change to Data Set: Changed Description
CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Overview
For a "Full Screen" view, click CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2 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 CODE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER CODE | V | ||
| O | 0..1 | CDS UNIQUE IDENTIFIER | F S9 | ||
| M | 1..1 | CDS BULK REPLACEMENT GROUP CODE | 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 | ||
Change to Data Set: Changed Description
CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol Overview
For a "Full Screen" view, click CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| Notation | DATA GROUP: CDS V6-2 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 CODE | V | ||
| M | 1..1 | CDS PROTOCOL IDENTIFIER CODE | 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 S15 | ||
| O | 1..7 | CDS COPY RECIPIENT IDENTITY | F S5 S7 | ||
Change to Data Set: Changed Description
CDS V6-2 Type 010 - Accident and Emergency Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 010 - Accident and Emergency Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 010 - ACCIDENT AND EMERGENCY COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Accident And Emergency Attendance. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (A AND E) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient for an Accident and Emergency Attendance. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: LOCATION GROUP - ATTENDANCE | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Accident and Emergency Attendance location. | |
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | SITE CODE (OF TREATMENT) | 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. | |
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| O | 0..1 | COMMISSIONER REFERENCE NUMBER | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | 0..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..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| R | 1..1 | PROCEDURE DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange |
Change to Data Set: Changed Description
CDS V6-2 Type 020 - Outpatient Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 020 - Outpatient Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 020 - OUTPATIENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Outpatient Attendance. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 or is subject to Allied Health Professional Referral To Treatment Measurement. | |
| 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (CARE ACTIVITY) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V H4 | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| Notation | DATA GROUP: CARE EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | ATTENDED OR DID NOT ATTEND CODE | V | ||
| R | 0..1 | FIRST ATTENDANCE CODE | V H4 | ||
| R | 0..1 | MEDICAL STAFF TYPE SEEING PATIENT | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| R | 0..1 | OUTCOME OF ATTENDANCE CODE | V | ||
| M | 1..1 | APPOINTMENT DATE | F S1 S13 | ||
| O | 0..1 | APPOINTMENT TIME | F S14 | ||
| O | 0..1 | EXPECTED DURATION OF APPOINTMENT | F | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| O | 0..1 | EARLIEST CLINICALLY APPROPRIATE DATE | F S13 | ||
| O | 0..1 | CONSULTATION MEDIUM USED | V | ||
| O | 0..1 | MULTI-PROFESSIONAL OR MULTI-DISCIPLINARY INDICATION CODE (PAYMENT BY RESULTS) | V N3 | ||
| O | 0..1 | REHABILITATION ASSESSMENT TEAM TYPE | V N3 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | CLINIC CODE | 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: 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 CODE | V | ||
| R | 0..1 | SERVICE TYPE REQUESTED CODE | V | ||
| R | 0..1 | SOURCE OF REFERRAL FOR OUT-PATIENTS | V | ||
| R | 0..1 | REFERRAL REQUEST RECEIVED DATE | F S13 | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 021- Future Outpatient Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 021 - Future Outpatient Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 021 - FUTURE OUTPATIENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Future (or Planned) Outpatient Attendance. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS (CARE ACTIVITY) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| Notation | DATA GROUP: CARE EPISODE - PERSON GROUP (CONSULTANT) | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Responsible Care Professional. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| O | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | ATTENDED OR DID NOT ATTEND CODE | V | ||
| R | 0..1 | FIRST ATTENDANCE CODE | V | ||
| R | 0..1 | MEDICAL STAFF TYPE SEEING PATIENT | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| R | 0..1 | OUTCOME OF ATTENDANCE CODE | V | ||
| M | 1..1 | APPOINTMENT DATE | F S1 S13 | ||
| O | 0..1 | APPOINTMENT TIME | F S14 | ||
| O | 0..1 | EXPECTED DURATION OF APPOINTMENT | F | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| O | 0..1 | EARLIEST CLINICALLY APPROPRIATE DATE | F S13 | ||
| O | 0..1 | CONSULTATION MEDIUM USED | V | ||
| O | 0..1 | MULTI-PROFESSIONAL OR MULTI-DISCIPLINARY INDICATION CODE (PAYMENT BY RESULTS) | V N3 | ||
| O | 0..1 | REHABILITATION ASSESSMENT TEAM TYPE | V N3 | ||
| Notation | DATA GROUP: CARE ATTENDANCE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | CLINIC CODE | 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: 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 CODE | V | ||
| R | 0..1 | SERVICE TYPE REQUESTED CODE | V | ||
| R | 0..1 | SOURCE OF REFERRAL FOR OUT-PATIENTS | V | ||
| R | 0..1 | REFERRAL REQUEST RECEIVED DATE | F S13 | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT CHANGE 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 CODE | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE CODE | V | ||
| R | 0..1 | INTENDED MANAGEMENT CODE | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS CODE | V | ||
| R | 0..1 | PRIORITY TYPE CODE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | 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: REFERRAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. |
| O | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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 CODE | 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 CODE | V | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 040 - Elective Admission List - End of Period Census (Old) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT CHANGE 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| M | 1..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S1 S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 050 - Elective Admission List - End of Period Census (New) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT CHANGE 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 CODE | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE CODE | V | ||
| R | 0..1 | INTENDED MANAGEMENT CODE | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS CODE | V | ||
| R | 0..1 | PRIORITY TYPE CODE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | 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: REFERRAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. |
| 0 | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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 CODE | 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 CODE | V | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 060 - Elective Admission List - Event During Period (Add) CDS Overview
For a "Full Screen" view, click CDS V6-2 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT CHANGE 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 CODE | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE CODE | V | ||
| R | 0..1 | INTENDED MANAGEMENT CODE | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS CODE | V | ||
| R | 0..1 | PRIORITY TYPE CODE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | 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: REFERRAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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 CODE | 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 CODE | V | ||
| O | 0..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 CODE | V | ||
| M | 1..1 | ELECTIVE ADMISSION LIST REMOVAL DATE | F S1 S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 CODE | 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-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 090 - Elective Admission List - Event During Period (Available or Unavailable) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT CHANGE 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| M | 1..1 | NHS SERVICE AGREEMENT CHANGE DATE | F S1 S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: EAL PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V | ||
| O | 0..1 | CARER SUPPORT INDICATOR | V | ||
| Notation | DATA GROUP: EAL SERVICE AGREEMENT CHANGE 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 CODE | V | ||
| R | 0..1 | COUNT OF DAYS SUSPENDED | F | ||
| R | 0..1 | ELECTIVE ADMISSION LIST STATUS | V | ||
| R | 0..1 | ELECTIVE ADMISSION TYPE CODE | V | ||
| R | 0..1 | INTENDED MANAGEMENT CODE | V | ||
| R | 0..1 | INTENDED PROCEDURE STATUS CODE | V | ||
| R | 0..1 | PRIORITY TYPE CODE | V | ||
| M | 1..1 | DECIDED TO ADMIT DATE | F S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | 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: REFERRAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. |
| O | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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 CODE | 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: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS TYPE V6-2 120 - FINISHED BIRTH EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished Birth Episode. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED OR PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Baby). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V H4 | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | LIVE OR STILL BIRTH CODE | 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V H4 | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| 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 CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD CODE (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 | ||
| O | 0..1 | DISCHARGE TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| O | 0..1 | DISCHARGED TO HOSPITAL AT HOME SERVICE INDICATOR | V | ||
| Notation | DATA GROUP: BIRTH 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 CODE | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE CODE | V H4 | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| M | 1..1 | END DATE (EPISODE) | F H4 S1 S13 | ||
| O | 0..1 | END TIME (EPISODE) | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: BIRTH EPISODE- OVERSEAS VISITOR STATUS | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient (the Baby) during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | V | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | V | ||
| Notation | DATA GROUP: BIRTH EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | F | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | F | ||
| 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 | ||
| R | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | START TIME (WARD STAY) | F S14 | ||
| O | 0..1 | END DATE | F S13 | ||
| O | 0..1 | END TIME (WARD STAY) | F S14 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| Notation | DATA GROUP: BIRTH EPISODE - NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES INDICATION CODE | 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (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 CODE | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY CODE | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD CODE | 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 CODE | V | ||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | ||
| R | 0..1 | RESUSCITATION METHOD CODE | V | ||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY CODE | 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE (MOTHER) | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE (MOTHER) National Code = 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 CODE (MOTHER) | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE (MOTHER) 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 CODE (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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - OVERSEAS VISITOR STATUS AT CDS ACTIVITY DATE GROUP | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Overseas Visitor Status of the Mother. | |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 130 - FINISHED GENERAL EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished General Episode. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE 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 | MENTAL HEALTH ACT 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V H4 | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| O | 0..1 | AMBULANCE INCIDENT NUMBER | F | ||
| O | 0..1 | ORGANISATION CODE (CONVEYING AMBULANCE TRUST) | F | ||
| 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 CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD CODE (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 | ||
| O | 0..1 | DISCHARGE TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| O | 0..1 | DISCHARGED TO HOSPITAL AT HOME SERVICE INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE CODE | V H4 | ||
| O | 0..1 | FIRST REGULAR DAY OR NIGHT ADMISSION CODE | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS CODE | V | ||
| M | 1..1 | START DATE (EPISODE) | F S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| M | 1..1 | END DATE (EPISODE) | F H4 S1 S13 | ||
| O | 0..1 | END TIME (EPISODE) | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| O | 0..1 | MULTI-PROFESSIONAL OR MULTI-DISCIPLINARY INDICATION CODE (PAYMENT BY RESULTS) | V N3 | ||
| O | 0..1 | REHABILITATION ASSESSMENT TEAM TYPE | V N3 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - LENGTH OF STAY ADJUSTMENT | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry details of length of stay adjustments to the Consultant Episode . |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | LENGTH OF STAY ADJUSTMENT (REHABILITATION) | F | ||
| O | 0..1 | LENGTH OF STAY ADJUSTMENT (SPECIALIST PALLIATIVE CARE) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE- OVERSEAS VISITOR STATUS GROUP | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | F S13 | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| R | 0..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | START TIME (WARD STAY) | F S14 | ||
| O | 0..1 | END DATE | F S13 | ||
| O | 0..1 | END TIME (WARD STAY) | F S14 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| Notation | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: REFERRAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | DECIDED TO ADMIT DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 140 - FINISHED DELIVERY EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of a Finished Delivery Episode. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | R | 0..1 | PERSON BIRTH DATE | F S3 S12 |
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Mother). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE 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 | MENTAL HEALTH ACT 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V H4 | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| O | 0..1 | AMBULANCE INCIDENT NUMBER | F | ||
| O | 0..1 | ORGANISATION CODE (CONVEYING AMBULANCE TRUST) | F | ||
| 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 CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD CODE (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 | ||
| O | 0..1 | DISCHARGE TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| R | 0..1 | DISCHARGED TO HOSPITAL AT HOME SERVICE INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS CODE | V | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| M | 1..1 | END DATE (EPISODE) | F H4 S1 S13 | ||
| O | 0..1 | END TIME (EPISODE) | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| O | 0..1 | MULTI-PROFESSIONAL OR MULTI-DISCIPLINARY INDICATION CODE (PAYMENT BY RESULTS) | V N3 | ||
| O | 0..1 | REHABILITATION ASSESSMENT TEAM TYPE | V N3 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE- OVERSEAS VISITOR STATUS GROUP | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient (the Mother) during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | F S13 | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | CONSULTANT CODE | F | ||
| R | 0..1 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | START TIME (WARD STAY) | F S14 | ||
| O | 0..1 | END DATE | F S13 | ||
| O | 0..1 | END TIME (WARD STAY) | F S14 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| R | 0..1 | SITE CODE (OF TREATMENT) | F | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | F N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 0..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 | 0..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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES INDICATION CODE | 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 | 0..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 | 0..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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (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 | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | ANAESTHETIC GIVEN DURING LABOUR OR DELIVERY CODE | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY CODE | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD CODE | 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 CODE | V | |||||||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | |||||||
| R | 0..1 | RESUSCITATION METHOD CODE | V | |||||||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY CODE | 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 Commissioning Data Set record has been anonymised | Rules | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| R | 0..1 | WITHHELD IDENTITY REASON | V | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE (BABY) National Code = 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 CODE (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE (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 CODE (BABY) | V | |||||||
| R | 0..1 | Data Element Components | Rules | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| Notation | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - BABY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT (BABY) | V | ||
| R | 0..1 | LIVE OR STILL BIRTH CODE | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Birth Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 150 - OTHER BIRTH EVENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details for an Other Birth. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Baby). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V H4 | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | LIVE OR STILL BIRTH CODE | 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 INDICATION CODE | 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (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 CODE | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY CODE | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD CODE | V | ||
| M | 1..1 | DELIVERY DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 CODE | V | ||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | ||
| R | 0..1 | RESUSCITATION METHOD CODE | V | ||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY CODE | 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE (MOTHER) | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE (MOTHER) National Code = 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 CODE (MOTHER) | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE (MOTHER) 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 CODE (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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - OVERSEAS VISITOR STATUS AT CDS ACTIVITY DATE GROUP | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Overseas Visitor Status of the Mother. | |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 160 - OTHER DELIVERY EVENT COMMISSIONING DATA SET | |
| FUNCTION: To support the details for an Other Delivery. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | R | 0..1 | PERSON BIRTH DATE | F S3 S12 |
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Mother). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE 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 INDICATION CODE | 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (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 CODE | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY CODE | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD CODE | V | ||
| M | 1..1 | DELIVERY DATE | F S1 S13 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: LABOUR/DELIVERY SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..1 | FUNCTION: To carry the details of the Service Agreement for the Delivery. | |
| 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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 CODE | V | |||||||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | |||||||
| R | 0..1 | RESUSCITATION METHOD CODE | V | |||||||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY CODE | 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 Commissioning Data Set record has been anonymised | Rules | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| R | 0..1 | WITHHELD IDENTITY REASON | V | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE (BABY) National Code = 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 CODE (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE (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 CODE (BABY) | V | |||||||
| R | 0..1 | Data Element Components | Rules | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| Notation | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - BABY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT (BABY) | V | ||
| R | 0..1 | LIVE OR STILL BIRTH CODE | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Birth Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 170 - Admitted Patient Care - Detained and or Long Term Psychiatric Census Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE 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 | MENTAL HEALTH ACT 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 | MENTAL HEALTH ACT 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 HEALTH ACT 2007 MENTAL CATEGORY | V N6 | ||
| R | 0..1 | STATUS OF PATIENT INCLUDED IN THE PSYCHIATRIC CENSUS CODE | 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| 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 | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS CODE | V | ||
| M | 1..1 | START DATE (EPISODE) | F S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| M | 1..1 | DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE | F S1 S10 S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE- OVERSEAS VISITOR STATUS GROUP | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | F S13 | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | F S13 | ||
| Notation | DATA GROUP: SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| R | 0..1 | INTENDED AGE GROUP | V | ||
| R | 0..1 | SEX OF PATIENTS CODE | V | ||
| R | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| R | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE | F N7 S1 S10 S13 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | 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: 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 CODE | V | ||
| R | 0..1 | DECIDED TO ADMIT DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
CDS V6-2 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set Overview
For a "Full Screen" view, click CDS V6-2 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 180 - UNFINISHED BIRTH EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished Birth Episode. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | V | ||
| O | 0..1 | PATIENT NAME - PERSON NAME STRUCTURED Or PATIENT NAME - PERSON NAME UNSTRUCTURED | F S3 | ||
| R | 0..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Baby). | |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT | V H4 | ||
| R | 0..1 | ETHNIC CATEGORY | V | ||
| R | 0..1 | LIVE OR STILL BIRTH CODE | 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V H4 | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| 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 CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD CODE (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 | ||
| O | 0..1 | DISCHARGE TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| O | 0..1 | DISCHARGED TO HOSPITAL AT HOME SERVICE INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE CODE | V H4 | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S1 S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| R | 0..1 | END DATE (EPISODE) | F S13 | ||
| O | 0..1 | END TIME (EPISODE) | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE- OVERSEAS VISITOR STATUS GROUP | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | F | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | START TIME (WARD STAY) | F S14 | ||
| O | 0..1 | END DATE | F S13 | ||
| O | 0..1 | END TIME (WARD STAY) | F S14 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | V | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | V | ||
| Notation | DATA GROUP: BIRTH EPISODE - NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: BIRTH EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES INDICATION CODE | 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (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 CODE | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY CODE | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD CODE | 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 CODE | V | ||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | ||
| R | 0..1 | RESUSCITATION METHOD CODE | V | ||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY CODE | 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE (MOTHER) | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE (MOTHER) National Code = 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 CODE (MOTHER) | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS (MOTHER) | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE (MOTHER) 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 CODE (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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE (MOTHER) | F S3 S12 | ||
| Notation | DATA GROUP: DELIVERY OCCURRENCE - OVERSEAS VISITOR STATUS AT CDS ACTIVITY DATE GROUP | ||
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Overseas Visitor Status of the Mother. | |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 190 - UNFINISHED GENERAL EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished General Episode. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | V | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient. | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE 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 | MENTAL HEALTH ACT 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V H4 | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| O | 0..1 | AMBULANCE INCIDENT NUMBER | F | ||
| O | 0..1 | ORGANISATION CODE (CONVEYING AMBULANCE TRUST) | F | ||
| 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 CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD CODE (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 | ||
| O | 0..1 | DISCHARGE TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| O | 0..1 | DISCHARGED TO HOSPITAL AT HOME SERVICE INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| O | 0..1 | NEONATAL LEVEL OF CARE CODE | V H4 | ||
| O | 0..1 | FIRST REGULAR DAY OR NIGHT ADMISSION CODE | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS CODE | V | ||
| M | 1..1 | START DATE (EPISODE) | F S1 S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| R | 0..1 | END DATE (EPISODE) | F S13 | ||
| O | 0..1 | END TIME (EPISODE) | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 S8 | ||
| O | 0..1 | MULTI-PROFESSIONAL OR MULTI-DISCIPLINARY INDICATION CODE (PAYMENT BY RESULTS) | V N3 | ||
| O | 0..1 | REHABILITATION ASSESSMENT TEAM TYPE | V N3 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - LENGTH OF STAY ADJUSTMENT | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry details of length of stay adjustments to the Consultant Episode . |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | LENGTH OF STAY ADJUSTMENT (REHABILITATION) | F | ||
| O | 0..1 | LENGTH OF STAY ADJUSTMENT (SPECIALIST PALLIATIVE CARE) | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE- OVERSEAS VISITOR STATUS GROUP | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | F S13 | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | START TIME (WARD STAY) | F S14 | ||
| O | 0..1 | END DATE | F S13 | ||
| O | 0..1 | END TIME (WARD STAY) | F S14 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| Notation | DATA GROUP: NEONATAL CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Neonatal Care facilities. |
| M | 1..1 | DATA GROUP: NEONATAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..1 | GESTATION LENGTH (AT DELIVERY) | V | ||
| M | 1..999 | DATA GROUP: NEONATAL DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| R | 0..1 | PERSON WEIGHT | F | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: NEONATAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | V N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: REFERRAL | |
| Group Status O | Group Repeats 0..1 | FUNCTION: To carry the details of the Referral. |
| O | 0..1 | Data Element Components | Rules | ||
| O | 0..1 | DIRECT ACCESS REFERRAL INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | DECIDED TO ADMIT DATE | F S13 | ||
| O | 0..1 | EARLIEST REASONABLE OFFER DATE | F S13 | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Data Set: Changed Description
For a "Full Screen" view, click CDS V6-2 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set.
In the "Full Screen" view, to return to the "Data Set" view, click the browser "back" button.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
| CDS V6-2 TYPE 200 - UNFINISHED DELIVERY EPISODE COMMISSIONING DATA SET | |
| FUNCTION: To support the details of an Unfinished Delivery Episode. |
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 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-2 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-2 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-2 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-2 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-2 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 PERIOD STATUS | V | |||
| M | 1..1 | WAITING TIME MEASUREMENT TYPE | V | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD START DATE | F S13 | |||
| O | 0..1 | REFERRAL TO TREATMENT PERIOD END DATE | F S13 | |||
| 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 Commissioning Data Set record has been anonymised | ||||
| M | 1..1 | Data Element Components | Rules | ||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE | V | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | WITHHELD IDENTITY REASON | F | ||
| OR |
| 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 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 CODE | V | ||
| M | 1..1 | POSTCODE OF USUAL ADDRESS | F S3 | ||
| R | 0..1 | ORGANISATION CODE (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | PERSON BIRTH DATE | F S3 S12 | ||
| OR |
| 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE 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 CODE | 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 (RESIDENCE RESPONSIBILITY) | F | ||
| R | 0..1 | R | 0..1 | PERSON BIRTH DATE | F S3 S12 |
| Notation | DATA GROUP: PATIENT CHARACTERISTICS | ||
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Patient (the Mother). | |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE 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 | MENTAL HEALTH ACT 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 CODE (ON ADMISSION) | V | ||
| R | 0..1 | PATIENT CLASSIFICATION CODE | V H4 | ||
| R | 0..1 | ADMISSION METHOD CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | SOURCE OF ADMISSION CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| M | 1..1 | START DATE (HOSPITAL PROVIDER SPELL) | F H4 S13 | ||
| O | 0..1 | START TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| M | 1..1 | AGE ON ADMISSION | F H4 | ||
| O | 0..1 | AMBULANCE INCIDENT NUMBER | F | ||
| O | 0..1 | ORGANISATION CODE (CONVEYING AMBULANCE TRUST) | F | ||
| 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 CODE (HOSPITAL PROVIDER SPELL) | V H4 | ||
| R | 0..1 | DISCHARGE METHOD CODE (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 | ||
| O | 0..1 | DISCHARGE TIME (HOSPITAL PROVIDER SPELL) | F S14 | ||
| O | 0..1 | DISCHARGED TO HOSPITAL AT HOME SERVICE INDICATOR | V | ||
| 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 CODE | V | ||
| R | 0..1 | OPERATION STATUS CODE | V | ||
| R | 0..1 | PSYCHIATRIC PATIENT STATUS CODE | V | ||
| M | 1..1 | START DATE (EPISODE) | F H4 S1 S13 | ||
| O | 0..1 | START TIME (EPISODE) | F S14 | ||
| R | 0..1 | END DATE (EPISODE) | F S13 | ||
| O | 0..1 | END TIME (EPISODE) | F S14 | ||
| M | 1..1 | AGE AT CDS ACTIVITY DATE | F H4 | ||
| O | 0..1 | MULTI-PROFESSIONAL OR MULTI-DISCIPLINARY INDICATION CODE (PAYMENT BY RESULTS) | V N3 | ||
| O | 0..1 | REHABILITATION ASSESSMENT TEAM TYPE | V N3 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE- OVERSEAS VISITOR STATUS GROUP | ||
| Group Status O | Group Repeats 0..5 | FUNCTION: To carry the details of the Overseas Visitor Status of the Patient (the Mother) during the Episode. | |
| O | 0..1 | Data Element Components | Rules | ||
| M | 1..1 | OVERSEAS VISITOR STATUS CLASSIFICATION | V | ||
| M | 1..1 | OVERSEAS VISITOR STATUS START DATE | F S13 | ||
| R | 0..1 | OVERSEAS VISITOR STATUS END DATE | F S13 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - SERVICE AGREEMENT DETAILS | ||
| Group Status M | Group Repeats 1..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 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF PROVIDER) | F H4 | ||
| M | 1..1 | ORGANISATION CODE (CODE OF COMMISSIONER) | F | ||
| 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 | CARE PROFESSIONAL MAIN SPECIALTY CODE | V H4 | ||
| R | 0..1 | ACTIVITY TREATMENT FUNCTION CODE | V H4 | ||
| O | 0..1 | LOCAL SUB-SPECIALTY CODE | F | ||
| 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 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| R | 0..* | DATA GROUP: SECONDARY DIAGNOSES | Rules | ||
| M | 1..1 | SECONDARY DIAGNOSIS (ICD) | F H4 | ||
| O | 0..1 | PRESENT ON ADMISSION INDICATOR | V | ||
| 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 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 | 1..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| R | 0..* | DATA GROUP: SECONDARY PROCEDURES | Rules | ||
| M | 1..1 | PROCEDURE (OPCS) | F | ||
| R | 0..1 | PROCEDURE DATE | F S13 | ||
| O | 0..1 | DATA GROUP: MAIN OPERATING HEALTHCARE PROFESSIONAL | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (MAIN OPERATING CARE PROFESSIONAL) | F | ||
| O | 0..1 | DATA GROUP: RESPONSIBLE ANAESTHETIST | Rules | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ISSUER CODE | V | ||
| M | 1..1 | PROFESSIONAL REGISTRATION ENTRY IDENTIFIER (RESPONSIBLE ANAESTHETIST) | F | ||
| 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 | ||
| R | 0..1 | PROCEDURE DATE | F 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | START DATE | F S13 | ||
| O | 0..1 | START TIME (WARD STAY) | F S14 | ||
| O | 0..1 | END DATE | F S13 | ||
| O | 0..1 | END TIME (WARD STAY) | F S14 | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| O | 0..1 | INTENDED CLINICAL CARE INTENSITY CODE | V | ||
| O | 0..1 | INTENDED AGE GROUP | V | ||
| O | 0..1 | SEX OF PATIENTS CODE | V | ||
| O | 0..1 | WARD DAY PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD NIGHT PERIOD AVAILABILITY CODE | V | ||
| O | 0..1 | WARD SECURITY LEVEL | V | ||
| O | 0..1 | WARD CODE | F | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - PAEDIATRIC CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Paediatric Care facilities. |
| M | 1..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| M | 1..999 | DATA GROUP: PAEDIATRIC DAILY CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| M | 1..1 | ACTIVITY DATE (CRITICAL CARE) | F S13 | ||
| M | 1..20 | CRITICAL CARE ACTIVITY CODE | F N4 | ||
| R | 0..20 | HIGH COST DRUGS (OPCS) | F N4 | ||
| R | 0..1 | DATA GROUP: PAEDIATRIC CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| Notation | DATA GROUP: CONSULTANT EPISODE - ADULT CRITICAL CARE PERIOD | |
| Group Status R | Group Repeats 0..9 | FUNCTION: See CRITICAL CARE PERIOD To carry the details of the first 9 Critical Care Periods for care provided using Adult Care facilities. |
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ADMISSION CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE LOCAL IDENTIFIER | F | ||
| M | 1..1 | CRITICAL CARE START DATE | F H4 S13 | ||
| O | 0..1 | CRITICAL CARE START TIME | F S14 | ||
| M | 1..1 | CRITICAL CARE UNIT FUNCTION | V H4 | ||
| O | 0..1 | CRITICAL CARE UNIT BED CONFIGURATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION SOURCE | V | ||
| O | 0..1 | CRITICAL CARE SOURCE LOCATION | V | ||
| O | 0..1 | CRITICAL CARE ADMISSION TYPE | V | ||
| M | 1..1 | DATA GROUP: ADULT CRITICAL CARE - ACTIVITY CHARACTERISTICS | Rules | ||
| R | 0..1 | ADVANCED RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC RESPIRATORY SUPPORT DAYS | F H4 | ||
| R | 0..1 | ADVANCED CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | BASIC CARDIOVASCULAR SUPPORT DAYS | F H4 | ||
| R | 0..1 | RENAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | NEUROLOGICAL SUPPORT DAYS | F H4 | ||
| O | 0..1 | GASTRO-INTESTINAL SUPPORT DAYS | F | ||
| R | 0..1 | DERMATOLOGICAL SUPPORT DAYS | F H4 | ||
| R | 0..1 | LIVER SUPPORT DAYS | F H4 | ||
| O | 0..1 | ORGAN SUPPORT MAXIMUM | V | ||
| R | 0..1 | CRITICAL CARE LEVEL 2 DAYS | F H4 | ||
| R | 0..1 | CRITICAL CARE LEVEL 3 DAYS | F H4 | ||
| R | 0..1 | DATA GROUP: ADULT CRITICAL CARE - DISCHARGE CHARACTERISTICS | Rules | ||
| M | 1..1 | CRITICAL CARE DISCHARGE DATE | F H4 S13 | ||
| M | 1..1 | CRITICAL CARE DISCHARGE TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY DATE | F S13 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE READY TIME | F S14 | ||
| O | 0..1 | CRITICAL CARE DISCHARGE STATUS | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE DESTINATION | V | ||
| O | 0..1 | CRITICAL CARE DISCHARGE LOCATION | V | ||
| Notation | DATA GROUP: GP REGISTRATION | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the Patient's General Medical Practitioner and the General Practice details. |
| R | 1..1 | Data Element Components | Rules | ||
| O | 0..1 | GENERAL MEDICAL PRACTITIONER (SPECIFIED) | F | ||
| R | 0..1 | GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION) | F | ||
| Notation | DATA GROUP: REFERRER | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Referrer. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | REFERRER CODE | F | ||
| R | 0..1 | REFERRING ORGANISATION CODE | F | ||
| Notation | DATA GROUP: PREGNANCY - ACTIVITY CHARACTERISTICS | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Pregnancy. |
| R | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | NUMBER OF BABIES INDICATION CODE | 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 | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE CHANGE REASON CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (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 CODE | V | ||
| R | 0..1 | ANAESTHETIC GIVEN POST LABOUR OR DELIVERY CODE | V | ||
| O | 0..1 | GESTATION LENGTH (LABOUR ONSET) | V | ||
| R | 0..1 | LABOUR OR DELIVERY ONSET METHOD CODE | 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 CODE | V | |||||||
| R | 0..1 | GESTATION LENGTH (ASSESSMENT) | V | |||||||
| R | 0..1 | RESUSCITATION METHOD CODE | V | |||||||
| R | 0..1 | STATUS OF PERSON CONDUCTING DELIVERY CODE | 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 Commissioning Data Set record has been anonymised | Rules | |||||||
| M | 1..1 | NHS NUMBER STATUS INDICATOR CODE (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| R | 0..1 | WITHHELD IDENTITY REASON | V | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: VERIFIED IDENTITY STRUCTURE Must be used where the NHS NUMBER STATUS INDICATOR CODE (BABY) National Code = 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 CODE (BABY) | V | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| OR | ||||||||||
| M | 1..1 | DATA GROUP: UNVERIFIED IDENTITY STRUCTURE Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE (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 CODE (BABY) | V | |||||||
| R | 0..1 | Data Element Components | Rules | |||||||
| R | 0..1 | PERSON BIRTH DATE (BABY) | F S3 S12 | |||||||
| Notation | DATA GROUP: BIRTH OCCURRENCE - PERSON CHARACTERISTICS - BABY | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the characteristics of the Baby. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | PERSON GENDER CODE CURRENT (BABY) | V | ||
| R | 0..1 | LIVE OR STILL BIRTH CODE | V | ||
| R | 0..1 | BIRTH WEIGHT | F | ||
| O | 0..1 | OVERSEAS VISITOR STATUS CLASSIFICATION AT CDS ACTIVITY DATE | V | ||
| Notation | DATA GROUP: BIRTH OCCURRENCE - LOCATION GROUP - DELIVERY PLACE ACTUAL | |
| Group Status R | Group Repeats 0..1 | FUNCTION: To carry the details of the Actual Birth Location. |
| M | 1..1 | Data Element Components | Rules | ||
| R | 0..1 | LOCATION CLASS | V | ||
| O | 0..1 | ACTIVITY LOCATION TYPE CODE | V | ||
| R | 0..1 | DELIVERY PLACE TYPE CODE (ACTUAL) | V | ||
| Notation | DATA GROUP: CDS V6-2 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-2 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-2 TYPE 002 - COMMISSIONING DATA SET INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and address using information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-1 Type 005N - CDS Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 001 - COMMISSIONING DATA SET INTERCHANGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set Interchange submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header One per Commissioning Data Set Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-1 Type 005N - CDS Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer is shown below.A high-level view of the Data Groups is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 002 - CDS INTERCHANGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-1 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-1 Type 003 - Commissioning Data Set Message Header should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 003 - Commissioning Data Set Message Header is shown below.A high-level view of the Data Groups is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 003 - CDS MESSAGE HEADER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-2-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer is shown below.A high-level view of the Data Groups is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 004 - COMMISSIONING DATA SET MESSAGE TRAILER | ||
| Group Status | Group Repeats | FUNCTION: To define the mandatory identity and addressing information for a Commissioning Data Set submission. | |
| M | 1..* | DATA GROUP: CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 005B - TRANSACTION HEADER GROUP - BULK UPDATE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Update Mechanisms of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol should only be used when submitting the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Net Change Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-1 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol - Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 005N - CDS TRANSACTION HEADER GROUP - NET CHANGE PROTOCOL | ||
| Group Status | Group Repeats | FUNCTION: To carry Commissioning Data Set identification and addressing data and other data indicating the specific use of one of the Update Mechanisms of the Commissioning Data Set Submission Protocol. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set record submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set carries the data for an Emergency Care Attendance.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-1 Type 011 - Emergency Care Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-1 TYPE 011 - EMERGENCY CARE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of an Emergency Care Attendance. | |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 001 - Commissioning Data Set Interchange Header One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..* | DATA GROUP: CDS V6-2-1 Type 003 - Commissioning Data Set Message Header One per Commissioning Data Set Message submitted to the Secondary Uses Service. |
| M | 1..1 | DATA GROUP: COMMISSIONING DATA SET TRANSACTION HEADER GROUP Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used per Commissioning Data Set Message submitted to the Secondary Uses Service: CDS V6-2-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PATIENT IDENTITY |
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS (EMERGENCY CARE) |
| R | 0..* | DATA GROUP: MENTAL HEALTH ACT LEGAL STATUS |
| R | 0..1 | DATA GROUP: GP REGISTRATION |
| R | 0..1 | DATA GROUP: EMERGENCY CARE ATTENDANCE LOCATION |
| R | 0..1 | DATA GROUP: AMBULANCE DETAILS |
| M | 1..1 | DATA GROUP: EMERGENCY CARE ATTENDANCE ACTIVITY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: INJURY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: PATIENT CLINICAL HISTORY |
| M | 1..1 | SERVICE AGREEMENT DETAILS |
| R | 0..* | DATA GROUP: CARE PROFESSIONALS (EMERGENCY CARE) |
| R | 0..* | DATA GROUP: EMERGENCY CARE DIAGNOSES |
| R | 0..* | DATA GROUP: EMERGENCY CARE INVESTIGATIONS |
| R | 0..* | DATA GROUP: EMERGENCY CARE TREATMENTS |
| R | 0..* | DATA GROUP: REFERRALS TO OTHER SERVICES |
| R | 0..1 | DATA GROUP: DISCHARGE FROM EMERGENCY CARE |
| O | 0..1 | DATA GROUP: RESEARCH AND DISEASE OUTBREAK NOTIFICATION |
| M | 1..* | DATA GROUP: CDS V6-2-1 Type 004 - Commissioning Data Set Message Trailer One per Commissioning Data Set Message submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
| M | 1..1 | DATA GROUP: CDS V6-2-1 Type 002 - Commissioning Data Set Interchange Trailer One per Interchange submitted to the Secondary Uses Service. Multiple Commissioning Data Set Messages may be submitted in a single Commissioning Data Set Interchange. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-1 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 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-2-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 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-2-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-2 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-2 Type 003 - Commissioning Data Set Message Header should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 003 - Commissioning Data Set Message Header is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 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-2-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 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-2-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.Note that the CDS V6-2-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 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-2-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.
Note that the CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol should only be used when submitting the CDS V6-2-2 Type 011 - Emergency Care CDS.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Net Change Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
- CDS V6-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol - Mandatory, one per CDS TypeCDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol- Mandatory, one per CDS Type
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 005N - CDS Transaction Header Group - Net Change Protocol is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 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-2-2 Type 005N - CDS 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2-2 Type 011 - Emergency Care Commissioning Data Set carries the data for an Emergency Care Attendance.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2-2 Type 011 - Emergency Care CDS Overview is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2-2 TYPE 011 - EMERGENCY CARE COMMISSIONING DATA SET | ||
| Group Status | Group Repeats | FUNCTION: To support the details of an Emergency Care Attendance. | |
| M | 1..1 | DATA GROUP: CDS V6-2-2 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-2-2 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-2-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol | ||
| O | 0..1 | DATA GROUP: PATIENT PATHWAY |
| M | 1..1 | DATA GROUP: PATIENT IDENTITY |
| R | 0..1 | DATA GROUP: PATIENT CHARACTERISTICS (EMERGENCY CARE) |
| R | 0..* | DATA GROUP: MENTAL HEALTH ACT LEGAL STATUS |
| R | 0..1 | DATA GROUP: GP REGISTRATION |
| R | 0..1 | DATA GROUP: EMERGENCY CARE ATTENDANCE LOCATION |
| R | 0..1 | DATA GROUP: AMBULANCE DETAILS |
| M | 1..1 | DATA GROUP: EMERGENCY CARE ATTENDANCE ACTIVITY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: INJURY CHARACTERISTICS |
| R | 0..1 | DATA GROUP: PATIENT CLINICAL HISTORY |
| M | 1..1 | SERVICE AGREEMENT DETAILS |
| R | 0..* | DATA GROUP: CARE PROFESSIONALS (EMERGENCY CARE) |
| R | 0..* | DATA GROUP: EMERGENCY CARE DIAGNOSES |
| R | 0..* | DATA GROUP: EMERGENCY CARE INVESTIGATIONS |
| R | 0..* | DATA GROUP: EMERGENCY CARE TREATMENTS |
| R | 0..* | DATA GROUP: REFERRALS TO OTHER SERVICES |
| R | 0..1 | DATA GROUP: DISCHARGE FROM EMERGENCY CARE |
| O | 0..1 | DATA GROUP: RESEARCH AND DISEASE OUTBREAK NOTIFICATION |
| M | 1..* | DATA GROUP: CDS V6-2-2 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-2-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 001 - Commissioning Data Set Interchange Header carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set InterchangeCDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 001 - Commissioning Data Set Interchange Header is shown below.A high-level view of the Data Groups is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer carries mandatory controls for a Commissioning Data Set Interchange and is only used by inclusion in other CDS Types.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 003 - Commissioning Data Set Message Header carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 003 - Commissioning Data Set Message Header is shown below.A high-level view of the Data Groups is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 004 - Commissioning Data Set Message Trailer carries mandatory controls for a Commissioning Data Set Message and is only used by inclusion in other CDS Types.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 004 - Commissioning Data Set Message Trailer is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set Interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol carries mandatory controls for a Commissioning Data Set Type and is only used by inclusion in other CDS Types.
Commissioning Data Set Interchanges containing Commissioning Data Set Messages submitted to the Secondary Uses Service must use the required Commissioning Data Set interchange and Message Header and Trailer Controls to provide the correct addressing and identification for the data flows. All CDS Types using the Commissioning Data Set Bulk Replacement Update Mechanism of the Commissioning Data Set Submission Protocol must begin with this Mandatory Data Group.
Multiple Commissioning Data Set messages are usually sent in a single Commissioning Data Set Interchange which consists of:
- CDS V6-2 Type 001 - Commissioning Data Set Interchange Header - Mandatory - One per Commissioning Data Set Interchange
- CDS V6-2 Type 003 - Commissioning Data Set Message Header - Mandatory - One per Commissioning Data Set Message
Dependent upon the Commissioning Data Set Submission Protocol being used, one of the following must be used:
Followed by:
- The CDS Type - As required to carry the specific Commissioning Data Set data records
Each Commissioning Data Set message ends with:
- CDS V6-2 Type 004 - Commissioning Data Set Message Trailer - Mandatory - One per Commissioning Data Set Message
Each Commissioning Data Set Interchange ends with:
- CDS V6-2 Type 002 - Commissioning Data Set Interchange Trailer - Mandatory - One per Commissioning Data Set Interchange
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 010 - Accident and Emergency Commissioning Data Set carries the data for an Accident and Emergency Attendance.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 010 - Accident and Emergency Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - ATTENDANCE | ||
| M | 1..1 | DATA GROUP: ATTENDANCE OCCURRENCE | ||
| M | 1..1 | DATA GROUP: ACTIVITY CHARACTERISTICS | ||
| M | 1..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 TREATMENT GROUP (A AND E) | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 020 - Outpatient Commissioning Data Set carries the data for an Outpatient Attendance or a cancelled/missed APPOINTMENT.
It covers all NHS and private Outpatient ACTIVITY taking place in any:
- acute, community, mental health NHS Trust or NHS Foundation Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow, unless the ACTIVITY falls under the Allied Health Professional Referral To Treatment Measurement standard. In this case, an out-patient record for the Allied Health Professional ACTIVITY must be submitted, with the CDS DATA GROUP : PATIENT PATHWAY data elements completed as necessary.
Where the Outpatient data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.This CDS Type may also be used to submit Referral To Treatment Clock Stop Administrative Events.
This CDS Type must not be used for "Future Outpatients" - for this the CDS V6-2 Type 021 - Future Outpatient Commissioning Data Set must be used.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 020 - Outpatient Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| M | 1..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 | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
The CDS V6-2 Type 021 - Future Outpatient Commissioning Data Set carries the data for a Future Outpatient Attendance or a future cancelled APPOINTMENT.
This CDS Type was not approved by the Information Standards Board for Health and Social Care and submissions to support local activities and commissioning will be supported for piloting purposes only.
It covers all NHS and private Outpatient ACTIVITY taking place in any:
- acute, community, mental health NHS Trust or NHS Foundation Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
This CDS Type must not be used for "Outpatients" - for this the CDS V6-2 Type 020 - Outpatient Commissioning Data Set must be used.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 021 - Future Outpatient Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| M | 1..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 | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set carries the data for all booked, planned and waiting list admissions.
This consists of records for PATIENTS waiting for Elective Admission at a specified date and should be sent to the Secondary Uses Service within one month of the end of the period to which they relate unless a shorter time-scale has been agreed with the recipient.
Some Health Care Providers also send a final CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set after the PATIENT has been removed from the WAITING LIST to identify when and why this took place. Commissioners who do not wish to use such final Elective Admission List-End Of Period Census Commissioning Data Sets should ignore them.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 |
| 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 | ||
| O | 0..1 | DATA GROUP: REFERRAL | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| O | 0..1 | DATA GROUP: EAL ENTRY REMOVAL | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 040 - Elective Admission List - End of Period Census (Old) Commissioning Data Set is used to report to the previous (old) Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of another Commissioner.
This CDS Type should be sent within one month of the end of the period to which it relates unless a shorter time-scale has been agreed with the recipient.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 040 - Elective Admission List - End of Period Census (Old) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 050 - Elective Admission List - End of Period Census (New) Commissioning Data Set is used to report to a new Commissioner an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.
This CDS Type should be sent within one month of the end of the period to which it relates unless a shorter time-scale has been agreed with the recipient.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 050 - Elective Admission List - End of Period Census (New) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..1 | DATA GROUP: REFERRAL | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| O | 0..1 | DATA GROUP: EAL ENTRY REMOVAL | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is used to make an initial report that an ELECTIVE ADMISSION LIST ENTRY has been added to the Health Care Provider's ELECTIVE ADMISSION LIST.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 060 - Elective Admission List - Event During Period (Add) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 |
| 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 | ||
| O | 0..1 | DATA GROUP: REFERRAL | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is used to report that the ELECTIVE ADMISSION LIST ENTRY has been removed from the Health Care Provider's ELECTIVE ADMISSION LIST.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 070 - Elective Admission List - Event During Period (Remove) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is used to report that an OFFER OF ADMISSION has been made to the PATIENT.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 080 - Elective Admission List - Event During Period (Offer) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 090 - Elective Admission List - Event During Period (Available or Unavailable) Commissioning Data Set is used to report changes in the PATIENT's availability for treatment.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 090 - Elective Admission List - Event During Period (Available or Unavailable) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is used to report to the previous Commissioner that the ELECTIVE ADMISSION LIST ENTRY is now the responsibility of a new Commissioner.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 100 - Elective Admission List - Event During Period (Old Service Agreement) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set used to make an initial report to a new Commissioner of an ELECTIVE ADMISSION LIST ENTRY that had previously been the responsibility of another Commissioner.
It covers ELECTIVE ADMISSION LIST ENTRIES under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Elective Admission List Event During Period CDS Types are intended for those ORGANISATIONS who have the capability to implement transaction-based processing, and are transmitted using Net Change Commissioning Data Set Submission Protocol. They should be supplemented where required by an annual (or other agreed time-cycle) submission of the CDS V6-2 Type 030 - Elective Admission List - End of Period Census (Standard) Commissioning Data Set.
Note: for Elective Admission List Event During Period CDS Types, the CDS UNIQUE IDENTIFIER, as held in the Commissioning Data Set Transaction Header Group, must be completed in order to provide the ELECTIVE ADMISSION LIST identity.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..1 | DATA GROUP: REFERRAL | ||
| R | 0..1 | DATA GROUP: OFFER OF ADMISSION | ||
| R | 0..1 | DATA GROUP: ORIGINAL EAL ENTRY | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set carries the data for a Finished Birth Episode.
This is required when a delivery has resulted in a REGISTRABLE BIRTH which has taken place in either an NHS Hospital or in an non-NHS ORGANISATION funded by the NHS.
The information is taken from the birth notification for each baby born.
In addition to Finished Birth Episodes, Unfinished Birth Episode Commissioning Data Set records are required for all Unfinished Birth Episodes as at midnight on 31st March each year.
CDS V6-2 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set should be used for the submission of this Unfinished Birth Episode Commissioning Data Set.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..5 | DATA GROUP: OVERSEAS VISITOR STATUS | ||
| M | 1..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: DELIVERY 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) | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set carries the data for a Finished General Episode.
It covers all NHS and private Admitted Patient Care (day case and inpatient) ACTIVITY taking place in any:
- acute, community, mental health NHS Trust or NHS Foundation Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
An Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes as at midnight on 31 March each year and for all unfinished short-stay informal psychiatric PATIENTS who are resident in hospital or on leave of absence (Home Leave) on 31 March and who have been in hospital for less than 12 months.
CDS V6-2 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set should be used for the submission of this Unfinished General Episode Commissioning Data Set.
To access more detailed information on the Commissioning Data Sets, see the Commissioning Data Sets Introduction.
Data Group Overview
A high-level view of the Data Groups carried in the CDS V6-2 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..1 | DATA GROUP: LENGTH OF STAY ADJUSTMENT | ||
| O | 0..5 | DATA GROUP: OVERSEAS VISITOR STATUS | ||
| M | 1..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 |
| O | 0.1 | DATA GROUP: REFERRAL |
| R | 0.1 | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY |
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 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-2 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-2 Type 140 - Admitted Patient Care - Finished Delivery Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..5 | DATA GROUP: OVERSEAS VISITOR STATUS | ||
| M | 1..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: 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) | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set carries the data for an Other Birth.This CDS Type applies to:
- NHS funded home births and
- all other birth events which are not NHS-funded, either directly or under an NHS SERVICE AGREEMENT.
The data in these records originates from birth notification records and requires only a limited data set to be completed.
Maternity events, taking place in either NHS hospitals or in non-NHS ORGANISATIONS funded by the NHS, will be recorded using CDS V6-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set and CDS V6-2 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-2 Type 150 - Admitted Patient Care - Other Birth Event Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| M | 1..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) | ||
| O | 0..1 | DATA GROUP: OVERSEAS VISITOR STATUS AT CDS ACTIVITY DATE | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP - DELIVERY PLACE ACTUAL | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 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-2 Type 120 - Admitted Patient Care - Finished Birth Episode Commissioning Data Set and CDS V6-2 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-2 Type 160 - Admitted Patient Care - Other Delivery Event Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| M | 1..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-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 Type 170 - Admitted Patient Care - Detained and or Long Term Psychiatric Census Commissioning Data Set carries the data for the Psychiatric Census.
The NHS Digital 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 than 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 Organisation Mergers and demergers occurring, where the Hospital Provider Spell would have lasted longer than 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-2 Type 170 - Admitted Patient Care - Detained and or Long Term Psychiatric Census Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..1 | DATA GROUP: OVERSEAS VISITOR STATUS | ||
| M | 1..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 | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 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-2 Type 180 - Admitted Patient Care - Unfinished Birth Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..5 | DATA GROUP: OVERSEAS VISITOR STATUS | ||
| M | 1..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: 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) | ||
| O | 0..1 | DATA GROUP: OVERSEAS VISITOR STATUS AT CDS ACTIVITY DATE | ||
| R | 0..1 | DATA GROUP: LOCATION GROUP (DELIVERY PLACE ACTUAL) | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 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, mental health NHS Trust or NHS Foundation Trust
- other NHS hospital
- non-NHS hospitals or institutions where the care delivered is NHS-funded.
under the care of a CONSULTANT, MIDWIFE or NURSE, where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists.
ACTIVITY taking place under the care of Allied Health Professionals, other Biomedical Scientists and Clinical Scientists may also be carried (where an appropriate MAIN SPECIALTY CODE and TREATMENT FUNCTION CODE exists) if required although this is not a Commissioning Data Set Mandated Data Flow.
Where the Care Activity data relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, the CDS DATA GROUP : PATIENT PATHWAY data elements must be completed where appropriate.
An Unfinished General Episode Commissioning Data Set record is required for all Unfinished General Episodes as at midnight on 31 March each year and for all unfinished short-stay informal psychiatric PATIENTS who are resident in hospital or on leave of absence (Home Leave) on 31 March and who have been in hospital for less than 12 months.
CDS V6-2 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set 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-2 Type 190 - Admitted Patient Care - Unfinished General Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW: CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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 | ||
| O | 0..1 | LENGTH OF STAY ADJUSTMENT | ||
| O | 0..5 | OVERSEAS VISITOR STATUS | ||
| M | 1..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 | ||
| O | 0..1 | DATA GROUP: REFERRAL | ||
| R | 0..1 | DATA GROUP: ELECTIVE ADMISSION LIST ENTRY |
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Change to Supporting Information: Changed Description
Introduction
CDS V6-2 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-2 Type 200 - Admitted Patient Care - Unfinished Delivery Episode Commissioning Data Set is shown below.A high-level view of the Data Groups carried is shown below.
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
| Notation | DATA GROUP OVERVIEW CDS V6-2 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-2 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-2 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-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol Or CDS V6-2 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: ACTIVITY CHARACTERISTICS | ||
| O | 0..5 | DATA GROUP: OVERSEAS VISITOR STATUS | ||
| M | 1..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: 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) | ||
| M | 1..* | DATA GROUP: CDS V6-2 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-2 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. |
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
For enquiries about this Change Request, please email information.standards@nhs.net
