mhmds v4.0 interim mapping guidance v1.2
TRANSCRIPT
Mental Health Minimum Dataset (MHMDS)MHMDS v4.0 Interim Mapping Guidance
Purpose of this document
Document Version History
Version Date Issued Brief Summary of Change Owner’s Name
1.0 5/23/2011 Final version for publication
1.1 5/25/2011
1.2 6/14/2011
IMPORTANT
This document should be read in conjunction with the corresponding User Guidance and Information Standards Notice ISN ISB 87/2010
Mental Health and Community Care Team
The NHS Information Centre for Health and Social Care1 Trevelyan SquareBoar LaneLeeds, LS1 6AE
Tel: 0845 300 6016
E-mail: [email protected]
Date of Issue 6/14/2011Reference
Copyright © 2011 The NHS Information Centre
The purpose of this document is an interim aid to help NHS Trusts and Independant Service Providers, where system changes will not be completed in time, to create the new MHMDS v4.0 submission in time for the Q1 primary 2011/12 deadline in September 2011. This guide has been provided to mitigate the risk that some organisations' systems may be not ready in time for the first submission of MHMDS v4.0 This document supports NHS Trusts and Independant Service Providers who will need to map information captured in MHMDS v3.5 to create a submission for MHMDS v4.0.
It is being issued to coincide with the release of the new version 4 Intermediate Database and could also be used to help organisations produce a sample version 4 IDB which might be used during piloting of the new arrangements for processing data, during Summer 2011.
It is not expected that organisations will need to map data from version 3.5 to version 4 for the Q1R submission in November. The new data quality reports that will be produced using Q1R submissions include a number of items that are new in version 4 and cannot be mapped from version 3.5. (Proposed new data quality measures can be found here: http://www.ic.nhs.uk/services/mhmds/quarterly).
Please note that not all information that was captured in MHMDS v3.5 can be used to create the MHMDS v4.0 submission. Trusts will need to review local collections in order to populate new tables/data items with MHMDS v4.0
Martin Hepplestone
Format added to Ethnic Category in table 1 MPIFormat change to HOURSWORK in table 3 EMPDescription for StaffID in table 12 INPATEP amended
Martin Hepplestone
11 PROVSPELL - format change to ADMMODE (n2 to an2)13 WARDSTAYS - format change to CAREINTENS (n2 to an2)13 WARDSTAYS - format change to SECUREACC (n1 to an1)13 WARDSTAYS - format change to WARDAGE (n2 to an2)16 STAFF - format change to OCCCODE (an6 to an3)19 HCPCONT - format change to LOCATION (n3 to an3)19 HCPCONT - format change to ATTENDED (n1 to an1)20 DAYATT - format change to ATTENDED (n1 to an1)35 SCT - format change to ENDREASON (n2 to an2)40 AWOL - format change to ENDREASON (n2 to an2)
Martin Hepplestone
For more information on the status of this document, please see the covering letter or contact:
Internet: www.ic.nhs.uk
Mental Health Minimum Dataset (MHMDS)MHMDS v4.0 Interim Mapping Guidance - Introduction
Introduction
The purpose of this document is to provider users of the Mental Health Minimum Dataset (MHMDS) with assurance when mapping MHMDS v3.5 to the new MHMDS v4.0.
Referrals (Table 5 - REFER)
The Referrals table (5 REFER) is a new addition in version MHMDS v4.0 and is a key component in the creation of a MHMDS record. Where activity data is sent without a referral record and/or the referral record is not open for any part of the reporting period the activity will not be processed.
There may be a number of reasons why a referral record is not available in your organisation which may include:-
• Your system is not a referral based system (a referral based system is where the system cannot record activity without it being related to a valid referral).• There is some referral functionality in your current system, but this is not system enforced or part of your organisations normal business process to use it.• There is no referral functionality at all in the current system.
In examples where you have no referral records available a possible solution is to create ‘Dummy’ referrals, the purpose of which will simply allow your activity to flow.
Example Dummy Referral
For each patient with activity create a referral record with a referral start date (REFRECDATE) of the day before the start of the current reporting period and a discharge date (DISCHDATE) of the last day in the current reporting period. This is the minimum to allow the activity to flow, and should more activity be received for the same patient in the next reporting period then this will relate to the same centrally derived ‘spell of care’.
Your local IT section may be able to provide you with a more advanced solution which has a closer relationship to the activity.
Care Programme Approach (CPA) - (Table 21 REV and Table 24 CPAEP)
Following changes to the Care Programme Approach (CPA), patients are either on CPA or not on CPA, so there is no longer a national requirement to report CPA Levels.
The Care Programme Approach Episode (CPAEP) table requires a record for all patients on CPA. In some instances records may still be coded using the old CPA Levels (Standard/Enhanced). Any patients coded as 'Enhanced' should have a record in the CPAEP table and their CPA reviews should be recorded in the REV table.
Contents
This provides a link to each mapping table for MHMDS v4.0 and provides a status as to what changes have occurred.
Key:
New Table: New table (name) introduced in MHMDS v4.0Amended: Existing table in MHMDS with amendments to existing data itemsReconfigured: Existing table in MHMDS with structural data item changes (items rearranged in alternative table)No Change: No change to a table has occurred
How to use the Document
There are 45 tabs starting with 1 MPI to 45 Seclusion each one representing a table within MHMDS v4.0.
Each table provides a summary of any changes and indicates the tables within MHMDS v3.5 from which it should be populated. Text colour represents a specific action that has occurred to a specific data item. Please see below for details:
Items marked as RED indicate this is a NEW item to MHMDS v4.0 and are new requirements for services to collectItems marked as PURPLE indicate this is a NEW item in MHMDS v4.0 (but already flow through other collections)'Items marked as BLUE indicate this is a NEW item in MHMDS v4.0 (but currently collected by services)Items marked as GREEN indicate CHANGES to existing items in MHMDS (Eg: Revised definitions or revised value lists)Items marked as BLACK indicate existing items in MHMDS remain UNCHANGED in MHMDS v4.0
Table Details
Access Name: The name of the data item within the Access database.
M/R/O: A column has been included within the table to identify whether a data item is mandatory or optional as follows:
(M) Mandatory: These data items MUST be reported. Failure to submit these items will result in the rejection of the submitted data item.(R) Required: These data items SHOULD be reported where they apply. Failure to submit these items will not result in the rejection of the submission but may affect the derivation of national indicators or national analysis.(O) Optional: Optional data items are to be used at the Trusts discretion, as they may or may not be appropriate for all services and conditions. These data items MAY be submitted on an optional basis at the submitters discretion.
Please note that these rules are applied at record level i.e. they only apply where a record is present.
Data Item Name: The name of the data item.
Definition: The definition of the data item
Format: The format of the data item to be collected. This is made up of the data type and length.
National Code: The code associated with a particular data item value.
Value Description: Any list of permissible data values associated with the data item where applicable.
Mapping Notes: This provides a decription of the data items within v3.5 this data item can be populated.
Mental Health Minimum Dataset (MHMDS)MHMDS v4.0 Interim Mapping Guidance - Contents
Table No. MHMDS v4.0 Table Name Change from MHMDS v3.5Table 1 AmendedTable 2 NewTable 3 ReconfiguredTable 4 ReconfiguredTable 5 NewTable 6 ReconfiguredTable 7 No ChangeTable 8 No ChangeTable 9 No ChangeTable 10 No ChangeTable 11 AmendedTable 12 NewTable 13 AmendedTable 14 NewTable 15 AmendedTable 16 ReconfiguredTable 17 AmendedTable 18 AmendedTable 19 ReconfiguredTable 20 No ChangeTable 21 AmendedTable 22 ReconfiguredTable 23 ReconfiguredTable 24 ReconfiguredTable 25 NewTable 26 No ChangeTable 27 No ChangeTable 28 ReconfiguredTable 29 NewTable 30 NewTable 31 NewTable 32 NewTable 33 No ChangeTable 34 AmendedTable 35 AmendedTable 36 No ChangeTable 37 ReconfiguredTable 38 No ChangeTable 39 No ChangeTable 40 No ChangeTable 41 NewTable 42 NewTable 43 NewTable 44 NewTable 45 New
Master Patient Index (MPI)Psychosis Service (PSCHOSIS)Employment Status (EMP)Accommodation Details (ACCOMM)Referral (REFER)Mental Health Team Episode (TEAMAP)NHS Day Care Episode (DAYEP)Consultant Outpatient Episode (OPEP)Acute Home-based Care Episode (HBCAREEP)Mental Health NHS Care Home Stay Episode (NHSCAREHOMEEP)Hospital Provider Spell (PROVSPELL)Inpatient Episode (INPATEP)Ward Stay within Hospital Provider Spell (WARDSTAYS)Delayed Discharge (DELAYEDDISCHARGE)Clinical Team (CLINTEAM)Staff Details (STAFF)Care Co-ordinator Assignment (CCASS)Responsible Clinician Assignment (RCASS)Health Care Professionals Contact (HCPCONT)NHS Day Care Facility Attendance (DAYATT)Review (REV)Primary Diagnosis (PRIMDIAG)Secondary Diagnosis (SECDIAG)CPA Episode (CPAEP)Crisis Plan (CRISISPLAN)Mental Health Clustering Tool (MHCT)Payment by Results Care Cluster (CLUSTER)Health of Nation Outcome Scales (Working Age Adult) - (HoNOS)Health of Nation Outcome Scales 65+ (Older Persons) - (HoNOS65+)Health of Nation Outcome Scales (Child and Adolescent) - (HoNOS-CA)Health of Nation Outcome Scales Secure (HoNOSSECURE)Patient Health Questionnaire (PHQ-9)Social Service Statutory Assessment (SSASS)Mental Health Act Event Episodes (MHAEVENT)Supervised Community Treatment (SCT)Supervised Community Treatment Recalls (SCTRECALL)Intervention (Read) - (INTERVENTION)Electro-Convulsive Therapy (ECT)Leave of Absence (LOA)Absence without Leave (AWOL)Home Leave (HOMELEAVE)Self Harm (SELFHRM)Use of Restraint (RESTRAINT)Assault on Patient (ASSAULT)Periods of Seclusion (SECLUSION)
Table 1 - MPI
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 1 - Master Patient Index
Information within the MPI table should be mapped from Table 1 MPI in v3.5
ACCESS TABLE 1 MPIACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
DOB R Person Birth Date date
SEX R an1 0 Not known
1 Male
2 Female
9 Not specified
MARSTAT R Person Marital Status an1 S SingleM Married/Civil PartnerD
W Widowed/Surviving Civil PartnerP SeparatedN Not Disclosed8
9 Not known
ETHNIC R Ethnic Category an2 WhiteA BritishB IrishC Any other White background
MixedD White and Black CaribbeanE White and Black AfricanF White and AsianG Any other mixed background
Asian or Asian BritishH IndianJ PakistaniK Bangladeshi
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date on which a person was born or is officially deemed to have been born.
Person Gender Code Current
The current gender of the Patient.
Note: The classification is phenotypical rather than genotypical, i.e. it does not provide codes for medical or scientific purposes.
An indicator to identify the legal marital status of a PERSON.
Divorced/Person whose Civil Partnership has been dissolved
Not applicable, i.e. not a psychiatric episode
NB: National code [8] Not Applicable is not appropriate for use within MHMDS.
The ethnicity of a PERSON, as specified by the PERSON. The first character of the value must be from the list below.
The second character, if present, is for local use.
Please note that Ethnic Category should be recorded for ALL patients and not only patients who have had an inpatient stay.
Table 1 - MPI
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 1 MPIACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
ETHNIC R Ethnic Category an2
L Any other Asian backgroundBlack or Black British
M CaribbeanN AfricanP Any other Black background
Other Ethnic GroupsR ChineseS Any other ethnic groupZ Not Stated99 Not Known
NHSNO R NHS Number n10
POSTCODE R an8
GPCD R an6
ORGCOM R an5
The ethnicity of a PERSON, as specified by the PERSON. The first character of the value must be from the list below.
The second character, if present, is for local use.
Please note that Ethnic Category should be recorded for ALL patients and not only patients who have had an inpatient stay.
The NHS Number, the primary identifier of a PERSON, is a unique identifier for a PATIENT within the NHS in England and Wales.
Postcode of Usual Address
The postcode of an address nominated by the patient and classified as their 'Main Permanent Residence' or 'Other Permanent Residence'
General Medical Practice Codes (Patient Registration)
The national Organisation Code of the general medical practice with which the patient is registered. The name of the practice with which the patient is registered will be contained in the initial referral or must be obtained from the patient. This name can be converted to an Organisation Code using Table 27 (General Medical Practice).
Organisation Code (Code of Commissioner)
The national Organisation Code of the Primary Care Trust (PCT) commissioning the mental health care.
Commissioning responsibility for individual Patients rests with the PCT with whom the Patient is registered. PCTs are also responsible for non-registered Patients who are resident within their boundaries. For more complicated cases and for further information relating to the Organisation Code (Code of Commissioner) please see the NHS Data Dictionary.
Organisation Code (Code of Commissioner)
Table 1 - MPI
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 1 MPIACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
FIRSTCARE O n4Year of First Known Psychiatric Care
The first year in which the patient is known to have received care from any specialist mental health service. This may have been from the same or a different provider unit. It need not have been provided in the NHS or even in the UK. This should be routinely asked as a part of clinical history taking.
Leave blank if the value cannot be determined with certainty.
Table 1 - MPI
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 1 - Master Patient Index
Information within the MPI table should be mapped from Table 1 MPI in v3.5
ACCESS TABLE 1 MPIMAPPING NOTES
This is a direct mapping of the data item 'Date of birth' in Table 1 MPI within MHMDS v3.5
This is a direct mapping of the data item 'Patient's current gender' and its associated values in Table 1 MPI within MHMDS v3.5
This is a direct mapping of the data item 'Patient's martial status' and its associated values in Table 1 MPI within MHMDS v3.5
Please note that Code [8] Not Applicable is not approriate for use in MHMDS v4.0
This is a direct mapping of the data item 'Patient's ethnic category' and its associated values in Table 1 MPI within MHMDS v3.5
Table 1 - MPI
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 1 MPIMAPPING NOTES
This is a direct mapping of the data item 'Patient's ethnic category' and its associated values in Table 1 MPI within MHMDS v3.5
This is a direct mapping of the data item 'Patient's NHS number' in Table 1 MPI within MHMDS v3.5
This is a direct mapping of the data item 'Postcode of patient's normal residence' in Table 1 MPI within MHMDS v3.5
This is a direct mapping of the data item 'Organisation code of patient's registered General Medical Practice' in Table 1 MPI within MHMDS v3.5
This is a direct mapping of the data item 'Organisation Code (Code of Commissioner)' in Table 1 MPI within MHMDS v3.5
Table 1 - MPI
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 1 MPIMAPPING NOTES
This data item in v4.0 is to replace the data item 'Date of patient's first mental health treatment' in Table 1 MPI within MHMDS v3.5.
As this item was originally captured as a date field (CCYY-MM-DD) then only year part of the date (CCYY) should be mapped.
Table 2 - PSYCHOSIS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 2 - Psychosis Service
ACCESS TABLE 2 PSYCHOSISACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
PTID M an20
PROPSYCHDATE R date
EMERPSYCHDATE R date
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing these data items for local use then it is advised that the information should be submitted as specified in Table 2 PSYCHOSIS.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Prodrome Psychosis Date
Date at which first noticeable change in behaviour or mental state occurred prior to emergence of full-blown psychosis for the patient. There should be a clear deterioration in functioning from previous levels.
Examples include poor attendance/worsening performance at school/work, trouble sleeping, withdrawing from/fighting with friends/family, attenuated psychotic symptoms (increased suspiciousness,/jealously, occasionally hearing name being called when no’ ones around, whisperings, slight confusion in thinking etc.).
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Please note that the collection of this table is only applicable to services that provide an Early Intervention in Psychosis Team and should be collected currently in the FERN Database.
Emergent Psychosis Date
Date at which there was first clear evidence of a positive psychotic symptom for the patient (i.e. delusion, hallucination, or thought disorder), regardless of its duration.
Such a symptom would be scored 4 or more on the PANSS
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Please note that the collection of this table is only applicable to services that provide an Early Intervention in Psychosis Team and should be collected currently in the FERN Database.
Table 2 - PSYCHOSIS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 2 PSYCHOSISACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
MANPSYCHDATE R Manifest Psychosis Date date
PSYCHPRESCDATE R date
Date at which a positive psychotic symptom has lasted for a week for the patient. This is usually just 7 days after the date of the first psychotic symptom.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Please note that the collection of this table is only applicable to services that provide an Early Intervention in Psychosis Team and should be collected currently in the FERN Database.
Psychosis Prescription Date
Date the patient was prescribed anti-psychotic medication.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Please note that the collection of this table is only applicable to services that provide an Early Intervention in Psychosis Team and should be collected currently in the FERN Database.
Table 2 - PSYCHOSIS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 2 PSYCHOSISACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
PSYCHTREATDATE R datePsychosis Treatment Start Date
Date the patient commenced prescribed (not PRN) anti-psychotic medication and thereafter was compliant for at least 75% of the time during the subsequent month (using clinical judgement).
Note: For the majority of people this will be the same date as the date of prescription.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Please note that the collection of this table is only applicable to services that provide an Early Intervention in Psychosis Team and should be collected currently in the FERN Database.
Table 3 - EMP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 3 - Employment Status
Information within the EMP table should be mapped from Table 19 REV in v3.5
ACCESS TABLE 3 EMPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
PTID M an20
EVENTDATE M date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of employment status
The date that the patient's employment status details were recorded by the healthcare professional.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Where Services are not locally capturing an explicit date of employment status then it is advised that the data item 'Date of Review' Table 19 REV in MHMDS v3.5 where a code has been recorded/updated against the data item Employment Status of the patient.
Please note that the Date of Review may not necessarily be the date the employment status changed. Systems may capture this data item more accurately.
Table 3 - EMP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 3 EMPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
EMPSTAT R an2
01 Employed
02 Unemployed and Seeking Work
03
04
Employment Status of the patient
The current employment status of the patient at the time of their latest assessment or review.
This should be captured periodically for all patients aged 18-69, either as part of the formal Care Programme Approach (CPA) review, or other informal reviews.
This data item should be mapped from from the data item 'Employment Status of the patient' in Table 19 REV within MHMDS v3.5. Additional new values have been added to this data item in MHMDS v4.0.
Please note that code [03] Other employment status such as in education or training can not be mapped in v4.0 and codes [98] Not Applicable and [99] Not Known have been removed from MHMDS v4.0
This is a direct mapping to code [01] Employed
This is a direct mapping to code [02] Unemployed
Students who are undertaking full (at least 16 hours per week) or part-time (less than 16 hours per week) education or training and who are not working or actively seeking work
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Long-term sick or disabled, those who are receiving Incapacity Benefit, Income Support or both; or Employment and Support Allowance
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 3 - EMP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 3 EMPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
EMPSTAT R an2
05
06
07
08 Retired
ZZ
HOURSWORK O an2
01 30 + hours
02 16-29 hours
03 5-15 hours
Employment Status of the patient
The current employment status of the patient at the time of their latest assessment or review.
This should be captured periodically for all patients aged 18-69, either as part of the formal Care Programme Approach (CPA) review, or other informal reviews.
Homemaker looking after the family or home and who are not working or actively seeking work
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Not receiving benefits and who are not working or actively seeking work
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Unpaid voluntary work who are not working or actively seeking work
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Not Stated (PERSON asked but declined to provide a response)
This is a direct mapping to code [97] Not disclosed
Notes: Employed refers to those who are either employed for a company or self-employed. It should also include those who are unpaid family workers (i.e. those who do unpaid work for business they own or for a business a relative owns), as well as those who participate in a government-supported training and employment programmes.
Weekly hours worked for a patient in employment
The number of hours worked in a typical week.
This should be captured periodically in conjunction with Employment Status for all adults aged 18-69 that are in employment.
Please note that the format of an2 is not line with the MHMDS specification but it has been updated in Data Dictionary.
This is a direct mapping of the data item 'Weekly hours worked for a patient in employment' and its associated values within Table 19 REV within MHMDS v3.5
Table 3 - EMP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 3 EMPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
HOURSWORK O an2
04 1-4 hours
97 Not disclosed
98 Not applicable
99 Not known
Weekly hours worked for a patient in employment
The number of hours worked in a typical week.
This should be captured periodically in conjunction with Employment Status for all adults aged 18-69 that are in employment.
Please note that the format of an2 is not line with the MHMDS specification but it has been updated in Data Dictionary.
This is a direct mapping of the data item 'Weekly hours worked for a patient in employment' and its associated values within Table 19 REV within MHMDS v3.5
Table 4 - ACCOMM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 4 - Accommodation Details
Information within the ACCOMM table should be mapped from Table 19 REV in v3.5
ACCESS TABLE 4 ACCOMMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
PTID M an20
EVENTDATE M date
SETACC R an1 0
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of accommodation status
The date that the patient's accommodation status details were recorded by the healthcare professional.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
Where Services are not locally capturing an explicit date of employment status then it is advised that the data item 'Date of Review' Table 19 REV in MHMDS v3.5 where a code has been recorded/updated against the data item Employment Status of the patient.
Please note that the Date of Review may not necessarily be the date the employment status changed. Systems may capture this data item more accurately.
Settled Accommodation Indicator for the patient
An indication of whether the main/permanent residence of the patient is settled or non-settled accommodation.
This should be captured periodically as part of a formal Care Programme Approach (CPA) review or other informal review or assessment. The current Settled Accommodation Indicator should be agreed by the care worker/coordinator and the client. Carers should also have an input where appropriate.
Notes: Accommodation should be classified as either Settled or Non-Settled in accordance with PSA Delivery Agreement 16 (Social Exclusion) Technical Definitions and Guidance available on the Cabinet Office website:
www.cabinetoffice.gov.uk
Non-settled. Accommodation that is precarious, or where the person has no or low security of tenure/residence in their usual accommodation and so may be required to leave at very short notice.
This is a direct mapping of the data item 'Settled Accommodation Indicator for the patient' and its associated values in Table 19 REV within MHMDS v3.5.
Table 4 - ACCOMM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 4 ACCOMMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
SETACC R an1
1
7 Not disclosed8 Not applicable9 Not known
ACCSTAT O an4 MA00 Mainstream HousingMA01 Owner occupierMA02
MA03
MA04
MA05 Tenant - Housing AssociationMA06 Tenant - private landlordMA09 Other mainstream housingHM00 HomelessHM01 Rough sleeperHM02 SquattingHM03
HM04
HM05
HM06
HM07 Other homelessMH00
Settled Accommodation Indicator for the patient
An indication of whether the main/permanent residence of the patient is settled or non-settled accommodation.
This should be captured periodically as part of a formal Care Programme Approach (CPA) review or other informal review or assessment. The current Settled Accommodation Indicator should be agreed by the care worker/coordinator and the client. Carers should also have an input where appropriate.
Notes: Accommodation should be classified as either Settled or Non-Settled in accordance with PSA Delivery Agreement 16 (Social Exclusion) Technical Definitions and Guidance available on the Cabinet Office website:
www.cabinetoffice.gov.uk
This is a direct mapping of the data item 'Settled Accommodation Indicator for the patient' and its associated values in Table 19 REV within MHMDS v3.5.
Settled. Secure, medium to long term accommodation where the occupier, or head of household, has security of tenure/residence in their usual accommodation in the medium to long term.
Accommodation Status of the patient
The current accommodation status of the patients main or permanent residence.
This should be captured periodically as part of a formal Care Programme Approach (CPA) review or other informal review or assessment.
This is a direct mapping of the data item 'Accommodation Status of the patient' and its associated values in Table 19 REV within MHMDS v3.5.
Settled mainstream housing with family/friends
Shared ownership scheme e.g. Social Homebuy Scheme (tenant purchase percentage of home value from landlord)
Tenant - Local Authority/Arms Length Management Organisation/Registered Landlord
Night shelter/emergency hostel/Direct access hostel (temporary accommodation accepting self referrals, no waiting list and relatively frequent vacancies)
Sofa surfing (sleeps on different friends floor each night)
Placed in temporary accommodation by Local Authority (including Homelessness resettlement service) e.g. Bed and Breakfast accommodation
Staying with friends/family as a short term guest
Accommodation with mental health care support
Table 4 - ACCOMM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 4 ACCOMMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
ACCSTAT O an4
MH01
MH02
MH03
MH04 Mental Health Registered Care Home
MH09
HS00
HS01 NHS acute psychiatric wardHS02 Independent hospital/clinicHS03 Specialist rehabilitation/recoveryHS04 Secure psychiatric unitHS05 Other NHS facilities/hospitalHS09
CH00
CH01
CH02 RefugeCH03
CH09
CJ00
CJ01 Bail/Probation hostelCJ02 PrisonCJ03 Young Offenders InstitutionCJ04 Detention CentreCJ09
Accommodation Status of the patient
The current accommodation status of the patients main or permanent residence.
This should be captured periodically as part of a formal Care Programme Approach (CPA) review or other informal review or assessment.
This is a direct mapping of the data item 'Accommodation Status of the patient' and its associated values in Table 19 REV within MHMDS v3.5.
Supported accommodation (accommodation supported by staff or resident caretaker)
Supported lodgings (lodgings supported by staff or resident caretaker)
Supported group home (supported by staff or resident caretaker)
Other accommodation with mental health care and support
Acute/long stay healthcare residential facility/hospital
Other Acute/long stay healthcare residential facility/hospital
Accommodation with other (not specialist mental health) care support
Foyer - accommodation for young people aged 16-25 who are homeless or in housing need
Non-Mental Health Registered Care Home
Other accommodation with care and support (not specialist mental health)
Accommodation with criminal justice support
Other accommodation with criminal justice support such as ex-offender support
Table 4 - ACCOMM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 4 ACCOMMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION MAPPING NOTES
ACCSTAT O an4
SH00
SH01 Sheltered housing for older persons
SH02
SH03 Nursing Home for older personsSH09 Other sheltered housingML00 Mobile accommodation
Other codesOC96 Not elsewhere classifiedOC97 Not specifiedOC98 Not applicableOC99 Not known
Accommodation Status of the patient
The current accommodation status of the patients main or permanent residence.
This should be captured periodically as part of a formal Care Programme Approach (CPA) review or other informal review or assessment.
This is a direct mapping of the data item 'Accommodation Status of the patient' and its associated values in Table 19 REV within MHMDS v3.5.
Sheltered Housing (accommodation with a scheme manager or warden living on the premises or nearby, contactable by an alarm system if necessary)
Extra care sheltered housing (also known as 'very sheltered housing'. For people who are less able to manage on their own, but who do need an extra level of care. Services offered vary between schemes, but meals and some personal care are often provided.)
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 5 - Referral
ACCESS TABLE 5 REFERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
REFRECDATE M date
REFERRAL R Source of initial referral
Primary Health CareA1A2
A3 Other Primary Health Care
Self ReferralB1 SelfB2 Carer
Local Authority ServicesC1 Social ServicesC2 Education Service
Employer
Information within the REFER table should be mapped from Table 19 REV in v3.5
Please see 'Introduction' tab for further details about the new referrals table and how to create a dummy referral if required.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Referral Request Received Date
The date that the referral was received by the Healthcare Provider.
For both electronic and written referral requests the date that the request was received should be used and NOT the date that the referral was read, processed, or actioned i.e. the date stamped as the date of receipt and not the date entered onto a system. For referral requests received by telephone use the date of the follow up letter if received, otherwise the date of the phone call.
A classification which identifies the source of referral of a Mental Health Care Spell.
an2
GENERAL MEDICAL PRACTITIONERHealth Visitor
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
REFERRAL R Source of initial referral
D1 EmployerJustice System
E1 PoliceE2 CourtsE3 Probation ServiceE4 Prison
E5 Court Liaison and Diversion Service
Child HealthF1
F2 Hospital-based Paediatrics
F3 Community-based Paediatrics
Independent/Voluntary SectorG1
G2
G3
G4 Voluntary Sector
Acute Secondary Care
A classification which identifies the source of referral of a Mental Health Care Spell.
an2
School Nurse
Independent sector - Medium Secure Inpatients
Independent Sector - Low Secure Inpatients
Other Independent Sector Mental Health Services
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
REFERRAL R Source of initial referral
H1
H2 Other secondary care specialty
Other Mental Health NHS TrustI1
I2
J1
J2
J3
J4
K1 Inpatient Service (Adult Mental Health)
K2 Inpatient Service (Older People)
K3 Inpatient Service (Forensics)
A classification which identifies the source of referral of a Mental Health Care Spell.
an2
Accident And Emergency Department
Temporary transfer from another Mental Health NHS Trust
Permanent transfer from another Mental Health NHS Trust
Internal referrals from Community Mental Health Team (within own NHS Trust)
Community Mental Health Team (Adult Mental Health)
Community Mental Health Team (Older People)
Community Mental Health Team (Learning Disabilities)
Community Mental Health Team (Child and Adolescent Mental Health)
Internal referrals from Inpatient Service (within own NHS Trust)
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
REFERRAL R Source of initial referral
K4
K5
L1
L2
OtherM1 Asylum Services
M2 NHS Direct
M3 Out of Area Agency
M4
M5 Jobcentre Plus
M6 Other service or agencyEVENTDATE O date
A classification which identifies the source of referral of a Mental Health Care Spell.
an2
Inpatient Service (Child and Adolescent Mental Health)
Inpatient Service (Learning Disabilities)
Transfer by graduation (within own NHS Trust)
Transfer by graduation from Child and Adolescent Mental Health Services to Adult Mental Health Services
Transfer by graduation from Adult Mental Health Services to Older Peoples Mental Health Services
Drug Action Team / Drug Misuse Agency
Referral Request Status Date
The date that the referral status of the patient was updated by the mental health provider.
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
REFSTATUS R an2 Accepted
01 Accepted for immediate action02
Not Accepted
03
04
Closed05 Patient declined to be treated06 Patient Died
DISCHDATE R date
END R an2
01Discharged on professional advice
02
Status of Service Request (Mental Health)
The status of a referral request for the patient received by the mental healthcare provider.
Accepted and placed on appointment waiting list
Service request passed back to referrer
Service request redirected to another agency
Date of discharge from mental health service
The date that the patient was discharged from the mental health service.
Discharge From Mental Health Service Reason
The reason that a patient was discharged from the mental health service.
Discharged against professional advice
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
END R an2
03PATIENT non-attendance
04
05
06
08
PATIENT moved out of the area
09 PATIENT died
Discharge From Mental Health Service Reason
The reason that a patient was discharged from the mental health service.
Transferred to other Health Care Provider Medium Secure Unit
Transferred to other Health Care Provider High Secure Unit
Transferred to other Health Care Provider not Medium/High Secure
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 5 - Referral
ACCESS TABLE 5 REFERMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please see 'Introduction' tab for further details about the new referrals table and how to create a dummy referral if required.
This data item should be mapped from from the data item 'Source of initial referral' in Table 19 REV within MHMDS v3.5.
Please note that there are a large number of additional values which have been added to this data item in v4.0.
This is a direct mapping to code [00] GPNew Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [01] Self
This is a direct mapping to code [08] Carer
This is a direct mapping to code [02] LA Social Services
This is a direct mapping to code [05] Education Service
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERMAPPING NOTES
This is a direct mapping to code [04] Employer
This is a direct mapping to code [06] Police
This is a direct mapping to code [09] Courts
This is a direct mapping to code [10] Probation serviceNew Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERMAPPING NOTES
This is a direct mapping to code [03] A & E department
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [20] Temporary transfer from another mental health unit
This is a direct mapping to code [21] Permanent transfer from another mental health unit
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERMAPPING NOTES
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [22] Transfer by graduation from local child and adolescent mental health services
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [13] OtherThis is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it should be mapped.
Where Services are not locally capturing an explicit date of discharge from mental health service then it is advised that the data item 'Date of Review' Table 19 REV in MHMDS v3.5 where a code has been recorded/updated against the data item date of discharge from mental health service.
Please note that the Date of Review may not necessarily be the date of discharge from mental health service changed. Systems may capture this data item more accurately.
Also note that where multiple referrals have been sent for the same patient the 'Date of discharge from mental health service' must be recorded against each referral to allow the date of discharge to be accepted.
Please see 'Introduction' tab for further details about the new referrals table and how to create a dummy referral if required.
This data item should be mapped from the data item 'Method of Termination' in Table 19 REV within MHMDS v3.5.
Please note that there is an additional value 'Patient moved out of the area' and that value names have changed in v4.0.
This is a direct mapping to code [00] Finished on professional advice
This is a direct mapping to code [01] Finished against professional advice
Table 5 - REFER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 5 REFERMAPPING NOTES
This is a direct mapping to code [02] Finished by patient's non-attendance
This is a direct mapping to code [21] Transfer to medium-secure unit
This is a direct mapping to code [23] Transfer to high-secure unit
This is a direct mapping to code [25] Transfer to other health provider
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [03] Patient died
Table 6 - TEAMEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 6 - Mental Health Team Episode
Information within the TEAMEP table should be mapped from Table 2 CEP and Table 9 PGEP in v3.5
ACCESS TABLE 6 TEAMEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M The start date of a mental health team episode. date
ENDDATE R The end date of a mental health team episode. date
CLINTEAM R Unique Team ID an10
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start Date of Team Episode
End Date of Team Episode
A unique code used locally to identify the team.
NB. Please ensure that there is a corresponding record within the CLINTEAM table for every Unique Team ID. Unique Team IDs are required to derive the Team Type but are not included in any MHMDS extracts.
Table 6 - TEAMEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 6 - Mental Health Team Episode
Information within the TEAMEP table should be mapped from Table 2 CEP and Table 9 PGEP in v3.5
ACCESS TABLE 6 TEAMEPMAPPING NOTES
This is a direct mapping of the data items 'Start Date of Community Episode' in Table 2 CEP and 'Start Date of a Professional Staff Episode' in Table 9 PGEP within MHMDS v3.5.
This is a direct mapping of the data items 'End Date of Community Episode' in Table 2 CEP and 'End Date of a Professional Staff Episode' in Table 9 PGEP within MHMDS v3.5.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 7 - DAYEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 7 - NHS Day Care Episode
Information within the DAYEP table should be mapped from Table 3 DAYEP in v3.5
ACCESS TABLE 7 DAYEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M The start date of an NHS Day Care episode date
ENDDATE R The end date of an NHS Day Care episode date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start date of NHS Day care episode
End date of NHS Day care episode
Table 7 - DAYEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 7 - NHS Day Care Episode
Information within the DAYEP table should be mapped from Table 3 DAYEP in v3.5
ACCESS TABLE 7 DAYEPMAPPING NOTES
This is a direct mapping of the data item 'Start date of NHS Day Care episode' in Table 3 DAYEP within MHMDS v3.5
This is a direct mapping of the data item 'End date of NHS Day Care episode' in Table 3 DAYEP within MHMDS v3.5
Table 8 - OPEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 8 - Consultant Outpatient Episode
Information within the OPEP table should be mapped from Table 8 OPEP in v3.5
ACCESS TABLE 8 OPEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M The start date of a Consultant Outpatient episode. date
ENDDATE R The end date of a Consultant Outpatient episode. date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start date of Consultant Outpatient Episode
End date of Consultant Outpatient Episode
Table 8 - OPEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 8 - Consultant Outpatient Episode
Information within the OPEP table should be mapped from Table 8 OPEP in v3.5
ACCESS TABLE 8 OPEPMAPPING NOTES
This is a direct mapping of the data item 'Start date of consultant outpatient episode' in Table 8 OPEP within MHMDS v3.5
This is a direct mapping of the data item 'End date of consultant outpatient episode' in Table 8 OPEP within MHMDS v3.5
Table 9 - HBCAREEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 9 - Acute Home-based Care Episode
Information within the HBCAREEP table should be mapped from Table 4 HBCAREEP in v3.5
ACCESS TABLE 9 HBCAREEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
ENDDATE R The end date of an Acute Home-Based Treatment episode. date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start date of acute home-based treatment episode
The start date of an Acute Home-Based Treatment episode.
End date acute home-based treatment episode
Table 9 - HBCAREEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 9 - Acute Home-based Care Episode
Information within the HBCAREEP table should be mapped from Table 4 HBCAREEP in v3.5
ACCESS TABLE 9 HBCAREEPMAPPING NOTES
This is a direct mapping of the data item 'Start date of acute home-based treatment episode' in Table 4 HBCAREEP within MHMDS v3.5
This is a direct mapping of the data item 'End date of acute home-based treatment episode' in Table 4 HBCAREEP within MHMDS v3.5
Table 10 - NHSCAREHOMEEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 10 - Mental Health NHS Care Home Stay Episode
Information within the NHSCOMBEDEP table should be mapped from Table 7 NHSCOMBEDEP in v3.5
ACCESS TABLE 10 NHSCAREHOMEEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
ENDDATE R date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start date of MH NHS community care episode
The start date of a Mental Health NHS Community Care episode.
End date MH NHS community care episode
The end date of a Mental Health NHS Community Care episode.
Table 10 - NHSCAREHOMEEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 10 - Mental Health NHS Care Home Stay Episode
Information within the NHSCOMBEDEP table should be mapped from Table 7 NHSCOMBEDEP in v3.5
ACCESS TABLE 10 NHSCAREHOMEEPMAPPING NOTES
This is a direct mapping of the data item 'Start date of MH NHS Community care episode' in Table 7 NHSCOMBEDEP within MHMDS v3.5
This is a direct mapping of the data item 'End date of MH NHS Community care episode' in Table 7 NHSCOMBEDEP within MHMDS v3.5
Table 11 - PROVSPELL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 11 - Hospital Provider Spell
Information within the PROVSPELL table should be mapped from Table 5 IPEP in v3.5
ACCESS TABLE 11 PROVSPELLACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M This will be the admission date of the patient to hospital date
ENDDATE R This will be the discharge date of the patient from hospital date
ADMMODE R Admission method an2
Elective Admission11 Waiting list
12 Booked
13 Planned
Emergency admission
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start date of hospital provider spell
End date of hospital provider spell
The method of admission to a Hospital Provider Spell. A detailed definition of Elective Admission is given in ELECTIVE ADMISSION TYPE.
Table 11 - PROVSPELL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 11 PROVSPELLACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
ADMMODE R Admission method an2
21
22
23 Bed bureau
24
25
28
Other Admission81
The method of admission to a Hospital Provider Spell. A detailed definition of Elective Admission is given in ELECTIVE ADMISSION TYPE.
Accident and emergency, or dental casualty department of the Health Care Provider
General Practitioner after a request has been made direct to the Health Care Provider (i.e. not through a bed bureau) by a General Practitioner or deputy
Consultant clinic of this or another Health Care Provider
Admission via Mental Health Crisis Resolution Team
Other means including admission through the accident and emergency department of another Health Care Provider
Transfer of any admitted patient from other hospital provider other than in an emergency. This does not include admissions to high security psychiatric hospitals
Table 11 - PROVSPELL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 11 PROVSPELLACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
DISMETH R Discharge Method The method of discharge from a Hospital Provider Spell an1 1
2
3
4 Patient died5 Stillbirth 8
9 Not known
Patient discharged on clinical advice or with clinical consent
Patient discharged him/herself or was discharged by a relative or advocate
Patient discharged by mental health review tribunal, Home Secretary or court
Not applicable - hospital provider spell not finished (ie not discharged)
NB: National code [5] Still birth is not appropriate for use within MHMDS
Table 11 - PROVSPELL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 11 - Hospital Provider Spell
Information within the PROVSPELL table should be mapped from Table 5 IPEP in v3.5
ACCESS TABLE 11 PROVSPELLMAPPING NOTES
This is a direct mapping of the data item 'Start date of hospital provider spell' in Table 5 IPEP within MHMDS v3.5
This is a direct mapping of the data item 'End date of hospital provider spell' in Table 5 IPEP within MHMDS v3.5
This data item should be mapped from from the data item 'Admission method' in table 5 IPEP in MHMDS v3.5.
Please note that there is an additional value 'Admission via Mental Health Crisis Resolution Team' which has been added in MHMDS v4.0.
This is a direct mapping to code [11] Waiting list
This is a direct mapping to code [12] Booked
This is a direct mapping to code [13] Planned
Table 11 - PROVSPELL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 11 PROVSPELLMAPPING NOTES
This is a direct mapping to code [21] Accident and emergency, or dental casualty department of the Health Care Provider
This is a direct mapping to code [22] General Practitioner after a request has been made direct to the Health Care Provider (i.e. not through a bed bureau) by a General Practitioner or deputy
This is a direct mapping to code [23] Bed bureau
This is a direct mapping to code [24] Consultant clinic of this or another Health Care Provider
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [28] Other means including admission through the accident and emergency department of another Health Care Provider
This is a direct mapping to code [81] Transfer of any admitted patient from other hospital provider other than in an emergency. This does not include admissions to high security psychiatric hospitals
Table 11 - PROVSPELL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 11 PROVSPELLMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 12 - INPATEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 12 - Inpatient Episode
ACCESS TABLE 12 INPATEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
ENDDATE R date
STAFFID R Unique Staff ID an10
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 12 INPATEP.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Start date of inpatient episode
The start date of an Inpatient Episode.
This is a period of continuous care under a consultant, nurse or other healthcare professional.
End date of inpatient episode
The end date of an Inpatient Episode.
This is a period of continuous care under a consultant, nurse or other healthcare professional.
The unique identifier of the staff member (Consultant/Nurse) responsible for a continuous period of care for the patient whilst an inpatient.
NB. Please ensure that there is a corresponding record within the STAFF table for every Unique Staff ID. Unique Staff IDs are vital for deriving the relevant information about main specialty codes and job roles.
Please note that this definition differs to the MHMDS v4.0 specification. The MHMDS v4.0 specification will be updated at a later date to match this definition.
Table 12 - INPATEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 12 - Inpatient Episode
ACCESS TABLE 12 INPATEPMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 13 - WARDSTAYS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 13 - Ward Stay within Hospital Provider Spell
Information within the WARDSTAYS table should be mapped from Table 13 WARDSTAYS in v3.5
ACCESS TABLE 13 WARDSTAYSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M Start date of ward stay The start date for a Ward Stay. date
ENDDATE R End date ward stay The end date for a Ward Stay. date
CAREINTENS R an2
51
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Intended Clinical Care Intensity Code (Mental Health)
The level of resources and intensity of care which it is intended to provide or is provided in a particular WARD.
Note: Only the NHS Data Dictionary codes relating to mental illness as listed below should be used within MHMDS.
For Intensive Care - specially designated ward for PATIENTS needing containment and more intensive management (eg Psychiatric Intensive Care Unit (PICU)). This is not to be confused with intensive nursing where a PATIENT may require one-to-one nursing while on a standard WARD
Table 13 - WARDSTAYS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 13 WARDSTAYSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CAREINTENS R an2
52
53
Learning Disability Services61 Designated or interim secure unit
62
63
98 Not applicable
SECUREACC R Ward Security Level an1
0 General (Non-secure)
Intended Clinical Care Intensity Code (Mental Health)
The level of resources and intensity of care which it is intended to provide or is provided in a particular WARD.
Note: Only the NHS Data Dictionary codes relating to mental illness as listed below should be used within MHMDS.
For Short Stay - PATIENTS intended to stay for less than a year
For Long Stay - PATIENTS intended to stay for a year or more
PATIENTS intending to stay less than a year
PATIENTS intending to stay a year or more
The type of secure accommodation required by or provided for mentally disordered people and others with similar needs.
The level of security for the ward.
Table 13 - WARDSTAYS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 13 WARDSTAYSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
SECUREACC R Ward Security Level an1
1 Low secure
2 Medium secure
3 High secure
WARDGENDER R Sex of Patients Code an1 1 Males
2 Females
3 Either sex
WARDAGE R Intended Age Group an1 1 Neonates
2 Children and/or adolescents
3 Elderly
8 Any age
The type of secure accommodation required by or provided for mentally disordered people and others with similar needs.
The level of security for the ward.
The sex of PATIENTS intended to use a WARD indicated in the operational plans. (Classified Codes)
The age group of PATIENTS intended to use a WARD indicated in the operational plan.
Table 13 - WARDSTAYS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 13 - Ward Stay within Hospital Provider Spell
Information within the WARDSTAYS table should be mapped from Table 13 WARDSTAYS in v3.5
ACCESS TABLE 13 WARDSTAYSMAPPING NOTES
This is a direct mapping of the data item 'Start date of ward stay' in Table 6 WARDSTAYS within MHMDS v3.5
This is a direct mapping of the data item 'End date of ward stay' in Table 6 WARDSTAYS within MHMDS v3.5
This data item should be mapped from the data item 'Intended Clinical Care Intensity Code (Mental Health)' in Table 6 WARDSTAYS within MHMDS v3.5.
Please note that additional new values have been added to this data item but are currently out of scope in MHMDS v4.0.
This is a direct mapping to code [51] Intensive care: a designated or interim secure ward for patients needing containment or more intensive management. This is not to be confused with intensive nursing where a patient requires one-to-one nursing while on a standard ward.
Table 13 - WARDSTAYS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 13 WARDSTAYSMAPPING NOTES
This is a direct mapping to code [52] Short stay: patients intended to stay less than a year
This is a direct mapping to code [53] Long stay: patients intended to stay more than a year
New Value
Please note that is currently out of scope of MHMDS v4.0.
New Value
Please note that is currently out of scope of MHMDS v4.0.
New Value
Please note that is currently out of scope of MHMDS v4.0.
This is a direct mapping to code [98] Not applicable
This data item should be mapped from the data item 'Indicates if hospital accommodation is classified as medium secure' in Table 6 WARDSTAYS within MHMDS v3.5.
Please note that code [0] No: Accommodation not medium secure can not be mapped to the new code in MHMDS v4.0
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 13 - WARDSTAYS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 13 WARDSTAYSMAPPING NOTES
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [1] Yes: Accommodation is medium secure
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped. It may be possible to derive this information from your local ward configuration.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped. It may be possible to derive this information from your local ward configuration.
Table 14 - DELAYEDDISCHARGE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 14 - Delayed Discharge
ACCESS TABLE 14 DELAYEDDISCHARGEACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
DISREADYSTARTDATE M date
DISREADYENDDATE R date
R an2A1
Awaiting completion of assessment
B1 Awaiting public funding
C1
D1
D2
E1Awaiting care package in own home
F1
G1 Patient or Family choiceH1 Disputes
I1
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 14 DELAYEDDISCHARGE.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Mental Health Delayed Discharge Start Date
Date that multi-disciplinary team agree that patient is ready for discharge
Mental Health Delayed Discharge End Date
The date that a period of delayed discharge for a patient who had previously been ready for discharge ended. This may end because the patient was discharged or because the patient was no longer ready for discharge.
DELYEDDISCHARGEREASON
Mental Health Delayed Discharge Reason
The reason that a patient was not able to be discharged despite being medically ready for discharge.
Awaiting further non-acute (including PCT and mental health) NHS care (including intermediate care, rehabilitation services etc)
Awaiting residential home placement or availability
Awaiting nursing home placement or availability
Awaiting community equipment and adaptations
Housing – patients not covered by NHS and Community Care Act
Table 14 - DELAYEDDISCHARGE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 14 - Delayed Discharge
ACCESS TABLE 14 DELAYEDDISCHARGEMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 15 - Clinical Team
Information within the CLINTEAM table should be mapped from Table 23 CLINTEAM in v3.5
ACCESS TABLE 15 CLINTEAMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLINTEAM M Unique Team ID an10
TEAMNAME O Team Name The name of the clinical team.
CLINTEAMgrp R The type of team. an3
General Mental Health Services
A01 Day Care Service
A02
A03 Adult Community Mental Health Team
A04
A unique code used locally to identify the team.
NB: Please ensure this corresponds to the Unique Team IDs entered in activity tables. Unique Team IDs are required to derive the Team Type but are not included in any MHMDS extracts.
an100 (variable length)
Adult Mental Health Team Type
Crisis Resolution Team/Home Treatment
Older People Community Mental Health Team
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 15 CLINTEAMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLINTEAMgrp R The type of team. an3
A05 Assertive Outreach Team
A06 Rehabilitation & Recovery Service
A07 General Psychiatry
A08 Psychiatric Liaison
A09 Psychotherapy Service
A10 Psychological Therapy Service (IAPT)
A11
A12 Young Onset Dementia
A13 Personality Disorder Service
A14 Early Intervention in Psychosis Team
Adult Mental Health Team Type
Psychological Therapy Service (non IAPT)
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 15 CLINTEAMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLINTEAMgrp R The type of team. an3
A15 Primary Care Mental Health Service
A16 Memory Services/Clinic
Forensic ServicesB01 Forensic Service
B02 Community Forensic Service
Specialist Mental Health Services
C01 Learning Disability Service
C02 Autistic Spectrum Disorder Service
C03 Peri-Natal Mental Illness
C04 Eating Disorders/Dietetics
Other Mental Health Services
Adult Mental Health Team Type
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 15 CLINTEAMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLINTEAMgrp R The type of team. an3
D01 Substance Misuse Team
D02
D03 Prison Psychiatric Inreach Service
D04 Asylum Service
OtherZZZ Other Mental Health Service
Adult Mental Health Team Type
Criminal Justice Liaison and Diversion Service
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 15 - Clinical Team
Information within the CLINTEAM table should be mapped from Table 23 CLINTEAM in v3.5
ACCESS TABLE 15 CLINTEAMMAPPING NOTES
This is a direct mapping of the data item 'Local Team Identifier' in Table 23 CLINTEAM within MHMDS v3.5.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item is for local use only.This is a direct mapping of the data item 'Clinical Team Classification Group' in Table 23 CLINTEAM within MHMDS v3.5.
Please note that there are a large number of additional values which have been added to this data item in v4.0. If may be more appropriate to map the list of adult mental health team types to what is currently captured on your local system.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [04] Home Treatment/Crisis Resolution Team
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 15 CLINTEAMMAPPING NOTES
This is a direct mapping to code [06] Assertive Outreach Team
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [05] Early Intervention in Psychosis Team
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 15 CLINTEAMMAPPING NOTES
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 15 - CLINTEAM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 15 CLINTEAMMAPPING NOTES
This is a direct mapping to code [03] Substance Misuse Team
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
This is a direct mapping to code [20] Other Teams
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 16 - Staff Details
Information within the STAFF table should be mapped from Table 16 KWS and 18 RC in v3.5
ACCESS TABLE 16 STAFFACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
STAFFID M Unique Staff ID an10
SPECFC R an3 600 General Medical Practice700 Learning Disability710 Adult Mental illness711 Child and Adolescent Psychiatry712 Forensic psychiatry713 Psychotherapy715 Old age psychiatry950 Nursing Episode960 Allied Health Professional
OCCCODE R NHS Occupation Code an3
JOBROLE R Job Role an501001 Medical Director01002 Clinical Director01003 Professor01004 Senior Lecturer0100501006
01007
01008
01009
01010 Hospital Practitioner01011 Clinical Assistant
The unique identifier used locally to identify the staff member.
NB. Please ensure that there is a corresponding record within the STAFF table for every Unique Staff ID. Unique Staff IDs are vital for deriving the relevant information about main specialty codes and job roles.
Main Specialty code (Mental Health)
The Main Specialty of the mental health professional.
This will be recorded as 600 – General Medical Practice if the Responsible Clinician is the patients registered GP.
Where the approved clinician is not a consultant the appropriate pseudo-specialty code should be used or this item should be left blank.
The coding set is found in the NHS Workforce Census Occupational Coding Manual. Details can be found be following the hyperlink below:
http://www.ic.nhs.uk/webfiles/data%20collections/NHS%20Occupation%20Code%20Manual%20Version%206.pdf
The Electronic Staff Record (ESR) Job Role Code for the mental health professional.
01000 Medical and Dental
CONSULTANT Dental surgeon acting as CONSULTANT
Special salary scale in Public Health Medicine
Associate Specialist (Closed to new entrants from 01 April 2008 or regrading from 01 April 2009)
Staff Grade (Closed to new entrants 01 April 2008)
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
JOBROLE R Job Role an5
01012 Specialist Registrar01013 Senior House Officer01014 House Officer - Pre-registration01015 House Officer - Post-registration01016
01017 Trust Grade Doctor - SHO level01018
01019
01020 Director of Public Health01021 Clinical Medical Officer01022 Senior Clinical Medical Officer01023 'Other' Community Health Service0102401025
0102601027 Regional Dental Officer01028 Dental Clinical Director01029 Dental Officer01030 Senior Dental Officer01031 Salaried Dental Practitioner01032 Specialty Doctor
020010200202003
02004
0200502006
02007 Student District Nurse02008
02009 Student Practice Nurse02010
The Electronic Staff Record (ESR) Job Role Code for the mental health professional.
Trust Grade Doctor - House Officer level
Trust Grade Doctor - Specialist Registrar level
Trust Grade Doctor - Career Grade level
GENERAL DENTAL PRACTITIONER GENERAL MEDICAL PRACTITIONER
Salaried GENERAL PRACTITIONER
02000 Students Student NURSE - Adult Branch
Student NURSE - Child BranchStudent NURSE - Mental Health Branch
Student NURSE - Learning Disabilities Branch
Student MIDWIFE Student Specialist Community Public Health Nurse - Health Visitor
Student Specialist Community Public Health Nurse - School Nurse
Student Specialist Community Public Health Nurse - Occupational Health Nurse
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
JOBROLE R Job Role an5
02011
02012
02013
02014 Student Chiropodist02015 Student Dietitian02016 Student Occupational Therapist02017 Student Orthoptist02018 Student Physiotherapist02019 Student Radiographer - Diagnostic02020 Student Radiographer - Therapeutic
02021
02022 Art, Music and Drama Student02023 Student Psychotherapist
03001 Director of Nursing03002 Nurse Consultant03003 Nurse Manager03004 Modern Matron03005 Specialist Nurse Practitioner03006 Sister/Charge Nurse03007 Staff Nurse0300803009 Midwife - Consultant03010 Midwife - Specialist Practitioner03011 Midwife Manager030120301303014 Community Practitioner03015
0400104002 Art Therapist Consultant04003 Art Therapist Manager04004 Art Therapist Specialist Practitioner04013 Drama Therapist
The Electronic Staff Record (ESR) Job Role Code for the mental health professional.
Student Specialist Community Public Health Nurse Children's Nurse
Student Specialist Community Public Health Nurse Mental Health Nurse
Student Specialist Community Public Health Nurse Learning Disabilities Nurse
Student Speech and Language Therapist
03000 Nursing and Midwifery Registered
Enrolled Nurse
MIDWIFE - Sister/Charge NurseMIDWIFE
Specialist Community Public Health Nurse
04000 Allied Health Professionals
Arts Therapist
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
JOBROLE R Job Role an5
04014 Drama Therapist Consultant04015 Drama Therapist Manager04016
04017 Multi Therapist04018 Multi Therapist Consultant04019 Multi Therapist Manager04020 Multi Therapist Specialist Practitioner
04021 Music Therapist04022 Music Therapist Consultant04023 Music Therapist Manager04024 Music Therapist Specialist Practitioner
0402504026 Occupational Therapist Consultant04027 Occupational Therapist Manager04028
0404104042 Physiotherapist Consultant04043 Physiotherapist Manager04044 Physiotherapist Specialist Practitioner
0405704058
04059
04060
05001 Clinical Director0500305004 Psychotherapist05005050070500805009 Youth Worker05010 Specialist Practitioner05011 Practitioner05012 Technician05014 Psychological Therapist - Qualified
05015 Psychological Therapist - Trainee
The Electronic Staff Record (ESR) Job Role Code for the mental health professional.
Drama Therapist Specialist Practitioner
Occupational Therapist
Occupational Therapist Specialist Practitioner
Physiotherapist
Speech and Language Therapist
Speech and Language Therapist Consultant
Speech and Language Therapist Manager
Speech and Language Therapist Specialist Practitioner
05000 Additional Professional, Scientific and Technical
Pharmacist
Clinical Psychologist
Social Worker Approved Social Worker
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
JOBROLE R Job Role an5
07001 Health Care Support Worker07002 Social Care Support Worker07003 Home Help07004 Healthcare Assistant07005 Nursery Nurse07006 Play Therapist07007 Play Specialist07010 Associate Practitioner07011 Counsellor07012 Helper/Assistant07014 Medical Laboratory Assistant07015 Phlebotomist07016 Cytoscreener07019 Trainee Practitioner07020 Nursing Cadet07021 Healthcare Cadet07022 Pre-reg Pharmacist07023 Assistant Psychologist07024 Assistant Psychotherapist07026 Gateway Worker07027 Support, Time, Recovery Worker07028 Therapy Worker - Qualified
07029 Therapy Worker - Trainee
The Electronic Staff Record (ESR) Job Role Code for the mental health professional.
07000 Additional Clinical Services
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 16 - Staff Details
Information within the STAFF table should be mapped from Table 16 KWS and 18 RC in v3.5
ACCESS TABLE 16 STAFFMAPPING NOTES
This is a direct mapping of the data items 'Care Co-ordinator's Identifying Code' in Table 16 KWS and 'Personal Identifier for the Responsible Clinician' in Table 18 RC within MHMDS v3.5
This is a direct mapping of the data item 'Main Specialty code (Mental Health)' and its associated values in Table 18 RC within MHMDS v3.5
This is a direct mapping of the data item 'Care Co-ordinator's occupation code' and its associated values in Table 16 KWS within MHMDS v3.5
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 16 - STAFF
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 16 STAFFMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 17 - CCASS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 17 - Care Co-ordinator Assignment
Information within the CCASS table should be mapped from Table 15 KWASS in v3.5
ACCESS TABLE 17 CCASSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M Date
ENDDATE R Date
STAFFID R Unique Staff ID an10
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Care Co-ordinator Assignment Start Date
The start date of a Care Co-ordinator assignment to a patient.
Care Co-ordinator Assignment End Date
The end date of a Care Co-ordinator assignment to a patient.
The unique identifier of the staff member assigned to the patient as a Care Co-ordinator.
NB. Please ensure that there is a corresponding record within the STAFF table for every Unique Staff ID. Unique Staff IDs are vital for deriving the relevant information about main specialty codes and job roles.
Table 17 - CCASS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 17 - Care Co-ordinator Assignment
Information within the CCASS table should be mapped from Table 15 KWASS in v3.5
ACCESS TABLE 17 CCASSMAPPING NOTES
This is a direct mapping of the data item 'Start date of Care Co-ordinator assignment' in Table 15 KWASS within MHMDS v3.5
This is a direct mapping of the data item 'End date of Care Co-ordinator assignment' in Table 15 KWASS within MHMDS v3.5
This is a direct mapping of the data item 'Care Co-ordinator's occupation code' and its associated values in Table 15 KWASS within MHMDS v3.5
Table 18 - RCASS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 18 - Responsible Clinician Assignment
Information within the RCASS table should be mapped from Table 17 RCASS in v3.5
ACCESS TABLE 18 RCASSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
ENDDATE R date
STAFFID R Unique Staff ID an10
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Responsible Clinician Assignment Start Date
The start date of an assignment of a Responsible Clinician to a patient.
Responsible Clinician Assignment End Date
The end date of an assignment of a Responsible Clinician to a patient.
The unique identifier of the staff member assigned to a patient detained under the Mental Health Act 1983 as the Responsible Clinician.
NB. Please ensure that there is a corresponding record within the STAFF table for every Unique Staff ID. Unique Staff IDs are vital for deriving the relevant information about main specialty codes and job roles.
Table 18 - RCASS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 18 - Responsible Clinician Assignment
Information within the RCASS table should be mapped from Table 17 RCASS in v3.5
ACCESS TABLE 18 RCASSMAPPING NOTES
This is a direct mapping of the data item 'Date of assignment to responsible clinician' in Table 17 RCASS within MHMDS v3.5
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a direct mapping of the data item 'Personal Identifier for responsible clinician' in Table 17 RCASS within MHMDS v3.5
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 19 - Health Care Professionals Contact
Information within the HPCCONT table should be mapped from Table 10 CCONT, Table 13 PGCONT and Table 14 KWCONT in v3.5
ACCESS TABLE 19 HPCCONTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Date of contact The date on which a patient contact takes place. date
TIME O Time of Contact time
DURATION R Duration of Contact n3
STAFFID R Unique Staff ID an10
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
FOR LOCAL USE ONLY: This field is not part of the MHMDS standard although it may be useful to allow recording of multiple contacts on the same day for local activity reporting purposes.
The duration of the Clinical Contact at an APPOINTMENT in minutes, excluding any administration time.
Any administrative/preparatory work undertaken before or after the appointment but relating to the appointment should be excluded.
The unique identifier of the staff member undertaking a contact with a patient.
NB. Please ensure that there is a corresponding record within the STAFF table for every Unique Staff ID. Unique Staff IDs are vital for deriving the relevant information about main specialty codes and job roles.
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 19 HPCCONTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLINTEAM R Unique Team ID an10
CONSULTMED R an2 01 Face to face communication02 Telephone03 Telemedicine web camera04 Talk type for a person unable to speak
05 Email06 Text (Short Messaging Service 'SMS')
CONTACTATT R Care Contact Subject an2 01 Patient
02
LOCATION R an3
A01 Patients homeA02 Carers homeA03 Patients workplaceA04 Other patient related location
Health Centre premisesB01 Primary Care Health CentreB02 Polyclinic
C01 General Medical Practice C02 General Dental PracticeC03
D01 Walk In CentreD02 Out of Hours Centre
A unique code used locally to identify the team.
NB. Please ensure that there is a corresponding record within the CLINTEAM table for every Unique Team ID. Unique Team IDs are required to derive the Team Type but are not included in any MHMDS extracts.
Consultation Medium Used
Identifies the communication mechanism used to relay information between the CARE PROFESSIONAL and the PERSON who is the subject of the consultation, during a CARE ACTIVITY.
Identifies whether the care contact for a patient was with the patient or a proxy (in lieu of a contact with the patient).
Proxy (in lieu of a contact with the patient)
Contact Location Type Code
Type of physical location where PATIENTS are seen or where services are provided or from which requests for services are sent.
Patient main residence or related location
General Practitioner and Ophthalmic Medical Practitioner Premises
Ophthalmic Medical Practitioner premises
Walk In Centres, Out of Hours Premises and Emergency Community Dental Services
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 19 HPCCONTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
LOCATION R an3
D03
Locations on Hospital Premises
E01 Out-Patient ClinicE02 WardE03 Day HospitalE04
E99 Other departmentsHospice premises
F01 HospiceNursing and Residential Homes
G01 Residential Care HomeG03 Nursing HomeG04 Children's Home
Day Centre premises H01 Day Centre
Resource Centre premisesJ01 Resource Centre
K02 Sure Start Children's CentreK03 Child Development Centre
L01 SchoolL02 Further Education CollegeL03 University L04 Nursery premisesL05 Other childcare premisesL06 Training establishmentsL99 Other educational premises
Justice and Home Office premises
M01 PrisonM02 Probation Service premisesM03 Police StationM04 Young Offenders InstitutionM05 Immigration Centre
Public locationsN01 Street or other public open space N02
Contact Location Type Code
Type of physical location where PATIENTS are seen or where services are provided or from which requests for services are sent.
Emergency Community Dental Service
Accident & Emergency or Minor Injuries Department
Dedicated Facilities for Children and Families
Educational, Childcare and Training Establishments
Other publicly accessible area or building
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 19 HPCCONTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
LOCATION R an3
N03
N04 Dispensing Optician premisesOther Locations
X01
ATTENDED R an1 5
6
7
2
3
4
Contact Location Type Code
Type of physical location where PATIENTS are seen or where services are provided or from which requests for services are sent.
Voluntary or charitable agency premises
Other locations not elsewhere classified
Indicator of whether the patient attended or did not attend
This indicates whether or not an APPOINTMENT for a CARE CONTACT took place. If the APPOINTMENT did not take place it also indicates whether or not advanced warning was given.
Attended on time or, if late, before the relevant professional was ready to see the patient
Arrived late, after the relevant professional was ready to see the patient, but was seen
Patient arrived late and could not be seen
Appointment cancelled by, or on behalf of, the patient
Did not attend, no advance warning given
Appointment cancelled or postponed by the health care provider
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 19 - Health Care Professionals Contact
Information within the HPCCONT table should be mapped from Table 10 CCONT, Table 13 PGCONT and Table 14 KWCONT in v3.5
ACCESS TABLE 19 HPCCONTMAPPING NOTES
This is a direct mapping of the data items 'Date of CPN Contact' in Table 10 CCONT, 'Date of professional staff group contact' in Table 13 PGCONT and 'Date of Care Co-ordinator contact' in Table 14 KWCONT within MHMDS v3.5.
This is a direct mapping of the data items 'Time of Contact' in Table 10 CCONT, 'Time of Contact' in Table 13 PGCONT and 'Time of Contact' in Table 14 KWCONT within MHMDS v3.5.
Please note that this is for local purposes only.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a direct mapping of the data item 'Staff ID' in Table 13 PGCONT within MHMDS v3.5.
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 19 HPCCONTMAPPING NOTES
'This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
'This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that the data value list in 'Contact Location Type Code' has been reviewed and revised it is not appropriate to provide a mapping table.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 19 HPCCONTMAPPING NOTES
Please note that the data value list in 'Contact Location Type Code' has been reviewed and revised it is not appropriate to provide a mapping table.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 19 - HPCCONT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 19 HPCCONTMAPPING NOTES
Please note that the data value list in 'Contact Location Type Code' has been reviewed and revised it is not appropriate to provide a mapping table.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 20 - DAYATT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 20 - NHS Day Care Facility Attendance
Information within the DAYATT table should be mapped from Table 11 DAYATT in v3.5
ACCESS TABLE 20 DAYATTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
ATTENDED R an1 5
6
7
2
3
4
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Planned date of NHS day care attendance
The planned date of an NHS Day Care Attendance for the patient.
Indicator of whether the patient attended or did not attend
This indicates whether or not an APPOINTMENT for a CARE CONTACT took place. If the APPOINTMENT did not take place it also indicates whether or not advanced warning was given.
Attended on time or, if late, before the relevant professional was ready to see the patient
Arrived late, after the relevant professional was ready to see the patient, but was seen
Patient arrived late and could not be seen
Appointment cancelled by, or on behalf of, the patient
Did not attend, no advance warning given
Appointment cancelled or postponed by the health care provider
Table 20 - DAYATT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 20 - NHS Day Care Facility Attendance
Information within the DAYATT table should be mapped from Table 11 DAYATT in v3.5
ACCESS TABLE 20 DAYATTMAPPING NOTES
This is a direct mapping of the data item 'Date of NHS day care attendance' in Table 11 DAYATT within MHMDS v3.5
This is a direct mapping of the data items 'Indicator of whether the patient attended or did not attend' in Table 11 DAYATT within MHMDS v3.5.
Table 21 - REV
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 21 - Review
ACCESS TABLE 21 REVACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Date of review date
ABUSEQUEST R an1 Y Yes
N No
9 Not known
STAFFID R Unique Staff ID an10
CLINTEAM R Unique Team ID an10
Information within the REV table should be mapped from Table 21 REV in v3.5 only for patients that are on CPA.
Please see 'Introduction' tab for further details on CPA
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of review.
Abuse Question Asked Indicator
An indicator identifying whether the patient has been asked the Abuse Question as part of a CPA Review.NOTE: This indicator should NOT be used to record the answer to the Abuse Question itself.
This is a new question within the CPA Guidance. Full details are available on the Care Programme Approach Association (CPPAA) website:http://cpaa.co.uk/files/AbuseQuestion-CPA-refocus.doc
The unique identifier of the staff member undertaking the review for the patient.
NB. Please ensure that there is a corresponding record within the STAFF table for every Unique Staff ID. Unique Staff IDs are vital for deriving the relevant information about main specialty codes and job roles.
A unique code used locally to identify the team.
NB. Please ensure that there is a corresponding record within the CLINTEAM table for every Unique Team ID. Unique Team IDs are required to derive the Team Type but are not included in any MHMDS extracts.
Table 21 - REV
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 21 - Review
ACCESS TABLE 21 REVMAPPING NOTES
This is a direct mapping of the data item 'Date of review' in Table 19 REV within MHMDS v3.5
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item then it should be mapped.
This is a direct mapping of the data item 'Local code of clinical team delivering review'' in Table 19 REV within MHMDS v3.5.
Table 22 - PRIMDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 22 - Primary Diagnosis
Information within the PRIMDIAG table should be mapped from Table 21 REV in v3.5
ACCESS TABLE 22 PRIMDIAGACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Date of Diagnosis date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date that a diagnosis was made for the patient.
This should be the first date that the specific diagnosis was made.
Table 22 - PRIMDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 22 PRIMDIAGACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PRIMDIAG R Primary Diagnosis an6The primary diagnosis for the patient. This is the main condition treated or investigated in an episode of care. Where there is no definitive diagnosis record the main symptom, abnormal finding or problem.
Please note that a patient can only have one primary diagnosis for a single care pathway. Where multiple primary diagnoses are recorded for a patient the most recent will be used for national analysis purposes.
Please see the NHS Classifications Service for further information and coding advice.
http://www.connectingforhealth.nhs.uk/systemsandservices/data/clinicalcoding
Table 22 - PRIMDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 22 - Primary Diagnosis
Information within the PRIMDIAG table should be mapped from Table 21 REV in v3.5
ACCESS TABLE 22 PRIMDIAGMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit date of diagnosis then it is advised that the data item 'Date of Review' Table 19 REV in MHMDS v3.5 where a code has been recorded/updated against the data items Diagnosis 1, Diagnosis 2, Diagnosis 3, Diagnosis 4, Diagnosis 5 and Diagnosis 6.
Please note that the Date of Review may not necessarily be the date the patient was diagnosed. Systems may capture this data item more accurately.
Table 22 - PRIMDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 22 PRIMDIAGMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit primary diagnosis then it is advised that the data item 'Diagnosis 1' in Table 19 REV in MHMDS v3.5.
Table 23 - SECDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 23 - Secondary Diagnosis
Information within the SECDIAG table should be mapped from Table 21 REV in v3.5
ACCESS TABLE 23 SECDIAGACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Date of Diagnosis date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date that a diagnosis was made for the patient.
This should be the first date that the specific diagnosis was made.
Table 23 - SECDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 23 SECDIAGACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
SECONDDIAG R Secondary Diagnosis an6A secondary diagnosis for the patient. This should include any secondary diagnosis of conditions treated or investigated in an episode of care which are NOT a primary diagnosis i.e. not the main condition treated or investigated. Where there is no definitive diagnosis this may include any symptoms, abnormal findings or problems where these are not the main symptoms.
Please note that a patient can have multiple secondary diagnosis for a care pathway.
Please see the NHS Classifications Service for further information and coding advice.
http://www.connectingforhealth.nhs.uk/systemsandservices/data/clinicalcoding
Table 23 - SECDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 23 - Secondary Diagnosis
Information within the SECDIAG table should be mapped from Table 21 REV in v3.5
ACCESS TABLE 23 SECDIAGMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit date of diagnosis then it is advised that the data item 'Date of Review' Table 19 REV in MHMDS v3.5 where a code has been recorded/updated against the data items Diagnosis 1, Diagnosis 2, Diagnosis 3, Diagnosis 4, Diagnosis 5 and Diagnosis 6.
Please note that the Date of Review may not necessarily be the date the patient was diagnosed. Systems may capture this data item more accurately.
Table 23 - SECDIAG
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 23 SECDIAGMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit secondary diagnosis then it is advised that the data items 'Diagnosis 2', 'Diagnosis 3', 'Diagnosis 4', 'Diagnosis 5' and 'Diagnosis 6' in Table 19 REV in MHMDS v3.5.
Table 24 - CPAEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 24 - CPA Episode
ACCESS TABLE 24 CPAEPACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE R Start date of CPA The start date for a period on CPA for a patient date
ENDDATE R End date of CPA The end date for a period on CPA for a patient date
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing these data items for local use then it is advised that the information should be submitted as specified in Table 24 CPAEP.
Although data can not be directly mapped from v3.5 REV table, patients with a CPALEVEL = 2 should probably have a record in this new table.
This table should contain a record for each separate period on the Care Programme Approach (CPA) for the patient. Please see 'Introduction' tab for further details.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Table 24 - CPAEP
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 24 - CPA Episode
ACCESS TABLE 24 CPAEPMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing these data items for local use then it is advised that the information
This table should contain a record for each separate period on the Care Programme Approach (CPA) for the patient. Please see 'Introduction' tab for further details.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 25 - CRISISPLAN
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 25 - Crisis Plan
ACCESS TABLE 25 CRISISPLANACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
CRISISCREATE R date
CRISISUPDATE R date
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing these data items for local use then it is advised that the information should be submitted as specified in Table 25 CRISISPLAN.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Crisis Plan Creation Date
The date that a crisis plan was created for a patient in the format dd/mm/yyyy.
Crisis Plan Last Update Date
The date that a crisis plan was last updated for a patient in the format dd/mm/yyyy.
Where the Crisis Plan has not otherwise been updated this will be the same as the Crisis Plan Creation Date.
Table 25 - CRISISPLAN
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 25 - Crisis Plan
ACCESS TABLE 25 CRISISPLANMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing these data items for local use then it is advised that the information
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 26 - Mental Health Clustering Tool
Information within the MHCT table should be mapped from Table X MHCT in v3.5
ACCESS TABLE 26 MHCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
ASSREASON R an2 01 New referral02 CPA review03 Review (non CPA)04 Other significant change in need97 Other not elsewhere specified99 Not known
HONOSRating1 R HoNOS Rating 1 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating2 R HoNOS Rating 2 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating3 R HoNOS Rating 3 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating4 R HoNOS Rating 4 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating5 R HoNOS Rating 5 Score n1 0 No problem1 Minor problem requiring no action
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Assessment Tool Completion Date
The date on which a Mental Health Cluster Tool (MHCT) Assessment was completed for a patient.
Mental Health Clustering Tool Assessment Reason
The reason that the MHCT Assessment for the patient was undertaken.
The score for rating 1 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient:Overactive, aggressive, disruptive or agitated behaviour (current)
The score for rating 2 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient:Non-accidental self injury (current)
The score for rating 3 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problem drinking or drug taking (current)
The score for rating 4 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Cognitive problems (current)
The score for rating 5 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Physical illness or disability problems (current)
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTIONHONOSRating5 R HoNOS Rating 5 Score n1
2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating6 R HoNOS Rating 6 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating7 R HoNOS Rating 7 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating8 R HoNOS Rating 8 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating8TYPE R HoNOS Rating 8 Type an1 A PhobicB AnxietyC Obsessive-compulsiveD StressE DissociativeF SomatoformG EatingH SleepI SexualJ Other
HONOSRating9 R HoNOS Rating 9 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating10 R HoNOS Rating 10 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating11 R HoNOS Rating 11 Score n1 0 No problem
The score for rating 5 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Physical illness or disability problems (current)
The score for rating 6 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems associated with hallucinations and delusions (current)
The score for rating 7 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems with depressed mood (current)
The score for rating 8 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Other mental and behavioural problems (current)
The type of other mental and behavioural problem to which the score for rating 8 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient relates.
Enter letter of most severe problem.
The score for rating 9 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems with relationships (current)
The score for rating 10 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems with activities of daily living (current)
The score for rating 11 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems with living conditions (current)
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTIONHONOSRating11 R HoNOS Rating 11 Score n1
1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
HONOSRating12 R HoNOS Rating 12 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
SACRating13 R SAC Rating 13 Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
SACRatingA R SAC Rating A Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
SACRatingB R SAC Rating B Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
SACRatingC R SAC Rating C Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
SACRatingD R SAC Rating D Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem4 Severe to very severe problem9 Unknown
SACRatingE R SAC Rating E Score n1 0 No problem1 Minor problem requiring no action2 Mild problem but definitely present3 Moderately severe problem
The score for rating 11 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems with living conditions (current)
The score for rating 12 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient.Problems with occupation and activities (current)
The score for rating 13 of the Summary Assessment of Characteristics (SAC) assessment for the patient.Strong unreasonable beliefs occurring in non-psychotic disorders only (current)
The score for rating A of the Summary Assessment of Characteristics (SAC) assessment for the patient.Agitated behaviour / expansive mood (historical)
The score for rating B of the Summary Assessment of Characteristics (SAC) assessment for the patient.Repeat self-harm (historical)
The score for rating C of the Summary Assessment of Characteristics (SAC) assessment for the patient.Safeguarding children and vulnerable dependent adults (historical)
The score for rating D of the Summary Assessment of Characteristics (SAC) assessment for the patient.Engagement (historical)
The score for rating E of the Summary Assessment of Characteristics (SAC) assessment for the patient.Vulnerability (historical)
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
SACRatingE R SAC Rating E Score n1
4 Severe to very severe problem9 Unknown
PROFSUPERCLUSTER R an1 A Non-PsychoticB PsychosisC OrganicZ
CLUSTER R an2 00 Care Cluster 0: Variance01
02
03
04
05
06
07
08
09 Care Cluster 9: Cluster Under Review
10
11
12
13
14 Care Cluster 14: Psychotic Crisis15
16 Care Cluster 16: Dual Diagnosis
The score for rating E of the Summary Assessment of Characteristics (SAC) assessment for the patient.Vulnerability (historical)
Mental Health Care Cluster Super Class Code
The 'Super' Class to which the patient has been assigned by the professional following completion of the MHCT but prior to Care Cluster allocation.
Unable to assign patient to super care cluster
PbR Care Cluster assigned to the patient
The Care Cluster for a patient resulting from a Mental Health Cluster Tool (MHCT) assessment. Care Cluster 1: Common Mental
Health Problems (Low Severity)
Care Cluster 2: Common Mental Health Problems (Low Severity with Greater Need)
Care Cluster 3: Non-Psychotic (Moderate Severity)
Care Cluster 4: Non-Psychotic (Severe)
Care Cluster 5: Non-Psychotic Disorders (Very Severe)
Care Cluster 6: Non-Psychotic Disorder of Over-Valued Ideas
Care Cluster 7: Enduring Non-Psychotic Disorders (High Disability)
Care Cluster 8: Non-Psychotic Chaotic and Challenging Disorders
Care Cluster 10: First Episode Psychosis
Care Cluster 11: Ongoing Recurrent Psychosis (Low Symptoms)
Care Cluster 12: Ongoing or Recurrent Psychosis (High Disability)
Care Cluster 13: Ongoing or Recurrent Psychosis (High Symptoms and Disability)
Care Cluster 15: Severe Psychotic Depression
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLUSTER R an2
17
18
19
20
21
PbR Care Cluster assigned to the patient
The Care Cluster for a patient resulting from a Mental Health Cluster Tool (MHCT) assessment.
Care Cluster 17: Psychosis and Affective Disorder (Difficult to Engage)
Care Cluster 18: Cognitive Impairment (Low Need)
Care Cluster 19: Cognitive Impairment or Dementia Complicated (Moderate Need)
Care Cluster 20: Cognitive Impairment or Dementia (High Need)
Care Cluster 21: Cognitive Impairment or Dementia (High Physical or Engagement)
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 26 - Mental Health Clustering Tool
Information within the MHCT table should be mapped from Table X MHCT in v3.5
ACCESS TABLE 26 MHCTMAPPING NOTES
This is a direct mapping of the data item 'MHCT Assessment Date' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'Mental Health Clustering Tool Assessment Reason' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 1 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 2 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 3 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 4 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 5 Score' in Table X MHCT within MHMDS v3.5
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTMAPPING NOTESThis is a direct mapping of the data item 'HoNOS Rating 5 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 6 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 7 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 8 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 8 Type' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 9 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 10 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 11 Score' in Table X MHCT within MHMDS v3.5
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTMAPPING NOTESThis is a direct mapping of the data item 'HoNOS Rating 11 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'HoNOS Rating 12 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'SAC Rating 13 Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'SAC Rating A Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'SAC Rating B Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'SAC Rating C Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'SAC Rating D Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'SAC Rating E Score' in Table X MHCT within MHMDS v3.5
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTMAPPING NOTES
This is a direct mapping of the data item 'SAC Rating E Score' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'Mental Health Care Cluster Super Class Code' in Table X MHCT within MHMDS v3.5
This is a direct mapping of the data item 'PbR Care Cluster assigned to the patient' in Table X MHCT within MHMDS v3.5
Table 26 - MHCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 26 MHCTMAPPING NOTES
This is a direct mapping of the data item 'PbR Care Cluster assigned to the patient' in Table X MHCT within MHMDS v3.5
Table 27 - CLUSTER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 27 - Payment by Results Care Clustering
Information within the MHCT table should be mapped from Table X CLUSTER in v3.5
ACCESS TABLE 27 CLUSTERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M Care Cluster Start Date date
ENDDATE R Care Cluster End Date date
CLUSTER R PbR Care Cluster an2 00 Care Cluster 0: Variance01
02
03
04
05
06
07
08
09 Care Cluster 9: Cluster Under Review
10
11
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date on which the assignment of a patient to a Care Cluster started following a MHCT Assessment.
The date on which the assignment of a patient to a Care Cluster ended.
The Care Cluster to which the patient has been assigned following the HoNOS PbR Assessment Care Cluster 1: Common Mental
Health Problems (Low Severity)
Care Cluster 2: Common Mental Health Problems (Low Severity with Greater Need)
Care Cluster 3: Non-Psychotic (Moderate Severity)
Care Cluster 4: Non-Psychotic (Severe)
Care Cluster 5: Non-Psychotic Disorders (Very Severe)
Care Cluster 6: Non-Psychotic Disorder of Over-Valued Ideas
Care Cluster 7: Enduring Non-Psychotic Disorders (High Disability)
Care Cluster 8: Non-Psychotic Chaotic and Challenging Disorders
Care Cluster 10: First Episode Psychosis
Care Cluster 11: Ongoing Recurrent Psychosis (Low Symptoms)
Table 27 - CLUSTER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 27 CLUSTERACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
CLUSTER R PbR Care Cluster an2
12
13
14 Care Cluster 14: Psychotic Crisis15
16 Care Cluster 16: Dual Diagnosis17
18
19
20
21
END REASON R an2 01
02 Patient discharged from service03 Patient transferred to another provider
04 Patient Died99 Not known
The Care Cluster to which the patient has been assigned following the HoNOS PbR Assessment
Care Cluster 12: Ongoing or Recurrent Psychosis (High Disability)
Care Cluster 13: Ongoing or Recurrent Psychosis (High Symptoms and Disability)
Care Cluster 15: Severe Psychotic Depression
Care Cluster 17: Psychosis and Affective Disorder (Difficult to Engage)
Care Cluster 18: Cognitive Impairment (Low Need)
Care Cluster 19: Cognitive Impairment or Dementia Complicated (Moderate Need)
Care Cluster 20: Cognitive Impairment or Dementia (High Need)
Care Cluster 21: Cognitive Impairment or Dementia (High Physical or Engagement)
Care Cluster End Reason
The reason that a patients assignment to a Care Cluster ended
Please see PbR Guidance for further details.
Patient assigned to another Care Cluster following MHCT Assessment
Table 27 - CLUSTER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 27 - Payment by Results Care Clustering
Information within the MHCT table should be mapped from Table X CLUSTER in v3.5
ACCESS TABLE 27 CLUSTERMAPPING NOTES
This is a direct mapping of the data item 'Care Cluster Start Date' in Table X Payment by Results (PbR) Cluster within MHMDS v3.5
This is a direct mapping of the data item 'Care Cluster End Date' in Table X Payment by Results (PbR) Cluster within MHMDS v3.5
This is a direct mapping of the data item 'PbR Care Cluster' in Table X Payment by Results (PbR) Cluster within MHMDS v3.5
Table 27 - CLUSTER
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 27 CLUSTERMAPPING NOTES
This is a direct mapping of the data item 'PbR Care Cluster' in Table X Payment by Results (PbR) Cluster within MHMDS v3.5
This is a direct mapping of the data item 'Care Cluster End Reason' in Table X Payment by Results (PbR) Cluster within MHMDS v3.5
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 28 Health of Nation Outcome Scales (Working Age Adult)
Information within the HONOS table should be mapped from Table 19 REV in v3.5
ACCESS TABLE 28 HONOSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
HONOSRating1 R HoNOS Rating 1 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Assessment Tool Completion Date
The date on which a HoNOS Assessment was completed for a patient by a healthcare professional in format dd/mm/yyyy.
The score for question 1 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSRating1 R HoNOS Rating 1 Score n1
4 Severe to very severe problem
9 Unknown
HONOSRating2 R HoNOS Rating 2 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating3 R HoNOS Rating 3 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating4 R HoNOS Rating 4 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
The score for question 1 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 2 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 3 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 4 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSRating5 R HoNOS Rating 5 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating6 R HoNOS Rating 6 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating7 R HoNOS Rating 7 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating8 R HoNOS Rating 8 Score n1 0 No problem
1 Minor problem requiring no action
The score for question 5 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 6 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 7 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 8 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSRating8 R HoNOS Rating 8 Score n1
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating8TYPE R HoNOS Rating 8 Type an1 A Phobic
B Anxiety
C Obsessive-compulsive
D Stress
E Dissociative
F Somatoform
G Eating
H Sleep
I Sexual
J Other
HONOSRating9 R HoNOS Rating 9 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating10 R HoNOS Rating 10 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
The score for question 8 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The type of other mental and behavioural problem to which the score for question 8 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient relates.
Enter letter of most severe problem
The score for question 9 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 10 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSRating10 R HoNOS Rating 10 Score n1
4 Severe to very severe problem
9 Unknown
HONOSRating11 R HoNOS Rating 11 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSRating12 R HoNOS Rating 12 Score n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
The score for question 10 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 11 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
The score for question 12 of the Health of Nation Outcome Scales (HoNOS) assessment for the patient
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 28 Health of Nation Outcome Scales (Working Age Adult)
Information within the HONOS table should be mapped from Table 19 REV in v3.5
ACCESS TABLE 28 HONOSMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit assessment tool completion date then it is advised that the data item 'Date of Review' in Table 19 REV within MHMDS v3.5 where a Full HoNOS rating made at review has been recorded.
Please note that the Date of Review may not necessarily be the date that the HoNOS assessment took place. Systems may capture this data item more accurately.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSMAPPING NOTES
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSMAPPING NOTES
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSMAPPING NOTES
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
Table 28 - HONOS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 28 HONOSMAPPING NOTES
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
This is a new data item in v4.0.
This data item was originally captured as 'Full HoNOS rating made at review' in Table 19 REV within MHMDS v3.5. This could be derived either from the source system or could be disaggregated from the HONSTRING in the sequence it appears for all 13 characters.
Table 29 - HONOS65+
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 29 - Health of Nation Outcome Scales 65+ (Older Persons)
ACCESS TABLE 29 HONOS65+ACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
HONOS65Rating1 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating2 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating3 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating4 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 29 HONOS65+.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Assessment Tool Completion Date
The date on which a HoNOS 65+ Assessment was completed for a patient by a healthcare professional in format dd/mm/yyyy.
HoNOS65+ Rating 1 Score
The score for question 1 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 2 Score
The score for question 2 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 3 Score
The score for question 3 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 4 Score
The score for question 4 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
Table 29 - HONOS65+
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 29 HONOS65+ACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOS65Rating4 R n1
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating5 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating6 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating7 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating8 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating8TYPE R an1 A PhobicB AnxietyC Obsessive-compulsiveD StressE DissociativeF SomatoformG EatingH SleepI Sexual
HoNOS65+ Rating 4 Score
The score for question 4 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 5 Score
The score for question 5 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 6 Score
The score for question 6 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 7 Score
The score for question 7 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 8 Score
The score for question 8 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 8 Type
The type of other mental and behavioural problem to which the score for question 8 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient relates.
Enter letter of most severe problem
Table 29 - HONOS65+
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 29 HONOS65+ACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOS65Rating8TYPE R an1
J OtherHONOS65Rating9 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating10 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating11 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOS65Rating12 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HoNOS65+ Rating 8 Type
The type of other mental and behavioural problem to which the score for question 8 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient relates.
Enter letter of most severe problem
HoNOS65+ Rating 9 Score
The score for question 9 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 10 Score
The score for question 10 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 11 Score
The score for question 11 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
HoNOS65+ Rating 12 Score
The score for question 12 of the Health of Nation Outcome Scales 65+ (HoNOS65+) assessment for the patient
Table 29 - HONOS65+
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 29 - Health of Nation Outcome Scales 65+ (Older Persons)
ACCESS TABLE 29 HONOS65+MAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 29 - HONOS65+
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 29 HONOS65+MAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 29 - HONOS65+
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 29 HONOS65+MAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 30 - Health of Nation Outcome Scales (Child and Adolescent)
ACCESS TABLE 30 HONOSCAACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
HONOSCARating1 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating2 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating3 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating4 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 30 HONOSCA.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Assessment Tool Completion Date
The date on which a HoNOS-CA Assessment was completed for a patient by a healthcare professional in format dd/mm/yyyy.
HoNOS-CA Rating 1 Score
The score for question 1 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 2 Score
The score for question 2 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 3 Score
The score for question 3 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 4 Score
The score for question 4 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 30 HONOSCAACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSCARating4 R n1
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating5 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating6 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating7 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating8 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating9 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HoNOS-CA Rating 4 Score
The score for question 4 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 5 Score
The score for question 5 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 6 Score
The score for question 6 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 7 Score
The score for question 7 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 8 Score
The score for question 8 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 9 Score
The score for question 9 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 30 HONOSCAACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSCARating10 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating11 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating12 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating13 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating14 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSCARating15 R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
HoNOS-CA Rating 10 Score
The score for question 10 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 11 Score
The score for question 11 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 12 Score
The score for question 12 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating 13 Score
The score for question 13 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating B14 Score
The score for question B14 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
HoNOS-CA Rating B15 Score
The score for question B15 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 30 HONOSCAACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSCARating15 R n1
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HoNOS-CA Rating B15 Score
The score for question B15 of the Health of Nation Outcome Scales for Children and Adolescents (HoNOS-CA) assessment for the patient
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 30 - Health of Nation Outcome Scales (Child and Adolescent)
ACCESS TABLE 30 HONOSCAMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 30 HONOSCAMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 30 HONOSCAMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 30 - HONOSCA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 30 HONOSCAMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 31 - HONOSSECURE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 31 - Health of Nation Outcome Scales Secure
ACCESS TABLE 31 HONOSSECUREACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
HONOSSECURERatingA R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSSECURERatingB R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSSECURERatingC R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSSECURERatingD R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 31 HONOSSECURE.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Assessment Tool Completion Date
The date on which a HoNOS-Secure Assessment was completed for a patient by a healthcare professional in format dd/mm/yyyy.
HoNOS-SECURE Rating A Score
The score for question A of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
HoNOS-SECURE Rating B Score
The score for question B of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
HoNOS-SECURE Rating C Score
The score for question C of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
HoNOS-SECURE Rating D Score
The score for question D of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
Table 31 - HONOSSECURE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 31 HONOSSECUREACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
HONOSSECURERatingD R n1
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSSECURERatingE R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSSECURERatingF R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HONOSSECURERatingG R n1 0 No problem
1 Minor problem requiring no action
2 Mild problem but definitely present
3 Moderately severe problem
4 Severe to very severe problem
9 Unknown
HoNOS-SECURE Rating D Score
The score for question D of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
HoNOS-SECURE Rating E Score
The score for question E of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
HoNOS-SECURE Rating F Score
The score for question F of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
HoNOS-SECURE Rating G Score
The score for question G of the Health of Nation Outcome Scales (HoNOS-Secure) assessment for the patient
Table 31 - HONOSSECURE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 31 - Health of Nation Outcome Scales Secure
ACCESS TABLE 31 HONOSSECUREMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 31 - HONOSSECURE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 31 HONOSSECUREMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 32 - PHQ-9
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 32 - Patient Health Questionnaire
ACCESS TABLE 32 PHQ-9ACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
PHQ9_1 O PHQ-9 Question 1 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_2 O PHQ-9 Question 2 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_3 O PHQ-9 Question 3 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_4 O PHQ-9 Question 4 Score n1 0 Not at all
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 32 PHQ-9.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Assessment Tool Completion Date
The date on which a PHQ-9 Assessment was completed for a patient by a healthcare professional in format dd/mm/yyyy.
"Little interest or pleasure in doing things"
The score for question 1 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Feeling down, depressed, or hopeless"
The score for question 2 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Trouble falling or staying asleep, or sleeping too much"
The score for question 3 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Feeling tired or having little energy"
The score for question 4 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
Table 32 - PHQ-9
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 32 PHQ-9ACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTIONPHQ9_4 O PHQ-9 Question 4 Score n1
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_5 O PHQ-9 Question 5 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_6 O PHQ-9 Question 6 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_7 O PHQ-9 Question 7 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_8 O PHQ-9 Question 8 Score n1 0 Not at all
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_9 O PHQ-9 Question 9 Score n1 0 Not at all
"Feeling tired or having little energy"
The score for question 4 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Poor appetite or overeating"
The score for question 5 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Feeling bad about yourself - or that you are a failure or have let yourself or your family down?"
The score for question 6 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Trouble concentrating on things, such as reading the newspaper or watching television"
The score for question 7 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Moving or speaking so slowly that other people could have noticed? Or the opposite - being so fidgety or restless that you have been moving around a lot more than usual?"
The score for question 8 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
"Thoughts that you would be better off dead, or of hurting yourself in some way?"
The score for question 9 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
Table 32 - PHQ-9
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 32 PHQ-9ACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTIONPHQ9_9 O PHQ-9 Question 9 Score n1
1 Several days
2 More than half the days
3 Nearly every day
9 Missing value
PHQ9_Score O PHQ-9 Total Score n2
"Thoughts that you would be better off dead, or of hurting yourself in some way?"
The score for question 9 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
The total score for questions 1-9 of the Patient Health Questionnaire (PHQ-9) assessment for the patient.
The total score for the nine items can range from 0 to 27. For example a PHQ-9 depression severity score of 16 is derived from 3 items scored 1, 2 items scored 2 and 3 items scored 3).
Note: The PHQ-9 depression total severity score can be categorised using the following cut-points:Total score: 0-5 = mild Total score: 6-10 = moderateTotal score: 11-15 = moderately severeTotal score: 16-20+ = severe depression
Table 32 - PHQ-9
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 32 - Patient Health Questionnaire
ACCESS TABLE 32 PHQ-9MAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 32 - PHQ-9
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 32 PHQ-9MAPPING NOTESThis is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 32 - PHQ-9
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 32 PHQ-9MAPPING NOTESThis is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 33 - SSASS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 33 - Social Service Statutory Assessment
Information within the SSASS table should be mapped from Table 20 SSASS in v3.5
ACCESS TABLE 33 SSASSACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
ASSESSMENT O an3
CCA Community Care Act 1990
MHA Mental Health Act 1983
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of Statutory assessment
The date that a Social Services Statutory Assessment was undertaken for the patient.
Act under which assessed
The Act under which a Social Services Statutory Assessment is undertaken for the patient.
Table 33 - SSASS
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 33 - Social Service Statutory Assessment
Information within the SSASS table should be mapped from Table 20 SSASS in v3.5
ACCESS TABLE 33 SSASSMAPPING NOTES
This data item should be mapped from the data item 'Date of Statutory assessment' in Table 20 SSASS within MHMDS v3.5.
This data item should be mapped from the data item 'Act under which assessed' in Table 20 SSASS within MHMDS v3.5.
This is a direct mapping to code [CCA] Community Care Act 1990
This is a direct mapping to code [MHA] Mental Health Act 1983
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 34 - Mental Health Act Event Episodes
ACCESS TABLE 34 MHAEVENTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
STARTTIME M time
EXPIRYDATE R date
Information within the MHAEVENT table should be mapped from Table 21 MHAEVENT in v3.5
Although the STARTDATE can not be directly mapped from dates in v3.5 MHAEVENT table, patients with an EVENTDATE in v3.5 should have a record in this new table.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Mental Health Act Legal Status Start Date
The date which the Mental Health Act Legal Status for a patient started.
Mental Health Act Legal Status Start Time
The time which the Mental Health Act Legal Status for a patient started in the format hh:mm.
Mental Health Act Legal Status Expiry Date
The date which the Mental Health Act Legal Status for a patient was due to expire. This should be updated following the renewal of a section.
This data item only needs to be recorded where the Mental Health Legal Status for the patient has not ended. Where the patient is detained under a Mental Health Act section that is not timebound i.e.is indefinite this data item should be left blank.
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 34 MHAEVENTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
EXPIRYTIME R time
ENDDATE R date
ENDTIME R time
LSTATUS R an2 01
02
03
04
05
06
07
08
09
Mental Health Act Legal Status Expiry Time
The time which the Mental Health Act Legal Status for a patient was due to expire in the format hh:mm.
Mental Health Act Legal Status End Date
The date which the Mental Health Act Legal Status for a patient ended following discharge from the provisions, or detention under a different section of the Mental Health Act. This should include any renewals of the section.
Mental Health Act Legal Status End Time
The time which the Mental Health Act Legal Status for a patient ended in the format hh:mm.
Legal Status Classification Code following event
A Patient will have a Legal Status Classification if they are or have been formally detained under the Mental Health Act or if they are under the care of a Consultant in the psychiatric specialties whether or not formally detained.
Informal (Not formally detained and not receiving supervised aftercare)
Formally detained under Mental Health Act Section 2
Formally detained under Mental Health Act Section 3
Formally detained under Mental Health Act Section 4
Formally detained under Mental Health Act Section 5(2)
Formally detained under Mental Health Act Section 5(4)
Formally detained under Mental Health Act Section 35
Formally detained under Mental Health Act Section 36
Formally detained under Mental Health Act Section 37 with section 41 restrictions
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 34 MHAEVENTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
LSTATUS R an2
10
12
13
14
15
16
17
18
19
20
31
32 Formally detained under other acts34
35
36
99 Not KnownMENTCAT07 R an1 A
B
Legal Status Classification Code following event
A Patient will have a Legal Status Classification if they are or have been formally detained under the Mental Health Act or if they are under the care of a Consultant in the psychiatric specialties whether or not formally detained.
Formally detained under Mental Health Act Section 37
Formally detained under Mental Health Act Section 38
Formally detained under Mental Health Act Section 44
Formally detained under Mental Health Act Section 46
Formally detained under Mental Health Act Section 47 with section 49 restrictions
Formally detained under Mental Health Act Section 47
Formally detained under Mental Health Act Section 48 with section 49 restrictions
Formally detained under Mental Health Act Section 48
Formally detained under Mental Health Act Section 135
Formally detained under Mental Health Act Section 136
Formally detained under Criminal Proceedings (Insanity) Act 1964 as amended by the Criminal Procedures (Insanity and Unfitness to Plead) Act 1991
Formally detained under Mental Health Act Section 45A
Subject to guardianship under Mental Health Act Section 7
Subject to guardianship under Mental Health Act Section 37
Mental Health Act 2007 Mental Category following event
The mental category of a detained patient.
A single definition of mental disorder has been introduced by the Mental Health Act 2007, replacing the four mental categories defined under the MHA 1983.
The new amended Mental Categories are intended to identify whether a learning disability was the primary reason for the patient being detained under the MHA 1983, in line with the safeguards introduced by the MHA 2007. It is not intended to purely identify whether a patient detained under the MHA1983 happens to have a learning disability.
The new Mental Categories listed below should be used for all patients detained under the Mental Health Act 1983 from 3rd November 2008.
Mental Disorder (Learning Disability not present or not primary reason for using Act)
Mental Disorder (Learning Disability primary reason for using Act)
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 34 MHAEVENTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
MENTCAT07 R an1
8 Not applicable (Not detained)
9 Not known
Mental Health Act 2007 Mental Category following event
The mental category of a detained patient.
A single definition of mental disorder has been introduced by the Mental Health Act 2007, replacing the four mental categories defined under the MHA 1983.
The new amended Mental Categories are intended to identify whether a learning disability was the primary reason for the patient being detained under the MHA 1983, in line with the safeguards introduced by the MHA 2007. It is not intended to purely identify whether a patient detained under the MHA1983 happens to have a learning disability.
The new Mental Categories listed below should be used for all patients detained under the Mental Health Act 1983 from 3rd November 2008.
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 34 - Mental Health Act Event Episodes
ACCESS TABLE 34 MHAEVENTMAPPING NOTES
Although the STARTDATE can not be directly mapped from dates in v3.5 MHAEVENT table, patients with an EVENTDATE in v3.5 should have a record in this new table.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 34 MHAEVENTMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a direct mapping of the data item 'Legal status classification code following event' and its associated values in Table 21 MHAEVENT within MHMDS v3.5
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 34 MHAEVENTMAPPING NOTES
This is a direct mapping of the data item 'Legal status classification code following event' and its associated values in Table 21 MHAEVENT within MHMDS v3.5
This is a direct mapping of the data item 'Mental Health Act 2007 Mental Category following event' and its associated values in Table 21 MHAEVENT within MHMDS v3.5
Table 34 - MHAEVENT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 34 MHAEVENTMAPPING NOTES
This is a direct mapping of the data item 'Mental Health Act 2007 Mental Category following event' and its associated values in Table 21 MHAEVENT within MHMDS v3.5
Table 35 - SCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 35 - Supervised Community Treatment
Information within the SCT table should be mapped from Table 21a SCT in v3.5
ACCESS TABLE 35 SCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
EXPIRYDATE R date
ENDDATE R date
ENDREASON R an2
01 Patient discharged
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Supervised Community Treatment Start Date
The start date for a period of Supervised Community Treatment (SCT) under S17A of the Mental Health Act 1983 (as amended by the Mental Health Act 2007).
Supervised Community Treatment Expiry Date
The date which the Supervised Community Treatment (SCT) for a patient was due to expire. This should be updated following the extension of a Supervised Community Treatment.
NB - This data item should only be recorded where the Supervised Community Treatment for the patient has been extended
Supervised Community Treatment End Date
The end date for a period of Supervised Community Treatment (SCT) under S17A of the Mental Health Act 1983 (as amended by the Mental Health Act 2007).
Supervised Community Treatment End Reason
The reason for the termination of a period of Supervised Community Treatment.
Table 35 - SCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 35 SCTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
ENDREASON R an2
02
03 Patient died
04 Patient transferred outside of England
05 Patient transferred to another provider
Supervised Community Treatment End Reason
The reason for the termination of a period of Supervised Community Treatment.
Supervised Community Treatment revoked
Table 35 - SCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 35 - Supervised Community Treatment
Information within the SCT table should be mapped from Table 21a SCT in v3.5
ACCESS TABLE 35 SCTMAPPING NOTES
This is a direct mapping of the data item 'Supervised Community Treatment Start Date' in Table 21a SCT within MHMDS v3.5
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a direct mapping of the data item 'Supervised Community Treatment End Date' in Table 21a SCT within MHMDS v3.5
This data item should be mapped from from the data item 'Supervised Community Treatment End Reason' in Table 21a SCT within MHMDS v3.5.
Please note that there is an additional value 'Patient transferred to another provider' which has been added in MHMDS v4.0.
This is a direct mapping to code [01] Patient discharged
Table 35 - SCT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 35 SCTMAPPING NOTES
This is a direct mapping to code [02] Supervised Community Treatment revoked
This is a direct mapping to code [03] Patient died
This is a direct mapping to code [04] Patient transferred outside of England
New Value
Please note that Services may be capturing this value for local requirements and should be mapped where possible.
Table 36 - SCTRECALL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 36 - Supervised Community Treatment Recalls
Information within the SCTRECALL table should be mapped from Table 21b SCTRECALL in v3.5
ACCESS TABLE 36 SCTRECALLACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
STARTTIME M time
ENDDATE R date
ENDTIME R time
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Supervised Community Treatment Recall Start Date
The start date for a period of Recall to hospital for treatment for a patient on Supervised Community Treatment (SCT) under S17A of the Mental Health Act 1983 (as amended by the Mental Health Act 2007) in the format dd/mm/ccyy.
Supervised Community Treatment Recall Start Time
The start time for a period of Recall to hospital for treatment for a patient on Supervised Community Treatment (SCT) under S17A of the Mental Health Act 1983 (as amended by the Mental Health Act 2007) in the format hh:mm.
Supervised Community Treatment Recall End Date
The end date for a period of Recall to hospital for treatment for a patient on Supervised Community Treatment (SCT) under S17A of the Mental Health Act 1983 (as amended by the Mental Health Act 2007) in the format dd/mm/ccyy.
Supervised Community Treatment Recall End Time
The end time for a period of Recall to hospital for treatment for a patient on Supervised Community Treatment (SCT) under S17A of the Mental Health Act 1983 (as amended by the Mental Health Act 2007) in the format hh:mm.
Table 36 - SCTRECALL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 36 - Supervised Community Treatment Recalls
Information within the SCTRECALL table should be mapped from Table 21b SCTRECALL in v3.5
ACCESS TABLE 36 SCTRECALLMAPPING NOTES
This is a direct mapping of the data item 'Supervised Community Treatment Recall Start Date' in Table 21b SCTRECALL within MHMDS v3.5
This is a direct mapping of the data item 'Supervised Community Treatment Recall Start Time' in Table 21b SCTRECALL within MHMDS v3.5
This is a direct mapping of the data item 'Supervised Community Treatment Recall End Date' in Table 21b SCTRECALL within MHMDS v3.5
This is a direct mapping of the data item 'Supervised Community Treatment Recall End Time' in Table 21b SCTRECALL within MHMDS v3.5
Table 37 - INTERVENTION
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 37 - Intervention (Read)
Information within the INTERVENTION table should be mapped from Table 21 REV in v3.5
ACCESS TABLE 37 INTERVENTIONACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Intervention Date date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date that treatment or an intervention was undertaken for the patient.
Table 37 - INTERVENTION
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 37 INTERVENTIONACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
TREAT O Intervention (Read) an6The treatment or intervention undertaken for the patient.
http://www.connectingforhealth.nhs.uk/systemsandservices/data/clinicalcoding
Table 37 - INTERVENTION
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 37 - Intervention (Read)
Information within the INTERVENTION table should be mapped from Table 21 REV in v3.5
ACCESS TABLE 37 INTERVENTIONMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit Intervention Date then it is advised that the data item 'Date of Review' in Table 19 REV in MHMDS v3.5 where a code has been recorded/updated against the data items:
RX1 Treatment element 1 agreed at reviewRX2 Treatment element 2 agreed at reviewRX3 Treatment element 3 agreed at reviewRX4 Treatment element 4 agreed at reviewRX5 Treatment element 5 agreed at reviewRX6 Treatment element 6 agreed at review
Please note that the Date of Review may not necessarily be the date of a particular intervention. Systems may capture this data item more accurately.
Table 37 - INTERVENTION
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
ACCESS TABLE 37 INTERVENTIONMAPPING NOTES
This is a new data item in v4.0 so can not be mapped from v3.5.
Where Services are currently capturing this data item for local use then it is advised that the information should be submitted as specified.
Where Services are not locally capturing an explicit Intervention code then it is advised that the following data items are used from Table 19 REV in MHMDS v3.5:
RX1 Treatment element 1 agreed at reviewRX2 Treatment element 2 agreed at reviewRX3 Treatment element 3 agreed at reviewRX4 Treatment element 4 agreed at reviewRX5 Treatment element 5 agreed at reviewRX6 Treatment element 6 agreed at review
Table 38 - ECT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 38 - Electro-Convulsive Therapy
Information within the ECT table should be mapped from Table 22 ECT in v3.5
ACCESS TABLE 38 ECTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of ECT administration
The date that Electro-Convulsive Therapy (ECT) was administered to a patient.
Table 38 - ECT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 38 - Electro-Convulsive Therapy
Information within the ECT table should be mapped from Table 22 ECT in v3.5
ACCESS TABLE 38 ECTMAPPING NOTES
This is a direct mapping of the data item 'Date of ECT administration' in Table 22 ECT within MHMDS v3.5
Table 39 - LOA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 39 - Leave of Absence
Information within the LOA table should be mapped from Table 21c LOA in v3.5
ACCESS TABLE 39 LOAACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
ENDDATE R date
ENDREASON R an2 01
02
03 Period of leave to be extended04
05
06
07
08 Patient's death96 Other99 Not known
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Leave of Absence Start Date
The start date for a period of S17 Leave of Absence involving an overnight stay for a patient liable for detention under the Mental Health Act 1983 in the format dd/mm/ccyy.
Leave of Absence End Date
The end date for a period of S17 Leave of Absence involving an overnight stay for a patient liable for detention under the Mental Health Act 1983 in the format dd/mm/ccyy.
Leave of Absence End Reason
A coding which identifies the reason a Leave of Absence was ended.
Patient returned on or before day specified
Leave revoked and patient recalled by Mental Health Responsible Clinician
Patient failed to return on or before day specified and is absent without leave
Patient's liability for detention terminated by Mental Health Responsible Clinician
Patient's liability for detention terminated by Mental Health Act Tribunal
Patient's liability for detention terminated by Hospital Managers
Table 39 - LOA
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 39 - Leave of Absence
Information within the LOA table should be mapped from Table 21c LOA in v3.5
ACCESS TABLE 39 LOAMAPPING NOTES
This is a direct mapping of the data item 'Leave of Absence Start Date' in Table 21c LOA within MHMDS v3.5
This is a direct mapping of the data item 'Leave of Absence End Date' in Table 21c LOA within MHMDS v3.5
This is a direct mapping of the data item 'Leave of Absence End Reason' and its associated values in Table 21c LOA within MHMDS v3.5
Table 40 - AWOL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 40 - Absence without Leave
Information within the AWOL table should be mapped from Table 21d SCT in v3.5
ACCESS TABLE 40 AWOLACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M date
ENDDATE R date
ENDREASON R an2 01 Patient returned voluntarily02 Patient is taken back into custody03
04
05 Patient died99 Not known
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Absence Without Leave Start Date
The start date for a period of Absence without Leave (AWOL) involving an overnight absence for a patient detained under the Mental Health Act 1983.
Absence Without Leave End Date
The end date for a period of Absence without Leave (AWOL) involving an overnight absence for a patient detained under the Mental Health Act 1983.
Absence without Leave End Reason
The method that an occurrence of Absence without Leave was ended.
Patient fails to return by the end of the relevant period for which they are liable to be detained or subject to guardianship
Patient discharged, care or treatment finished
Table 40 - AWOL
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 40 - Absence without Leave
Information within the AWOL table should be mapped from Table 21d SCT in v3.5
ACCESS TABLE 40 AWOLMAPPING NOTES
This is a direct mapping of the data item 'Absence without Leave Start Date' in Table 21d AWOL within MHMDS v3.5
This is a direct mapping of the data item 'Absence without Leave End Date' in Table 21d AWOL within MHMDS v3.5
This is a direct mapping of the data item 'Absence without Leave End Reason' and its associated values in Table 21d AWOL within MHMDS v3.5
Table 41 - HOMELEAVE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 41 - Home Leave
ACCESS TABLE 41 HOMELEAVEACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
STARTDATE M Home Leave Start Date date
ENDDATE R Home Leave End Date date
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 41 HOMELEAVE.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The start date for a period of Home Leave for patients NOT liable for detention under the Mental Health Act 1983..
The end date for a period of Home Leave for patients NOT liable for detention under the Mental Health Act 1983..
Table 41 - HOMELEAVE
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 41 - Home Leave
ACCESS TABLE 41 HOMELEAVEMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Table 42 - SELFHRM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 42 - Self Harm
ACCESS TABLE 42 SELFHRMACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Date of Self Harm date
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 42 SELFHRM.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date that an incident of self-harm for the patient occurred.
Table 42 - SELFHRM
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 42 - Self Harm
ACCESS TABLE 42 SELFHRMMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item was currently collected as part of the Count Me In Census.
Table 43 - RESTRAINT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 43 - Use of Restraint
ACCESS TABLE 43 RESTRAINTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M The date that a patient was subjected to physical restraint. date
DURATION O n3
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 43 RESTRAINT.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of Physical Restraint
Duration of Physical Restraint
The duration of a period of physical restraint of the patient in minutes.
Table 43 - RESTRAINT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 43 - Use of Restraint
ACCESS TABLE 43 RESTRAINTMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item was currently collected as part of the Count Me In Census.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item was currently collected as part of the Count Me In Census.
Table 44 - ASSAULT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 44 - Assault on Patient
ACCESS TABLE 44 ASSAULTACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M date
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 44 ASSAULT.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
Date of Assault on Patient
The date that a reported incident of assault on the patient occurred.
Table 44 - ASSAULT
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 44 - Assault on Patient
ACCESS TABLE 44 ASSAULTMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item was currently collected as part of the Count Me In Census.
Table 45 - SECLUSION
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 45 - Periods of Seclusion
ACCESS TABLE 45 SECLUSIONACCESS NAME M/R/O DATA ITEM NAME DEFINITION FORMAT NATIONAL CODE VALUE DESCRIPTION
PTID M an20
EVENTDATE M Date of Seclusion date
DURATION O Duration of Seclusion n3
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in Table 45 SECLUSION.
MHMDS Local Patient Identifier
The MHMDS Local Patient Identifier used to identify the patient for the purposes of this dataset. It may be different from that used in any of the source systems.
The date that the patient was subjected to a period of seclusion.
The duration of a period of seclusion of the patient in minutes.
Table 45 - SECLUSION
Title: MHMDS v4.0 Interim Mapping Guidance Version: 1.2 Date: 14/06/2011
Table 45 - Periods of Seclusion
ACCESS TABLE 45 SECLUSIONMAPPING NOTES
This a new table in MHMDS v4.0 so can not be mapped from v3.5. Where Services are currently capturing this information for local use then it is advised to submit as specified in
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item was currently collected as part of the Count Me In Census.
This is a new data item in v4.0 so can not be mapped from v3.5.
If Services are currently collecting this item for local use then it possible for it to be mapped.
Please note that this item was currently collected as part of the Count Me In Census.