CDS V6-2 Type 110 - Elective Admission List - Event During Period (New Service Agreement) CDS
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.
Overview
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.
Notation
See Commissioning Data Set Notation for an explanation of Group Status and Group Repeats.
Business Rules
See Commissioning Data Set Business Rules for an explanation of the business and/or processing rules which apply to individual Data Elements.
XML Schema
For guidance on the XML Schema constraints, see the Commissioning Data Set Version 6-2 XML Schema Constraints.
For guidance on downloading the XML Schema, see XML Schema TRUD Download.
Specification
Notation |
Data Group: CDS V6-2 Type 001 - CDS 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 - 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 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..1 |
Data Group: CDS V6-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 options must be used:
Notation |
Data Group: CDS V6-2 Type 005B - CDS 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 - CDS Transaction Header Group - Bulk Update Protocol 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 - 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 Net Change Update Mechanism of the Commissioning Data Set Submission Protocol. |
|||
M |
1..1 |
Data Group: CDS V6-2 Type 005N - CDS Transaction Header Group - Net Change Protocol CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol One per Commissioning Data Set re cord 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 |
PATIENT PATHWAY IDENTITY | Rules | ||||
M Or M |
1..1 Or 1..1 |
UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) Or |
F
F I2 |
||||
M |
1..1 |
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) |
F I2 |
||||
M |
1..1 |
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 |
WITHHELD IDENTITY STRUCTURE
Must be used where the Commissioning Data Set record has been anonymised |
Rules | |||||
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 |
VERIFIED IDENTITY STRUCTURE
Must be used where the NHS NUMBER STATUS INDICATOR CODE National Code = 01 (Number present and verified) |
Rules | |||||
R |
0..1 |
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 |
UNVERIFIED IDENTITY STRUCTURE
Must be used for all other values of the NHS NUMBER STATUS INDICATOR CODE NOT included in the above |
Rules | |||||
R |
0..1 |
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 |
F S3 |
|||||
O |
0..1 |
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 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 |
PRIMARY PROCEDURE | Rules | ||||
M |
1..1 |
PRIMARY PROCEDURE (READ) |
F |
||||
R |
0..1 |
PROCEDURE DATE |
F S13 |
||||
O |
0..* |
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 - CDS 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 - 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 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 - 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. |
Also Known As
This data set is also known by these names:
Context | Alias |
---|---|
Full name | CDS V6-2 Type 110 - Elective Admission List - Event During Period (New Service Agreement) Commissioning Data Set |
Short name | CDS V6-2 Type 110 |