|current-year| MHE NMDS ======================== Essential definitions --------------------- | Scope - Mental health establishments |current-year| (METEOR ID `790463 `__). | Statistical unit - Specialised mental health service (METEOR ID `268984 `__). | Changes for |current-year| ------------------------------ The specific detailed changes to the |current-year| (version |version|) specifications, compared to |previous-year| (version |previous-version|) are listed below. Changes to the data model ^^^^^^^^^^^^^^^^^^^^^^^^^^ .. No changes to the data model have been made. The data model changes to the |current-year| specifications, compared to |previous-year| are listed in :numref:`table-data-model-changes`. .. _table-data-model-changes: .. csv-table:: Changes made to |current-year| data model compared to |previous-year| :file: data-model-changes.csv :header-rows: 1 Changes to definitions ^^^^^^^^^^^^^^^^^^^^^^ The definitional changes to the |current-year| specifications, compared to |previous-year| are listed in :numref:`table-changes`. .. _table-changes: .. csv-table:: Changes made to |current-year| definitions compared to |previous-year| :file: changes.csv :header-rows: 1 Reporting statistical units --------------------------- The statistical units in the MHE NMDS are *Specialised Mental Health Services* METEOR identifier `268984 `__). These are the: - specialised mental health components of the state and territory health authorities, and of regions within states and territories; - specialised mental health service organisations; - hospitals or service unit clusters; - service units; and - specialised mental health services provided by private hospitals, and non-government residential service units in receipt of state or territory government funding. In general, states and territories determine the organisational units that will report as *regions,* *organisations,* and *service units* for this NMDS. Only those specialised mental health services provided by private hospitals and non government residential mental health services that receive state or territory government funding are included as service units for this NMDS. Ambulatory services managed by non-government organisations (NGOs) are not defined as statistical units for this NMDS. The following sections provide more information on each of the statistical units and reporting levels used in the MHE NMDS. State or territory ^^^^^^^^^^^^^^^^^^^ This level refers to the state or territory and should be reported using the *State/Territory identifier* data element. Region ^^^^^^^ The region refers to an administrative concept not a geographical one. States and territories may have one or more regions into which the state or territory is divided and to which its mental health service organisations belong. Region would be reported using the *Region identifier* (RegId) data element. In the smaller states or in the territories there may only be one or no region. In these cases, the *Region identifier* is to be reported as ‘00’ and the *Region name* (RegName) would repeat the name of the state or territory. Organisation ^^^^^^^^^^^^^ The organisation is defined according to the Object class *Specialised mental health service organisation* (METEOR identifier `795837 `__) and reported using the *Organisation Identifier* (OrgId) data element. An organisation is a separately constituted specialised mental health service that is responsible for the clinical governance, administration and financial management of service units providing specialised mental health care. An organisation may consist of one or more service units based in different locations and providing services in the admitted patient, residential and ambulatory settings. For example, a mental health service organisation may consist of several hospitals or two or more community centres. Where the mental health service organisation consists of multiple service units, those units can be considered to be components of the same organisation where they: - Operate under a common clinical governance arrangement; - Aim to work together as interlocking services that provide integrated, coordinated care to consumers across all mental health service settings; and - Share clinical records or, in the case where there is more than one physical clinical record for each patient, staff may access (if required) the information contained in all of the physical records held by the organisation for that patient. For most states and territories, the mental health service organisation is equivalent to the Area or District Mental Health Service. These are usually organised to provide the full range of admitted patient, residential and ambulatory services to a given catchment population. However, the term may also be used to refer to health care organisations which provide only one type of mental health service (for example, acute admitted patient care) or which serve a specialised or state-wide function. Hospital or service unit cluster ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ A specialised mental health service organisation may consist of one or more clusters of service units providing services in admitted patient, residential and ambulatory settings. For example, a specialised mental health service organisation may consist of several hospitals (clusters of admitted patient service units) and/or two or more ambulatory or residential service clusters (for example, a cluster of child and adolescent ambulatory service units, and a cluster of aged residential service units). To allow service units to be reported individually, but still to be identified as part of a hospital (for the admitted patient service setting), or as part of another type of cluster (for example, other cluster type for ambulatory or residential service setting), a separate reporting level has been created. - ‘Hospital’ is for admitted patient service units, and - ‘Service unit cluster’ is for ambulatory service units and residential service units. Ambulatory or residential service units will not necessarily belong to a ‘cluster’. However, for some ambulatory service units, the cluster the service unit belongs to may be a hospital that contains both admitted patient and ambulatory service units. In this instance, the *Service unit cluster identifier* for the ambulatory service unit would be the *Hospital identifier*. Other groups of ambulatory and residential service units could also be usefully reported as clusters. For example, clusters may exist of groups of residential services for aged persons, or groups of ambulatory service units in particular geographical areas. Each hospital reported to the Public Hospital Establishments NMDS, with an inpatient unit in scope as specialised mental health, must be reported as a *hospital* for the purposes of the MHE NMDS. Specialised mental health service units ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The reporting of service units specified in this section relates to the minimum reporting that is required for NMDS purposes, defined on the basis of MHE NMDS reporting requirements. States and territories are free to report more service units than this. For example, if a hospital had two older persons acute admitted patient service units, these only need to be reported as one combined older persons acute admitted patient service unit, but could be reported as two separate service units if desired. However, identification of service units should not combine target populations—there is no code available to identify ‘mixed’ target populations. Therefore, where a service delivery outlet provides discrete and specifically funded programs for multiple target populations, each of these should be identified as a separate service unit. Admitted patient setting """""""""""""""""""""""" For the admitted patient setting, data are to be reported by target population and program type. For example, if a hospital had separate wards/programs for child and adolescent, youth, older person, general adult and forensic there would be a separate service unit reported for each. Additionally, if there are acute and other program types, that would require separate service units to be reported (that is, defined by the program type as well as the target population). For example, an older persons acute unit would be reported separately from an older persons unit providing rehabilitation or extended care. Organisations can, however, report multiple service units with the same target population and program type, if the distinction between the units is known to the organisation and expected to be separately identifiable across a number of years. Ambulatory service setting """"""""""""""""""""""""""" For the ambulatory service setting, the service unit is equivalent to the organisation’s ambulatory services as a whole. However, the data element *Target population* should be used to distinguish between general adult, child and adolescent, youth, older person and forensic services. An organisation may choose to report a number of separate ambulatory service units with the same target population, however this is not compulsory. Residential service setting """"""""""""""""""""""""""" For the residential service setting, as a minimum, 24-hour staffed residential services that employ mental health trained staff on-site 24 hours per day and other services with less intensive staffing (but mental health trained staff on-site for a minimum of 6 hours a day and at least 50 hours per week) should be defined as separate service units. This applies to both government-operated residential services and government-funded residential services operated by non-government organisations. In addition, the data element *Target population* should be used to distinguish between general adult, child and adolescent, youth, older person and forensic services. Sector ^^^^^^^ Sector is not considered part of the identifier. Within this NMDS, sector is an attribute of ambulatory and residential service units. Sector is an attribute of the ‘Hospital’ table for admitted patient service units. Statistical unit identifiers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The reporting of service entities aims to create relationships between the mental health NMDSs, and where possible, the National Outcomes and Casemix Collection (NOCC), Public Hospital Establishments (PHE) NMDS and Admitted Patient Care (APC) NMDS (see :numref:`table-reporting-requirements`). The identifiers for the MHE NMDS are: - State or territory (1 character) (use *State/Territory identifier*) - Region (2 characters) (use *Region identifier*) - Mental health non-government organisation identifier (11 characters) - Specialised mental health service organisation (9 characters) - Hospital or service unit cluster (9 characters) - Service unit (9 characters) Identifiers should be assigned as follows: - *State/Territory identifier:* as per *National health data dictionary* codes; - *Region identifier:* at the discretion of each state or territory as no national code set is available; - *Organisation identifier:* at the discretion of each state or territory as no national code set is available; - *Mental health non-government organisation identifier:* where the funded organisation is a Primary Health network, the identifiers are those specified in the data element Guide for use. For other mental health non-government organisations, the identifiers are at the discretion of each state or territory as no national code set is available; - *Hospital identifier:* the same as used in the PHE NMDS where physically separate hospitals have been distinguished; where multiple hospitals have been reported as a single establishment, new identifiers will be needed to distinguish these hospitals; - *Service unit cluster identifier:* at the discretion of each state or territory as no national code set is available; - *Admitted patient service unit identifier:* at the discretion of each state or territory as no national code set is available; - *Ambulatory service unit identifier:* the same as those used in the Community Mental Health Care (CMHC) NMDS; - *Residential service unit identifier:* the same as those used in the Residential Mental Health Care (RMHC) NMDS. .. _table-reporting-requirements: .. csv-table:: Reporting requirements for mental health and related NMDSs :file: reporting-requirements.csv :header-rows: 1 The use of identical identifiers between the various Mental Health Datasets is tested via the Mental Health Establishments Skeleton files, handled by the Online Validator. An additional identifier was introduced in the MHE NMDS 2014–15 and subsequent MHE NMDSs: the Local hospital network identifier (METEOR identifier `790673 `__). This data element is reported at the service unit level and is not part of the identifier string. An additional identifier was also introduced in the MHE NMDS 2025–26 and subsequent MHE NMDSs: the Non-government organisation identifier (METEOR identifier `795673 `__). This data element is reported for the Non-Government Organisation details and payment records and is not part of the identifier string. Consistency of identifiers across reference periods ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In the specifications from 2025–26 onwards, establishment identifiers (OrgId, ClusId, HospId, AdmiId, AmbuId, ResiId) have increased the maximum character length to 9 characters. Where no major service reorganisations have occurred, the region, organisation, hospital, service unit cluster and service unit identifiers (*RegId*, *OrgId*, *HospId*, *ClusId*, *AdmiId*, *AmbuId*, *ResiId*) used by a jurisdiction should be preferably identical to the previous year. However, given that all jurisdictions have committed to aligning ID numbers between the different NMDS’s, changes in ID numbers due to this process will be accepted, as will be the case for those jurisdictions that have undergone significant reorganisation of service delivery that warrant new service entity identifiers. In these cases, jurisdictions should provide a supplementary mapping document that clearly illustrates the changes in ID numbers between collection periods, at all levels. Region, organisation, hospital, cluster and service unit name changes are acceptable, especially if the new name is more locally relevant. These will be identified as a change in the Online Validator, however will not affect the generation of the historical trends reports. Data model of the MHE Extract ------------------------------- :numref:`figure-data-model-1` provides an abbreviated overview of the structure of the data to be reported. Information is provided at each level: State/Territory; Region; Organisation; Hospital/Service unit cluster; and Service unit (Admitted patient services, Residential services and Ambulatory services). Each level has a unique set of attributes which comprise the NMDS data elements and additional supplementary information. .. _figure-data-model-1: .. figure:: data-model-1.png :alt: Data model diagram Overview of Data model underlying the Mental Health Establishments NMDS data extract Data integrity --------------- For cases of missing data (that is, unknown, not stated or not available): - For **Numeric [Num] fields**, the data should be reported as zero, using leading zeros when necessary to pad out the field to the required length. The principle here is that all numeric fields require a valid value. - For **Text [Char] fields**, the data should be space-filled to the required length. For single character fields where a ‘missing/not stated’ value has been specified for a particular data element (for example, ‘9’ has been specified for missing data), use the stated value for ‘missing/not stated’ rather than simply space filling. Values in **Date** [**Date**\ ] fields must be recorded in compliance with the standard format used across the *National health data dictionary*; specifically, dates must be of fixed 8 column width in the format DDMMYYYY, with leading zeros used when necessary to pad out a value. For instance, 13 March |end-year| would appear as 1303\ |end-year|. Values in **Numeric** [**Num**\ ] fields must be zero-filled and right-justified. These should consist only of the numerals 0 to 9 and the decimal (’.’) point if applicable to the data element. Note: Fields defined as ‘Numeric’ are those that have numeric properties—that is, the values, for example, can be added or subtracted in a manner that is valid. Where a field uses numeric characters that do not have these properties (for example, the use of numbers for *Patient identifier*), the field is defined as ‘Character’. Values in **Character** [**Char**\ ] fields must be left justified and space-filled. These should consist of any of the printable ASCII character set (that is, excluding control codes such as newline, bell and linefeed). Data set specification (DSS) ----------------------------- As noted earlier, the proposed file structure for the transmission of data from jurisdictions to the AIHW is a single Fixed Format data file. The following tables specify the order in which the data items should be provided to the AIHW. The extract format consists of a set of hierarchically ordered *Data records*, of which there are fourteen types (see :numref:`table-record-types`). In each extract file for any given period, the *Data records* must be preceded by a single *File Header Record* having the structure outlined in :numref:`table-records/hr`. All records presented in the extract file should be grouped in the following order: Header Record; State/Territory details records; State MH NGO details records; Region details records; Region MH NGO details records; Organisation details records; Hospital/Service unit cluster details records; and Service unit details records. With the exception of State MH NGO, Region, Region MH NGO, Organisation and Service unit cluster details records, all *Data records* should include the following elements in the order shown: - Record type - Establishment identifier (comprising: *State/Territory identifier; Region identifier; Organisation identifier; Hospital identifier/Service unit cluster identifier;* and *Service unit identifier*) - Specific data in the format specified for the given record type The State MH NGOE and Region MH NGOE payments records use different Establishment identifier compositions: - State MH NGOE: *State/Territory identifier*; and *Mental health non-government organisation identifier* - Region MH NGOE: *State/Territory identifier*; *Region identifier*; and *Mental health non-government organisation identifier* The order of fields in a record must be the same as the order they are listed in the Record Layouts specified below. Field values should be formatted as specified in the Record Layouts. The first field in each record must be *Record Type*. Valid values for *Record Type* are shown in :numref:`table-record-types`. .. _table-record-types: .. csv-table:: Valid values for Record Type :file: record-types.csv :header-rows: 1 File header record ^^^^^^^^^^^^^^^^^^^ The first record of the extract file must be a File Header Record (*Record Type* = ‘HR’), and it must be the only such record in the file. The File Header Record is a quality control mechanism, which uniquely identifies each file that is sent to the AIHW (that is, who sent the file, what date the file was sent, batch number of file, etc). The information contained in the header fields will be checked against the actual details of the file to ensure that the file received has not been corrupted. The layout of the File Header Record is shown in :numref:`table-records/hr`. .. _table-records/hr: .. csv-table:: Record Layout for *File Header Record* within the data extract :file: records/hr.csv :header-rows: 1 .. include:: records/hr-notes.rst State/Territory data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The extract format for the *Data records* is specified in detail in tables :numref:`table-records/hr` to :numref:`table-records/resi`. The order of fields in each record must be the same as the order they are shown below. Field values should be formatted as specified. .. csv-table:: Data record layout - *State/Territory details* :file: records/st.csv :header-rows: 1 .. include:: records/st-notes.rst State MH NGO details record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - State MH NGO details :file: records/stngo.csv :header-rows: 1 .. include:: records/stngo-notes.rst State MH NGOE Payments data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *State MH NGOE Payments* :file: records/stngoe.csv :header-rows: 1 .. include:: records/stngoe-notes.rst Region data record ^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *Region details* :file: records/reg.csv :header-rows: 1 .. include:: records/reg-notes.rst Region MH NGO details record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - Region MH NGO details :file: records/regngo.csv :header-rows: 1 .. include:: records/regngo-notes.rst Region MH NGOE Payments data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *Region MH NGOE Payments* :file: records/regngoe.csv :header-rows: 1 .. include:: records/regngoe-notes.rst Organisation data record ^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *Organisation details* :file: records/org.csv :header-rows: 1 .. include:: records/org-notes.rst Organisation: FTE Staff by Service Setting data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *Organisation Details: FTE Staff by Service Setting data record* :file: records/fteorg.csv :header-rows: 1 .. include:: records/fteorg-notes.rst Hospital data record ^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *Hospital details* :file: records/hosp.csv :header-rows: 1 .. include:: records/hosp-notes.rst Service Unit Cluster data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout - *Service Unit Cluster details* :file: records/clus.csv :header-rows: 1 .. include:: records/clus-notes.rst Admitted Patient Service Unit data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout — *Admitted Patient Service Unit details* :file: records/admi.csv :header-rows: 1 .. include:: records/admi-notes.rst Ambulatory Patient Service Unit data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Data record layout — *Ambulatory Patient Service Unit details* :file: records/ambu.csv :header-rows: 1 .. include:: records/ambu-notes.rst Residential Patient Service Unit data record ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. _table-records/resi: .. csv-table:: Data record layout — *Residential Patient Service Unit details* :file: records/resi.csv :header-rows: 1 .. include:: records/resi-notes.rst Data elements ------------- .. include:: records/data-elements.rst Virtual elements ---------------- .. include:: records/virtual-elements.rst Rules ----- .. include:: records/rules.rst