NHS Information Authority
Data & Information Standards Programme
Reference: | Change Request 410 |
Version No: | 1.10 |
Subject: | Removal of CMDS from the NHS Data Dictionary |
Type of Change: | Changes to NHS Data Dictionary and NHS CDS Manual |
Effective Date: | 1 March 2004 |
Reason for Change: | The 3 CMDS referenced by the NHS Data Dictionary are either obsolete or have been superseded by the existing CDS |
Background:
Support of standard national data flows requires the 3 CMDS in the NHS Data Dictionary to be removed. They are either obsolete, in the case of the GP Referral Letter CMDS, or have been superseded by the existing CDS in the case of the Elective Admission List (EAL) CMDS.
These changes will be implemented in the NHS Data Dictionary in due course. This will coincide with the uploading of the EAL CDS Types from the NHS CDS Manual, which will be the subject of a future DSCN.
Summary of changes:
Data Elements | |
Change to Description | |
Change to Description | |
Change to Description | |
Change to Description | |
Change to Description | |
Change to Description | |
Data Sets (CDS, CMDS, HES) | |
Deleted | |
Deleted | |
Deleted | |
Diagrams | |
Deleted | |
Deleted | |
Deleted | |
Supporting Information | |
Change to Name | |
Change to Name | |
Change to Supporting Information | |
Change to Supporting Information | |
Change to Name | |
Change to Supporting Information | |
Deleted | |
Deleted | |
Deleted | |
Deleted | |
Change to Supporting Information | |
Change to Supporting Information | |
Change to Supporting Information | |
Change to Supporting Information | |
Change to Supporting Information | |
Change to Supporting Information | |
Change to Supporting Information |
Name: | Kevin Shine |
Date: | 3 June 2004 |
Sponsor: | Data and Information Standards Programme |
Note: Additions shown in highlighted with a blue background. Deletions are shown using strikeout. Within the Diagrams deleted classes and relationships are shown as red in colour, blue is used for changed items and green is used for created items.
COUNT OF DAYS SUSPENDED
Change to Data Element: Change to Description
Format/length: | n4 |
HES item: | |
National Codes: | |
Default Codes: | 9998 - Not applicable |
9999 - Not known |
Notes:
This data element is also known by these names:
Context | Alias |
---|---|
plural | COUNT OF DAYS SUSPENDED |
DATE STATUS
Change to Data Element: Change to Description
Format/length: | n1 |
HES item: | |
National Codes: | |
Default Codes: |
Notes:
1 | Date supplied |
8 | Date not applicable |
9 | Date not known |
This data element is also known by these names:
Context | Alias |
---|---|
plural | DATE STATUS |
GMP (CODE OF REGISTERED OR REFERRING GMP)
Change to Data Element: Change to Description
Format/length: | an8 |
HES item: | REGGMP |
National Codes: | |
Default Codes: | G9999998 - GP code is unknown |
G9999981 - No registered GP | |
R9999981 - Referrer other than GMP, GDP or Consultant | |
Other GP Codes | |
A9999998 - MOD doctor refers | |
P9999981 - Prison doctor |
Notes:
A doctor receives a GMC number on qualification. If he/she then chooses to enter general practice, a further number is allocated - the GMP code - by the Department of Health (STATS(W)). This number is passed to the PRIMARY CARE TRUST (PCT) requesting the number who then liaise with the Prescription Pricing Authority (PPA) on the issue of prescription pads etc. The code of the GMP linked to his/her main practice is included on the Organisation Codes Service (OCS) CD-ROM.
The GMP code is an eight character alphanumeric code, see NHS Administrative Codes - Practitioner Codes, PERSON IDENTIFIER and PERSON IDENTIFIER TYPE.
When a locum refers, use the code of the GP for whom the locum is acting. See PERSON IDENTIFIER TYPE classification 'Code of General Practitioner - PPA Code'.
For GPs working in hospitals, the following codes should be used:
- | if the GP is working as an assistant, use the code of the responsible consultant; |
- | if the GP is working as a consultant, use the GP's GMC code. |
Whilst both MOD and prison doctors provide general medical services to their communities, they are not GMPs and should not be recorded as Registered GMPs. They can refer (Referrer code).
This data element is also known by these names:
Context | Alias |
---|---|
plural | GMP (CODE OF REGISTERED OR REFERRING GMPS) |
INTENDED PROCEDURE
Change to Data Element: Change to Description
Format/length: | an4 for OPCS-4, an7 for Clinical Terms (The Read Codes) |
HES item: | |
National Codes: | |
Default Codes: |
Notes:
This is the INTENDED PATIENT PROCEDURE. Up to three INTENDED PROCEDURESS may be included in the CMDS to give commissioners an indication of the procedures for which a resident is waiting so that they can be costed and linked to other events. Up to three INTENDED PROCEDURES may be included in the CDS to give commissioners an indication of the procedures for which a resident is waiting so that they can be costed and linked to other events. To complete this field, use the first three character set of OPCS-4 (or four characters, if agreed locally). Clinical Terms (The Read Codes) can be used as an optional addition. Some operations involving minimal access surgery may require two codes to identify them.
This data element is also known by these names:
Context | Alias |
---|---|
plural | INTENDED PROCEDURES |
INTENDED PROCEDURE (OPCS)
Change to Data Element: Change to Description
Format/length: | an4 |
HES item: | |
National Codes: | |
Default Codes: |
Notes:
See INTENDED PROCEDURE for details on coding.
This is an intended procedure recorded for CMDS purposes. This is an intended procedure recorded for CDS purposes. Up to a maximum of 3 intended procedures can be reported.
The procedure is as recorded by CLINICAL INTERVENTION DATE of an INTENDED PATIENT PROCEDURES. The procedure is as recorded by CLINICAL INTERVENTION DATE of an INTENDED PATIENT PROCEDURE.
This data element is also known by these names:
Context | Alias |
---|---|
plural | INTENDED PROCEDURES (OPCS) |
cds_1 | INTENDED PROCEDURE 2 (OPCS) |
cds_2 | INTENDED PROCEDURE 3 (OPCS) |
INTENDED PROCEDURE (READ)
Change to Data Element: Change to Description
Format/length: | an7 |
HES item: | |
National Codes: | |
Default Codes: |
Notes:
See INTENDED PROCEDURE for details on coding.
This is an intended procedure recorded for CMDS purposes. This is an intended procedure recorded for CDS purposes. Up to a maximum of 3 intended procedures can be reported.
This data element is also known by these names:
Context | Alias |
---|---|
plural | INTENDED PROCEDURES (READ) |
cds_1 | INTENDED PROCEDURE 2 (READ) |
cds_2 | INTENDED PROCEDURE 3 (READ) |
ELECTIVE ADMISSION LIST CMDS-END OF PERIOD CENSUS
Change to Data Set (CDS, CMDS, HES): Deleted
Deleted
ELECTIVE ADMISSION LIST CMDS-EVENT DURING PERIOD
Change to Data Set (CDS, CMDS, HES): Deleted
Deleted
GP REFERRAL LETTER CMDS
Change to Data Set (CDS, CMDS, HES): Deleted
Deleted
CMDS010 COMMISSIONING DETAILS AND SERVICE ARRANGEMENT CHANGE DETAILS - ELECTIVE ADMISSION LIST CMDS
Change to Diagram: Deleted
Deleted
CMDS020 ELECTIVE ADMISSION LIST, SUSPENSION, OFFER OF ADMISSION AND REMOVAL DETAILS - ELECTIVE ADMISSION LIST CMDS
Change to Diagram: Deleted
Deleted
CMDS030 GP REFERRAL LETTERS CMDS
Change to Diagram: Deleted
Deleted
CDS CMDS DIAGRAMS MENU
Change to Supporting Information: Change to Name
CDS CMDS Diagrams Menu
CDS Middle Pane
CDS CMDS+HES SECURITY ISSUES-IMPORTANT SECURITY ISSUES AND OTHER NOTES
Change to Supporting Information: Change to Name
CDS CMDS+HES Security Issues-IMPORTANT SECURITY ISSUES AND OTHER NOTES
CDS+HES Security Issues-IMPORTANT SECURITY ISSUES AND OTHER NOTES
CDS CMDS+HES SECURITY ISSUES-IMPORTANT SECURITY ISSUES AND OTHER NOTES renamed CDS+HES SECURITY ISSUES-IMPORTANT SECURITY ISSUES AND OTHER NOTES
Change to Supporting Information: Change to Supporting Information
IMPORTANT SECURITY ISSUES AND OTHER NOTES
IMPORTANT SECURITY ISSUES AND OTHER NOTES
A. Removal of name and address where the NHS Number is present
-
From 1 April 1999, PATIENT NAME and PATIENT USUAL ADDRESS (not POSTCODE OF USUAL ADDRESS) must be removed from all commissioning data sets where a valid NHS NUMBER is present. This applies to all nationally defined Commissioning Data Sets Types (CDS) and Commissioning Minimum Data Sets (CMDS) and any additional locally agreed flows from service providers to commissioning bodies.
-
A valid NHS NUMBER is one that has passed the check digit calculation on entry into the source system. If an NHS NUMBER is not valid (i.e. does not conform with the check digit algorithm) then PATIENT NAMES and PATIENT USUAL ADDRESS should not be removed, as the reliability of the NHS NUMBER will not be known.
-
TheNHS NUMBER STATUS INDICATORis a mandatory part of the CMDS. PATIENT NAMES and PATIENT USUAL ADDRESS should be removed when a valid NHS NUMBER is present, even if the NHS Number Status Indicator does not have a status of 01,Number present and verified.
-
The NHS NUMBER STATUS INDICATOR is a mandatory part of the CDS. PATIENT NAMES and PATIENT USUAL ADDRESS should be removed when a valid NHS NUMBER is present, even if the NHS Number Status Indicator does not have a status of 01, Number present and verified.
-
Following the recommendations of the Data Protection Registrar, Providers should not recordMARITAL STATUSin any CDS Type/CMDS, except in respect of the psychiatric specialities in the Admitted Patient Care CDS Types, where it will continue to be recorded.
B. Marital Status
-
Following the recommendations of the Data Protection Registrar, Providers should not record MARITAL STATUS in any CDS Type, except in respect of the psychiatric specialities in the Admitted Patient Care CDS Types, where it will continue to be recorded.
-
The Human Fertilisation and Embryology Act 1990 as amended by the Human Fertilisation and Embryology (Disclosure of Information) Act 1992 imposes statutory restrictions on the disclosure of information about identifiable individuals in connection with certain infertility treatments. A list of the relevant codes is given in the table below. In these cases the NHS NUMBER,LOCAL PATIENT IDENTIFIER, PATIENT NAMES, POSTCODE OF USUAL ADDRESS andBIRTH DATEshould be omitted from the CDS Types and CMDS.
C. Sensitive data
-
The Human Fertilisation and Embryology Act 1990 as amended by the Human Fertilisation and Embryology (Disclosure of Information) Act 1992 imposes statutory restrictions on the disclosure of information about identifiable individuals in connection with certain infertility treatments. A list of the relevant codes is given in Table 1. In these cases the NHS NUMBER, LOCAL PATIENT IDENTIFIER, PATIENT NAMES, POSTCODE OF USUAL ADDRESS and BIRTH DATE should be omitted from the CDS Types.
-
Other statutory restrictions on the disclosure of patient information do not prohibit the disclosure to individuals involved with the treatment and prevention of certain specific diseases (HIV/AIDS and venereal diseases) in the population.
-
All records containing patient identifiable information, other than those covered by the Human Fertilisation & Embryology Acts, as outlined in the Table above, should be treated as sensitive. Organisations may continue to exchange records containing NHS NUMBER, POSTCODE OF USUAL ADDRESS and BIRTH DATE in these cases, but receiving organisations must ensure that only those staff with legitimate need have access to this information, e.g. public health departments, and strictly on a need to know basis. No-one should have unrestricted access unless fully justified in accordance with the principles of the Caldicott Committee Report.
TABLE OF TREATMENTS PROVIDED UNDER THE LICENCE OF THE HUMAN FERTILISATION AND EMBRYOLOGY AUTHORITY TABLE 1: TREATMENTS PROVIDED UNDER THE LICENCE OF THE HUMAN FERTILISATION AND EMBRYOLOGY AUTHORITY
Description | OPCS-4 | ICD-10 |
---|---|---|
Standard In Vitro Fertilisation (IVF) | Q13.-1 Introduction of gamete into uterine cavity, or Q38.3 Endoscopic intrafallopian transfer of gamete |
Z31.2 In vitro fertilization |
IVF with donor sperm | Q13.- 1 Introduction of gamete into uterine cavity, or Q38.3 Endoscopic intrafallopian transfer of gamete |
Z31.2 In vitro fertilization |
IVF with donor eggs | Q13.-1 Introduction of gamete into uterine cavity, or Q38.3 Endoscopic intrafallopian transfer of gamete |
Z31.2 In vitro fertilization |
Donor insemination (DI) | Q13.3 Intrauterine artificial insemination, or Q13.2 Intracervical artificial insemination |
Z31.1 Artificial insemination |
Gamete intrafallopian transfer (GIFT) with donor sperm | Q38.3 Endoscopic intrafallopian transfer of gamete | Z31.3 Other assisted fertilization methods |
Gamete intrafallopian transfer (GIFT) with donor eggs | Q38.3 Endoscopic intrafallopian transfer of gamete | Z31.3 Other assisted fertilization methods |
Intracytoplasmic sperm injection (ICSI) | ||
Sub-zonal insemination (SUZI) | ||
Zygote intrafallopian transfer (ZIFT) | Q38.3 Endoscopic intrafallopian transfer of gamete | Z31.2 In vitro fertilization |
Partial Zona Dissection (PZD) | ||
Zona drilling | ||
Hamster- egg penetration test | ||
Assisted hatching | ||
Pre-implantation Genetic Diagnosis (PGD) | ||
Storage of sperm | ||
Storage of embryos | ||
Use and storage of testicular tissue | ||
Transport/satellite IVF/ICSI | ||
Embryo donation | Z31.8 Other procreative management | |
Research |
1.- means all fourth characters of this rubric should be included.
-
Where patient level data is required for other purposes within an organisation, it should be anonymised/aggregated prior to disclosure by someone with legitimate access. If this is not practicable, local protocols defining which CDS Types/CMDS are particularly sensitive (including, but not necessarily restricted to HIV/AIDS and venereal disease) agreed by the organisation Caldicott Guardian, should be put in place and identifiers stripped from these records.
-
Where patient level data is required for other purposes within an organisation, it should be anonymised/aggregated prior to disclosure by someone with legitimate access. If this is not practicable, local protocols defining which CDS Types are particularly sensitive (including, but not necessarily restricted to HIV/AIDS and venereal disease) agreed by the organisation Caldicott Guardian, should be put in place and identifiers stripped from these records.
-
Your Caldicott Guardian will be able to advise you further on all issues relating to patient confidentiality.
-
Where appropriate, further information about confidentiality is contained within the notes for individual data items.
CDS CMDS DIAGRAMS MENU renamed CDS MIDDLE PANE
Change to Supporting Information: Change to Supporting Information
- Introduction
- Diagramming Conventions
- CDS Diagrams
CMDS Diagrams- [DELETED]
CDS CMDS HES MENU
Change to Supporting Information: Change to Name
CDS CMDS HES Menu
CDS HES Middle Pane
CDS CMDS HES MENU renamed CDS HES MIDDLE PANE
Change to Supporting Information: Change to Supporting Information
Contextual OverviewImportant Security Issues and Other NotesCDS Type ListCMDS Type ListHES Cross Reference Tables
Important Security Issues and Other Notes
CDS Type List
HES Cross Reference Tables
CMDS DIAGRAMS
Change to Supporting Information: Deleted
Deleted
CMDS TYPE LIST
Change to Supporting Information: Deleted
Deleted
CMDS TYPE LIST NAVIGATION
Change to Supporting Information: Deleted
Deleted
CMDS VIEW DIAGRAM ENTITY DEFINITION
Change to Supporting Information: Deleted
Deleted
DATA FIELD NOTES INTRODUCTION
Change to Supporting Information: Change to Supporting Information
Data Elements Introduction
Data Elements Introduction
Data elements are used to identify or indicate the content of:
i. | the Commissioning Data Sets (CDS) |
ii. | the Hospital Episode Statistics (HES) |
iii. | the Central Returns |
In addition, data elements can contain text providing guidance, support, values or other information concerning the data element and its use with the above.
The data elements are listed in alphabetical order. Click on a letter in the Data Element Bookmarks to display the list of data element names for that letter. Click on a letter in the Data Element Bookmarks to display the list of data element names for that letter in the right hand screen frame. To display the content of a specific data element, click on the data element name. The content of the data element replaces the list of data element names in the rightmost screen frame.
Each attribute name, class name or data element name which appears in the data element content text is in uppercase. Where the name also appears in blue, this indicates that it is clickable and if clicked on will display the definition for that class or attribute, or the content of the data element. In the same way, if a data link is present and clicked on, the definition of the class or attribute will be displayed. Where the name also appears in blue and is underlined indicates that it is clickable and if clicked on will display the definition for that class or attribute, or the content of the data element. In the same way, if a data button is present and clicked on, the definition of the class or attribute will be displayed.
The following information may be shown within a data element:
Data button | A data button indicates that a class or attribute definition exists with the same name. Click on the button to display the class or attribute definition. When no button is present, the data element itself is either a derived item which is derivable from classes and/or attributes or only exists as a data element. |
Format/length: | An entry in this field defines the format and length of the data element, the following conventions are used for format: a is alphabetic characters only n is numeric characters only an is alphanumeric i.e. alphabetic and numeric characters allowed The number following the format code indicates the field length of the data element, e.g. an3 has a field length of three alphanumeric characters. |
HES item: | An entry in this field indicates that the data element is used by HES and is identified by the entered name e.g. data element BIRTH DATE has a HES item name of DOB. If the field is blank, the data element is not used by HES. |
An entry in this field indicates that the National Codes or classifications exist for the data element (usually as an attribute but occasionally as an class type) and describes how to view them e.g. Press Definition tab for the National Codes or Press Definition tab for the Classifications. If there are no agreed National Codes or classifications for the data element, the field is blank. A National Code has nationally agreed values for each code which must be used in conjunction with the data element whereas for a classification, the classifications will be nationally agreed but will have no nationally agreed values assigned to them. Usually for classifcations, the values to be used in conjunction with the data element will be contained within Notes: content e.g. see AGE GROUP INTENDED. |
|
Default Codes: | An entry in this field indicates that in addition to the nationally agreed National Codes or classifications, default codes may be used. These default codes only appear within data elements and are not nationally agreed data standards i.e. they are not supported by an class or attribute definition. The following formats for default codes may be used: Not known coded as 99 (2-digit codes) and 9 (1-digit code) Not applicable coded as 98 (2-digit codes) and 8 (1-digit code) This general rule however, is not totally consistent. For some data elements, code 8 has been assigned a meaning other than Not applicable e.g. DELIVERY PLACE TYPE (ACTUAL). Such exceptions are indicated within the Notes: content. |
Notes: | Provides guidance, support, values or other information concerning the data element and its usage. Any attribute name, class name or data element name which appears in the Notes text is in uppercase. Where the name also appears in blue indicates that it is clickable and if clicked on will display the definition for that class or attribute, or the content of the data element. |
National Codes: | An entry in this field indicates that the National Codes or classifications exist for the data element (usually as an attribute but occasionally as an class type) and describes how to view them e.g. Press Definition button for the National Codes or Press Definition button for the Classifications. If there are no agreed National Codes or classifications for the data element, the field is blank. A National Code has nationally agreed values for each code which must be used in conjunction with the data element whereas for a classification, the classifications will be nationally agreed but will have no nationally agreed values assigned to them. Usually for classifications, the values to be used in conjunction with the data element will be contained within Notes: content e.g. see AGE GROUP INTENDED. |
Default Codes: | An entry in this field indicates that in addition to the nationally agreed National Codes or classifications, default codes may be used. These default codes only appear within data elements and are not nationally agreed data standards i.e. they are not supported by an class or attribute definition. The following formats for default codes may be used: Not known coded as 99 (2-digit codes) and 9 (1-digit code) Not applicable coded as 98 (2-digit codes) and 8 (1-digit code) This general rule however, is not totally consistent. For some data elements, code 8 has been assigned a meaning other than Not applicable e.g. DELIVERY PLACE TYPE (ACTUAL). Such exceptions are indicated within the Notes: content. |
Notes: | Provides guidance, support, values or other information concerning the data element and its usage. Any attribute name, class name or data element name which appears in the Notes text is in uppercase. Where the name also appears in blue and is underlined indicates that it is clickable and if clicked on will display the definition for that class or attribute, or the content of the data element. |
DIAGRAMS MENU
Change to Supporting Information: Change to Supporting Information
- Model View Diagrams
- Central Return Diagrams
CDS and CMDS Diagrams- CDS Diagrams
- Data Set Diagrams
GN030
Change to Supporting Information: Change to Supporting Information
GN030 - NHS SERVICE AGREEMENTS
-
This diagram illustrates NHS commissioning agreements, including OUT OF AREA TREATMENTS.
-
A NHS SERVICE AGREEMENT is a formal agreement between a commissioning ORGANISATION and one or more HEALTH CARE PROVIDERS for the provision of patient care services.
-
In circumstances when care or treatment is provided to a PATIENT where there is no NHS SERVICE AGREEMENT between the HEALTH CARE PROVIDER and the ORGANISATION responsible for commissioning the PATIENT's care or treatment, it will be covered by an OUT OF AREA TREATMENT.
-
Normally each SERVICE will relate to only one NHS SERVICE AGREEMENT but there will be occasions where, for instance, a SERVICE comprising a HOSPITAL PROVIDER SPELL (see GN040), will relate to more than one NHS SERVICE AGREEMENT. In this case, there would be more than one SERVICE PROVIDED UNDER AGREEMENT for the HOSPITAL PROVIDER SPELL.
-
NHS SERVICE AGREEMENT CHANGE and NHS SERVICE AGREEMENT CHANGE DETAIL are used when there is a change from an existing NHS SERVICE AGREEMENT to a different NHS SERVICE AGREEMENT for an ELECTIVE ADMISSION LIST ENTRY.
-
A SERVICE PROVIDED UNDER AGREEMENT may be related to one or moreNHS SERVICE AGREEMENT LINES. NHS SERVICE AGREEMENT LINES are non-mandatory data within the CMDS.
-
A SERVICE PROVIDED UNDER AGREEMENT may be related to one or more NHS SERVICE AGREEMENT LINES. NHS SERVICE AGREEMENT LINES are non-mandatory data within the CDS.
-
A SERVICE may be provided at a number of SERVICE PROVISION POINTS each one being a particular SERVICE POINT.
LOCATION TYPE CODES
Change to Supporting Information: Change to Supporting Information
LOCATION TYPE CODES
-
The codes enable the classification of LOCATION TYPE. This is the type of physical location where patients are seen or where services are provided or from which requests for services are sent.
-
Each LOCATION must be classified by one, and only one, LOCATION TYPE, i.e. once a building (or department or unit within that building) has been allocated a specific LOCATION TYPE, that LOCATION TYPE should be used by all users regardless of the type of activity, specialty or client group involved. The LOCATION TYPE should only be altered if there is a complete change in use.
-
Note that the term Professional Staff Group refers to health professional staff and covers Chiropody, Clinical Psychology, Dietetics, Occupational Therapy, Physiotherapy and Speech and Language Therapy.
-
Tables 1 to 3 gives the groupings used on the following Central Returns:
-
Note that the leading zero of Location Type Code should be omitted for use with the cdstab/CMDS.
KC56: Patient Care in the Community: District Nursing
KC57: Patient Care in the Community: Community Psychiatric Nursing
KC58: Patient Care in the Community: Learning Disability Nursing
-
Note that the leading zero of Location Type Code should be omitted for use with the cdstab/CDS.
Location Type Codes
Code | Description |
---|---|
001 | Client's or Patient's Home |
002 | Health Centre |
003 | Other GMP Premises |
004 | Ward on NHS Hospital Site |
006 | Hospice |
007 | Other Voluntary or Private Hospital or Nursing Home |
008 | Group Home managed by the NHS |
009 | Group Home managed by Local Authority |
010 | Group Home managed by Voluntary or Private Agents |
011 | Other Residential Care Homes managed by Local Authority |
012 | Other Residential Care Homes managed by Voluntary or Private Agents |
013 | NHS Day Care Facility on NHS Hospital Site |
014 | NHS Day Care Facility on Other Sites |
015 | Day Centre managed by Local Authority |
016 | Day Centre managed by Voluntary or Private Agents |
017 | NHS Consultant Clinic Premises on a NHS Hospital site |
018 | NHS Consultant Clinic Premises off a NHS Hospital site |
019 | Health Clinic managed by the NHS |
020 | Health Clinic managed by Voluntary or Private Agents |
021 | Resource Centre on NHS Hospital Site |
022 | Resource Centre managed by the NHS off NHS Hospital Site |
023 | Resource Centre managed by Local Authority |
024 | Resource Centre managed by Voluntary or Private Agents |
025 | Professional Staff Group Department on NHS Hospital Site |
026 | Professional Staff Group Department managed by the NHS off NHS Hospital Site |
027 | Professional Staff Group Department managed by Local Authority |
028 | Professional Staff Group Department managed by Voluntary or Private Agents |
029 | School Premises managed by Local Authority or Grant Maintained |
030 | School Premises managed by Voluntary or Private Agents |
031 | Other Health or Local Authority Facility on NHS Hospital Site |
032 | Other Health or Local Authority Site managed by the NHS off NHS Hospital Site |
033 | Other Health or Local Authority Site managed by Local Authority |
034 | Other Health or Local Authority Site managed by Voluntary or Private Agents |
035 | Prison Department Establishments |
036 | Public Place or Street, or Police Station |
037 | Other locations not classified elsewhere |
038 | NHS Nursing Home |
039 | Other Residential Care Homes managed by the NHS |
Location Type Codes-Table 1
Location Type Codes-Table 2
MESSAGES MENU
Change to Supporting Information: Change to Supporting Information
CDS, CMDS and HES:- CDS and HES:
- Contextual Overview
- Important Security Issues and Other Notes
- CDS Type List
CMDS Type List- HES Cross Reference Tables
- XML Messages:
- Introduction
- e-GIF Types
- XML Message Sets are still in development
THE NHS DATA DICTIONARY ELEMENTS
Change to Supporting Information: Change to Supporting Information
THE NHS DATA DICTIONARY ELEMENTS
The NHS Data Dictionary and the NHS Data Manual were originally published separately. The elements of both these publications have been consolidated into one browsable integrated publication called the NHS Data Dictionary.NHS Data Standards
The NHS Data Dictionary gives common definitions and guidance to support the sharing, exchange and comparison of information across the NHS. The common definitions, known as data standards, are used in commissioning and make up the base currency of Commissioning Data Sets (CDS). On the monitoring side, they support comparative data analysis, preparation of performance tables, and data returned to the Department of Health. NHS data standards also support clinical messages, such as those used for pathology and radiology. NHS data standards are presented as a logical data model, ensuring that the standards are consistent and integrated across all NHS business areas.
NHS data standards should not just be seen as supporting the collection of data on a consistent basis throughout the NHS. They also have an important role in supporting the flow and quality of information used in different parts of the NHS so that health care professionals are presented with the relevant information where and when it is required. An example of this is the linking of all records about a patient collected in different parts of the NHS, to be available to a health care professional wherever the patient attends to be seen for treatment, thus facilitating the Electronic Patient Record. Changes to NHS data standards are still being published as Data Set Change Notices (DSCNs) at the time of publication. The NHS Information Standards Board may eventually use a different form of change notification, but the principles of regulated changes will still apply.
See the
The NHS Data Dictionary Elements
Class Definitions | All the classes that appear within the NHS data standards logical data model. Each class contains its nationally agreed definition, all of its attributes, all relationships it has with other classes and a clickable button if a data element also exists for it. |
Attribute Definitions | All the attributes of the classes that appear within the NHS data standards logical data model. Each attribute contains its nationally agreed definition which may also include its agreed National Codes or classifications and a clickable button if a data element also exists for it. |
Data Elements | Data elements which may be supported by an class or attribute definition i.e the data element has the same name as an class or attribute, be a derived item which is derivable from classes and/or attributes or only exists as a data element. Data elements are used in completion of CDS, HES and Central Returns. The data element information comprises format and field length, HES name if applicable, National Codes or classifications and useful notes clarifying the selected data element. |
Model View Diagrams | The NHS data standards logical data model is too large to be represented in just one diagram showing all the defined classes and their relationships. Consequently the data model has been split into a number of separate diagrams, each representing a sub-set of the whole data model. Each diagram is referred to as a Model View and they are individually named and grouped by functional area heading. |
Central Return Diagrams | The NHS data standards logical data model includes all the classes, attributes and relationships necessary to support the information required for Central Returns to ensure that returned information is consistent. A Central Return is represented by a diagram which contains the class types and their relationships which are required to support it. The Central Return Diagrams are grouped by functional area heading. |
CDS View Diagrams | The NHS data standards logical data model includes the Commissioning Data Set (CDS); all of which cannot be represented in just one diagram. Consequently the sub-set of the data model which supports the CDS has been split into a number of separate diagrams each representing a specific CDS Type. Each CDS Type view is represented by a diagram which contains the classes and their relationships which are required to support it. |
CDS and HES | Guidance on completion of Commissioning Data Sets (CDS). Hospital Episode Statistics (HES) for information purposes (HES is now extracted automatically from the NHS-wide Clearing Service database). |
Central Return Forms | Guidance on completion of Central Returns for hospital activity, complaints management process, cervical and breast screening activity, patient transport and some community activity. |
Supporting Information | Supporting information such as clinical coding, organisation codes etc., is provided to help users understand the CDS and Central Returns. |
WHAT ARE CDS VIEW DIAGRAMS-INTRODUCTION
Change to Supporting Information: Change to Supporting Information
Introduction
What are CDS View Diagrams
Introduction
What are CDS View Diagrams?
The NHS data standards logical data model supports the Commissioning Data Sets (CDS). This is too large to be represented in a single diagram. Consequently the sub-set of the data model which supports the CDS has been split into a number of separate diagrams each representing a specific CDS Type. Each CDS Type view is represented by a diagram which contains the classes and their relationships which are required to support it. Not all items of information required by a CDS Type are defined classes or attributes but instead are derived by combining values of attributes or totalling attributes where particular conditions apply. The classes from which such information is derived or calculated will be shown on the CDS View diagrams. Not all items of information required by a CDS Type are defined classes or attributes but instead are derived by combining values of attributes or totalling attributes where particular conditions apply, The classes from which such information is derived or calculated will be shown on the CDS View diagrams.
What are CMDS View Diagrams
The Commissioning Minimum Data Sets (CMDS) are a set of nationally agreed data items which support the commissioning process in the NHS. The Commissioning Data Sets (CDS) have been developed to carry the CMDS data in a structured EDIFACT message format. To overcome various differences between the CMDS and CDS, it was agreed to consolidate both CMDS and CDS to reflect a single national data standard for commissioning data to be known as the Consolidated Commissioning Data Sets. This title has been shortened to Commissioning Data Sets. Wherever the term Commissioning Data Set or CDS appears in this publication it has the meaning of the single national data standard. The change to the consolidated Commissining Data Sets has therefore replaced and eliminated most usage of the original Commissioning Minimum Data Sets (CMDS). There are however, two Commissioning Minimum Data Sets (CMDS) which as yet have not been aligned to the equivalent CDS as they are still subject of review, these two CMDSs are:
ELECTIVE ADMISSION LIST CMDS: End of Period CensusELECTIVE ADMISSION LIST CMDS: Event During Period
The NHS data standards logical data model supports the two remaining Commissioning Minimum Data Sets (CMDSs). Each CMDS view is represented by a diagram which contains the classes and their relationships which are required to support it. Not all items of information required by a CMDS are defined classes or attributes but instead are derived by combining values of attributes or totalling attributes where particular conditions apply. The classes from which such information is derived or calculated will be shown on the CMDS View diagrams.
A class may occur in more than one CDS View diagram and can be identified by using the Entities to Diagrams Where Used. This lists the class names in alphabetical order cross-referenced to the CDS View diagrams in which they appear.
Nicola Spendlove