NHS Connecting for Health

NHS Data Model and Dictionary Service

Type:Patch
Reference:1365
Version No:1.0
Subject:CDS V 6-2 patch
Effective Date:Immediate
Reason for Change:Patch
Publication Date:12 February 2013

Background:

Change Request 1166 "CDS 6-2" introduced version 6-2 of the Commissioning Data Sets to the NHS Data Model and Dictionary to support the Information Standard.

This patch adds:

To view a demonstration on "How to Read an NHS Data Model and Dictionary Change Request", visit the NHS Data Model and Dictionary help pages at: http://www.datadictionary.nhs.uk/Flash_Files/changerequest.htm.

Note: if the web page does not open, please copy the link and paste into the web browser.

Summary of changes:

Data Set
CRITICAL CARE MINIMUM DATA SET   Changed Description
NEONATAL CRITICAL CARE MINIMUM DATA SET   Changed Description
PAEDIATRIC CRITICAL CARE MINIMUM DATA SET   Changed Description
 
Supporting Information
CDS NOTATION   Changed Description
CDS SUBMISSION PROTOCOL   Changed Description
COMMISSIONING DATA SET OVERVIEW   Changed Description
REFERRAL TO TREATMENT CLOCK STOP ADMINISTRATIVE EVENT   Changed Description
 
Attribute Definitions
FIRST ATTENDANCE   Changed Description
 
Data Elements
APPOINTMENT DATE   Changed Description
CDS RECORD IDENTIFIER   Changed Description
DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE   Changed Description
FIRST ATTENDANCE   Changed Description
FIRST ATTENDANCE CODE   Changed Description
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER)   Changed Description
PATIENT PATHWAY IDENTIFIER   Changed Description
PATIENT USUAL ADDRESS (MOTHER)   Changed Description
REFERRAL TO TREATMENT PERIOD END DATE   Changed Description
REFERRAL TO TREATMENT PERIOD START DATE   Changed Description
REFERRAL TO TREATMENT PERIOD STATUS   Changed Description
REFERRAL TO TREATMENT STATUS   Changed Description
UNIQUE BOOKING REFERENCE NUMBER (CONVERTED)   Changed Description
 

Date:12 February 2013
Sponsor:Richard Kavanagh, NHS Connecting for Health

Note: New text is shown with a blue background. Deleted text is crossed out. Retired text is shown in grey. Within the Diagrams deleted classes and relationships are red, changed items are blue and new items are green.

Click here for a printer friendly view of this page.


CRITICAL CARE MINIMUM DATA SET

Change to Data Set: Changed Description

Critical Care Minimum Data Set Overview

Critical Care Minimum Data Set excludes neonatal critical care. A subset of this minimum data set is used to derive Adult Critical Care HRGs. The subset is sent in the following Commissioning Data Set messages:

Data Set Data Elements
NHS NUMBER
LOCAL PATIENT IDENTIFIER
CRITICAL CARE LOCAL IDENTIFIER
SITE CODE (OF TREATMENT)
GENERAL MEDICAL PRACTICE CODE (PATIENT REGISTRATION)
TREATMENT FUNCTION CODE
TREATMENT FUNCTION CODE (CDS V6-1)
or
ACTIVITY TREATMENT FUNCTION CODE (CDS V6-2)
PERSON BIRTH DATE
POSTCODE OF USUAL ADDRESS
CRITICAL CARE START DATE
CRITICAL CARE START TIME
CRITICAL CARE UNIT FUNCTION
CRITICAL CARE UNIT BED CONFIGURATION
CRITICAL CARE ADMISSION SOURCE
CRITICAL CARE SOURCE LOCATION
CRITICAL CARE ADMISSION TYPE
ADVANCED RESPIRATORY SUPPORT DAYS
BASIC RESPIRATORY SUPPORT DAYS
ADVANCED CARDIOVASCULAR SUPPORT DAYS
BASIC CARDIOVASCULAR SUPPORT DAYS
RENAL SUPPORT DAYS
NEUROLOGICAL SUPPORT DAYS
GASTRO-INTESTINAL SUPPORT DAYS
DERMATOLOGICAL SUPPORT DAYS
LIVER SUPPORT DAYS
ORGAN SUPPORT MAXIMUM
CRITICAL CARE LEVEL 2 DAYS
CRITICAL CARE LEVEL 3 DAYS
CRITICAL CARE DISCHARGE STATUS
CRITICAL CARE DISCHARGE DESTINATION
CRITICAL CARE DISCHARGE LOCATION
CRITICAL CARE DISCHARGE READY DATE
CRITICAL CARE DISCHARGE READY TIME
CRITICAL CARE DISCHARGE DATE
CRITICAL CARE DISCHARGE TIME

top


NEONATAL CRITICAL CARE MINIMUM DATA SET

Change to Data Set: Changed Description

Neonatal Critical Care Minimum Data Set Overview

The Neonatal Critical Care Minimum Data Set is sent as a subset in the following Commissioning Data Set messages:

 

Data Set Data Elements
Person Group (Patient):
To carry the personal details of the Patient (the baby).
One occurrence of this Group is permitted.
PERSON BIRTH DATE
DISCHARGE DATE (HOSPITAL PROVIDER SPELL)
DISCHARGE METHOD (HOSPITAL PROVIDER SPELL)
Neonatal Critical Care Group:
To carry the details of the Neonatal Critical Care Period.
One occurrence of this Group is permitted.
CRITICAL CARE LOCAL IDENTIFIER
CRITICAL CARE START DATE
CRITICAL CARE START TIME
CRITICAL CARE DISCHARGE DATE
CRITICAL CARE DISCHARGE TIME
CRITICAL CARE UNIT FUNCTION
GESTATION LENGTH (AT DELIVERY)
Neonatal Critical Care Daily Activity Group:
To carry the daily activity data for each day of the Neonatal Critical Care Period.
999 occurrences of this Group are permitted.
ACTIVITY DATE (CRITICAL CARE)
PERSON WEIGHT
20 occurrences of Critical Care Activity Codes are permitted within the Neonatal Critical Care Daily Activity Group. All codes relate to care provided on the ACTIVITY DATE (CRITICAL CARE).
CRITICAL CARE ACTIVITY CODE
20 occurrences of High Cost Drugs OPCS codes are permitted within the Neonatal Critical Care Daily Activity Group. All codes relate to drugs provided on the ACTIVITY DATE (CRITICAL CARE).
HIGH COST DRUGS (OPCS)

top


PAEDIATRIC CRITICAL CARE MINIMUM DATA SET

Change to Data Set: Changed Description

Paediatric Critical Care Minimum Data Set Overview

The Paediatric Critical Care Minimum Data Set is sent as a subset in the following Commissioning Data Set messages:

Data Set Data Elements
Person Group (Patient):
To carry the personal details of the Patient.
One occurrence of this Group is permitted.
PERSON BIRTH DATE
DISCHARGE DATE (HOSPITAL PROVIDER SPELL)
DISCHARGE METHOD (HOSPITAL PROVIDER SPELL)
Paediatric Critical Care Group:
To carry the details of the Paediatric Critical Care Period.
CRITICAL CARE LOCAL IDENTIFIER
CRITICAL CARE START DATE
CRITICAL CARE START TIME
CRITICAL CARE DISCHARGE DATE
CRITICAL CARE DISCHARGE TIME
CRITICAL CARE UNIT FUNCTION
Paediatric Critical Care Daily Activity Group:
To carry the daily activity data for each day of the Paediatric Critical Care Period. 999 occurrences of this Group are permitted.
ACTIVITY DATE (CRITICAL CARE)
20 occurrences of Critical Care Activity Codes are permitted within the Paediatric Critical Care Daily Activity Group. All codes relate to care provided on the CRITICAL CARE START DATE.
CRITICAL CARE ACTIVITY CODE
2 HIGH COST DRUGS (OPCS) codes are permitted but there is the capacity for 20 codes within the Paediatric Critical Care Daily Activity Group, to allow future refinement. All codes relate to drugs provided on the CRITICAL CARE LOCAL IDENTIFIER.
HIGH COST DRUGS (OPCS)

top


CDS NOTATION

Change to Supporting Information: Changed Description

The Commissioning Data Set is the basic structure used for the submission of commissioning data to the Secondary Uses Service and is designed to be capable of individually conveying many different Commissioning Data Set structures, encompassing Accident and Emergency Attendances, Out-Patient Attendances, Admitted Patient Care and Elective Admission List.

Commissioning Data Set Messages have been defined in specific components known as a CDS TYPE.

Specific notation is used to indicate the requirements of the CDS-XML Message Schema Design conditions for submission of data in the Commissioning Data Sets.

The structure of the Commissioning Data Set message is shown by the use of Data Groups and Sub Groups within those Data Groups.  For each Data Group, Sub Group and individual Data Element, the allowed cardinality at each level is also shown in the "Status" and "Repeats" columns.

The CDS TYPE specifications must therefore be read in this hierarchy, using the Status and Repeat conditions within the Data Groups and Sub Groups, to determine the requirements for the individual Data Elements.


Status Column Notation

The Notation used for the "STATUS" column is as follows:

STATUS MEANING DESCRIPTION 
M MANDATORY This signifies that the collection and submission of this Commissioning Data Set data is deemed MANDATORY and its presence is necessary for the CDS TYPE to be correctly validated and accepted for processing by the Secondary Uses Service.

If a data item is shown as MANDATORY, this should also be regarded as REQUIRED by the Department of Health.

In most instances, data marked as MANDATORY in a Sub Group will result in its parent Data Group also being marked as mandatory, but this is not always the case.

For instance, although the Consultant Episode - Clinical Diagnosis Group (ICD) is marked as R=REQUIRED (and therefore need not actually be populated), if it is used then both the DIAGNOSIS SCHEME IN USE and the PRIMARY DIAGNOSIS (ICD) are marked as M=MANDATORY and must both be present. 

R REQUIRED This signifies that the collection and submission of this Commissioning Data Set data is deemed REQUIRED by the Department of Health to comply with authorised NHS Standards, Policies and Directives. Therefore whenever a Commissioning Data Set is collected and subsequently submitted to the Secondary Uses Service, this data must be supported and populated into the relevant data sets if the data is available.

Note that "temporal" conditions may mean that there are instances where this directive cannot be fulfilled.

For instance in a CDS V6-2 Type 130 - Admitted Patient Care - Finished General Episode Commissioning Data Set, ICD and OPCS data elements are marked as "Required" indicating that this data should be included.  However, if at the time of submission to the Secondary Uses Service this data remains incomplete (perhaps awaiting coding in the ORGANISATION), the remaining data in the CDS record should still be submitted. Once the ORGANISATION has updated its systems with the data, the CDS TYPE relating to that ACTIVITY should then be resubmitted to the Secondary Uses Service

O OPTIONAL This signifies that the collection and submission of this Commissioning Data Set data is OPTIONAL. Its inclusion in the Commissioning Data Set is therefore determined by "local agreement" between the ORGANISATIONS exchanging the data.

Note that even if marked O=OPTIONAL, any data included in a Commissioning Data Set submission to the Secondary Uses Service must comply with its specification published in the NHS Data Model and Dictionary otherwise the data may be deemed invalid and rejected. 

X X This is used where the Data Element has been included in the Commissioning Data Set design, usually for pilot use, but is not yet authorised for transmission by the wider NHS. The Data Element will be in italics and not linked to the Data Element where one exists. 

Repeats Column Notation

The Notation used for the "REPEATS" column is as follows:

REPEATS DESCRIPTION 
0..1 This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to a maximum of 1.
0..9 This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to a maximum of 9.
0..* This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 0 to an unlimited maximum.
1..1 This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to a maximum of 1.
1..97 This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to a maximum of 97.
1..* This signifies that the permitted occurrences of the Data Group, Sub Group or individual Data Element are from a minimum of 1 to an unlimited maximum.

Rules Column Notation

An entry in the "Rules" column shows that a specific Rule applies to submission of an individual Data Element.

The meaning of these Rules can be found in Commissioning Data Set Business Rules.


Notation Examples

The following are examples of some common scenarios.

EXAMPLE 1:
A MANDATORY Data Group with differing Sub-Groups and component data status conditions.
 

The following example shows a MANDATORY Data Group - therefore the Data Group must be present for the CDS TYPE to be validated and accepted for processing by the Secondary Uses Service.

When a Data Group is used:

  1. All MANDATORY Sub Groups and/or Data Elements must be present
  2. Any REQUIRED Sub Groups and/or Data Elements must be present if the data is available
  3. Any OPTIONAL Sub Groups and/or Data Elements may be omitted

The following data structure is one of three options when completing the Patient Identity Data Group:

 
1..1DATA GROUP: VERIFIED IDENTITY STRUCTURE
Must be used where the
NHS NUMBER STATUS INDICATOR CODE Code Value = 01 = Verified 
Rules 
R0..1DATA GROUP: LOCAL IDENTIFIER STRUCTURE  
M 1..1 LOCAL PATIENT IDENTIFIER F
M 1..1 ORGANISATION CODE (LOCAL PATIENT IDENTIFIER) F
M 1..1 Data Element Components Rules 
M 1..1 NHS NUMBER F
M 1..1 NHS NUMBER STATUS INDICATOR CODE V
M 1..1 POSTCODE OF USUAL ADDRESS S3
R0..1ORGANISATION CODE (RESIDENCE RESPONSIBILITY) F
R0..1PERSON BIRTH DATE F
S3
R0..1PERSON BIRTH DATE F
S3
S12

EXPLANATION:

The parent Data Group has a "Status" of M=MANDATORY which indicates that this Data Group must be present in the Commissioning Data Set to ensure correct validation and acceptance when submitted to the Secondary Uses Service.  The parent Data Group "Repeats" = 1..1 indicates that only one occurrence of this Data Group must flow in this particular Commissioning Data Set record.

The Sub Group of "Local Identifier Structure" is marked as R=REQUIRED and therefore must be populated if the data is available. The "Repeats" notation of 0..1 indicates that population of this Sub Group is not necessary to enable the Commissioning Data Set record to be sent to the Secondary Uses Service. If it is sent, then only one occurrence of this Sub Group may flow in this particular Commissioning Data Set record.
Both Data Elements in the Sub Group are marked M=MANDATORY and must both be correctly populated.

The Sub Group of "Data Element Components" is a "generic" structure and is marked as M=MANDATORY and therefore must be populated. The "Repeats" notation of 1..1 indicates that only one occurrence of this Data Group may flow in this particular Commissioning Data Set record.  All the Data Elements marked with M=MANDATORY must be populated.  PERSON BIRTH DATE however is marked with R=REQUIRED, so must also be completed if the data is available. 


EXAMPLE 2:
A REQUIRED Data Group with differing component data status conditions.
 

The following example shows a REQUIRED Data Group. This data must be present in the relevant Commissioning Data Set if available.  However, if submitted to the Secondary Uses Service, omission of this REQUIRED Data Group will not cause rejection.

When the Data Group is used:

  1. All MANDATORY Sub Groups and/or Data Elements must be utilised
  2. Any REQUIRED Sub Groups and/or Data Elements must be present if the data is available
  3. Any OPTIONAL Sub Groups and/or Data Elements may be omitted
 
Notation DATA GROUP: CONSULTANT EPISODE - CLINICAL DIAGNOSIS GROUP (ICD) 
Group
Status
R
 
Group
Repeats
0..1
 
FUNCTION:
To carry the details of the ICD coded Clinical Diagnoses.
 
M 1..1 Data Element Components Rules 
M 1..1 PROCEDURE SCHEME IN USE V
M 1..1 DATA GROUP: PRIMARY DIAGNOSIS Rules 
M 1..1 PRIMARY DIAGNOSIS (ICD) F
H4
O0..1PRESENT ON ADMISSION INDICATOR F
O0..*DATA GROUP: SECONDARY DIAGNOSIS Rules 
M 1..1 SECONDARY DIAGNOSIS (ICD) F
H4
O0..1PRESENT ON ADMISSION INDICATOR F

EXPLANATION:

The Data Group "Status" = R = Required indicates that this Data Group must be populated in the relevant Commissioning Data Set if the data is available.  The Data Group "Repeats" = 0..1 indicates that population of this Data Group is not necessary to enable the Commissioning Data Set to be sent to the Secondary Uses Service. If it is sent, then only one occurrence of this Data Group may flow in this particular Commissioning Data Set record.

If the Data Group is completed then the Data Element PROCEDURE SCHEME IN USE, marked as M=MANDATORY, must be populated. The "Repeats" notation of 1..1 indicates that only one occurrence of this Data Element is valid.

If the Data Group is completed then the Data Element PRIMARY DIAGNOSIS (ICD), marked as M=MANDATORY, must be populated. The "Repeats" notation of 1..1 indicates that only one occurrence of this Data Element is valid.

If the Data Group is completed then the Sub Group "Secondary Diagnoses", marked as O=OPTIONAL, may be omitted, but if populated it must be in the correct format. The "Repeats" notation of 0..* indicates that unlimited occurrences of this Data Element are valid. Each occurrence must contain a valid SECONDARY DIAGNOSIS (ICD). 

top


CDS SUBMISSION PROTOCOL

Change to Supporting Information: Changed Description

The Commissioning Data Set messages submitted by providers carry information to determine the update method to be used by the Secondary Uses Service in order to update the national database.

These update rules are known as the Commissioning Data Set Submission Protocol and the set of data controls used to indicate this are carried in the Commissioning Data Set Transaction Header Group which must be present and correct in every CDS TYPE submitted to the Secondary Uses Service.

Two Update Mechanisms are available:

  • Net Change - to support the management of an individual CDS TYPE in the Secondary Uses Service database and enables Commissioning data to be inserted/ updated or deleted.
    CDS Senders are expected to use the Net Change Update Mechanism wherever possible.

  • Bulk Replacement - to support the management of bulk commissioning data for an identified CDS BULK REPLACEMENT GROUP of data for a specified time period and for a specified CDS PRIME RECIPIENT IDENTITY.
    CDS Senders should only use the Bulk Replacement Update Mechanism in exceptional circumstances.

It is strongly advised that all NHS Trusts should, as a minimum process, commence migration to use the CDS-XML Version 6 Message for weekly Net Change submissions by March 2009 as this is the date mandated by the "NHS Operating Framework".

Net Change:
Net Change processes are managed by specific data settings as defined in the CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol / CDS V6-2 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol option of the CDS Transaction Header Group. The Secondary Uses Service uses the following data to manage the database:

Each CDS TYPE must have a CDS UNIQUE IDENTIFIER which must be uniquely maintained for the life of that Commissioning Data Set record. This is a particular consideration where mergers and/or healthcare systems are changed or upgraded, see CDS Submission and Organisation Mergers. Any change to the CDS UNIQUE IDENTIFIER during the "lifetime" of a Commissioning Data Set record will almost certainly result in a duplicate record being lodged in the Secondary Uses Service database.

A Commissioning Data Set record delete transaction must be sent to the Secondary Uses Service database when any previously sent Commissioning Data Set record requires deletion/removal, for example to reflect Commissioner changes etc. 

From Commissioning Data Set version 6-2 onwards, the process for submitting Net Change records carrying a CDS UPDATE TYPE 1 (to indicate a CDS deletion or cancellation) changes.  In previous CDS versions, it was necessary to send the original mandatory content of the deleted record in the CDS TYPE attached to the CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol.  From Commissioning Data Set version 6-2, an empty XML element called 'Delete Transaction' can be used instead of the original CDS TYPE, after the CDS V6-2 Type 005N - CDS Transaction Header Group - Net Change Protocol.  Note that CDS UPDATE TYPE code 1 should still be used to indicate a delete/cancellation when this mechanism is used.

The CDS APPLICABLE DATE and CDS APPLICABLE TIME must be used to ensure that all Commissioning data is updated in the Secondary Uses Service database in the correct chronological order.

The CDS SENDER IDENTITY must not change during the lifetime of the CDS data.
This is particularly significant for multiple and/or merged organisations, and for those services who submit data on behalf of another Primary Care Trust or NHS Trust.

Bulk Replacement
Bulk Replacement processes are managed by specific data settings as defined in the CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol / CDS V6-2 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol option of the CDS Transaction Header Group. The Secondary Uses Service uses the following data to manage the database:


Every CDS TYPE must be submitted using the correct CDS BULK REPLACEMENT GROUP (CDS-XML schema version 6-1-1) / CDS BULK REPLACEMENT GROUP CODE (CDS_XML schema version 6-2).Every CDS TYPE must be submitted using the correct CDS BULK REPLACEMENT GROUP (CDS-XML schema version 6-1-1) / CDS BULK REPLACEMENT GROUP CODE (CDS-XML schema version 6-2).

The CDS REPORT PERIOD START DATE and the CDS REPORT PERIOD END DATE, (i.e. the effective date period), must be valid and consistent, and reflect the dates relevant to the Commissioning data contained in the interchange.

The CDS SENDER IDENTITY must not change during the lifetime of the Commissioning Data Set record. This is particularly significant for multiple and/or merged organisations, and for those services who submit data on behalf of another ORGANISATION.

The CDS PRIME RECIPIENT IDENTITY must be identified in each Commissioning Data Set and must not be changed during the lifetime of the Commissioning Data Set record otherwise the data stored in the Secondary Uses Service database may lose its integrity (e.g. duplicate Commissioning data may be stored).

For this reason it is advised that the ORGANISATION CODE (PCT OF RESIDENCE) (CDS-XML schema version 6-1-1) or ORGANISATION CODE (RESIDENCE RESPONSIBILITY) (CDS-XML schema version 6-2) should always be used to determine the CDS PRIME RECIPIENT IDENTITY as detailed in the Commissioning Data Set Addressing Grid. Senders must also be aware that if the ORGANISATION CODE (PCT OF RESIDENCE) or ORGANISATION CODE (RESIDENCE RESPONSIBILITY) is itself derived from the PATIENT's POSTCODE OF USUAL ADDRESS then great care must be taken to manage all elements of this relationship.

If it is necessary to change any of this data during the lifetime of a Commissioning Data Set record, then the
Secondary Uses Service help desk should be contacted for advice.

It is strongly advised that users of the Bulk Replacement Mechanism maintain a correctly generated CDS UNIQUE IDENTIFIER within the Commissioning data. This will establish a migration path towards the use of the Net Change Mechanism and will also then minimise the risk of creating duplicate Commissioning Data Set data.

Sub contracting
If a Health Care Provider sub-contracts healthcare provision and its associated Commissioning Data Set submission to a second ORGANISATION (eg a different Health Care Provider or a Shared Services Organisation), arrangements to submit the Commissioning Data Set data must be made locally to ensure that only one ORGANISATION sends the Commissioning Data Set data to the Secondary Uses Service.

If the second ORGANISATION wishes to add other Commissioning data to the Secondary Uses Service database to that already submitted by the first ORGANISATION, both parties need to ensure that a different CDS SENDER IDENTITY is used. Often this is done by changing the last 2 digits of the 5 digit code (the Site element of the ORGANISATION CODE).

Note: Data sent using the same CDS SENDER IDENTITY by two different parties will most likely overwrite each other's data in the Secondary Uses Service database. Further advice can be obtained from the Secondary Uses Service helpdesk.

Users should be aware of how the 15 character code of their CDS INTERCHANGE SENDER IDENTITY (also known as the EDI Address) is created. This may depend on how their XML interface solution has been set up. It may not be possible to rely on a change to the ORGANISATION CODE (CODE OF PROVIDER) in order to change the CDS INTERCHANGE SENDER IDENTITY should this become necessary.

top


COMMISSIONING DATA SET OVERVIEW

Change to Supporting Information: Changed Description

The primary purpose of national data sets is to enable conformant health information to be generated across the country, independent of the ORGANISATION or system that maintains it. In achieving this, the Health and Social Care Information Centre will enable healthcare professionals to measure and compare the delivery and quality of care provided and to support them in sharing information with other health professionals and ORGANISATIONS.

Information Requirements

  • monitor and manage NHS SERVICE AGREEMENTS;
  • develop commissioning plans;
  • support the Payment by Results processes;
  • support NHS Comparators;
  • monitor Health Improvement Programmes;
  • underpin clinical governance;
  • understand the health needs of the population.
  • support reporting against 18 week wait targets

Information on care provided for all PATIENTS by NHS Hospitals and Primary Care Trusts and Independent Sector Providers (for NHS PATIENTS only) is specified in the Commissioning Data Sets and must be submitted to the Secondary Uses Service according to issued guidelines.

Commissioners need access to data to monitor Non-Contract Activity as part of the management of their NHS SERVICE AGREEMENTS. Primary Care Trusts also need to monitor in-year referrals to investigate the sources and reasons for Non-Contract Activity.

Independent Sector Treatment Centres (TC) are responsible for providing Admitted Patient Care and Out-Patient Attendance Commissioning Data Sets and may submit this data on their own behalf or via a third party. Other Independent Sector activity for NHS PATIENTS is the responsibility of the NHS commissioning body for the provision of the appropriate central returns and data sets.

The Department of Health requires accurate data of all PATIENTS admitted to or treated as out-patients, or treated as an Accident and Emergency Attendance by NHS Hospital Providers and Primary Care Trusts, including PATIENTS receiving private treatment. The data also includes NHS PATIENTS treated electively in the independent sector and overseas. These Hospital Episode Statistics (HES) are derived from the Admitted Patient Care, Out-Patient Attendance and Accident and Emergency Attendance Commissioning Data Sets as stored in the Secondary Uses Service. This data provides information about hospital and PATIENT management, epidemiological data on PATIENT DIAGNOSES and OPERATIVE PROCEDURES.

Referral To Treatment Clock Stop Administrative Events may also flow using the CDS V6 Type 020 - Outpatient CDS.Referral To Treatment Clock Stop Administrative Events may also flow using the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set. This allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity.

Commissioning Data Set Data Flow Definitions

CDS TYPES

The Commissioning Data Set is the basic structure used for the submission of commissioning data to the Secondary Uses Service and is designed to be capable of individually conveying many different Commissioning Data Set structures encompassing Accident and Emergency Attendances, Out-Patient Attendances, Future Attendances, Admitted Patient Care and Elective Admission List data etc.

Commissioning Data Set Messages have been defined in specific components known as a CDS TYPE. Each Commissioning Data Set Type as configured into the Commissioning Data Set Message carries only one specific Commissioning Data Set Type, an examples being the Finished Consultant Episode Commissioning Data Set Type etc.

top


REFERRAL TO TREATMENT CLOCK STOP ADMINISTRATIVE EVENT

Change to Supporting Information: Changed Description

Data Set Change Notice 18/2006 published in December 2006, defined essential new data items required to support the measurement of 18 week REFERRAL TO TREATMENT PERIODS (monitoring of DH PSA target 13 - "By 2008, no one will have to wait longer than 18 weeks from GP referral to hospital treatment"). In particular, the Data Set Change Notice 18/2006 introduced the following new data items.

Strategic reporting of 18 weeks will be undertaken by the Secondary Uses Service using data obtained via the Commissioning Data Sets . The new data items defined in Data Set Change Notice 18/2006 are enabled to flow in Commissioning Data Set versions 6-1 and 6-2, and will continue to flow in subsequent versions.

However, an event which results in an update to the REFERRAL TO TREATMENT PERIOD STATUS may occur outside the events that are defined in the Commissioning Data Sets (typically Outpatient or Inpatient encounters) and will therefore not flow to the Secondary Uses Service. These types of events have been termed as "administrative events". They can be defined as any communication event between the Health Care Provider and the PATIENT that occurs outside of an outpatient attendance or inpatient admission and that results in the PATIENT's REFERRAL TO TREATMENT PERIOD STATUS being changed to stop the 18 week clock. These events are not face to face consultations and do not necessarily involve clinical staff.

These Referral To Treatment Clock Stop Administrative Events may be carried using the Commissioning Data Set Type 020 Outpatient record type. They are differentiated from PATIENT contact ACTIVITY by the FIRST ATTENDANCE value carried within them. FIRST ATTENDANCE national code 5 "Referral to treatment clock stop administrative event" signifies that an ACTIVITY has taken place which has ended the REFERRAL TO TREATMENT PERIOD and changed the REFERRAL TO TREATMENT PERIOD STATUS to one of the following:

When to Use Referral To Treatment Clock Stop Administrative Events

These events may happen because:

Secondary Uses Service Processing

The Secondary Uses Service currently processes the following Commissioning Data Set record types in order to build Referral To Treatment pathways.

All other types are not currently processed and so if they carry the  REFERRAL TO TREATMENT PERIOD END DATE for a REFERRAL TO TREATMENT PERIOD, a Referral To Treatment Clock Stop Administrative Event must also be sent in order to inform the Secondary Uses Service of the clock stop.

Note that future versions of the Secondary Uses Service will also process:

The dates when ORGANISATIONS submitting REFERRAL TO TREATMENT PERIOD data to the Secondary Uses Service can cease having to also send a Referral To Treatment Clock Stop Administrative Event when a clock stop is carried in one of the Elective Admission List Commissioning Data Set Types, will be notified as part of the Secondary Uses Service release documentation. It is also anticipated that CDS V6-2 Type 021 - Future Outpatient CDS will be processed once piloting is complete and its use is approved by the Information Standards Board for Health and Social Care. A cancelled future APPOINTMENT record could carry a REFERRAL TO TREATMENT PERIOD Clock Stop. Again the timescales will be notified as part of the Secondary Uses Service release documentation.

There are no current plans for the Secondary Uses Service to process the remaining Commissioning Data Set Types:

This is the because a Referral To Treatment Clock Stop Administrative Event occurring in the scenarios where these record types are generated, would be rare. However this will be reviewed as part of the ongoing maintenance of the Referral To Treatment Clock Stop Administrative Event, and the requirements for the Secondary Uses Service.

When NOT to Use a Referral To Treatment Clock Stop Administrative Event

The Referral To Treatment Clock Stop Administrative Event should NOT be used to correct previously submitted records where a REFERRAL TO TREATMENT PERIOD END DATE was submitted incorrectly to the Secondary Uses Service.

For example, if an Out-Patient Appointment took place where First Definitive Treatment was started, but the REFERRAL TO TREATMENT PERIOD END DATE was not sent in the corresponding CDS V6-2 Type 020 - Outpatient Commissioning Data Set record as it was not entered on the Patient Administration System until later; then the CDS V6-2 Type 020 - Outpatient Commissioning Data Set record should be resubmitted with the correct data.For example, if an Out-Patient Appointment took place where First Definitive Treatment was started, but the REFERRAL TO TREATMENT PERIOD END DATE was not sent in the corresponding CDS V6-1 Type 020 - Outpatient Commissioning Data Set/ CDS V6-2 Type 020 - Outpatient Commissioning Data Set record as it was not entered on the Patient Administration System until later; then the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set record should be resubmitted with the correct data. A Referral To Treatment Clock Stop Administrative Event should NOT be used.

Where an ORGANISATION's Patient Administration System supports the submission of cancelled and Did Not Attend appointments in the CDS V6-2 Type 020 - Outpatient Commissioning Data Set, the Referral To Treatment Clock Stop Administrative Event should NOT be used when a PATIENT has a booked Out-Patient Appointment, which is then cancelled because, for example, the PATIENT dies. In these cases the CDS V6-2 Type 020 - Outpatient Commissioning Data Set can carry the details of a cancelled CARE ACTIVITY, including the REFERRAL TO TREATMENT PERIOD END DATE and update to the REFERRAL TO TREATMENT PERIOD STATUS.Where an ORGANISATION's Patient Administration System supports the submission of cancelled and Did Not Attend appointments in the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set, the Referral To Treatment Clock Stop Administrative Event should NOT be used when a PATIENT has a booked Out-Patient Appointment, which is then cancelled because, for example, the PATIENT dies. In these cases the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set can carry the details of a cancelled CARE ACTIVITY, including the REFERRAL TO TREATMENT PERIOD END DATE and update to the REFERRAL TO TREATMENT PERIOD STATUS. (Note - not all Patient Administration Systems provide functionality to create and submit Commissioning Data Set records for cancellations/Did Not Attend's as this is not yet mandated - you should contact your Patient Administration System support team to ascertain whether your Patient Administration System supports this. If not, then it is permissible to send a Referral To Treatment Clock Stop Administrative Event in order to stop the clock in the Secondary Uses Service instead).

Referral To Treatment Clock Stop Administrative Events only require a sub-set of the data elements contained in the CDS V6-1 Type 020 - Outpatient Commissioning Data Set / CDS V6-2 Type 020 - Outpatient Commissioning Data Set record, to be submitted to the Secondary Uses Service. All other data elements not listed should be omitted from the XML submission of the CDS V6 Type 020 - Outpatient CDS record to the Secondary Uses Service. All other data elements not listed should be omitted from the XML submission of the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set record to the Secondary Uses Service. The submission of a Referral To Treatment Clock Stop Administrative Event is not reliant on the use of the Net Change Commissioning Data Set Submission Protocol to the Secondary Uses Service

The required data elements making up a Referral To Treatment Clock Stop Administrative Event are:

Data Element Required

Notes

UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) or PATIENT PATHWAY IDENTIFIERThe Commissioning Data Set Schema versions 6-1-1 and 6-2 require EITHER the PATIENT PATHWAY IDENTIFIER, or the UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) to be populated.
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER)If the UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) is used, the ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) should contain X09 (which relates to the Choose and Book system)
REFERRAL TO TREATMENT STATUS (CDS V6-1) or REFERRAL TO TREATMENT PERIOD STATUS (CDS V6-2)This should contain only one of the following codes to signify that the REFERRAL TO TREATMENT PERIOD has ended:
WAITING TIME MEASUREMENT TYPE (CDS V6-2 only)This item is XML mandatory in the CDS V6-2 schema (but is not present in the CDS V6-1 schema).
REFERRAL TO TREATMENT PERIOD START DATE  
REFERRAL TO TREATMENT PERIOD END DATE  
NHS NUMBER  

NHS NUMBER STATUS INDICATOR (CDS V6-1) or NHS NUMBER STATUS INDICATOR CODE (CDS V6-2)

 
POSTCODE OF USUAL ADDRESS  
ORGANISATION CODE (PCT OF RESIDENCE) (CDS V6-1 only) 
ORGANISATION CODE (RESIDENCE RESPONSIBILITY) (CDS V6-2 only) 
FIRST ATTENDANCE  (CDS V6-1) or FIRST ATTENDANCE CODE (CDS V6-2)This should always hold the National code 5 - "Referral to Treatment Period Clock Stop Administrative Event"
APPOINTMENT DATEThis field is XML mandatory in Commissioning Data Set Schema versions 6-1-1 and 6-2 for Type 020 Outpatients, and for the purposes of the Referral To Treatment Clock Stop Administrative Event, should hold the same date as the REFERRAL TO TREATMENT PERIOD END DATE 
AGE AT CDS ACTIVITY DATE This field is XML mandatory in the Commissioning Data Set Schema versions 6-1-1 and 6-2 for Type 020 Outpatients, and should hold the PATIENTS age at REFERRAL TO TREATMENT PERIOD END DATE
ORGANISATION CODE (CODE OF PROVIDER)This field is not XML mandatory in the Commissioning Data Set version 6-1-1 schema but is required by the Secondary Uses Service for processing of all records.  It is XML mandatory in the CDS V6-2 schema
ORGANISATION CODE (CODE OF COMMISSIONER) This field is not XML mandatory in the Commissioning Data Set version 6-1-1 schema but is required by the Secondary Uses Service for processing of all records.  It is XML mandatory in the CDS V6-2 schema

top


FIRST ATTENDANCE

Change to Attribute: Changed Description

This indicates whether a PATIENT is making a first attendance or contact; or a follow-up attendance or contact.

National Codes:

1First attendance face to face
2Follow-up attendance face to face
3First telephone or telemedicine consultation
4Follow-up telephone or telemedicine consultation
5Referral To Treatment Clock Stop Administrative Event*

 

*Referral to Treatment Clock Stop Administrative Event allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity. It flows through the CDS V6 Type 020 - Outpatient CDS structure. It flows through the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set structure. See Referral To Treatment Clock Stop Administrative Event.

 

top


APPOINTMENT DATE

Change to Data Element: Changed Description

Format/Length:See DATE 
HES Item: 
National Codes: 
Default Codes: 

Notes:
APPOINTMENT DATE is the same as attribute APPOINTMENT DATE.

Usage in the CDS:
The Outpatient and Future Outpatient CDS Types use the APPOINTMENT DATE as the "CDS ORIGINATING DATE" as a mandatory requirement of the CDS Exchange Protocol, see CDS ACTIVITY DATE.

For the Future Outpatient CDS where no APPOINTMENT DATE is available from the healthcare system, a default date value of 2999-12-31 may be applied.

Care must be taken to generate the correct CDS Exchange Protocol when using this default value.

When submitting a Referral To Treatment Clock Stop Administrative Event via the CDS V6 Type 020 - Outpatient CDS, APPOINTMENT DATE is equivalent to the REFERRAL TO TREATMENT PERIOD END DATE carried in the record.When submitting a Referral To Treatment Clock Stop Administrative Event via the CDS V6-1 Type 020 - Outpatient Commissioning Data Set/CDS V6-2 Type 020 - Outpatient Commissioning Data Set, APPOINTMENT DATE is equivalent to the REFERRAL TO TREATMENT PERIOD END DATE carried in the record.

 

top


CDS RECORD IDENTIFIER

Change to Data Element: Changed Description

Format/Length:an35
HES Item: 
National Codes: 
Default Codes: 

Notes:
CDS RECORD IDENTIFIER may also be referred to as the CDS-RID.

When exchanging Commissioning Data Set data, this is an optional data element and when used is a unique number generated by the sender and inserted into the Commissioning Data Set data to enable senders and recipients to be able to cross-match and uniquely identify each and every Commissioning Data Set record.

The CDS RECORD IDENTIFIER consists of the following components:

REFRID COMPONENTFORMATCODES / VALUES
1CDS SENDER IDENTITY an5As generated in the CDS V6-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol or the CDS V6-2 Type 005N - CDS Transaction Header Group - Net Change Protocol 
1CDS SENDER IDENTITY an5As generated in the CDS V6-1 Type 005B - Commissioning Data Set Transaction Header Group - Bulk Update Protocol/CDS V6-2 Type 005B - CDS Transaction Header Group - Bulk Update Protocol or the CDS V6-1 Type 005N - Commissioning Data Set Transaction Header Group - Net Change Protocol/CDS V6-2 Type 005N - CDS Transaction Header Group - Net Change Protocol 
2Not Usedan2Set = Blank
3CDS INTERCHANGE CONTROL REFERENCE an14
(n7) *
As generated in the CDS V6-2 Type 001 - CDS Interchange Header 
4CDS MESSAGE REFERENCE an14
(n7) *
As generated in the CDS V6-2 Type 003 - CDS Message Header 
3CDS INTERCHANGE CONTROL REFERENCE an14
(n7) *
As generated in the CDS V6-1 Type 001 - CDS Interchange Header/CDS V6-2 Type 001 - CDS Interchange Header 
4CDS MESSAGE REFERENCE an14
(n7) *
As generated in the CDS V6-1 Type 003 - CDS Message Header/CDS V6-2 Type 003 - CDS Message Header 

* This data item is configured as an14 format element, but a maximum value of 9999999 is permitted in the format of n7.

Usage:

The CDS-RID is an optional reference assigned to each record by the Commissioning Data Set sender to aid the identification and cross-referencing of data between the sender and the receiver(s) of the Commissioning Data Set data.

CDS-XML Interchanges:

The CDS-RID data element is carried in the CDS Message Header (CDS V6-2 Type 003 - CDS Message Header).The CDS-RID data element is carried in the CDS Message Header (CDS V6-1 Type 003 - CDS Message Header/CDS V6-2 Type 003 - CDS Message Header). 

top


DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE

Change to Data Element: Changed Description

Format/Length:See DATE 
HES Item:CENDATE
National Codes: 
Default Codes: 

Notes:
DETAINED AND (OR) LONG TERM PSYCHIATRIC CENSUS DATE is the date at which the Psychiatric Census of Detained and/or Long-Term PATIENTS is held.

The CDS V6 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census CDS must be submitted annually to the Secondary Uses Service using a date of 31 March for the year of the census.The CDS V6-1 Type 170 - Admitted Patient Care - Detained and/or Long Term Psychiatric Census Commissioning Data Set/CDS V6-2 Type 170 - Admitted Patient Care - Detained and or Long Term Psychiatric Census Commissioning Data Set must be submitted annually to the Secondary Uses Service using a date of 31 March for the year of the census.

See the CDS Mandated Data Flows for further information.

By local agreement, other submissions may be made and where this is undertaken, the date chosen must also be compatible with the CDS Submission Protocol used.

 

top


FIRST ATTENDANCE

Change to Data Element: Changed Description

Format/Length:n1
HES Item: 
National Codes:See FIRST ATTENDANCE
Default Codes: 

Notes:
FIRST ATTENDANCE indicates whether a PATIENT is making a FIRST ATTENDANCE or follow-up attendance or contact and whether the CONSULTATION MEDIUM USED national code was 'Face to face communication', 'Telephone' or 'Telemedicine web camera'.

A FIRST ATTENDANCE is the first in a series, or only attendance of an APPOINTMENT which took place regardless of how many previous APPOINTMENTS were made which did not take place for whatever reason. All subsequent attendances in the series which take place should be recorded as follow-up.

FIRST ATTENDANCE National Code 5 - "Referral to Treatment Clock Stop Administrative Event" allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity. It flows through the CDS V6 Type 020 - Outpatient CDS structure. It flows through the CDS V6-1 Type 021 - Future Outpatient CDS structure. See Referral To Treatment Clock Stop Administrative Event.

FIRST ATTENDANCE will be replaced with FIRST ATTENDANCE CODE, which should be used for all new and developing data sets and for XML messages.

 

top


FIRST ATTENDANCE CODE

Change to Data Element: Changed Description

Format/Length:an1
HES Item: 
National Codes:See FIRST ATTENDANCE
Default Codes: 

Notes:
FIRST ATTENDANCE CODE is the same as attribute FIRST ATTENDANCE.

FIRST ATTENDANCE CODE indicates whether a PATIENT is making a FIRST ATTENDANCE or follow-up attendance or contact and whether the CONSULTATION MEDIUM USED national code was 'Face to face communication', 'Telephone' or 'Telemedicine web camera'.

A FIRST ATTENDANCE is the first in a series, or only attendance of an APPOINTMENT which took place regardless of how many previous APPOINTMENTS were made which did not take place for whatever reason. All subsequent attendances in the series which take place should be recorded as follow-up.

FIRST ATTENDANCE National Code 5 - "Referral to Treatment Clock Stop Administrative Event" allows the Secondary Uses Service to build accurate PATIENT PATHWAYS for the reporting of 18 weeks activity. It flows through the CDS V6 Type 020 - Outpatient CDS structure. It flows through the CDS V6-2 Type 020 - Outpatient CDS structure. See Referral To Treatment Clock Stop Administrative Event.

FIRST ATTENDANCE CODE replaces FIRST ATTENDANCE, and should be used for all new and developing data sets and for XML messages.

 

top


ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER)

Change to Data Element: Changed Description

Format/Length:max an5
National Codes: 
Default Codes: 

Notes:
ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) is the same as attribute ORGANISATION CODE.

ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) is  the ORGANISATION CODE of the ORGANISATION issuing the PATIENT PATHWAY IDENTIFIER

Where Choose and Book has been used, the ORGANISATION CODE for NHS Connecting For Health (X09) should be used.

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then ORGANISATION CODE (PATIENT PATHWAY IDENTIFIER ISSUER) must be present in the Commissioning Data Set PATIENT PATHWAY Data Group. 

 

top


PATIENT PATHWAY IDENTIFIER

Change to Data Element: Changed Description

Format/length:an20
National Codes: 
Default Codes: 

Notes:
PATIENT PATHWAY IDENTIFIER is the same as PATIENT PATHWAY IDENTIFIER.

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then either UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) or PATIENT PATHWAY IDENTIFIER must be present in the Commissioning Data Set PATIENT PATHWAY Data Group. 

 

top


PATIENT USUAL ADDRESS (MOTHER)

Change to Data Element: Changed Description

top


REFERRAL TO TREATMENT PERIOD END DATE

Change to Data Element: Changed Description

Format/Length:See DATE 
HES Item: 
National Codes: 
Default Codes: 

Notes:
REFERRAL TO TREATMENT PERIOD END DATE is the same as attribute REFERRAL TO TREATMENT PERIOD END DATE.

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then REFERRAL TO TREATMENT PERIOD END DATE must be present in the Commissioning Data Set PATIENT PATHWAY Data Group, where the REFERRAL TO TREATMENT PERIOD has ended.

 

top


REFERRAL TO TREATMENT PERIOD START DATE

Change to Data Element: Changed Description

Format/Length:See DATE 
HES Item: 
National Codes: 
Default Codes: 

Notes:
REFERRAL TO TREATMENT PERIOD START DATE is the same as attribute REFERRAL TO TREATMENT PERIOD START DATE.

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then REFERRAL TO TREATMENT PERIOD START DATE must be present in the Commissioning Data Set PATIENT PATHWAY Data Group. 

 

top


REFERRAL TO TREATMENT PERIOD STATUS

Change to Data Element: Changed Description

Format/Length:an2
HES Item: 
National Codes:See REFERRAL TO TREATMENT PERIOD STATUS 
Default Codes: 

Notes:
REFERRAL TO TREATMENT PERIOD STATUS is the same as attribute REFERRAL TO TREATMENT PERIOD STATUS.

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then REFERRAL TO TREATMENT PERIOD STATUS must be present in the Commissioning Data Set PATIENT PATHWAY Data Group. 

REFERRAL TO TREATMENT PERIOD STATUS replaces REFERRAL TO TREATMENT STATUS and should be used for all new and developing data sets and for XML messages.

 

top


REFERRAL TO TREATMENT STATUS

Change to Data Element: Changed Description

Format/Length:n2
HES Item: 
National Codes:See REFERRAL TO TREATMENT PERIOD STATUS 
Default Codes: 

Notes:
REFERRAL TO TREATMENT STATUS is the same as attribute REFERRAL TO TREATMENT PERIOD STATUS.

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then REFERRAL TO TREATMENT STATUS must be present in the Commissioning Data Set PATIENT PATHWAY Data Group. 

REFERRAL TO TREATMENT STATUS will be replaced with REFERRAL TO TREATMENT PERIOD STATUS, which should be used for all new and developing data sets and for XML messages.

 

top


UNIQUE BOOKING REFERENCE NUMBER (CONVERTED)

Change to Data Element: Changed Description

Format/Length:n12
HES Item: 
National Codes: 
Default Codes: 

Notes:
UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) is the same as attribute UNIQUE BOOKING REFERENCE NUMBER (CONVERTED).

Use in Commissioning Data Set version 6-0 onwards

If the Commissioning Data Set record relates to a Referral To Treatment Period Included In Referral To Treatment Consultant-Led Waiting Times Measurement, and is of the following Commissioning Data Set Types:

then either UNIQUE BOOKING REFERENCE NUMBER (CONVERTED) or PATIENT PATHWAY IDENTIFIER must be present in the Commissioning Data Set PATIENT PATHWAY Data Group. 

 

top


For enquiries about this Change Request, please email datastandards@nhs.net