11. Appendix A - Record Layouts¶
11.1. File Header Record¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = HR | ||||||||||||||||
State/Territory Identifier (State) [1] | Char[1] | 9 | 720081 |
|
||||||||||||||||
Batch Number (BatchNo) | Char[9] | 10 | — | YYYYNNNNN | ||||||||||||||||
Report Period Start Date (RepStart) | Date[8] | 19 | — | The date of the start of the period to which the data included in the current file refers. | ||||||||||||||||
Report Period End Date (RepEnd) | Date[8] | 27 | — | The date of the finish of the period to which the data included in the current file refers. | ||||||||||||||||
Data File Generation Date (GenDt) | Date[8] | 35 | — | The date on which the current file was created. | ||||||||||||||||
Data File Type (FileType) | Char[4] | 43 | — | Value = NOCC | ||||||||||||||||
NOCC Reporting Specification Version (SpecVer) | Char[5] | 47 | — | Value = 02.03 |
Record length = 51
Notes
[1] | METeOR includes code 9, but that is not applicable to the NOCC |
11.2. Region Details¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = REG | ||||||||||||||||
State/Territory Identifier (State) [2] | Char[1] | 9 | 720081 |
|
||||||||||||||||
Region Identifier (RegId) | Char[2] | 10 | 269940 | AA: (values as specified by individual jurisdiction) | ||||||||||||||||
Region Name (RegName) | Char[60] | 12 | 407187 | Common name used to identify the Region. |
Record length = 71
Notes
[2] | METeOR includes code 9, but that is not applicable to the NOCC |
11.3. Organisation Details¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = ORG | ||||||||||||||||
State/Territory Identifier (State) [3] | Char[1] | 9 | 720081 |
|
||||||||||||||||
Region Identifier (RegId) | Char[2] | 10 | 269940 | AA: (values as specified by individual jurisdiction) | ||||||||||||||||
Organisation Identifier (OrgId) | Char[4] | 12 | 404186 | NNNN: Mental health service organisation identifier. Identifiers used in this collection should map to the identifiers used in data for the NMDS for Mental Health Establishments. Identifiers used to report Mental Health Service Organisations within NOCC should be the same as those used identify organisations in the NMDS - Mental Health Establishments. |
||||||||||||||||
Organisation Name (OrgName) | Char[100] | 16 | 405767 | Common name used to identify the Organisation. |
Record length = 115
Notes
[3] | METeOR includes code 9, but that is not applicable to the NOCC |
11.4. Hospital - Cluster Details¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = HOSPCLUS | ||||||||||||||||
State/Territory Identifier (State) [4] | Char[1] | 9 | 720081 |
|
||||||||||||||||
Region Identifier (RegId) | Char[2] | 10 | 269940 | AA: (values as specified by individual jurisdiction) | ||||||||||||||||
Organisation Identifier (OrgId) | Char[4] | 12 | 404186 | NNNN: Mental health service organisation identifier. Identifiers used in this collection should map to the identifiers used in data for the NMDS for Mental Health Establishments. Identifiers used to report Mental Health Service Organisations within NOCC should be the same as those used identify organisations in the NMDS - Mental Health Establishments. |
||||||||||||||||
Hospital - Cluster Identifier (HospClusId) | Char[5] | 16 | — | For admitted patient service units, the Hospital-Cluster identifier should be identical to that used to identify the hospital to which the service unit ‘belongs’. For ambulatory and residential services units, where there is no Service unit cluster, the Hospital - Cluster identifier is to be reported as ‘00000’ and the Hospital - Cluster Name would use the relevant organisation name. | ||||||||||||||||
Hospital - Cluster Name (HospClusName) | Char[100] | 21 | — | For admitted patient service units, the Hospital-Cluster identifier should be identical to that used to identify the hospital to which the service unit ‘belongs’. For ambulatory and residential services units, where there is no Service unit cluster, the Hospital - Cluster identifier is to be reported as ‘00000’ and the Hospital - Cluster Name would use the relevant organisation name. | ||||||||||||||||
Co-Location Status (CoLocStatus) | Char[1] | 121 | 286995 |
Code 8 should only be used only where Service Unit Type = 2 (Residential care service unit) or 3 (Ambulatory care service unit). |
Record length = 121
Notes
[4] | METeOR includes code 9, but that is not applicable to the NOCC |
11.5. Service Unit Details¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = SERV | ||||||||||||||||
State/Territory Identifier (State) [5] | Char[1] | 9 | 720081 |
|
||||||||||||||||
Region Identifier (RegId) | Char[2] | 10 | 269940 | AA: (values as specified by individual jurisdiction) | ||||||||||||||||
Organisation Identifier (OrgId) | Char[4] | 12 | 404186 | NNNN: Mental health service organisation identifier. Identifiers used in this collection should map to the identifiers used in data for the NMDS for Mental Health Establishments. Identifiers used to report Mental Health Service Organisations within NOCC should be the same as those used identify organisations in the NMDS - Mental Health Establishments. |
||||||||||||||||
Hospital - Cluster Identifier (HospClusId) | Char[5] | 16 | — | For admitted patient service units, the Hospital-Cluster identifier should be identical to that used to identify the hospital to which the service unit ‘belongs’. For ambulatory and residential services units, where there is no Service unit cluster, the Hospital - Cluster identifier is to be reported as ‘00000’ and the Hospital - Cluster Name would use the relevant organisation name. | ||||||||||||||||
Service Unit Identifier (SUId) | Char[6] | 21 | — | NNNNNN: Unique Service Unit Identifier Several guidelines apply to the way in which an organisation’s mental health services are identified as service units. These are based on the minimum reporting that is required for the purposes of the National Minimum Data Set, particularly the NMDS - Mental Health Establishments. A ‘Service Unit’ is defined as a discrete service provider unit within the ‘Mental Health Service Organisation’. Several guidelines apply to the way in which an organisation’s mental health services are reported as service units. These are based on the minimum reporting that is required for the purposes of the National Minimum Data Set, particularly the NMDS - Mental Health Establishments. ADMITTED PATIENT SERVICE UNITS: Admitted patient service units should be differentiated by Target Population (General, Older Persons, Child & Adolescent, Youth and Forensic) and Program Type (Acute vs Other). For example, if a hospital had separate wards for Child & Adolescent and General Adult populations, these should be reported as separate service units.Similarly, if the hospital provided separate wards for Older Persons acute and Older Person other program types, this would require separate service units to be identified (that is, defined by the program type as well as the target population). The overarching principle is that the same service unit identification policy must be applied to the admitted patient service units data reported under NOCC and the NMDS - Mental Health Establishments. RESIDENTIAL SERVICE UNITS: Residential service units should be differentiated by Target Population (General, Older Persons, Child & Adolescent, Youth and Forensic). Where possible, it is also desirable that residential service units identified in NOCC data correspond directly on one-to-one basis to those reported in the NMDS - Residential Mental Health Care. AMBULATORY SERVICE UNITS: Ambulatory service units should be differentiated by Target Population (General, Older Persons, Child & Adolescent, Youth and Forensic). Where an organisation provides multiple teams serving the same target population, these may be grouped and reported as a single Service Unit, or identified as individual Service Units in their own right. Where possible, it is also desirable that residential service units identified in NOCC data correspond directly on one-to-one basis to those reported in the NMDS - Community Mental Health Care. States should ensure that the ‘Service Unit identifiers’ are unique across all service unit types (i.e. admitted patient, ambulatory care, residential care services). Identifiers used to supply data to NOCC in respect of a particular service unit should be stable over time - that is, unless there has been a significant change to the unit, the same identifier should be used from year to year of reporting. The ‘Service Unit Identifier’ is reported at each ‘Collection Occasion’. Ideally, where a mental health servce provides mixed service types (eg, overnight inpatient care as well as ambulatory care), each component will be defined as a separate ‘Service Unit’ and assigned a unique ‘Service Unit Identifier.’ |
||||||||||||||||
Service Unit Name (SUName) | Char[100] | 27 | — | Common name used to identify the service unit. | ||||||||||||||||
Service Unit Sector (Sector) | Char[1] | 127 | 269977 |
|
||||||||||||||||
Target Population (TargetPop) [6] | Char[1] | 128 | 682403 |
|
||||||||||||||||
Program Type (ProgType) | Char[1] | 129 | 288889 |
ACUTE CARE Programs primarily providing specialist psychiatric care for people with acute episodes of mental disorder. These episodes are characterised by recent onset of severe clinical symptoms of mental disorder, that have potential for prolonged dysfunction or risk to self and/or others. The key characteristic of acute services is that this treatment effort is focused on short-term treatment. Acute services may be focused on assisting people who have had no prior contact or previous psychiatric history, or individuals with acontinuing mental disorder for whom there has been an acute exacerbation of symptoms. This category applies only to services with a mental health service setting of overnight admitted patient care or residential care. OTHER Refers to all other programs primarily providing admitted patient care. Includes programs providing rehabilitation services that have a primary focus on intervention to reduce functional impairments that limit the independence of patients. Rehabilitation services are focused on disability and the promotion of personal recovery. They are characterised by an expectation of substantial improvement over the short to mid-term. Patients treated by rehabilitation services usually have a relatively stable pattern of clinical symptoms. Also includes programs providing extended care services that primarily provide care over an indefinite period for patients who have a stable but severe level of functional impairment and an inability to function independently, thus requiring extensive care and support. Patients of extended care services present a stable pattern of clinical symptoms, which may include high levels of severe unremitting symptoms of mental disorder. Treatment is focused on preventing deterioration and reducing impairment; improvement is expected to occur slowly. |
||||||||||||||||
Geographical Location of Establishment (EstArea) | Char[9] | 130 | 659774 | Statistical Area Level 2 (SA2) code (ASGS 2016) An SA2 is identifiable by a 9-digit fully hierarchical code. The SA2 identifier is a 4-digit code, assigned in alphabetical order within an SA3. An SA2 code is only unique within a state/territory if it is preceded by the state/territory identifier.
For the purposes of the NOCC dataset, area is reported at Service Unit level. |
||||||||||||||||
Service Unit Type (SUType) | Char[1] | 139 | 493347 |
This data element is intended to describe the most common type of care provided by the service unit. It does not have to correspond to the Episode Service Setting data element reported on the Collection Occasion record. For example, a service unit that primarily provides admitted patient care may be the responsible service unit for a person receiving ambulatory care. In this scenario, data collected at each Collection Occasion would report the Episode Service Setting as ‘ambulatory’ (because this the setting within which the Episode of Mental Health Care takes place) and the Service Unit Type as ‘admitted patient service unit’ (because this correctly describes the typical setting in which care is provided by this service unit). |
Record length = 139
Notes
[5] | METeOR includes code 9, but that is not applicable to the NOCC |
[6] | Codes 7 and 9 are not applicable to NOCC |
11.6. Collection Occasion Details¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = COD | ||||||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||||||
Person Identifier (PID) | Char[20] | 39 | 290046 | Any valid identifier as defined by the ‘Mental Health Service Organisation.’ | ||||||||||||||||||
Date of Birth (DoB) | Date[8] | 59 | 287007 | The consumer’s date of birth. | ||||||||||||||||||
Sex (Sex) | Char[1] | 67 | 635126 |
|
||||||||||||||||||
Episode Service Setting (Setting) | Char[1] | 68 | — |
PSYCHIATRIC INPATIENT SERVICE Refers to overnight care provided in public psychiatric hospitals and designated psychiatric units in public acute hospitals. Psychiatric hospitals are establishments devoted primarily to the treatment and care of admitted patients with psychiatric, mental or behavioural disorders. Designated psychiatric units in a public acute hospital are staffed by health professionals with specialist mental health qualifications or training and have as their principal function the treatment and care of patients affected by mental disorder. For the purposes of NOCC specification, care provided by an Ambulatory mental health service team to a person admitted to a designated Special Care Suite or ‘Rooming-In’ facility within in a community general hospital for treatment of a mental or behavioural disorder is also included under this setting. COMMUNITY RESIDENTIAL MENTAL HEALTH SERVICE Refers to overnight care provided in residential units staffed on a 24-hour basis by health professionals with specialist mental health qualifications or training and established in a community setting which provides specialised treatment, rehabilitation or care for people affected by a mental illness or psychiatric disability. Psychogeriatric hostels and psychogeriatric nursing homes are included in this category. AMBULATORY MENTAL HEALTH SERVICE Refers to non-admitted, non-residential services provided by health professionals with specialist mental health qualifications or training. Ambulatory mental health services include community-based crisis assessment and treatment teams, day programs, psychiatric outpatient clinics provided by either hospital or community-based services, child and adolescent outpatient and community teams, social and living skills programs, psychogeriatric assessment services and so forth. For the purposes of NOCC specification, care provided by hospital-based consultation-liaison services to admitted patients in non-psychiatric and hospital emergency settings is also included under this setting. NOTES 1. This item will be used to derive the type of ‘Episode of Mental Health Care’ provided to the consumer. 2. A single ‘Service Unit’ may provide care in all three settings. For example, a psychiatric hospital may provide group programs tailored for people living in the community who attend on a regular basis, or run a community nursing outreach service that visits people in the homes. It is essential that these programs be differentiated when reporting the ‘Mental Health Service Setting’ that is providing the episode of care, even though all programs may share the same ‘Service Unit Identifier’. For example, in the above scenario, where a consumer who is not currently an overnight admitted patient attends the hospital-based group program, the ‘Episode Service Setting’ should be recorded as Ambulatory mental health service, NOT Psychiatric inpatient service. 3. Episode Service Setting should not be confused with ‘Service Unit Type’, which classifies service units into inpatient, residential or ambulatory service types. The former is an attribute of the Episode of Mental Health Care, the latter is an attribute of the Service Unit. 4. Where a person might be considered as receiving concurrently two or more episodes of mental health care by virtue of being treated in more than one setting simultaneously the following order of precedence applies: Inpatient, Community Residential, Ambulatory |
||||||||||||||||||
Age Group (AgeGrp) [7] | Char[1] | 69 | — |
|
||||||||||||||||||
Collection Occasion Date (ColDt) | Date[8] | 70 | — | The reference date for all data collected at any given ‘Collection Occasion,’ defined as the date on which the ‘Collection Occasion (Admission, Review, Discharge)’ occurred. The ‘Collection Occasion Date’ should be distinguished from the actual date of completion of individual measures that are required at the specific occasion. In practice, the various measures may be completed by clinicians and consumers over several days. For example, at ‘Review’ during ambulatory care, the client’s case manager might complete the HoNOS and LSP during the clinical case review on the scheduled date, but in order to include their client’s responses to the consumer self-report measure, they would most likely have asked the client to complete the measure at their last contact with them. For national reporting and statistical purposes, a single date is required which ties all the standardised measures and other data items together in a single ‘Collection Occasion’ . The actual collection dates of the individual data items and standard measures may be collected locally but is not required in the national reporting extract. |
||||||||||||||||||
Reason for Collection (ColRsn) | Char[2] | 78 | — |
NEW REFERRAL Admission to a new inpatient, community residential or ambulatory ‘Episode of Mental Health Care’ of a consumer not currently under the active care of the ‘Mental Health Service Organisation’. TRANSFER FROM OTHER TREATMENT SETTING Transfer of care between an inpatient, community residential or ambulatory setting of a consumer currently under the active care of the ‘Mental Health Service Organisation’. ADMISSION - OTHER Admission to a new inpatient, community residential or ambulatory episode of care for any reason other than defined above. 3-MONTH (91 DAY) REVIEW Standard review conducted at 91 days following admission to the current ‘Episode of Mental Health Care’ or 91 days subsequent to the preceding ‘Review’. REVIEW - OTHER Standard review conducted for reasons other than the above. NO FURTHER CARE Discharge from an inpatient, community residential or ambulatory episode of care of a consumer for whom no further care is planned by the ‘Mental Health Service Organisation’. TRANSFER TO CHANGE OF TREATMENT SETTING Transfer of care between an inpatient, community residential or ambulatory setting of a consumer currently under the care of the ‘Mental Health Service Organisation’ . DEATH Completion of an ‘Episode of Mental Health Care’ following the death of the consumer. DISCHARGE - OTHER Discharge from an inpatient, community residential or ambulatory ‘Episode of Mental Health Care’ for any reason other than defined above. |
||||||||||||||||||
State/Territory Identifier (State) [8] | Char[1] | 80 | 720081 |
|
||||||||||||||||||
Region Identifier (RegId) | Char[2] | 81 | 269940 | AA: (values as specified by individual jurisdiction) | ||||||||||||||||||
Organisation Identifier (OrgId) | Char[4] | 83 | 404186 | NNNN: Mental health service organisation identifier. Identifiers used in this collection should map to the identifiers used in data for the NMDS for Mental Health Establishments. Identifiers used to report Mental Health Service Organisations within NOCC should be the same as those used identify organisations in the NMDS - Mental Health Establishments. |
||||||||||||||||||
Hospital - Cluster Identifier (HospClusId) | Char[5] | 87 | — | For admitted patient service units, the Hospital-Cluster identifier should be identical to that used to identify the hospital to which the service unit ‘belongs’. For ambulatory and residential services units, where there is no Service unit cluster, the Hospital - Cluster identifier is to be reported as ‘00000’ and the Hospital - Cluster Name would use the relevant organisation name. | ||||||||||||||||||
Service Unit Identifier (SUId) | Char[6] | 92 | — | NNNNNN: Unique Service Unit Identifier Several guidelines apply to the way in which an organisation’s mental health services are identified as service units. These are based on the minimum reporting that is required for the purposes of the National Minimum Data Set, particularly the NMDS - Mental Health Establishments. A ‘Service Unit’ is defined as a discrete service provider unit within the ‘Mental Health Service Organisation’. Several guidelines apply to the way in which an organisation’s mental health services are reported as service units. These are based on the minimum reporting that is required for the purposes of the National Minimum Data Set, particularly the NMDS - Mental Health Establishments. ADMITTED PATIENT SERVICE UNITS: Admitted patient service units should be differentiated by Target Population (General, Older Persons, Child & Adolescent, Youth and Forensic) and Program Type (Acute vs Other). For example, if a hospital had separate wards for Child & Adolescent and General Adult populations, these should be reported as separate service units.Similarly, if the hospital provided separate wards for Older Persons acute and Older Person other program types, this would require separate service units to be identified (that is, defined by the program type as well as the target population). The overarching principle is that the same service unit identification policy must be applied to the admitted patient service units data reported under NOCC and the NMDS - Mental Health Establishments. RESIDENTIAL SERVICE UNITS: Residential service units should be differentiated by Target Population (General, Older Persons, Child & Adolescent, Youth and Forensic). Where possible, it is also desirable that residential service units identified in NOCC data correspond directly on one-to-one basis to those reported in the NMDS - Residential Mental Health Care. AMBULATORY SERVICE UNITS: Ambulatory service units should be differentiated by Target Population (General, Older Persons, Child & Adolescent, Youth and Forensic). Where an organisation provides multiple teams serving the same target population, these may be grouped and reported as a single Service Unit, or identified as individual Service Units in their own right. Where possible, it is also desirable that residential service units identified in NOCC data correspond directly on one-to-one basis to those reported in the NMDS - Community Mental Health Care. States should ensure that the ‘Service Unit identifiers’ are unique across all service unit types (i.e. admitted patient, ambulatory care, residential care services). Identifiers used to supply data to NOCC in respect of a particular service unit should be stable over time - that is, unless there has been a significant change to the unit, the same identifier should be used from year to year of reporting. The ‘Service Unit Identifier’ is reported at each ‘Collection Occasion’. Ideally, where a mental health servce provides mixed service types (eg, overnight inpatient care as well as ambulatory care), each component will be defined as a separate ‘Service Unit’ and assigned a unique ‘Service Unit Identifier.’ |
||||||||||||||||||
Episode Identifier (EpiId) | Char[36] | 98 | — | As constructed by the organisation which generates the file. If no Episode link is available, the field should be filled with spaces. | ||||||||||||||||||
Country of Birth (CoB) | Char[4] | 134 | 659454 | To be provided in accordance with the Standard Australian Classification of Countries (SACC). ABS catalogue no. 1269.0 (2011). Values from 1601-1607, inclusive, are not permitted in this NMDS (Antarctica). | ||||||||||||||||||
Indigenous Status (IndigSt) | Char[1] | 138 | 602543 |
|
||||||||||||||||||
Area of Usual Residence (ResArea) | Char[9] | 139 | 659725 | Statistical Area Level 2 (SA2) code (ASGS 2016) NNNNNNNNN |
Record length = 147
Notes
[7] | In some circumstances a person may be legitimately assigned to a different AGE GROUP to that in which they would assigned on the basis of their actual age. For example, a person aged 60 years who was being cared for in an inpatient psychogeriatric unit may be assigned to the Older person’s AGE GROUP. |
[8] | METeOR includes code 9, but that is not applicable to the NOCC |
11.7. HoNOS or HoNOS65+¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = HONOS | ||||||||||||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||||||||||||
HoNOS Version (HnosVer) | Char[2] | 39 | — |
|
||||||||||||||||||||||||
HoNOS Item 01 (Hnos01) | Number[1] | 41 | — |
|
||||||||||||||||||||||||
HoNOS Item 02 (Hnos02) | Number[1] | 42 | — |
|
||||||||||||||||||||||||
HoNOS Item 03 (Hnos03) | Number[1] | 43 | — |
|
||||||||||||||||||||||||
HoNOS Item 04 (Hnos04) | Number[1] | 44 | — |
|
||||||||||||||||||||||||
HoNOS Item 05 (Hnos05) | Number[1] | 45 | — |
|
||||||||||||||||||||||||
HoNOS Item 06 (Hnos06) | Number[1] | 46 | — |
|
||||||||||||||||||||||||
HoNOS Item 07 (Hnos07) | Number[1] | 47 | — |
|
||||||||||||||||||||||||
HoNOS Item 08 (Hnos08) | Number[1] | 48 | — |
|
||||||||||||||||||||||||
HoNOS Item 08a (Hnos08a) | Char[1] | 49 | — |
|
||||||||||||||||||||||||
HoNOS Item 09 (Hnos09) | Number[1] | 50 | — |
|
||||||||||||||||||||||||
HoNOS Item 10 (Hnos10) | Number[1] | 51 | — |
|
||||||||||||||||||||||||
HoNOS Item 11 (Hnos11) | Number[1] | 52 | — |
|
||||||||||||||||||||||||
HoNOS Item 12 (Hnos12) | Number[1] | 53 | — |
|
Record length = 53
Notes
11.8. LSP-16¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = LSP16 | ||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||
LSP-16 Version (LspVer) | Char[2] | 39 | — | Value = 01 | ||||||||||||
LSP-16 Item 01 (Lsp01) [9] | Number[1] | 41 | — |
|
||||||||||||
LSP-16 Item 02 (Lsp02) | Number[1] | 42 | — |
|
||||||||||||
LSP-16 Item 03 (Lsp03) | Number[1] | 43 | — |
|
||||||||||||
LSP-16 Item 04 (Lsp04) | Number[1] | 44 | — |
|
||||||||||||
LSP-16 Item 05 (Lsp05) | Number[1] | 45 | — |
|
||||||||||||
LSP-16 Item 06 (Lsp06) | Number[1] | 46 | — |
|
||||||||||||
LSP-16 Item 07 (Lsp07) | Number[1] | 47 | — |
|
||||||||||||
LSP-16 Item 08 (Lsp08) | Number[1] | 48 | — |
|
||||||||||||
LSP-16 Item 09 (Lsp09) | Number[1] | 49 | — |
|
||||||||||||
LSP-16 Item 10 (Lsp10) | Number[1] | 50 | — |
|
||||||||||||
LSP-16 Item 11 (Lsp11) | Number[1] | 51 | — |
|
||||||||||||
LSP-16 Item 12 (Lsp12) | Number[1] | 52 | — |
|
||||||||||||
LSP-16 Item 13 (Lsp13) | Number[1] | 53 | — |
|
||||||||||||
LSP-16 Item 14 (Lsp14) | Number[1] | 54 | — |
|
||||||||||||
LSP-16 Item 15 (Lsp15) | Number[1] | 55 | — |
|
||||||||||||
LSP-16 Item 16 (Lsp16) | Number[1] | 56 | — |
|
Record length = 56
Notes
[9] | The order of coding of domain for each LSP-16 item shows increasing levels of disability with increasing scores. No disability is coded as 0 whilst the most severe level of disability is coded as 3. This scoring is consistent with the scoring used by the other clinician- rated measures. However, the original 39 item version of the LSP employed the reverse of this convention, with high levels of disability being coded 0. |
11.9. RUG-ADL¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = RUGADL | ||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||
RUGADL Version (RugAdlVer) | Char[2] | 39 | — | Value = 01 | ||||||||||||
RUGADL Item 01 (RugAdl1) [10] | Number[1] | 41 | — |
|
||||||||||||
RUGADL Item 02 (RugAdl2) [11] | Number[1] | 42 | — |
|
||||||||||||
RUGADL Item 03 (RugAdl3) [12] | Number[1] | 43 | — |
|
||||||||||||
RUGADL Item 04 (RugAdl4) [13] | Number[1] | 44 | — |
|
Record length = 44
Notes
[10] | Notice that a rating of 2 is not included in the domain of valid ratings. |
[11] | Notice that a rating of 2 is not included in the domain of valid ratings. |
[12] | Notice that a rating of 2 is not included in the domain of valid ratings. |
[13] | Ratings of 4 and 5 are not included in the domain of valid ratings. |
11.10. HoNOSCA¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = HONOSCA | ||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||
HoNOSCA Version (HnosCVer) | Char[2] | 39 | — | Value = 01 | ||||||||||||||
HoNOSCA Item 01 (HnosC01) | Number[1] | 41 | — |
|
||||||||||||||
HoNOSCA Item 02 (HnosC02) | Number[1] | 42 | — |
|
||||||||||||||
HoNOSCA Item 03 (HnosC03) | Number[1] | 43 | — |
|
||||||||||||||
HoNOSCA Item 04 (HnosC04) | Number[1] | 44 | — |
|
||||||||||||||
HoNOSCA Item 05 (HnosC05) | Number[1] | 45 | — |
|
||||||||||||||
HoNOSCA Item 06 (HnosC06) | Number[1] | 46 | — |
|
||||||||||||||
HoNOSCA Item 07 (HnosC07) | Number[1] | 47 | — |
|
||||||||||||||
HoNOSCA Item 08 (HnosC08) | Number[1] | 48 | — |
|
||||||||||||||
HoNOSCA Item 09 (HnosC09) | Number[1] | 49 | — |
|
||||||||||||||
HoNOSCA Item 10 (HnosC10) | Number[1] | 50 | — |
|
||||||||||||||
HoNOSCA Item 11 (HnosC11) | Number[1] | 51 | — |
|
||||||||||||||
HoNOSCA Item 12 (HnosC12) | Number[1] | 52 | — |
|
||||||||||||||
HoNOSCA Item 13 (HnosC13) | Number[1] | 53 | — |
|
||||||||||||||
HoNOSCA Item 14 (HnosC14) | Number[1] | 54 | — |
Items 14 and 15 are excluded from the calculation of the Total Score because they describe the patient or client’s parent’s knowledge about the person’s problems and the services available rather than aspects of the child or adolescent’s problems. |
||||||||||||||
HoNOSCA Item 15 (HnosC15) | Number[1] | 55 | — |
Items 14 and 15 are excluded from the calculation of the Total Score because they describe the patient or client’s parent’s knowledge about the person’s problems and the services available rather than aspects of the child or adolescent’s problems. |
Record length = 55
Notes
11.11. CGAS¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values |
---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = CGAS |
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. |
CGAS Version (CgasVer) | Char[2] | 39 | — | Value = 01 |
CGAS Rating (Cgas) | Number[3] | 41 | — | Rating on the Children’s Global Assessment Scale. |
Record length = 43
Notes
11.12. FIHS¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = FIHS | ||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||
FIHS Version (FihsVer) | Char[2] | 39 | — | Value = 01 | ||||||||
FIHS Item 01 (Fihs1) | Number[1] | 41 | — |
Includes: Neglect or abandonment; Physical abuse; Sexual abuse; Psychological abuse. |
||||||||
FIHS Item 02 (Fihs2) | Number[1] | 42 | — |
Includes: Loss of love relationship in childhood; Removal from home in childhood; Altered pattern of family relationships in childhood; Problems related to alleged sexual abuse of child by person within primary support group; Problems related to alleged sexual abuse of child by person outside primary support group; Problems related to alleged physical abuse of child; Personal frightening experience in childhood; Other negative life events in childhood. |
||||||||
FIHS Item 03 (Fihs3) | Number[1] | 43 | — |
Includes: Inadequate parental supervision and control; Parental overprotection; Institutional upbringing; Hostility towards and scapegoating of child; Emotional neglect of child; Other problems related to neglect in upbringing; Inappropriate parental pressure and other abnormal qualities of upbringing; Other specified problems related to upbringing. |
||||||||
FIHS Item 04 (Fihs4) | Number[1] | 44 | — |
Includes: Problems in relationship with spouse or partner; Problems in relationship with parents and in-laws; Inadequate family support; Absence of family member; Disappearance or death of family member; Disruption of family by separation and divorce; Dependant relative needing care at home; Other stressful life events affecting family and household; Other problems related to primary support group. |
||||||||
FIHS Item 05 (Fihs5) | Number[1] | 45 | — |
Includes: Problems of adjustment to lifecycle transitions; Atypical parenting situation; Living alone; Acculturation difficulty; Social exclusion and rejection; Target of perceived adverse discrimination and rejection. |
||||||||
FIHS Item 06 (Fihs6) | Number[1] | 46 | — |
Includes: Problems related to unwanted pregnancy; Problems related to multiparity; Seeking or accepting physical, nutritional or chemical interventions known to be hazardous or harmful; Seeking or accepting behavioural or psychological interventions known to be hazardous or harmful; Discord with counsellors. |
||||||||
FIHS Item 07 (Fihs7) | Number[1] | 47 | — |
Includes: Conviction in civil and criminal proceedings without imprisonment; Imprisonment or other incarceration; Problems related to release from prison; Problems related to other legal circumstances; Victim of crime or terrorism; Exposure to disaster, war or other hostilities. |
Record length = 47
Notes
11.13. MHI38 (Standard 38 item version)¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = MHI38 | ||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||
MHI38 Version (MHIVer) | Char[2] | 39 | — | Value = 01 | ||||||||||||||
Collection Status (ColSt) | Char[1] | 41 | — |
Used within BASIS32, MHI38, K10LM, K10L3D and SDQ. |
||||||||||||||
MHI38 Item 01 (MHI01) | Number[1] | 42 | — |
|
||||||||||||||
MHI38 Item 02 (MHI02) | Number[1] | 43 | — |
|
||||||||||||||
MHI38 Item 03 (MHI03) | Number[1] | 44 | — |
|
||||||||||||||
MHI38 Item 04 (MHI04) | Number[1] | 45 | — |
|
||||||||||||||
MHI38 Item 05 (MHI05) | Number[1] | 46 | — |
|
||||||||||||||
MHI38 Item 06 (MHI06) | Number[1] | 47 | — |
|
||||||||||||||
MHI38 Item 07 (MHI07) | Number[1] | 48 | — |
|
||||||||||||||
MHI38 Item 08 (MHI08) | Number[1] | 49 | — |
|
||||||||||||||
MHI38 Item 09 (MHI09) | Number[1] | 50 | — |
|
||||||||||||||
MHI38 Item 10 (MHI10) | Number[1] | 51 | — |
|
||||||||||||||
MHI38 Item 11 (MHI11) | Number[1] | 52 | — |
|
||||||||||||||
MHI38 Item 12 (MHI12) | Number[1] | 53 | — |
|
||||||||||||||
MHI38 Item 13 (MHI13) | Number[1] | 54 | — |
|
||||||||||||||
MHI38 Item 14 (MHI14) | Number[1] | 55 | — |
|
||||||||||||||
MHI38 Item 15 (MHI15) | Number[1] | 56 | — |
|
||||||||||||||
MHI38 Item 16 (MHI16) | Number[1] | 57 | — |
|
||||||||||||||
MHI38 Item 17 (MHI17) | Number[1] | 58 | — |
|
||||||||||||||
MHI38 Item 18 (MHI18) | Number[1] | 59 | — |
|
||||||||||||||
MHI38 Item 19 (MHI19) | Number[1] | 60 | — |
|
||||||||||||||
MHI38 Item 20 (MHI20) | Number[1] | 61 | — |
|
||||||||||||||
MHI38 Item 21 (MHI21) | Number[1] | 62 | — |
|
||||||||||||||
MHI38 Item 22 (MHI22) | Number[1] | 63 | — |
|
||||||||||||||
MHI38 Item 23 (MHI23) | Number[1] | 64 | — |
|
||||||||||||||
MHI38 Item 24 (MHI24) | Number[1] | 65 | — |
|
||||||||||||||
MHI38 Item 25 (MHI25) | Number[1] | 66 | — |
|
||||||||||||||
MHI38 Item 26 (MHI26) | Number[1] | 67 | — |
|
||||||||||||||
MHI38 Item 27 (MHI27) | Number[1] | 68 | — |
|
||||||||||||||
MHI38 Item 28 (MHI28) | Number[1] | 69 | — |
|
||||||||||||||
MHI38 Item 29 (MHI29) | Number[1] | 70 | — |
|
||||||||||||||
MHI38 Item 30 (MHI30) | Number[1] | 71 | — |
|
||||||||||||||
MHI38 Item 31 (MHI31) | Number[1] | 72 | — |
|
||||||||||||||
MHI38 Item 32 (MHI32) | Number[1] | 73 | — |
|
||||||||||||||
MHI38 Item 33 (MHI33) | Number[1] | 74 | — |
|
||||||||||||||
MHI38 Item 34 (MHI34) | Number[1] | 75 | — |
|
||||||||||||||
MHI38 Item 35 (MHI35) | Number[1] | 76 | — |
|
||||||||||||||
MHI38 Item 36 (MHI36) | Number[1] | 77 | — |
|
||||||||||||||
MHI38 Item 37 (MHI37) | Number[1] | 78 | — |
|
||||||||||||||
MHI38 Item 38 (MHI38) | Number[1] | 79 | — |
|
Record length = 79
Notes
11.14. BASIS32 (Standard 32 item version)¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = BASIS32 | ||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||
BASIS32 Version (BASISVer) | Char[2] | 39 | — | Value = 01 | ||||||||||||
Collection Status (ColSt) | Char[1] | 41 | — |
Used within BASIS32, MHI38, K10LM, K10L3D and SDQ. |
||||||||||||
BASIS32 Item 01 (BASIS01) | Number[1] | 42 | — |
|
||||||||||||
BASIS32 Item 02 (BASIS02) | Number[1] | 43 | — |
|
||||||||||||
BASIS32 Item 03 (BASIS03) | Number[1] | 44 | — |
|
||||||||||||
BASIS32 Item 04 (BASIS04) | Number[1] | 45 | — |
|
||||||||||||
BASIS32 Item 05 (BASIS05) | Number[1] | 46 | — |
|
||||||||||||
BASIS32 Item 06 (BASIS06) | Number[1] | 47 | — |
|
||||||||||||
BASIS32 Item 07 (BASIS07) | Number[1] | 48 | — |
|
||||||||||||
BASIS32 Item 08 (BASIS08) | Number[1] | 49 | — |
|
||||||||||||
BASIS32 Item 09 (BASIS09) | Number[1] | 50 | — |
|
||||||||||||
BASIS32 Item 10 (BASIS10) | Number[1] | 51 | — |
|
||||||||||||
BASIS32 Item 11 (BASIS11) | Number[1] | 52 | — |
|
||||||||||||
BASIS32 Item 12 (BASIS12) | Number[1] | 53 | — |
|
||||||||||||
BASIS32 Item 13 (BASIS13) | Number[1] | 54 | — |
|
||||||||||||
BASIS32 Item 14 (BASIS14) | Number[1] | 55 | — |
|
||||||||||||
BASIS32 Item 15 (BASIS15) | Number[1] | 56 | — |
|
||||||||||||
BASIS32 Item 16 (BASIS16) | Number[1] | 57 | — |
|
||||||||||||
BASIS32 Item 17 (BASIS17) | Number[1] | 58 | — |
|
||||||||||||
BASIS32 Item 18 (BASIS18) | Number[1] | 59 | — |
|
||||||||||||
BASIS32 Item 19 (BASIS19) | Number[1] | 60 | — |
|
||||||||||||
BASIS32 Item 20 (BASIS20) | Number[1] | 61 | — |
|
||||||||||||
BASIS32 Item 21 (BASIS21) | Number[1] | 62 | — |
|
||||||||||||
BASIS32 Item 22 (BASIS22) | Number[1] | 63 | — |
|
||||||||||||
BASIS32 Item 23 (BASIS23) | Number[1] | 64 | — |
|
||||||||||||
BASIS32 Item 24 (BASIS24) | Number[1] | 65 | — |
|
||||||||||||
BASIS32 Item 25 (BASIS25) | Number[1] | 66 | — |
|
||||||||||||
BASIS32 Item 26 (BASIS26) | Number[1] | 67 | — |
|
||||||||||||
BASIS32 Item 27 (BASIS27) | Number[1] | 68 | — |
|
||||||||||||
BASIS32 Item 28 (BASIS28) | Number[1] | 69 | — |
|
||||||||||||
BASIS32 Item 29 (BASIS29) | Number[1] | 70 | — |
|
||||||||||||
BASIS32 Item 30 (BASIS30) | Number[1] | 71 | — |
|
||||||||||||
BASIS32 Item 31 (BASIS31) | Number[1] | 72 | — |
|
||||||||||||
BASIS32 Item 32 (BASIS32) | Number[1] | 73 | — |
|
Record length = 73
Notes
11.15. K10+LM (Last Month version)¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = K10LM | ||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||
K10+LM Version (K10LMVer) | Char[2] | 39 | — | Value = M1 | ||||||||||||||
Collection Status (ColSt) | Char[1] | 41 | — |
Used within BASIS32, MHI38, K10LM, K10L3D and SDQ. |
||||||||||||||
K10+LM Item 01 (K10LM01) | Number[1] | 42 | — |
|
||||||||||||||
K10+LM Item 02 (K10LM02) | Number[1] | 43 | — |
|
||||||||||||||
K10+LM Item 03 (K10LM03) | Number[1] | 44 | — |
|
||||||||||||||
K10+LM Item 04 (K10LM04) | Number[1] | 45 | — |
|
||||||||||||||
K10+LM Item 05 (K10LM05) | Number[1] | 46 | — |
|
||||||||||||||
K10+LM Item 06 (K10LM06) | Number[1] | 47 | — |
|
||||||||||||||
K10+LM Item 07 (K10LM07) | Number[1] | 48 | — |
|
||||||||||||||
K10+LM Item 08 (K10LM08) | Number[1] | 49 | — |
|
||||||||||||||
K10+LM Item 09 (K10LM09) | Number[1] | 50 | — |
|
||||||||||||||
K10+LM Item 10 (K10LM10) | Number[1] | 51 | — |
|
||||||||||||||
K10+LM Item 11 (K10LM11) | Number[2] | 52 | — | In the past four weeks, how many days were you totally unable to work, study or manage your day to day activities because of these feelings? | ||||||||||||||
K10+LM Item 12 (K10LM12) | Number[2] | 54 | — | Aside from those days [coded in ‘K10+LM Item 11’], in the past four weeks, ‘how many days’ were you able to work or study or manage your day to day activities, but had to ‘cut down’ on what you did because of those feelings? | ||||||||||||||
K10+LM Item 13 (K10LM13) | Number[2] | 56 | — | In the past four weeks, how many times have you seen a doctor or any other health professional about these feelings? | ||||||||||||||
K10+LM Item 14 (K10LM14) | Number[1] | 58 | — |
|
Record length = 58
Notes
11.16. K10L3D (Last 3 days version)¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = K10L3D | ||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||
K10L3D Version (K10L3DVer) | Char[2] | 39 | — | Value = 31 | ||||||||||||||
Collection Status (ColSt) | Char[1] | 41 | — |
Used within BASIS32, MHI38, K10LM, K10L3D and SDQ. |
||||||||||||||
K10L3D Item 01 (K10L3D01) | Number[1] | 42 | — |
|
||||||||||||||
K10L3D Item 02 (K10L3D02) | Number[1] | 43 | — |
|
||||||||||||||
K10L3D Item 03 (K10L3D03) | Number[1] | 44 | — |
|
||||||||||||||
K10L3D Item 04 (K10L3D04) | Number[1] | 45 | — |
|
||||||||||||||
K10L3D Item 05 (K10L3D05) | Number[1] | 46 | — |
|
||||||||||||||
K10L3D Item 06 (K10L3D06) | Number[1] | 47 | — |
|
||||||||||||||
K10L3D Item 07 (K10L3D07) | Number[1] | 48 | — |
|
||||||||||||||
K10L3D Item 08 (K10L3D08) | Number[1] | 49 | — |
|
||||||||||||||
K10L3D Item 09 (K10L3D09) | Number[1] | 50 | — |
|
||||||||||||||
K10L3D Item 10 (K10L3D10) | Number[1] | 51 | — |
|
Record length = 51
Notes
11.17. SDQ, all versions¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = SDQ | ||||||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||||||
SDQ Version (SDQVer) | Char[5] | 39 | — |
Version 1 of each of the above is reproduced in ‘Mental Health National Outcomes and Casemix Collection: Overview of clinical and self-report measures and data items, Version 1.50’. Commonwealth Department of Health and Ageing, Canberra, 2003. |
||||||||||||||||
Collection Status (ColSt) | Char[1] | 44 | — |
Used within BASIS32, MHI38, K10LM, K10L3D and SDQ. |
||||||||||||||||
SDQ Item 01 (SDQ01) | Number[1] | 45 | — |
|
||||||||||||||||
SDQ Item 02 (SDQ02) | Number[1] | 46 | — |
|
||||||||||||||||
SDQ Item 03 (SDQ03) | Number[1] | 47 | — |
|
||||||||||||||||
SDQ Item 04 (SDQ04) | Number[1] | 48 | — |
|
||||||||||||||||
SDQ Item 05 (SDQ05) | Number[1] | 49 | — |
|
||||||||||||||||
SDQ Item 06 (SDQ06) | Number[1] | 50 | — |
|
||||||||||||||||
SDQ Item 07 (SDQ07) | Number[1] | 51 | — |
|
||||||||||||||||
SDQ Item 08 (SDQ08) | Number[1] | 52 | — |
|
||||||||||||||||
SDQ Item 09 (SDQ09) | Number[1] | 53 | — |
|
||||||||||||||||
SDQ Item 10 (SDQ10) | Number[1] | 54 | — |
|
||||||||||||||||
SDQ Item 11 (SDQ11) | Number[1] | 55 | — |
|
||||||||||||||||
SDQ Item 12 (SDQ12) | Number[1] | 56 | — |
|
||||||||||||||||
SDQ Item 13 (SDQ13) | Number[1] | 57 | — |
|
||||||||||||||||
SDQ Item 14 (SDQ14) | Number[1] | 58 | — |
|
||||||||||||||||
SDQ Item 15 (SDQ15) | Number[1] | 59 | — |
|
||||||||||||||||
SDQ Item 16 (SDQ16) | Number[1] | 60 | — |
|
||||||||||||||||
SDQ Item 17 (SDQ17) | Number[1] | 61 | — |
|
||||||||||||||||
SDQ Item 18 (SDQ18) | Number[1] | 62 | — |
|
||||||||||||||||
SDQ Item 19 (SDQ19) | Number[1] | 63 | — |
|
||||||||||||||||
SDQ Item 20 (SDQ20) | Number[1] | 64 | — |
|
||||||||||||||||
SDQ Item 21 (SDQ21) | Number[1] | 65 | — |
|
||||||||||||||||
SDQ Item 22 (SDQ22) | Number[1] | 66 | — |
|
||||||||||||||||
SDQ Item 23 (SDQ23) | Number[1] | 67 | — |
|
||||||||||||||||
SDQ Item 24 (SDQ24) | Number[1] | 68 | — |
|
||||||||||||||||
SDQ Item 25 (SDQ25) | Number[1] | 69 | — |
|
||||||||||||||||
SDQ Item 26 (SDQ26) | Number[1] | 70 | — |
|
||||||||||||||||
SDQ Item 27 (SDQ27) | Number[1] | 71 | — |
|
||||||||||||||||
SDQ Item 28 (SDQ28) | Number[1] | 72 | — |
|
||||||||||||||||
SDQ Item 29 (SDQ29) | Number[1] | 73 | — |
|
||||||||||||||||
SDQ Item 30 (SDQ30) | Number[1] | 74 | — |
|
||||||||||||||||
SDQ Item 31 (SDQ31) | Number[1] | 75 | — |
|
||||||||||||||||
SDQ Item 32 (SDQ32) | Number[1] | 76 | — |
|
||||||||||||||||
SDQ Item 33 (SDQ33) | Number[1] | 77 | — |
|
||||||||||||||||
SDQ Item 34 (SDQ34) | Number[1] | 78 | — |
|
||||||||||||||||
SDQ Item 35 (SDQ35) | Number[1] | 79 | — |
|
||||||||||||||||
SDQ Item 36 (SDQ36) | Number[1] | 80 | — |
|
||||||||||||||||
SDQ Item 37 (SDQ37) | Number[1] | 81 | — |
|
||||||||||||||||
SDQ Item 38 (SDQ38) | Number[1] | 82 | — |
|
||||||||||||||||
SDQ Item 39 (SDQ39) | Number[1] | 83 | — |
|
||||||||||||||||
SDQ Item 40 (SDQ40) | Number[1] | 84 | — |
|
||||||||||||||||
SDQ Item 41 (SDQ41) | Number[1] | 85 | — |
|
||||||||||||||||
SDQ Item 42 (SDQ42) | Number[1] | 86 | — |
|
Record length = 86
Notes
11.18. Diagnosis¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values |
---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = DIAG |
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. |
Principal Diagnosis (Dx1) | Char[8] | 39 | 699609 | ICD-10-AM (11th Edition) Formatted as ANN{.N[N]} See comments for Dx2 |
Additional Diagnosis 1 (Dx2) | Char[8] | 47 | 699606 | ICD-10-AM (11th Edition) Formatted as ANN{.N[N]} The National Centre for Classification and Coding in Health has developed simplified ICD-10-AM Mental Health Subset for use in community-based mental health service settings. Services may use this subset as the basis for coding. Note that the ‘Principal’ and ‘Additional Diagnoses’ should not be confused with the patient or client’s current clinical diagnoses or with the reasons for contact with respect to any given Service contact. Also note that definition given here is conceptually consistent but not identical with that given in the NHDD. The NHDD definition refers to the preceding Episode of care. In episodes of acute inpatient care, the Episode of care and the Period of care will almost always refer to the same interval. In extended episodes of care, the reference interval is different. |
Additional Diagnosis 2 (Dx3) | Char[8] | 55 | 699606 | ICD-10-AM (11th Edition) Formatted as ANN{.N[N]} See comments for Dx2 |
Record length = 62
Notes
11.19. Phase of Care¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = POC | ||||||||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||||||||
Phase of Care (PoC) | Char[1] | 39 | 681789 |
ACUTE The primary goal of care is the short term reduction in severity of symptoms and/or personal distress associated with the recent onset or exacerbation of a psychiatric disorder. FUNCTIONAL GAIN The primary goal of care is to improve personal, social or occupational functioning or promote psychosocial adaptation in a patient with impairment arising from a psychiatric disorder. INTENSIVE EXTENDED The primary goal of care is prevention or minimisation of further deterioration, and reduction of risk of harm in a patient who has a stable pattern of severe symptoms, frequent relapses or severe inability to function independently and is judged to require care over an indefinite period. CONSOLIDATING GAIN The primary goal of care is to maintain the level of functioning, or improving functioning during a period of recovery, minimise deterioration or prevent relapse where the patient has stabilised and functions relatively independently. Consolidating gain may also be known as maintenance. ASSESSMENT ONLY The primary goal of care is to obtain information, including collateral information where possible, in order to determine the intervention/treatment needs and to arrange for this to occur (includes brief history, risk assessment, referral to treating team or other service). |
Record length = 39
Notes
11.20. Mental Health Legal Status¶
Data Element (Field Name) | Type [Length] | Start | METeOR Identifier | Notes / Values | ||||||
---|---|---|---|---|---|---|---|---|---|---|
Record Type (RecType) | Char[8] | 1 | — | Value = MHLS | ||||||
Collection Occasion Identifier (ColId) | Char[30] | 9 | — | A unique identifier for the collection occasion as constructed by the organisation which generates the file. | ||||||
Mental Health Legal Status (LegalSt) | Char[1] | 39 | 722675 |
|
Record length = 39
Notes