5. Data model and specifications¶
5.1. Data model¶
There are three contexts where data can be submitted using the version 4 specification:
- Intake teams
- Treatment organisations
- Combined Intake/Treatment organisations
Different records in the specification are intended to be used in each of these contexts.
Within the PMHC-MDS system a single intake team and individual service providers/treatment organisations will each have their own organisation path and report data against those organisations.
Below is the combined Intake/Treatment data model. If an Intake only or Treatment only organisation is submitting data, a sub set of this data model may be submitted. Please refer to Contexts for data models of the different contexts that may be submitted.
Fig. 5.1 PMHC MDS Version 4.0 combined data model
Note
- The above data model diagram is in the SVG format and can be enlarged or zoomed by opening in a new tab or window or by downloading it.
Fig. 5.2 PMHC MDS Version 4.0 Collection Occasion data model
Note
See PMHC MDS Version 4.0 combined data model for more details about how Collection Occasion records fit into the overall structure.
5.2. Key concepts¶
5.2.1. Primary Health Network¶
Primary Health Networks (PHNs) have been established by the Australian Government with the key objectives of increasing the efficiency and effectiveness of medical services for patients, particularly those at risk of poor health outcomes, and improving coordination of care to ensure patients receive the right care in the right place at the right time.
5.2.2. Provider Organisation¶
The Provider Organisation is the business entity that the PHN has commissioned to provide the service.
See Provider Organisation for the data elements for a provider organisation.
5.2.3. Practitioner¶
The Practitioner is the person who is delivering the service. Multiple practitioners can deliver a service.
See Practitioner for the data elements for a practitioner.
5.2.4. Client¶
The Client is the person who is receiving the service.
See Client for the data elements for a client.
5.2.4.1. Active Client¶
An active client is a client who has had one or more Service Contacts in a reference reporting period.
5.2.5. Intake¶
For the purpose of the PMHC MDS, an Intake is defined as a point of contact between a client and a PHN-commissioned organisation where the client is assessed to determine the appropriate level of care and referred to a service provider to provide clinical care. An Intake may include the collection of an IAR-DST measure.
The collection of Intake and IAR data may not be required for all programs. Please see Intake.
5.2.5.1. Concluded Intake¶
Concluded intakes are intakes where Organisation type referred to at Intake conclusion is not blank.
5.2.6. Intake Episode¶
The Intake Episode record links an Intake record and an Episode record. It must be provided by the organisation that delivers the episode, not the intake.
5.2.7. Episode¶
For the purposes of the PMHC MDS, an Episode of Care is defined as a more or less continuous period of contact between a client and a PHN-commissioned provider organisation/clinician that starts at the point of first contact, and concludes at discharge. Episodes comprise a series of one or more Service Contacts. This structure allows for a logical data collection protocol that specifies what data are collected when, and by whom. Different sets of PMHC MDS items are collected at various points in the client’s engagement with the provider organisation. Some items are only collected once at the episode level, while others are collected at each Service Contact.
Four business rules apply to how the Episode of Care concept is implemented across PHN-commissioned services:
One Intake may be associated with each episode. An episode is not required to be associated with an Intake.
One episode at a time for each client, defined at the level of the provider organisation.
While an individual may have multiple Episodes of Care over the course of their illness, they may be considered as being in only one episode at any given point of time for any particular PHN-commissioned provider organisation. The implication is that the care provided by the organisation to an individual client at any point in time is subject to only one set of reporting requirements.
Episodes commence at the point of first contact. The episode start date will be derived from the first service contact regardless of no show state as long as there is a service contact that isn’t a no show. Therefore, if there is no attended service contact the episode is uncommenced.
Some examples:
- If a service contact occurs on the 1/1/2018 that is recorded as a no show then the episode is uncommenced.
- If a service contact occurs on the 1/1/2018 that is recorded as a no show and another service contact occurs on the 2/1/2018 that is attended then the episode start date is derived as 1/1/2018.
Discharge from care concludes the episode
Discharge may occur clinically or administratively in instances where contact has been lost with the client. A new episode is deemed to commence if the person re-presents to the organisation.
See Episode for the data elements for a episode.
5.2.7.1. Open Episode¶
Open episodes are those with Episode Completion Status recorded as open (Response item 0).
5.2.7.2. Closed Episode¶
Closed episodes are those with Episode Completion Status recorded using one of the ‘Episode closed’ responses (Response items 1-6).
5.2.7.3. Active Episode¶
An active episode is an episode with one or more Attended Service Contacts recorded in a reference reporting period.
5.2.8. Service Contact¶
Service contacts are defined as the provision of a service by one or more PHN commissioned mental health service provider(s) for a client where the nature of the service would normally warrant a dated entry in the clinical record of the client.
A service contact must involve at least two persons, one of whom must be a mental health service provider.
Service contacts can be either with the client or with a third party, such as a carer or family member, and/or other professional or mental health worker, or other service provider.
Service contacts are not restricted to face‑to‑face communication but can include telephone, internet, video link or other forms of direct communication.
Service provision is only regarded as a service contact if it is relevant to the clinical condition of the client. This means that it does not include services of an administrative nature (e.g. telephone contact to schedule an appointment).
Definition based on METeOR: 493304 with modification.
5.2.8.1. Attended Service Contact¶
An attended service contact is one that is not marked as ‘No show’.
See Service Contact for the data elements for a service contact.
5.2.9. Service Contact Practitioner¶
Service Contacts can have more than one practitioner. Practitioners are linked to Service Contacts through Service Contact Practitioner.
One (and only one) practitioner must be specified as the Primary Practitioner for each Service Contact.
See Service Contact Practitioner for the data elements for a service contact practitioner.
5.2.10. Collection Occasion¶
A Collection Occasion is defined as an occasion during an Episode of Care when specific Service Activities are required to be collected. At a minimum, collection is required at both Episode Start and Episode End, but may be more frequent if clinically indicated and agreed by the client.
Measures will be the Kessler Psychological Distress Scale K10+ (in the case of Aboriginal and Torres Strait Islander clients, the K5) as well as the Strengths & Difficulties Questionnaires.
See Collection Occasion for the data elements for a collection occasion.
5.3. Record formats¶
5.3.1. Metadata¶
The Metadata table must be included in file uploads in order to identify the type and version of the uploaded data.
Data Element (Field Name) | Type (min,max) | Required | Format / Values |
---|---|---|---|
Key (key) | string | yes | A metadata key name. |
Value (value) | string | yes | The metadata value. |
For this version of the specification the required content is shown in the following table:
key | value |
type | PMHC |
version | 4.0 |
5.3.2. Provider Organisation¶
See Provider Organisation for the definition of a provider organisation.
Provider Organisation data is for administrative use within the PMHC MDS system. It is managed by the PHN’s via the PMHC MDS administrative interface, it cannot be uploaded.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||||||||||||||
Organisation Key (organisation_key) | string (2,50) | yes | A sequence of characters which uniquely identifies the provider organisation to the Primary Health Network. Assigned by the Primary Health Network. | ||||||||||||||||||||||||||||||
Name (organisation_name) | string (2,100) | yes | The name of the provider organisation. | ||||||||||||||||||||||||||||||
Legal Name (organisation_legal_name) | string | — | The legal name of the provider organisation. | ||||||||||||||||||||||||||||||
ABN (organisation_abn) | string (11) | yes | The Australian Business Number of the provider organisation. | ||||||||||||||||||||||||||||||
Organisation Type (organisation_type) | string | yes |
|
||||||||||||||||||||||||||||||
State (organisation_state) METeOR: 613718 |
string | yes |
|
||||||||||||||||||||||||||||||
Organisation Start Date (organisation_start_date) | date | yes | The date on which a provider organisation started delivering services. | ||||||||||||||||||||||||||||||
Organisation End Date (organisation_end_date) | date | yes | The date on which a provider organisation stopped delivering services. | ||||||||||||||||||||||||||||||
Organisation Tags (organisation_tags) | string | — | List of tags for the provider organisation. |
5.3.3. Practitioner¶
See Practitioner for the definition of a practitioner.
Practitioner data is intended to provide workforce planning data for use regionally by the PHN and nationally by the Department. It is managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||||||||||||
Practitioner Key (practitioner_key) | string (2,50) | yes | A unique identifier for a practitioner within the responsible provider organisation. Assigned by either the PHN or Provider Organisation depending on local procedures. | ||||||||||||||||||||||||||||
Practitioner Category (practitioner_category) | string | yes |
|
||||||||||||||||||||||||||||
ATSI Cultural Training (atsi_cultural_training) | string | yes |
|
||||||||||||||||||||||||||||
Year of Birth (practitioner_year_of_birth) | gYear | yes | gYear | ||||||||||||||||||||||||||||
Practitioner Gender (practitioner_gender) |
string | yes |
|
||||||||||||||||||||||||||||
Practitioner Aboriginal and Torres Strait Islander Status (practitioner_atsi_status) METeOR: 291036 |
string | yes |
|
||||||||||||||||||||||||||||
Active (practitioner_active) | string | yes |
|
||||||||||||||||||||||||||||
Practitioner Tags (practitioner_tags) | string | — | List of tags for the practitioner. |
5.3.4. Client¶
See Client for definition of a client.
Clients are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Key (client_key) | string (2,50) | yes | This is a number or code assigned to each individual client referred to the commissioned organisation. The client identifier must be unique and stable for each individual within the Provider Organisation. Assigned by either the PHN or Provider Organisation depending on local procedures. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Statistical Linkage Key (slk) METeOR: 349510 |
string (14,40) | yes | A key that enables two or more records belonging to the same individual to be brought together. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Date of Birth (date_of_birth) METeOR: 287007 |
date | yes | The date on which an individual was born. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Estimated Date of Birth Flag (est_date_of_birth) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Gender (client_gender) |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Aboriginal and Torres Strait Islander Status (client_atsi_status) METeOR: 291036 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Country of Birth (country_of_birth) METeOR: 459973 |
string (4) | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Main Language Spoken at Home (main_lang_at_home) METeOR: 460125 |
string (4) | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Proficiency in Spoken English (prof_english) METeOR: 270203 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Tags (client_tags) | string | — | List of tags for the client. |
5.3.5. Intake¶
See Intake for definition of an intake.
The collection of Intake and IAR data is a requirement for Head to Health programs. This includes the Head to Health Phone Service, centres, satellites and Pop-Up clinics. PHNs may choose to collect Intake and IAR data for other non-Head to Health programs using the PMHC-MDS v4 specification, however reporting of this data remains optional subject to further guidance from the department.
Intakes are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Intake Key (intake_key) | string (2,50) | yes | This is a number or code assigned to each intake. The Intake Key is unique and stable for each intake at the level of the organisation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Key (client_key) | string (2,50) | yes | This is a number or code assigned to each individual client referred to the intake organisation. The client identifier must be unique and stable for each individual within the intake organisation. Assigned by either the PHN or intake organisation depending on local procedures. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Consent to Anonymised Data (client_consent) | string | yes | An indication that the client has consented to their anonymised data being provided to the Department of Health for statistical purposes in planning and improving mental health services. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referral Date (referral_date) | date | yes | The date the referrer made the referral. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Program Type (program_type) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referrer Profession (referrer_profession) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referrer Organisation Type (referrer_organisation_type) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Date client contacted Intake (date_client_contacted_intake) | date | yes | The date on which the client first contacted the intake service | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Suicide Referral Flag (suicide_referral_flag) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Date referred to other service at Intake conclusion (date_referred_to_other_service_at_intake_conclusion) | date | — | The date the client was referred to another organisation at Intake conclusion. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Organisation type referred to at Intake conclusion (organisation_type_referred_to_at_intake_conclusion) | string | — |
Multiple space separated values allowed |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referred to Organisation Path (referred_to_organisation_path) | string | — | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation to which the intake referred the client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Intake Tags (intake_tags) | string | — | List of tags for the intake. |
5.3.6. Intake Episode¶
See Intake Episode for definition of an intake episode.
Intake Episodes are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values |
---|---|---|---|
Episode Organisation Path (episode_organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing the clinical service to the client. |
Episode Key (episode_key) | string (2,50) | yes | This is a number or code assigned to each PMHC MDS episode. The Episode Key is unique and stable for each episode at the level of the organisation. This key must link to an existing episode within the PMHC MDS. |
Intake Organisation Path (intake_organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing the intake to the client. |
Intake Key (intake_key) | string (2,50) | yes | This is a number or code assigned to each intake. The Intake Key is unique and stable for each intake at the level of the organisation. |
5.3.7. Episode¶
See Episode for definition of an episode.
Episodes are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Episode Key (episode_key) | string (2,50) | yes | This is a number or code assigned to each episode. The Episode Key is unique and stable for each episode at the level of the Provider Organisation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Key (client_key) | string (2,50) | yes | This is a number or code assigned to each individual client referred to the commissioned organisation. The client identifier is unique and stable for each individual within the Provider Organisation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Episode End Date (episode_end_date) METeOR: 614094 |
date | — | The date on which an Episode of Care is formally or administratively ended | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Client Consent to Anonymised Data (client_consent) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Episode Completion Status (episode_completion_status) | string | — |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referral Date (referral_date) | date | yes | The date the referrer made the referral. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Program Type (program_type) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Principal Focus of Treatment Plan (principal_focus) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GP Mental Health Treatment Plan Flag (mental_health_treatment_plan) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Homelessness Flag (homelessness) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Area of usual residence, postcode (client_postcode) METeOR: 429894 |
string | yes | The Australian postcode of the client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Labour Force Status (labour_force_status) METeOR: 621450 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Employment Participation (employment_participation) METeOR: 269950 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Source of Cash Income (income_source) METeOR: 386449 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Health Care Card (health_care_card) METeOR: 605149 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NDIS Participant (ndis_participant) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Marital Status (marital_status) METeOR: 291045 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Suicide Referral Flag (suicide_referral_flag) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Principal Diagnosis (principal_diagnosis) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Additional Diagnosis (additional_diagnosis) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Medication - Antipsychotics (N05A) (medication_antipsychotics) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Medication - Anxiolytics (N05B) (medication_anxiolytics) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Medication - Hypnotics and sedatives (N05C) (medication_hypnotics) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Medication - Antidepressants (N06A) (medication_antidepressants) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Medication - Psychostimulants and nootropics (N06B) (medication_psychostimulants) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referrer Profession (referrer_profession) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Referrer Organisation Type (referrer_organisation_type) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Organisation type referred to at Episode conclusion (organisation_type_referred_to_at_episode_conclusion) | string | — |
Multiple space separated values allowed |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Episode Tags (episode_tags) | string | — | List of tags for the episode. |
5.3.8. Service Contact¶
See Service Contact for definition of a service contact.
Service contacts are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||||||||||||||||||||||||
Service Contact Key (service_contact_key) | string (2,50) | yes | This is a number or code assigned to each service contact. The Service Contact Key is unique and stable for each service contact at the level of the Provider Organisation. | ||||||||||||||||||||||||||||||||||||||||
Episode Key (episode_key) | string (2,50) | yes | This is a number or code assigned to each episode. The Episode Key is unique and stable for each episode at the level of the organisation. | ||||||||||||||||||||||||||||||||||||||||
Service Contact Date (service_contact_date) METeOR: 494356 |
date | yes | The date of each mental health service contact between a health service provider and patient/client. | ||||||||||||||||||||||||||||||||||||||||
Service Contact Type (service_contact_type) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Postcode (service_contact_postcode) METeOR: 429894 |
string | yes | The Australian postcode where the service contact took place. | ||||||||||||||||||||||||||||||||||||||||
Modality (service_contact_modality) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Participants (service_contact_participants) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Venue (service_contact_venue) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Duration (service_contact_duration) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Copayment (service_contact_copayment) | number | yes | 0 - 999999.99 | ||||||||||||||||||||||||||||||||||||||||
Client Participation Indicator (service_contact_participation_indicator) METeOR: 494341 |
string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Interpreter Used (service_contact_interpreter) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
No Show (service_contact_no_show) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Final Service Contact (service_contact_final) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Start Time (service_contact_start_time) | time | yes | The start time of each mental health service contact between a health service provider and patient/client. | ||||||||||||||||||||||||||||||||||||||||
Funding Source (funding_source) | string | yes |
|
||||||||||||||||||||||||||||||||||||||||
Service Contact Tags (service_contact_tags) | string | — | List of tags for the service contact. |
5.3.9. Service Contact Practitioner¶
See Service Contact Practitioner for definition of a service contact practitioner.
Service contacts practitioners are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||
---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||
Service Contact Practitioner Key (service_contact_practitioner_key) | string (2,50) | yes | This is a number or code assigned to each service contact practitioner. The Service Contact Practitioner Key is unique and stable for each service contact practitioner at the level of the Provider Organisation. | ||||
Service Contact Key (service_contact_key) | string (2,50) | yes | This is a number or code assigned to each service contact. The Service Contact Key is unique and stable for each service contact at the level of the Provider Organisation. | ||||
Practitioner Key (practitioner_key) | string (2,50) | yes | A unique identifier for a practitioner within the provider organisation. | ||||
Primary Practitioner Indicator (primary_practitioner_indicator) | string | yes |
|
5.3.10. Collection Occasion¶
See Collection Occasion for definition of a collection occasion.
Individual item scores will eventually be required, however, it is noted that in the short term there are issues with collecting individual item scores. Therefore, as a transitional phase, reporting overall scores/subscales will be allowed.
Collection occasions are managed by the provider organisations via either the PMHC MDS administrative interface or upload.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||
---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||
Collection Occasion Key (collection_occasion_key) | string (2,50) | yes | This is a number or code assigned to each collection occasion of service activities. The Collection Occasion Key is unique and stable for each collection occasion at the level of the organisation. | ||||||
Episode Key (episode_key) | string (2,50) | yes | This is a number or code assigned to each PMHC MDS episode. The Episode Key is unique and stable for each episode at the level of the organisation. This key must link to an existing episode within the PMHC MDS. | ||||||
Collection Occasion Date (collection_occasion_date) | date | yes | The date of the collection occasion. | ||||||
Collection Occasion Reason (reason_for_collection) | string | yes |
|
||||||
Collection Occasion Tags (collection_occasion_tags) | string | — | List of tags for the collection occasion. |
5.3.11. Measures¶
5.3.11.1. Measures at Intake¶
5.3.11.1.1. IAR-DST¶
The collection of Intake and IAR DST data may not be required for all programs. Please see Intake.
Where an Intake is recorded, an associated IAR-DST should also be recorded. However, this is not enforced by the PMHC MDS as Intake data could be collected separately from IAR DST data.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||||
Measure Key (measure_key) | string (2,50) | yes | This is a number or code assigned to each instance of a measure. The Measure Key is unique and stable for each instance of a measure at the level of the organisation. | ||||||||||||||||||
Intake Key (intake_key) | string (2,50) | yes | This is a number or code assigned to each intake. The Intake Key is unique and stable for each intake at the level of the organisation. | ||||||||||||||||||
IAR-DST - Version (iar_dst_version) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 1 - Symptom Severity and Distress (Primary Domain) (iar_dst_domain_1) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 2 - Risk of Harm (Primary Domain) (iar_dst_domain_2) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 3 - Functioning (Primary Domain) (iar_dst_domain_3) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 4 - Impact of Co-existing Conditions (Primary Domain) (iar_dst_domain_4) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 5 - Treatment and Recovery History (Contextual Domain) (iar_dst_domain_5) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 6 - Social and Environmental Stressors (Contextual Domain) (iar_dst_domain_6) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 7 - Family and Other Supports (Contextual Domain) (iar_dst_domain_7) | string | yes |
|
||||||||||||||||||
IAR-DST - Domain 8 - Engagement and Motivation (Contextual Domain) (iar_dst_domain_8) | string | yes |
|
||||||||||||||||||
IAR-DST - Recommended Level of Care (iar_dst_recommended_level_of_care) | string | yes |
|
||||||||||||||||||
IAR-DST - Practitioner Level of Care (iar_dst_practitioner_level_of_care) | string | yes |
|
||||||||||||||||||
IAR-DST - Tags (iar_dst_tags) | string | — | List of tags for the measure. |
5.3.11.2. Measures during an Episode¶
PMHC MDS requires the use of one of the following three required measures, as follows:
- For adults (18+ years) - Kessler Psychological Distress Scale (K10+) is the prescribed measure, with the option to use the K5 for Aboriginal and Torres Strait Islander people if that is considered more appropriate.
- For children and young people (up to and including 17 years) - the Strengths & Difficulties Questionnaires (SDQ) is the prescribed tool. The specified versions include the parent-report for 4-10 years and 11-17 years; and the self-report for 11-17 years.
Please note: For adolescents, clinician-discretion is allowed, and that the K10+ or K5 may be used, even though the person is under 18 years
5.3.11.2.1. K10+¶
As noted above, reporting individual item scores will eventually be required. In the short term, respondents can either report all 14 item scores or report the K10 total score as well as item scores for the 4 extra items in the K10+.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||
Measure Key (measure_key) | string (2,50) | yes | This is a number or code assigned to each instance of a measure. The Measure Key is unique and stable for each instance of a measure at the level of the organisation. | ||||||||||||
Collection Occasion Key (collection_occasion_key) | string (2,50) | yes | This is a number or code assigned to each collection occasion of service activity. The Collection Occasion Key is unique and stable for each collection occasion at the level of the organisation. | ||||||||||||
K10+ - Question 1 (k10p_item1) | string | yes |
|
||||||||||||
K10+ - Question 2 (k10p_item2) | string | yes |
|
||||||||||||
K10+ - Question 3 (k10p_item3) | string | yes |
|
||||||||||||
K10+ - Question 4 (k10p_item4) | string | yes |
|
||||||||||||
K10+ - Question 5 (k10p_item5) | string | yes |
|
||||||||||||
K10+ - Question 6 (k10p_item6) | string | yes |
|
||||||||||||
K10+ - Question 7 (k10p_item7) | string | yes |
|
||||||||||||
K10+ - Question 8 (k10p_item8) | string | yes |
|
||||||||||||
K10+ - Question 9 (k10p_item9) | string | yes |
|
||||||||||||
K10+ - Question 10 (k10p_item10) | string | yes |
|
||||||||||||
K10+ - Question 11 (k10p_item11) | integer | yes | 0 - 28, 99 = Not stated / Missing | ||||||||||||
K10+ - Question 12 (k10p_item12) | integer | yes | 0 - 28, 99 = Not stated / Missing | ||||||||||||
K10+ - Question 13 (k10p_item13) | integer | yes | 0 - 89, 99 = Not stated / Missing | ||||||||||||
K10+ - Question 14 (k10p_item14) | string | yes |
|
||||||||||||
K10+ - Score (k10p_score) | integer | yes | 10 - 50, 99 = Not stated / Missing | ||||||||||||
K10+ - Tags (k10p_tags) | string | — | List of tags for the measure. |
When the client’s responses to Q1-10 are all recorded as 1 ‘None of the time’, they are not required to answer questions 11-14. Where a question has not been answered please select a response of ‘Not stated / missing’.
5.3.11.2.2. K5¶
As noted above, reporting individual item scores will eventually be required. In the short term, respondents can either report all 5 item scores or report the K5 total score.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||
Measure Key (measure_key) | string (2,50) | yes | This is a number or code assigned to each instance of a measure. The Measure Key is unique and stable for each instance of a measure at the level of the organisation. | ||||||||||||
Collection Occasion Key (collection_occasion_key) | string (2,50) | yes | This is a number or code assigned to each collection occasion of service activity. The Collection Occasion Key is unique and stable for each collection occasion at the level of the organisation. | ||||||||||||
K5 - Question 1 (k5_item1) | string | yes |
|
||||||||||||
K5 - Question 2 (k5_item2) | string | yes |
|
||||||||||||
K5 - Question 3 (k5_item3) | string | yes |
|
||||||||||||
K5 - Question 4 (k5_item4) | string | yes |
|
||||||||||||
K5 - Question 5 (k5_item5) | string | yes |
|
||||||||||||
K5 - Score (k5_score) | integer | yes | 5 - 25, 99 = Not stated / Missing | ||||||||||||
K5 - Tags (k5_tags) | string | — | List of tags for the measure. |
5.3.11.2.3. SDQ¶
Extensive support materials are available on the SDQ developers’ website, including copies of the various versions of the instrument, background information and scoring instructions. See http://www.sdqinfo.com. There are six versions (parent-report and youth-self report) currently specified format PMHC MDS reporting.
The “1” versions are administered on admission and are rated on the basis of the proceeding 6 months. The “2” follow up versions are administered on review and discharge and are rated on the basis of the previous 1 month period.
The versions specified for PMHC MDS reporting are:
- PC1 - SDQ Parent Report: 4-10 years (Baseline version);
- PC2 - SDQ Parent Report: 4-10 years (Follow up version);
- PY1 - SDQ Parent Report: 11-17 years (Baseline version);
- PY2 - SDQ Parent Report: 11-17 years (Follow up version);
- YR1 - SDQ Youth Report: 11-17 years (Baseline version); and
- YR2 - SDQ Youth Report: 11-17 years (Follow up version).
We acknowledge that there is also a parent-report for 2-4 years; and teacher versions for all the years (2-4; 4-10 and 11-17) but that these are not to be reported the PMHC-MDS.
Please note that the item numbering in the SDQ versions is deliberately non sequential because it covers all items in all versions, both to indicate item equivalence across versions and to assist data entry, especially of translated versions. The table below indicates the items that are included in each version, the rating periods used and the broad content covered by each item.
Informant | Parent | Young Person | |||||
---|---|---|---|---|---|---|---|
Age range | 4-10 | 11-17 | 11 - 17 | ||||
Application | Baseline | Followup | Baseline | Followup | Baseline | Followup | |
Rating period | 6 months | 1 month | 6 months | 1 month | 6 months | 1 month | |
Items | Item Content | Version | |||||
PC1 | PC2 | PY1 | PY2 | YR1 | YR2 | ||
1-25 | Symptoms | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
26 | Overall | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
27 | Duration | ✓ | X | ✓ | X | ✓ | |
28-33 | Impact | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
34-35 | Follow up progress | X | ✓ | X | ✓ | X | ✓ |
36-38 | Cross-Informant information | ✓ | X | ✓ | X | X | X |
39-42 | Cross-Informant information | X | X | X | X | ✓ | X |
As noted above, reporting individual item scores will eventually be required. In the short term, respondents can either report all 42 item scores or report the SDQ subscale scores.
5.3.11.2.3.1. SDQ items and Scale Summary scores¶
The first 25 items in the SDQ comprise 5 scales of 5 items each. It is usually easiest to score all 5 scales before working out the Total Difficulties score. For data entry, the responses to items should always be entered the same way (see below), but they are not all scored the same way. Somewhat True is always scored as 1, but the scoring of Not True and Certainly True varies with each item (see Table 5). For each of the 5 scales the score can range from 0-10 if all 5 items were completed. Scale scores can be prorated if at least 3 items were completed.
Not True | Some-what True | Certainly True | Summary Score | ||
---|---|---|---|---|---|
Standard Values for Data Entry | 0 | 1 | 2 | ||
Data element | SDQ Item number and description | Item Score | |||
Emotional Symptoms Scale | 0-10 | ||||
Item 03 | Often complains of headaches … | 0 | 1 | 2 | |
Item 08 | Many worries or often seems worried | 0 | 1 | 2 | |
Item 13 | Often unhappy, depressed or tearful | 0 | 1 | 2 | |
Item 16 | Nervous or clingy in new situations … | 0 | 1 | 2 | |
Item 24 | Many fears, easily scared | 0 | 1 | 2 | |
Conduct Problem Scale | 0-10 | ||||
Item 05 | Often loses temper … | 0 | 1 | 2 | |
Item 07 | Generally well behaved … | 2 | 1 | 0 | |
Item 12 | Often fights with other children … | 0 | 1 | 2 | |
Item 18 | Often lies or cheats | 0 | 1 | 2 | |
Item 22 | Steals from home, school … | 0 | 1 | 2 | |
Hyperactivity Scale | 0-10 | ||||
Item 02 | Restless, overactive … | 0 | 1 | 2 | |
Item 10 | Constantly fidgeting … | 0 | 1 | 2 | |
Item 15 | Easily distracted … | 0 | 1 | 2 | |
Item 21 | Thinks things out before acting | 2 | 1 | 0 | |
Item 25 | Good attention span … | 2 | 1 | 0 | |
Peer Problem Scale | 0-10 | ||||
Item 06 | Rather solitary, prefers to play alone | 0 | 1 | 2 | |
Item 11 | Has at least one good friend | 2 | 1 | 0 | |
Item 14 | Generally liked by other children | 2 | 1 | 0 | |
Item 19 | Picked on or bullied … | 0 | 1 | 2 | |
Item 23 | Gets along better with adults … | 0 | 1 | 2 | |
Prosocial Scale | 0-10 | ||||
Item 01 | Considerate of other people’s feelings | 0 | 1 | 2 | |
Item 04 | Shares readily with other children … | 0 | 1 | 2 | |
Item 09 | Helpful if someone is hurt … | 0 | 1 | 2 | |
Item 17 | Kind to younger children | 0 | 1 | 2 | |
Item 20 | Often volunteers to help others … | 0 | 1 | 2 | |
SDQ Total Difficulties Score = Sum of Scales below | 0-40 | ||||
Emotional Symptoms Scale | 0-10 | ||||
Conduct Problem Scale | 0-10 | ||||
Hyperactivity Scale | 0-10 | ||||
Peer Problem Scale | 0-10 |
- NB. Bold items indicate reverse scoring
5.3.11.2.3.2. Scoring the SDQ¶
The standard values for coding individual Item responses are 0 (Not True), 1 (Somewhat True), 2 (Certainly True) and 9 (Missing data).
For completed items (response coded 0,1,2) the Item scores are usually the same as the standard values. Them exceptions are item 07, 11, 14, 21 and 25. These items are “reverse-scored”, that is, the standard value is mapped to Item scores as follows: 0->2, 1->1, 2->0.
Summary scores are only calculated if at least three of the five items have been completed (that is, coded 0, 1 or 2). Otherwise the summary score is set to missing. For the Summary scores, the missing value used should be 99.
The Summary scores are computed using the equation shown below, with the result being rounded to the nearest whole number. In the first 25 SDQ questions, each summary scale is composed of five items.
Summary score = (sum of item scores/number of valid completed items) x number of items
The simplest way to calculate the total difficulties score is to add up the following summary scores with the result being rounded to the nearest whole number.
Total score = Emotional Scale + Conduct Scale + Hyperactivity Scale + Peer Problem Scale
However, some of the summary scores may be missing. The rule is if more than one summary score is missing the Total Score is set to missing, value 99.
Items 28-32 are not completed if respondents have answered “No” to Item 26, which asks for an overall opinion about difficulties being present. In this case, all Item responses for Items 27 through 33 should be coded “8” for “not applicable”, and the impact score should be coded to zero. Item 27 is not included in the Impact Score since it assesses the chronicity of the difficulties- the length of time they have been present. Item 33 is not included in the Impact Score, since it assess the burden on others rather than on the child/youth.
The coded Item Responses for the remaining Items 28 through 32 have to be mapped to their Item Scores before adding up. This mapping is the same for all, namely: 0->0, 1->0, 2->1, 3->2.
Data Element (Field Name) | Type (min,max) | Required | Format / Values | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Organisation Path (organisation_path) | string | yes | A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client. | ||||||||||||||||
Measure Key (measure_key) | string (2,50) | yes | This is a number or code assigned to each instance of a measure. The Measure Key is unique and stable for each instance of a measure at the level of the organisation. | ||||||||||||||||
Collection Occasion Key (collection_occasion_key) | string (2,50) | yes | This is a number or code assigned to each collection occasion of service activity. The Collection Occasion Key is unique and stable for each collection occasion at the level of the organisation. | ||||||||||||||||
SDQ Collection Occasion - Version (sdq_version) | string | yes |
|
||||||||||||||||
SDQ - Question 1 (sdq_item1) | string | yes |
|
||||||||||||||||
SDQ - Question 2 (sdq_item2) | string | yes |
|
||||||||||||||||
SDQ - Question 3 (sdq_item3) | string | yes |
|
||||||||||||||||
SDQ - Question 4 (sdq_item4) | string | yes |
|
||||||||||||||||
SDQ - Question 5 (sdq_item5) | string | yes |
|
||||||||||||||||
SDQ - Question 6 (sdq_item6) | string | yes |
|
||||||||||||||||
SDQ - Question 7 (sdq_item7) | string | yes |
|
||||||||||||||||
SDQ - Question 8 (sdq_item8) | string | yes |
|
||||||||||||||||
SDQ - Question 9 (sdq_item9) | string | yes |
|
||||||||||||||||
SDQ - Question 10 (sdq_item10) | string | yes |
|
||||||||||||||||
SDQ - Question 11 (sdq_item11) | string | yes |
|
||||||||||||||||
SDQ - Question 12 (sdq_item12) | string | yes |
|
||||||||||||||||
SDQ - Question 13 (sdq_item13) | string | yes |
|
||||||||||||||||
SDQ - Question 14 (sdq_item14) | string | yes |
|
||||||||||||||||
SDQ - Question 15 (sdq_item15) | string | yes |
|
||||||||||||||||
SDQ - Question 16 (sdq_item16) | string | yes |
|
||||||||||||||||
SDQ - Question 17 (sdq_item17) | string | yes |
|
||||||||||||||||
SDQ - Question 18 (sdq_item18) | string | yes |
|
||||||||||||||||
SDQ - Question 19 (sdq_item19) | string | yes |
|
||||||||||||||||
SDQ - Question 20 (sdq_item20) | string | yes |
|
||||||||||||||||
SDQ - Question 21 (sdq_item21) | string | yes |
|
||||||||||||||||
SDQ - Question 22 (sdq_item22) | string | yes |
|
||||||||||||||||
SDQ - Question 23 (sdq_item23) | string | yes |
|
||||||||||||||||
SDQ - Question 24 (sdq_item24) | string | yes |
|
||||||||||||||||
SDQ - Question 25 (sdq_item25) | string | yes |
|
||||||||||||||||
SDQ - Question 26 (sdq_item26) | string | yes |
|
||||||||||||||||
SDQ - Question 27 (sdq_item27) | string | yes |
|
||||||||||||||||
SDQ - Question 28 (sdq_item28) | string | yes |
|
||||||||||||||||
SDQ - Question 29 (sdq_item29) | string | yes |
|
||||||||||||||||
SDQ - Question 30 (sdq_item30) | string | yes |
|
||||||||||||||||
SDQ - Question 31 (sdq_item31) | string | yes |
|
||||||||||||||||
SDQ - Question 32 (sdq_item32) | string | yes |
|
||||||||||||||||
SDQ - Question 33 (sdq_item33) | string | yes |
|
||||||||||||||||
SDQ - Question 34 (sdq_item34) | string | yes |
|
||||||||||||||||
SDQ - Question 35 (sdq_item35) | string | yes |
|
||||||||||||||||
SDQ - Question 36 (sdq_item36) | string | yes |
|
||||||||||||||||
SDQ - Question 37 (sdq_item37) | string | yes |
|
||||||||||||||||
SDQ - Question 38 (sdq_item38) | string | yes |
|
||||||||||||||||
SDQ - Question 39 (sdq_item39) | string | yes |
|
||||||||||||||||
SDQ - Question 40 (sdq_item40) | string | yes |
|
||||||||||||||||
SDQ - Question 41 (sdq_item41) | string | yes |
|
||||||||||||||||
SDQ - Question 42 (sdq_item42) | string | yes |
|
||||||||||||||||
SDQ - Emotional Symptoms Scale (sdq_emotional_symptoms) | integer | yes | 0 - 10, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Conduct Problem Scale (sdq_conduct_problem) | integer | yes | 0 - 10, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Hyperactivity Scale (sdq_hyperactivity) | integer | yes | 0 - 10, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Peer Problem Scale (sdq_peer_problem) | integer | yes | 0 - 10, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Prosocial Scale (sdq_prosocial) | integer | yes | 0 - 10, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Total Difficulties Score (sdq_total) | integer | yes | 0 - 40, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Impact Score (sdq_impact) | integer | yes | 0 - 10, 99 = Not stated / Missing | ||||||||||||||||
SDQ - Tags (sdq_tags) | string | — | List of tags for the measure. |
5.4. Definitions¶
5.4.1. ABN¶
The Australian Business Number of the provider organisation.
Field name: | organisation_abn |
---|---|
Data type: | string (11) |
Required: | yes |
Notes: | The Australian Business Registry maintains ABN search and technical docs. The PMHC MDS does not check the if ABN is registered, only that it satisfies the algorithm documented at https://abr.business.gov.au/Help/AbnFormat |
5.4.2. Aboriginal and Torres Strait Islander Status¶
Whether a person identifies as being of Aboriginal and/or Torres Strait Islander origin, as represented by a code.
Field name: | client_atsi_status |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: |
|
||||||||||
METeOR: |
5.4.3. Active¶
A flag to represent whether a practitioner is actively delivering services. This is a system field that is aimed at helping organisations manage practitioner codes.
Field name: | practitioner_active |
||||
---|---|---|---|---|---|
Data type: | string |
||||
Required: | yes |
||||
Domain: |
|
5.4.4. Additional Diagnosis¶
The main additional condition or complaint co-existing with the Principal Diagnosis or arising during the episode of care.
Field name: | additional_diagnosis |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Additional Diagnosis gives information on conditions that are significant in terms of treatment required and resources used during the episode of care. Additional diagnoses should be interpreted as conditions that affect client management in terms of requiring any of the following:
Where the client one or more comorbid mental health conditions in addition to the condition coded as the Principal Diagnosis, record the main condition as the Additional Diagnosis. The following responses have been added to allow mapping of ATAPS data to PMHC format.
Note: These four codes should only be used for Episodes that are migrated from ATAPS MDS sources that cannot be described by any other Diagnosis. It is expected that the majority of Episodes delivered to clients from 1st July, 2017 can be assigned to other diagnoses. These responses will only be allowed on episodes where the original ATAPS referral date was before 1 July 2017 These responses will only be allowed on episodes with the !ATAPS flag. For further notes on the recording of diagnosis codes see Principal Diagnosis. |
5.4.5. Area of usual residence, postcode¶
The Australian postcode of the client.
Field name: | client_postcode |
---|---|
Data type: | string |
Required: | yes |
Notes: | A valid Australian postcode or 9999 if the postcode is unknown or the client has not provided sufficient information to confirm their current residential address. The full list of Australian Postcodes can be found at Australia Post. When collecting the postcode of a person’s usual place of residence, the ABS recommends that ‘usual’ be defined as: ‘the place where the person has or intends to live for 6 months or more, or the place that the person regards as their main residence, or where the person has no other residence, the place they currently reside.’ Postcodes are deemed valid if they are in the range 0200-0299, 0800-9999. |
METeOR: |
5.4.6. ATSI Cultural Training¶
Indicates whether a practitioner has completed a recognised training programme in the delivery of culturally safe services to Aboriginal and Torres Strait Islander peoples.
Field name: | atsi_cultural_training |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: | This item is reported by the practitioner and applies to service providers who are either:
|
5.4.7. Client Consent to Anonymised Data¶
An indication that the client has consented to their anonymised data being provided to the Department of Health for statistical purposes in planning and improving mental health services.
Field name: | client_consent |
---|---|
Data type: | string |
Required: | yes |
Notes: |
All data can be uploaded, regardless of consent flag. All data will be available to PHNs to extract for their own internal data evaluation purposes. |
5.4.8. Client Gender¶
The term ‘gender’ refers to the way in which a person identifies their masculine or feminine characteristics. A persons gender relates to their deeply held internal and individual sense of gender and is not always exclusively male or female. It may or may not correspond to their sex assigned at birth.
Field name: | client_gender |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: |
|
||||||||
ABS: |
5.4.9. Client Key¶
This is a number or code assigned to each individual client referred to the commissioned organisation. The client identifier must be unique and stable for each individual within the Provider Organisation. Assigned by either the PHN or Provider Organisation depending on local procedures.
Field name: | client_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | Client keys must be unique within each Provider Organisation. The Client Key will be managed by the Provider Organisation, however, the PHN may decide to play a role in coordinating assignment and management of these client keys. Clients should not be assigned multiple keys within the same Provider Organisation. Client keys are case sensitive and must be valid unicode characters. |
5.4.10. Client Participation Indicator¶
An indicator of whether the client participated, or intended to participate, in the service contact, as represented by a code.
Field name: | service_contact_participation_indicator |
||||
---|---|---|---|---|---|
Data type: | string |
||||
Required: | yes |
||||
Domain: |
|
||||
Notes: | Service contacts are not restricted to in-person communication but can include telephone, video link or other forms of direct communication.
Note: Where a client intended to participate in a service contact but failed to attend, Client Participation Indicator should be recorded as ‘1: Yes’ and No Show should be recorded as ‘1: Yes’. |
||||
METeOR: |
5.4.11. Client Tags¶
List of tags for the client.
Field name: | client_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.12. Collection Occasion Date¶
The date of the collection occasion.
Field name: | collection_occasion_date |
---|---|
Data type: | date |
Required: | yes |
Notes: | For Date fields, data 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, 13th March 2008 would appear as 13032008. If the date the activity was performed is unknown, 09099999 should be used.
|
5.4.13. Collection Occasion Key¶
This is a number or code assigned to each collection occasion of service activities. The Collection Occasion Key is unique and stable for each collection occasion at the level of the organisation.
Field name: | collection_occasion_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | Collection Occasion Keys must be generated by the organisation to be unique at the Provider Organisation level and must persist across time. See Identifier Management |
5.4.14. Collection Occasion Reason¶
The reason for the collection of the service activities on the identified Collection Occasion.
Field name: | reason_for_collection |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: |
|
5.4.15. Collection Occasion Tags¶
List of tags for the collection occasion.
Field name: | collection_occasion_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.16. Copayment¶
The co-payment is the amount paid by the client per session.
Field name: | service_contact_copayment |
---|---|
Data type: | number |
Required: | yes |
Domain: | 0 - 999999.99 |
Notes: | Up to 6 digits before the decimal point; up to 2 digits after the decimal point. The co-payment is the amount paid by the client per service contact, not the fee paid by the project to the practitioner or the fee paid by the project to the practitioner plus the client contribution. In many cases, there will not be a co-payment charged and therefore zero should be entered. Where a co-payment is charged it should be minimal and based on an individual’s capacity to pay. |
5.4.17. Country of Birth¶
The country in which the client was born, as represented by a code.
Field name: | country_of_birth |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string (4) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Standard Australian Classification of Countries (SACC), 2016 4-digit code (ABS Catalogue No. 1269.0) SACC 2016 is a four-digit, three-level hierarchical structure specifying major group, minor group and country. 9999 is used when the information is not known or the client has refused to provide the information. Organisations are encouraged to produce customised lists of the most common languages in use by their local populations from the above resource. Please refer to Country of Birth for help on designing forms. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
METeOR: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ABS: |
5.4.18. Date client contacted Intake¶
The date on which the client first contacted the intake service
Field name: | date_client_contacted_intake |
---|---|
Data type: | date |
Required: | yes |
Notes: | For Date fields, data 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, 13th March 2008 would appear as 13032008.
|
5.4.19. Date of Birth¶
The date on which an individual was born.
Field name: | date_of_birth |
---|---|
Data type: | date |
Required: | yes |
Notes: |
|
METeOR: |
5.4.20. Date referred to other service at Intake conclusion¶
The date the client was referred to another organisation at Intake conclusion.
Field name: | date_referred_to_other_service_at_intake_conclusion |
---|---|
Data type: | date |
Required: | no |
Notes: |
|
5.4.21. Duration¶
The time from the start to finish of a service contact.
Field name: | service_contact_duration |
||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||
Required: | yes |
||||||||||||||||||||
Domain: |
|
||||||||||||||||||||
Notes: | For group sessions the time for client spent in the session is recorded for each client, regardless of the number of clients or third parties participating or the number of service providers providing the service. Writing up details of service contacts is not to be reported as part of the duration, except if during or contiguous with the period of client or third party participation. Travel to or from the location at which the service is provided, for example to or from outreach facilities or private homes, is not to be reported as part of the duration of the service contact.
|
5.4.22. Employment Participation¶
Whether a person in paid employment is employed full-time or part-time, as represented by a code.
Field name: | employment_participation |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: | Applies only to people whose labour force status is employed. (See metadata item Labour Force Status, for a definition of ‘employed’). Paid employment includes persons who performed some work for wages or salary, in cash or in kind, and persons temporarily absent from a paid employment job but who retained a formal attachment to that job.
|
||||||||
METeOR: |
5.4.23. Episode Completion Status¶
An indication of the completion status of an Episode of Care.
Field name: | episode_completion_status |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | no |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | In order to use code 1 (Episode closed - treatment concluded) the client must have at least one service contact. All other codes may be applicable even when the client has no service contacts.
Episode Completion Status interacts with two other data items in the PMHC MDS - Service Contact - Final, and Episode End Date.
|
5.4.24. Episode End Date¶
The date on which an Episode of Care is formally or administratively ended
Field name: | episode_end_date |
---|---|
Data type: | date |
Required: | no |
Notes: |
An Episode of Care may be ended in one of two ways:
Episode End Date interacts with two other data items in the PMHC MDS - Service Contact - Final, and Episode Completion Status.
|
METeOR: |
5.4.25. Episode Key¶
This is a number or code assigned to each PMHC MDS episode. The Episode Key is unique and stable for each episode at the level of the organisation. This key must link to an existing episode within the PMHC MDS.
Field name: | episode_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | Episode Keys must be generated by the organisation to be unique at the Provider Organisation level and must persist across time. Creation of episode keys in this way allows clients to be merged (where duplicate Client Keys have been identified) without having to re-allocate episode identifiers since they can never clash. See Managing Episode Keys Episode Keys are case sensitive and must be valid unicode characters. A recommended approach for the creation of Episode Keys is to compute random UUIDs. |
5.4.26. Episode Organisation Path¶
A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing the clinical service to the client.
Field name: | episode_organisation_path |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
|||||||||||||||
Required: | yes |
|||||||||||||||
Notes: | A combination of the Primary Health Network’s (PHN’s) Organisation Key and the Provider Organisation’s Organisation Key separated by a colon. Here is an example organisation structure showing the Organisation Path for each organisation:
|
5.4.27. Episode Tags¶
List of tags for the episode.
Field name: | episode_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.28. Estimated Date of Birth Flag¶
The date of birth estimate flag records whether or not the client’s date of birth has been estimated.
Field name: | est_date_of_birth |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
5.4.29. Final Service Contact¶
An indication of whether the Service Contact is the final for the current Episode of Care
Field name: | service_contact_final |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | Service providers should report this item on the basis of future planned or scheduled contacts with the client. Where this item is recorded as 1 (No further services planned), the episode should be recorded as completed by:
Note that no further Service Contacts can be recorded against an episode once it is marked as completed. Where an episode has been marked as completed prematurely, the Episode End Date can be manually corrected to allow additional activity to be recorded. |
5.4.30. Funding Source¶
The source of PHN Mental Health funds that are wholly or primarily funding the Service Contact.
Field name: | funding_source |
||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||||||||
Notes: | Organisations must record this information for all new Service Contacts under the Version 4 specification.
|
5.4.31. GP Mental Health Treatment Plan Flag¶
An indication of whether a client has a GP mental health treatment plan. A GP should be involved in a referral where appropriate however a mental health treatment plan is not mandatory.
Field name: | mental_health_treatment_plan |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
5.4.32. Health Care Card¶
An indication of whether the person is a current holder of a Health Care Card that entitles them to arrange of concessions for Government funded health services.
Field name: | health_care_card |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: | Details on the Australian Government Health Care Card are available at: https://www.humanservices.gov.au/customer/services/centrelink/health-care-card |
||||||||
METeOR: |
5.4.33. Homelessness Flag¶
An indication of whether the client has been homeless in the 4 weeks prior to the current service episode.
Field name: | homelessness |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: |
Select the code that best fits the client’s sleeping arrangements over the preceding 4 weeks. Where multiple options apply (e.g., client has experienced more than one of the sleeping arrangements over the previous 4 weeks) the following coding hierarchy should be followed:
|
5.4.34. IAR-DST - Domain 1 - Symptom Severity and Distress (Primary Domain)¶
An initial assessment should examine severity of symptoms, distress and previous history of mental illness. Severity of current symptoms and associated levels of distress are important factors in assigning a level of care and making a referral decision. Assessing changes in symptom severity and distress also forms an important part of outcome monitoring.
Field name: | iar_dst_domain_1 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 1 - Symptom Severity and Distress (Primary Domain) |
5.4.35. IAR-DST - Domain 2 - Risk of Harm (Primary Domain)¶
An initial assessment should include an evaluation of risk to determine a person’s potential for harm to self or others. Results from this assessment are of fundamental importance in deciding the appropriate level of care required.
Field name: | iar_dst_domain_2 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 2 - Risk of Harm (Primary Domain) |
5.4.36. IAR-DST - Domain 3 - Functioning (Primary Domain)¶
An initial assessment should consider functional impairment caused by or exacerbated by the mental health condition. While other types of disabilities may play a role in determining what types of support services may be required, they should generally not be considered in determining mental health intervention intensity within a stepped care continuum.
Field name: | iar_dst_domain_3 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 3 - Functioning (Primary Domain) |
5.4.37. IAR-DST - Domain 4 - Impact of Co-existing Conditions (Primary Domain)¶
Increasingly, individuals are experiencing and managing multi-morbidity (coexistence of multiple conditions including chronic disease). An initial assessment should specifically examine the presence of other concurrent health conditions that contribute to (or have the potential to contribute to) increased severity of mental health problems and/or compromises the person’s ability to participate in the recommended treatment.
Field name: | iar_dst_domain_4 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 4 - Impact of Co-existing Conditions (Primary Domain) |
5.4.38. IAR-DST - Domain 5 - Treatment and Recovery History (Contextual Domain)¶
This initial assessment domain should explore the individual’s relevant treatment history and their response to previous treatment. Response to previous treatment is a reasonable predictor of future treatment need and is particularly important when determining appropriateness of lower intensity services.
Field name: | iar_dst_domain_5 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 5 - Treatment and Recovery History (Contextual Domain) |
5.4.39. IAR-DST - Domain 6 - Social and Environmental Stressors (Contextual Domain)¶
This initial assessment domain should consider how the person’s environment might contribute to the onset or maintenance of a mental health condition. Significant situational or social complexities can lead to increased condition severity and/or compromise ability to participate in the recommended treatment. Unresolved situational or social complexities can limit the likely benefit of treatment. Furthermore, understanding the complexities experienced by the individual (with carer/support person perspectives if available), may alter the type of service offered, or indicate that additional service referrals may be required (e.g., a referral to an emergency housing provider).
Field name: | iar_dst_domain_6 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 6 - Social and Environmental Stressors (Contextual Domain) |
5.4.40. IAR-DST - Domain 7 - Family and Other Supports (Contextual Domain)¶
This initial assessment domain should consider whether informal supports are present and their potential to contribute to recovery. A lack of supports might contribute to the onset or maintenance of the mental health condition and/or compromise ability to participate in the recommended treatment.
Field name: | iar_dst_domain_7 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 7 - Family and Other Supports (Contextual Domain) |
5.4.41. IAR-DST - Domain 8 - Engagement and Motivation (Contextual Domain)¶
This initial assessment domain should explore the person’s understanding of the mental health condition and their willingness to engage in or accept treatment.
Field name: | iar_dst_domain_8 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Please refer to IAR-DST Domain 8 - Engagement and Motivation (Contextual Domain) |
5.4.42. IAR-DST - Practitioner Level of Care¶
The individualised level of care assessed by the practitioner for the referral
Field name: | iar_dst_practitioner_level_of_care |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Please refer to IAR-DST Levels of Care This field was added on 25/2/2021. IAR-DST data entered into the PMHC-MDS before 25/2/2021 will have the Practitioner Level of Care set to 9: Missing. All data entered after 25/2/2021 must use responses 1-5. |
5.4.43. IAR-DST - Recommended Level of Care¶
The information gathered through the initial assessment is used to assign a recommended level of care and inform a referral decision. The levels of care are not intended to replace individualised assessment and care - rather to provide information to guide decision making.
Field name: | iar_dst_recommended_level_of_care |
||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||
Required: | yes |
||||||||||||||||||
Domain: |
|
||||||||||||||||||
Notes: | Please refer to IAR-DST Levels of Care |
5.4.44. IAR-DST - Tags¶
List of tags for the measure.
Field name: | iar_dst_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.45. IAR-DST - Version¶
The version of the IAR-DST collected.
Field name: | iar_dst_version |
||
---|---|---|---|
Data type: | string |
||
Required: | yes |
||
Domain: |
|
5.4.46. Intake Key¶
This is a number or code assigned to each intake. The Intake Key is unique and stable for each intake at the level of the organisation.
Field name: | intake_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | Intake Keys must be generated by the organisation to be unique at the provider organisation level and must persist across time. Creation of intake keys in this way allows clients to be merged (where duplicate Client Keys have been identified) without having to re-allocate intake identifiers since they can never clash. A recommended approach for the creation of Intake Keys is to compute random UUIDs. |
5.4.47. Intake Organisation Path¶
A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing the intake to the client.
Field name: | intake_organisation_path |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
|||||||||||||||
Required: | yes |
|||||||||||||||
Notes: | A combination of the Primary Health Network’s (PHN’s) Organisation Key and the Provider Organisation’s Organisation Key separated by a colon. Here is an example organisation structure showing the Organisation Path for each organisation:
|
5.4.48. Intake Tags¶
List of tags for the intake.
Field name: | intake_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.49. Interpreter Used¶
Whether an interpreter service was used during the Service Contact
Field name: | service_contact_interpreter |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | Interpreter services includes verbal language, non-verbal language and languages other than English.
|
5.4.50. Key¶
A metadata key name.
Field name: | key |
---|---|
Data type: | string |
Required: | yes |
Notes: | Current allowed metadata keys are type and version. Please refer to Metadata file for an example of the metadata file/worksheet that must be used with this specification. |
5.4.51. K5 - Question 1¶
In the last 4 weeks, about how often did you feel nervous?
Field name: | k5_item1 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.52. K5 - Question 2¶
In the last 4 weeks, about how often did you feel without hope?
Field name: | k5_item2 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.53. K5 - Question 3¶
In the last 4 weeks, about how often did you feel restless or jumpy?
Field name: | k5_item3 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.54. K5 - Question 4¶
In the last 4 weeks, about how often did you feel everything was an effort?
Field name: | k5_item4 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.55. K5 - Question 5¶
In the last 4 weeks, about how often did you feel so sad that nothing could cheer you up?
Field name: | k5_item5 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.56. K5 - Score¶
The overall K5 score.
Field name: | k5_score |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 5 - 25, 99 = Not stated / Missing |
Notes: | The K5 Total score is based on the sum of K5 item 1 through 5 (range: 5-25). The Total score is computed as the sum of the item scores. If any item has not been completed (that is, has not been coded 1, 2, 3, 4, 5), it is excluded from the calculation and not counted as a valid item. If any item is missing, the Total Score is set as missing. For the Total score, the missing value used should be 99. When reporting individual item scores use ‘99 - Not stated / Missing’ |
5.4.57. K5 - Tags¶
List of tags for the measure.
Field name: | k5_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.58. K10+ - Question 1¶
In the past 4 weeks, about how often did you feel tired out for no good reason?
Field name: | k10p_item1 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.59. K10+ - Question 2¶
In the past 4 weeks, about how often did you feel nervous?
Field name: | k10p_item2 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.60. K10+ - Question 3¶
In the past 4 weeks, about how often did you feel so nervous that nothing could calm you down?
Field name: | k10p_item3 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.61. K10+ - Question 4¶
In the past 4 weeks, how often did you feel hopeless?
Field name: | k10p_item4 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.62. K10+ - Question 5¶
In the past 4 weeks, how often did you feel restless or fidgety?
Field name: | k10p_item5 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.63. K10+ - Question 6¶
In the past 4 weeks, how often did you feel so restless you could not sit still?
Field name: | k10p_item6 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.64. K10+ - Question 7¶
In the past 4 weeks, how often did you feel depressed?
Field name: | k10p_item7 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.65. K10+ - Question 8¶
In the past 4 weeks, how often did you feel that everything was an effort?
Field name: | k10p_item8 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.66. K10+ - Question 9¶
In the past 4 weeks, how often did you feel so sad that nothing could cheer you up?
Field name: | k10p_item9 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.67. K10+ - Question 10¶
In the past 4 weeks, how often did you feel worthless?
Field name: | k10p_item10 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When reporting total score use ‘9 - Not stated / Missing’ |
5.4.68. K10+ - Question 11¶
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?
Field name: | k10p_item11 |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 28, 99 = Not stated / Missing |
Notes: | When the client’s responses to Q1-10 are all recorded as 1 ‘None of the time’, they are not required to answer questions 11-14. Where this question has not been answered a response of ‘99 - Not stated / Missing’ should be selected. |
5.4.69. K10+ - Question 12¶
Aside from those days, 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 these feelings?
Field name: | k10p_item12 |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 28, 99 = Not stated / Missing |
Notes: | When the client’s responses to Q1-10 are all recorded as 1 ‘None of the time’, they are not required to answer questions 11-14. Where this question has not been answered a response of ‘99 - Not stated / Missing’ should be selected. |
5.4.70. K10+ - Question 13¶
In the past four weeks, how many times have you seen a doctor or any other health professional about these feelings?
Field name: | k10p_item13 |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 89, 99 = Not stated / Missing |
Notes: | When the client’s responses to Q1-10 are all recorded as 1 ‘None of the time’, they are not required to answer questions 11-14. Where this question has not been answered a response of ‘99 - Not stated / Missing’ should be selected. |
5.4.71. K10+ - Question 14¶
In the past four weeks, how often have physical health problems been the main cause of these feelings?
Field name: | k10p_item14 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | When the client’s responses to Q1-10 are all recorded as 1 ‘None of the time’, they are not required to answer questions 11-14. Where this question has not been answered a response of ‘99 - Not stated / Missing’ should be selected. |
5.4.72. K10+ - Score¶
The overall K10 score.
Field name: | k10p_score |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 10 - 50, 99 = Not stated / Missing |
Notes: | The K10 Total score is based on the sum of K10 item 01 through 10 (range: 10-50). Items 11 through 14 are excluded from the total because they are separate measures of disability associated with the problems referred to in the preceding ten items. The Total score is computed as the sum of the scores for items 1 to 10. If any item has not been completed (that is, has not been coded 1, 2, 3, 4, 5), it is excluded from the total When items 01 through 10 has one item “not stated/missing” (value 9), the Total Score is pro-rated using the following formula:
When items 01 through 10 has more than one item “not stated/missing” (value 9), the Total Score is set as invalid. Where this is the case, the “not stated/missing” (value 99) should be used. For more information on scoring the K10+, please refer to page 58 of AMHOCN’s Overview of clinician-rated and consumer self-report measures at https://www.amhocn.org/sites/default/files/publication_files/nocc_clinician_and_self-report_measures_overview_v2.1_20210913_1.pdf When upload report individual item scores and use a Total Score ‘99 - Not stated / Missing’, the PMHC MDS will calculate the total score. |
5.4.73. K10+ - Tags¶
List of tags for the measure.
Field name: | k10p_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.74. Labour Force Status¶
The self-reported status the person currently has in being either in the labour force (employed/unemployed) or not in the labour force, as represented by a code.
Field name: | labour_force_status |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: |
Actively looked for work includes:
|
||||||||
METeOR: |
5.4.75. Legal Name¶
The legal name of the provider organisation.
Field name: | organisation_legal_name |
---|---|
Data type: | string |
Required: | no |
5.4.76. Main Language Spoken at Home¶
The language reported by a client as the main language other than English spoken by that client in his/her home (or most recent private residential setting occupied by the client) to communicate with other residents of the home or setting and regular visitors, as represented by a code.
Field name: | main_lang_at_home |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string (4) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Australian Standard Classification of Languages (ASCL), 2016 4-digit code (ABS Catalogue No. 1267.0) or 9999 if info is not known or client refuses to supply. The ABS recommends the following question in order to collect this data: Which language does the client mainly speak at home? (If more than one language, indicate the one that is spoken most often.) Organisations are encouraged to produce customised lists of the most common countries based on their local populations from the above resource. Please refer to Main Language Spoken at Home for help on designing forms. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
METeOR: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ABS: |
5.4.77. Marital Status¶
A person’s current relationship status in terms of a couple relationship or, for those not in a couple relationship, the existence of a current or previous registered marriage, as represented by a code.
Field name: | marital_status |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Refers to the current marital status of a person.
|
||||||||||||
METeOR: |
5.4.78. Measure Key¶
This is a number or code assigned to each instance of a measure. The Measure Key is unique and stable for each instance of a measure at the level of the organisation.
Field name: | measure_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | Measure keys are case sensitive and must be valid unicode characters. |
5.4.79. Medication - Antidepressants (N06A)¶
Whether the client is taking prescribed antidepressants for a mental health condition as assessed at intake assessment, as represented by a code.
Field name: | medication_antidepressants |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | The N06A class of drugs a therapeutic subgroup of the Anatomical Therapeutic Chemical Classification System, a system of alphanumeric codes developed by the World Health Organisation (WHO) for the classification of drugs and other medical products. It covers drugs designed for the depressive disorders. Details of drugs included in the category can be found here: http://www.whocc.no/atc_ddd_index/?code=N06A |
5.4.80. Medication - Antipsychotics (N05A)¶
Whether the client is taking prescribed antipsychotics for a mental health condition as assessed at intake assessment, as represented by a code.
Field name: | medication_antipsychotics |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | The N05A class of drugs a therapeutic subgroup of the Anatomical Therapeutic Chemical Classification System, a system of alphanumeric codes developed by the World Health Organisation (WHO) for the classification of drugs and other medical products. It covers drugs designed for the treatment of psychotic disorders. Details of drugs included in the category can be found here: http://www.whocc.no/atc_ddd_index/?code=N05A |
5.4.81. Medication - Anxiolytics (N05B)¶
Whether the client is taking prescribed anxiolytics for a mental health condition as assessed at intake assessment, as represented by a code.
Field name: | medication_anxiolytics |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | The N05B class of drugs a therapeutic subgroup of the Anatomical Therapeutic Chemical Classification System, a system of alphanumeric codes developed by the World Health Organisation (WHO) for the classification of drugs and other medical products. It covers drugs designed for the treatment of disorders associated with anxiety and tension. Details of drugs included in the category can be found here: http://www.whocc.no/atc_ddd_index/?code=N05B |
5.4.82. Medication - Hypnotics and sedatives (N05C)¶
Whether the client is taking prescribed hypnotics and sedatives for a mental health condition as assessed at intake assessment, as represented by a code.
Field name: | medication_hypnotics |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | The N05C class of drugs a therapeutic subgroup of the Anatomical Therapeutic Chemical Classification System, a system of alphanumeric codes developed by the World Health Organisation (WHO) for the classification of drugs and other medical products. It covers drugs designed to have mainly sedative or hypnotic actions. Hypnotic drugs are used to induce sleep and treat severe insomnia. Sedative drugs are prescribed to reduce excitability or anxiety. Details of drugs included in the category can be found here: http://www.whocc.no/atc_ddd_index/?code=N05C |
5.4.83. Medication - Psychostimulants and nootropics (N06B)¶
Whether the client is taking prescribed psychostimulants and nootropics for a mental health condition as assessed at intake assessment, as represented by a code.
Field name: | medication_psychostimulants |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | The N06B class of drugs a therapeutic subgroup of the Anatomical Therapeutic Chemical Classification System, a system of alphanumeric codes developed by the World Health Organisation (WHO) for the classification of drugs and other medical products. It covers drugs designed to attention-deficit hyperactivity disorder (ADHD) and to improve impaired cognitive abilities. Details of drugs included in the category can be found here: http://www.whocc.no/atc_ddd_index/?code=N06B |
5.4.84. Modality¶
How the service contact was delivered, as represented by a code.
Field name: | service_contact_modality |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: |
Note: If Service Contact Modality is not ‘Face to Face’ the postcode must be entered as unknown 9999. |
5.4.85. Name¶
The name of the provider organisation.
Field name: | organisation_name |
---|---|
Data type: | string (2,100) |
Required: | yes |
5.4.86. NDIS Participant¶
Is the client a participant in the National Disability Insurance Scheme?, as represented by a code.
Field name: | ndis_participant |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
5.4.87. No Show¶
Where an appointment was made for an intended participant(s), but the intended participant(s) failed to attend the appointment, as represented by a code.
Field name: | service_contact_no_show |
||||
---|---|---|---|---|---|
Data type: | string |
||||
Required: | yes |
||||
Domain: |
|
||||
Notes: |
|
5.4.88. Organisation End Date¶
The date on which a provider organisation stopped delivering services.
Field name: | organisation_end_date |
---|---|
Data type: | date |
Required: | yes |
Notes: | For Date fields, data 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, 13th March 2008 would appear as 13032008.
For validation rules please refer to Organisation. |
5.4.89. Organisation Key¶
A sequence of characters which uniquely identifies the provider organisation to the Primary Health Network. Assigned by the Primary Health Network.
Field name: | organisation_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | Organisation Keys must be generated by the PHN to be unique and must persist across time. See Managing Provider Organisation Keys Organisation keys are case sensitive and must be valid unicode characters. |
5.4.90. Organisation Path¶
A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation providing a service to the client.
Field name: | organisation_path |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
|||||||||||||||
Required: | yes |
|||||||||||||||
Notes: | A combination of the Primary Health Network’s (PHN’s) Organisation Key and the Provider Organisation’s Organisation Key separated by a colon. Here is an example organisation structure showing the Organisation Path for each organisation:
|
5.4.91. Organisation Start Date¶
The date on which a provider organisation started delivering services.
Field name: | organisation_start_date |
---|---|
Data type: | date |
Required: | yes |
Notes: | For Date fields, data 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, 13th March 2008 would appear as 13032008. For validation rules please refer to Organisation. |
5.4.92. Organisation Tags¶
List of tags for the provider organisation.
Field name: | organisation_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.93. Organisation Type¶
The category that best describes the provider organisation.
Field name: | organisation_type |
||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||
Notes: |
|
5.4.94. Organisation type referred to at Episode conclusion¶
Type of organisation to which the the client was referred at the Episode conclusion.
Field name: | organisation_type_referred_to_at_episode_conclusion |
||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||||||||||||||||||||
Required: | no |
||||||||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
Multiple space separated values allowed |
||||||||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Medical Specialist Consulting Rooms includes private medical practitioner rooms in public or private hospital or other settings. Public mental health service refers to a state- or territory-funded specialised mental health services (i.e., specialised mental health care delivered in public acute and psychiatric hospital settings, community mental health care services, and specialised residential mental health care services). |
5.4.95. Organisation type referred to at Intake conclusion¶
Type of organisation to which the the client was referred at the Intake conclusion.
Field name: | organisation_type_referred_to_at_intake_conclusion |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Required: | no |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
Multiple space separated values allowed |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Medical Specialist Consulting Rooms includes private medical practitioner rooms in public or private hospital or other settings. Public mental health service refers to a state- or territory-funded specialised mental health services (i.e., specialised mental health care delivered in public acute and psychiatric hospital settings, community mental health care services, and specialised residential mental health care services). The intent is that each referral out only has one organisation type and that multiple organisation types imples multiple referrals. Where an organisation could belong to multiple types, the type that best suits the reason for the referral should be selected. |
5.4.96. Participants¶
An indication of who participated in the Service Contact.
Field name: | service_contact_participants |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: |
Note: This item interacts with Client Participation Indicator. Where Participants has a value of ‘1: Individual’, Client Participation Indicator must have a value of ‘1: Yes’. No Show is used to record if the patient failed to attend the appointment. |
5.4.97. Postcode¶
The Australian postcode where the service contact took place.
Field name: | service_contact_postcode |
---|---|
Data type: | string |
Required: | yes |
Notes: | A valid Australian postcode or 9999 if the postcode is unknown. The full list of Australian Postcodes can be found at Australia Post.
|
METeOR: |
5.4.98. Practitioner Aboriginal and Torres Strait Islander Status¶
Whether a person identifies as being of Aboriginal and/or Torres Strait Islander origin, as represented by a code.
Field name: | practitioner_atsi_status |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: |
|
||||||||||
METeOR: |
5.4.99. Practitioner Category¶
The type or category of the practitioner, as represented by a code.
Field name: | practitioner_category |
||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||
Notes: | Practitioner category refers to the labour classification of the service provider delivering the Service Contact. Practitioners should be assigned to the code that best describes their role for which they are engaged to deliver services to clients. Practitioners are registered in the PMHC MDS by Provider Organisations, with each practitioner assigned a code that is unique within the organisation. In most cases, Practitioner Category will be determined by the training and qualifications of the practitioner. However, in some instances, a practitioner may be employed in a capacity that does not necessarily reflect their formal qualifications. For example, a person with a social work qualification may be employed primarily as a peer support worker on the basis of their lived experience of a mental illness. In such instances, the practitioner should be classified as a peer support worker.
Changes in effect from 1 January 2019
|
5.4.100. Practitioner Gender¶
The term ‘gender’ refers to the way in which a person identifies their masculine or feminine characteristics. A persons gender relates to their deeply held internal and individual sense of gender and is not always exclusively male or female. It may or may not correspond to their sex assigned at birth.
Field name: | practitioner_gender |
||||||||
---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||
Required: | yes |
||||||||
Domain: |
|
||||||||
Notes: |
|
||||||||
ABS: |
5.4.101. Practitioner Key¶
A unique identifier for a practitioner within the responsible provider organisation. Assigned by either the PHN or Provider Organisation depending on local procedures.
Field name: | practitioner_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | PMHC MDS keys are case sensitive and must have between 2-50 valid unicode characters. Keys must start with A-Za-z0-9 (POSIX :alnum:). Where data is being exported from client systems, these keys can be auto generated, providing that a key does not change once it is assigned. Keys must be generated by the organisation to be unique at the Provider Organisation level and must persist across time. Creation of keys in this way allows records to be merged (where duplicate keys of the same record type have been identified) without having to re-allocate keys since they can never clash. A recommended approach for the creation of keys is to compute random UUIDs. |
5.4.102. Practitioner Tags¶
List of tags for the practitioner.
Field name: | practitioner_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.103. Primary Practitioner Indicator¶
An indicator of whether the practitioner was the primary practitioner responsible for the service contact.
Field name: | primary_practitioner_indicator |
||||
---|---|---|---|---|---|
Data type: | string |
||||
Required: | yes |
||||
Domain: |
|
5.4.104. Principal Diagnosis¶
The Principal Diagnosis is the diagnosis established after study to be chiefly responsible for occasioning the client’s care during the current Episode of Care.
Field name: | principal_diagnosis |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Diagnoses are grouped into 8 major categories (9 for Additional Diagnosis):
The Principal Diagnosis should be determined by the treating or supervising clinical practitioner who is responsible for providing, or overseeing, services delivered to the client during their current episode of care. Each episode of care must have a Principal Diagnosis recorded and may have an Additional Diagnoses. In some instances the client’s Principal Diagnosis may not be clear at initial contact and require a period of contact before a reliable diagnosis can be made. If a client has more than one diagnosis, the Principal Diagnosis should reflect the main presenting problem. Any secondary diagnosis should be recorded under the Additional Diagnosis field. The coding options developed for the PMHC MDS have been selected to balance comprehensiveness and brevity. They comprise a mix of the most prevalent mental disorders in the Australian adult, child and adolescent population, supplemented by less prevalent conditions that may be experienced by clients of PHN-commissioned mental health services. The diagnosis options are based on an abbreviated set of clinical terms and groupings specified in the Diagnostic and Statistical Manual of Mental Disorders Fourth Edition (DSM-IV-TR). These code list summarises the approximate 300 unique mental health disorder codes in the full DSM-IV to a set to 9 major categories, and 37 individual codes. Diagnoses are grouped under higher level categories, based on the DSM-IV. Code numbers have been assigned specifically for the PMHC MDS to create a logical ordering but are capable of being mapped to both DSM-IV and ICD-10 codes. Options for recording Principal Diagnosis include the broad category ‘No formal mental disorder but subsyndromal problems’ (codes commencing with 9). These codes should be used for clients who present with problems that do not meet threshold criteria for a formal diagnosis - for example, people experiencing subsyndromal symptoms who may be at risk of progressing to a more severe symptom level. Each category has a final entry for capturing other conditions that don’t meet the more specific entries in the category. This includes the ‘No formal mental disorder but subsyndromal problems’ category. Code 905 (‘Other symptoms’) can be used to capture situations where a formal mental disorder has not be diagnosed, but the symptoms do not fall under the more specific 9XX series entries. The 905 code should not be used where there is a formal but unlisted mental disorder. In such a situation code 605 (‘Other mental disorder’) should be used. Reference: Diagnostic and Statistical Manual of Mental Disorders, Fourth Edition, Text Revision. Copyright 2000 American Psychiatric Association. The following responses have been added to allow mapping of ATAPS data to PMHC format.
Note: These four codes should only be used for Episodes that are migrated from ATAPS MDS sources that cannot be described by any other Diagnosis. It is expected that the majority of Episodes delivered to clients from 1st July, 2017 can be assigned to other diagnoses. These responses will only be allowed on episodes where the original ATAPS referral date was before 1 July 2017 These responses will only be allowed on episodes with the !ATAPS flag. |
5.4.105. Principal Focus of Treatment Plan¶
The range of activities that best describes the overall services intended to be delivered to the client throughout the course of the episode. For most clients, this will equate to the activities that account for most time spent by the service provider.
Field name: | principal_focus |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Describes the main focus of the services to be delivered to the client for the current Episode of Care, selected from a defined list of categories. Service providers are required to report on the ‘Principal Focus of Treatment Plan’ for all accepted referrals. This requires a judgement to be made about the main focus of the services to be delivered to the client for the current Episode of Care, made following initial assessment and modifiable at a later stage. It is chosen from a defined list of categories, with the provider required to select the category that best fits the treatment plan designed for the client. Principal Focus of Treatment Plan is necessarily a judgement made by the provider at the outset of service delivery but consistent with good practice, should be made on the basis of a treatment plan developed in collaboration with the client. It should not be confused with Service Type which is collected at each Service Contact.
|
5.4.106. Proficiency in Spoken English¶
The self-assessed level of ability to speak English, asked of people whose first language is a language other than English or who speak a language other than English at home.
Field name: | prof_english |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: |
|
||||||||||||
METeOR: |
5.4.107. Program Type¶
The overarching program area that an Intake or Episode record is associated with.
Field name: | program_type |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: |
|
5.4.108. Referral Date¶
The date the referrer made the referral.
Field name: | referral_date |
---|---|
Data type: | date |
Required: | yes |
Notes: | The referral date is the date the client was originally referred to an MDS reporting service. Typically the referral is made by an external (non-MDS) provider - such as a general practitioner, but it may be another MDS reporting service or the client themselves. Where there is a linked intake and treatment both the Intake and Episode records must use the same date - ie. the date the client was originally referred. The referral date is NOT the date that an intake service refers a client to a treatment organisation. For clients who self refer, the referral date should be the date the client first contacted the intake service or provider organisation. For the intake of a client who self referred, the referral date will be the same as the Date client contacted Intake. For Date fields, data 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, 13th March 2008 would appear as 13032008.
Referral date was optional in specifications prior to Version 4. In Version 4 referral date has been made mandatory. In order to export and re-upload episode data that was uploaded or entered prior to Version 4 the value ‘09099999’ will be used in data exports and allowed for existing episode data without a referral date. See Episode for rules on how this value may be used. |
5.4.109. Referred to Organisation Path¶
A sequence of colon separated Organisation Keys that fully specifies the Provider Organisation to which the intake referred the client.
Field name: | referred_to_organisation_path |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
|||||||||||||||
Required: | no |
|||||||||||||||
Notes: | A combination of the referred to Primary Health Network’s (PHN’s) Organisation Key and the referred to Provider Organisation’s Organisation Key separated by a colon. Here is an example organisation structure showing the Organisation Path for each organisation:
|
5.4.110. Referrer Organisation Type¶
Type of organisation in which the referring professional is based.
Field name: | referrer_organisation_type |
||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||||||||||||||
Notes: | Medical Specialist Consulting Rooms includes private medical practitioner rooms in public or private hospital or other settings. Public mental health service refers to a state- or territory-funded specialised mental health services (i.e., specialised mental health care delivered in public acute and psychiatric hospital settings, community mental health care services, and specialised residential mental health care services). Not applicable should only be selected in instances of Self referral. Where there is a linked intake and treatment, both the Intake and Episode records must use the same referrer organisation type - ie the intake service is NOT the referrer. |
5.4.111. Referrer Profession¶
Profession of the provider who referred the client.
Field name: | referrer_profession |
||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||||||||
Notes: | New arrangements for some services delivered in primary mental health care allows clients to refer themselves for treatment. Therefore, ‘Self’ is a response option included within ‘Referrer profession’. Where there is a linked intake and treatment, both the Intake and Episode records must use the same referrer profession - ie the intake service is not the referrer. |
5.4.112. SDQ Collection Occasion - Version¶
The version of the SDQ collected.
Field name: | sdq_version |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Domain values align with those collected in the NOCC dataset as defined at https://webval.validator.com.au/spec/NOCC/current/SDQ/SDQVer |
5.4.113. SDQ - Conduct Problem Scale¶
Field name: | sdq_conduct_problem |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 10, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Conduct Problem Scale. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.114. SDQ - Emotional Symptoms Scale¶
Field name: | sdq_emotional_symptoms |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 10, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Emotional Symptoms Scale. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.115. SDQ - Hyperactivity Scale¶
Field name: | sdq_hyperactivity |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 10, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Hyperactivity Scale. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.116. SDQ - Impact Score¶
Field name: | sdq_impact |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 10, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Impact Score. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.117. SDQ - Peer Problem Scale¶
Field name: | sdq_peer_problem |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 10, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Peer Problem Scale. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.118. SDQ - Prosocial Scale¶
Field name: | sdq_prosocial |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 10, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Prosocial Scale. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.119. SDQ - Question 1¶
Parent Report: Considerate of other people’s feelings.
Youth Self Report: I try to be nice to other people. I care about their feelings.
Field name: | sdq_item1 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.120. SDQ - Question 2¶
Parent Report: Restless, overactive, cannot stay still for long.
Youth Self Report: I am restless, I cannot stay still for long.
Field name: | sdq_item2 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.121. SDQ - Question 3¶
Parent Report: Often complains of headaches, stomach-aches or sickness.
Youth Self Report: I get a lot of headaches, stomach-aches or sickness.
Field name: | sdq_item3 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.122. SDQ - Question 4¶
Parent Report: Shares readily with other children {for example toys, treats, pencils} / young people {for example CDs, games, food}.
Youth Self Report: I usually share with others, for examples CDs, games, food.
Field name: | sdq_item4 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.123. SDQ - Question 5¶
Parent Report: Often loses temper.
Youth Self Report: I get very angry and often lose my temper.
Field name: | sdq_item5 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.124. SDQ - Question 6¶
Parent Report: {Rather solitary, prefers to play alone} / {would rather be alone than with other young people}.
Youth Self Report: I would rather be alone than with people of my age.
Field name: | sdq_item6 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.125. SDQ - Question 7¶
Parent Report: {Generally well behaved} / {Usually does what adults requests}.
Youth Self Report: I usually do as I am told.
Field name: | sdq_item7 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.126. SDQ - Question 8¶
Parent Report: Many worries or often seems worried.
Youth Self Report: I worry a lot.
Field name: | sdq_item8 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.127. SDQ - Question 9¶
Parent Report: Helpful if someone is hurt, upset or feeling ill.
Youth Self Report: I am helpful if someone is hurt, upset or feeling ill.
Field name: | sdq_item9 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.128. SDQ - Question 10¶
Parent Report: Constantly fidgeting or squirming.
Youth Self Report: I am constantly fidgeting or squirming.
Field name: | sdq_item10 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.129. SDQ - Question 11¶
Parent Report: Has at least one good friend.
Youth Self Report: I have one good friend or more.
Field name: | sdq_item11 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.130. SDQ - Question 12¶
Parent Report: Often fights with other {children} or bullies them / {young people}.
Youth Self Report: I fight a lot. I can make other people do what I want.
Field name: | sdq_item12 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.131. SDQ - Question 13¶
Parent Report: Often unhappy, depressed or tearful.
Youth Self Report: I am often unhappy, depressed or tearful.
Field name: | sdq_item13 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.132. SDQ - Question 14¶
Parent Report: Generally liked by other {children} / {young people}
Youth Self Report: Other people my age generally like me.
Field name: | sdq_item14 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.133. SDQ - Question 15¶
Parent Report: Easily distracted, concentration wanders.
Youth Self Report: I am easily distracted, I find it difficult to concentrate.
Field name: | sdq_item15 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.134. SDQ - Question 16¶
Parent Report: Nervous or {clingy} in new situations, easily loses confidence {omit clingy in PY}.
Youth Self Report: I am nervous in new situations. I easily lose confidence.
Field name: | sdq_item16 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.135. SDQ - Question 17¶
Parent Report: Kind to younger children.
Youth Self Report: I am kind to younger people.
Field name: | sdq_item17 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.136. SDQ - Question 18¶
Parent Report: Often lies or cheats.
Youth Self Report: I am often accused of lying or cheating.
Field name: | sdq_item18 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.137. SDQ - Question 19¶
Parent Report: Picked on or bullied by {children} / {youth}.
Youth Self Report: Other children or young people pick on me or bully me.
Field name: | sdq_item19 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.138. SDQ - Question 20¶
Parent Report: Often volunteers to help others (parents, teachers, {other} children) / Omit ‘other’ in PY.
Youth Self Report: I often volunteer to help others (parents, teachers, children).
Field name: | sdq_item20 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.139. SDQ - Question 21¶
Parent Report: Thinks things out before acting.
Youth Self Report: I think before I do things.
Field name: | sdq_item21 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.140. SDQ - Question 22¶
Parent Report: Steals from home, school or elsewhere.
Youth Self Report: I take things that are not mine from home, school or elsewhere.
Field name: | sdq_item22 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.141. SDQ - Question 23¶
Parent Report: Gets along better with adults than with other {children} / {youth}.
Youth Self Report: I get along better with adults than with people my own age.
Field name: | sdq_item23 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.142. SDQ - Question 24¶
Parent Report: Many fears, easily scared.
Youth Self Report: I have many fears, I am easily scared.
Field name: | sdq_item24 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.143. SDQ - Question 25¶
Parent Report: Good attention span sees chores or homework through to the end.
Youth Self Report: I finish the work I’m doing. My attention is good.
Field name: | sdq_item25 |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||
Required: | yes |
||||||||||
Domain: |
|
||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.144. SDQ - Question 26¶
Parent Report: Overall, do you think that your child has difficulties in any of the following areas: emotions, concentration, behaviour or being able to get along with other people?
Youth Self Report: Overall, do you think that you have difficulties in any of the following areas: emotions, concentration, behaviour or being able to get along with other people?
Field name: | sdq_item26 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.145. SDQ - Question 27¶
Parent Report: How long have these difficulties been present?
Youth Self Report: How long have these difficulties been present?
Field name: | sdq_item27 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: - PC101 - PY101 - YR101 When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.146. SDQ - Question 28¶
Parent Report: Do the difficulties upset or distress your child?
Youth Self Report: Do the difficulties upset or distress you?
Field name: | sdq_item28 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.147. SDQ - Question 29¶
Parent Report: Do the difficulties interfere with your child’s everyday life in the following areas? HOME LIFE.
Youth Self Report: Do the difficulties interfere with your everyday life in the following areas? HOME LIFE.
Field name: | sdq_item29 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.148. SDQ - Question 30¶
Parent Report: Do the difficulties interfere with your child’s everyday life in the following areas? FRIENDSHIPS.
Youth Self Report: Do the difficulties interfere with your everyday life in the following areas? FRIENDSHIPS.
Field name: | sdq_item30 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.149. SDQ - Question 31¶
Parent Report: Do the difficulties interfere with your child’s everyday life in the following areas? CLASSROOM LEARNING.
Youth Self Report: Do the difficulties interfere with your everyday life in the following areas? CLASSROOM LEARNING
Field name: | sdq_item31 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.150. SDQ - Question 32¶
Parent Report: Do the difficulties interfere with your child’s everyday life in the following areas? LEISURE ACTIVITIES.
Youth Self Report: Do the difficulties interfere with your everyday life in the following areas? LEISURE ACTIVITIES.
Field name: | sdq_item32 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.151. SDQ - Question 33¶
Parent Report: Do the difficulties put a burden on you or the family as a whole?
Youth Self Report: Do the difficulties make it harder for those around you (family, friends, teachers, etc)?
Field name: | sdq_item33 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions: All When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.152. SDQ - Question 34¶
Parent Report: Since coming to the services, are your child’s problems:
Youth Self Report: ‘Since coming to the service, are your problems:
Field name: | sdq_item34 |
||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||
Required: | yes |
||||||||||||||||
Domain: |
|
||||||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.153. SDQ - Question 35¶
Has coming to the service been helpful in other ways eg. providing information or making the problems bearable?
Field name: | sdq_item35 |
||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||
Required: | yes |
||||||||||||||
Domain: |
|
||||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.154. SDQ - Question 36¶
Over the last 6 months have your child’s teachers complained of fidgetiness, restlessness or overactivity?
Field name: | sdq_item36 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.155. SDQ - Question 37¶
Over the last 6 months have your child’s teachers complained of poor concentration or being easily distracted?
Field name: | sdq_item37 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.156. SDQ - Question 38¶
Over the last 6 months have your child’s teachers complained of acting without thinking, frequently butting in, or not waiting for his or her turn?
Field name: | sdq_item38 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.157. SDQ - Question 39¶
Does your family complain about you having problems with overactivity or poor concentration?
Field name: | sdq_item39 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.158. SDQ - Question 40¶
Do your teachers complain about you having problems with overactivity or poor concentration?
Field name: | sdq_item40 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.159. SDQ - Question 41¶
Does your family complain about you being awkward or troublesome?
Field name: | sdq_item41 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.160. SDQ - Question 42¶
Do your teachers complain about you being awkward or troublesome?
Field name: | sdq_item42 |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||
Required: | yes |
||||||||||||
Domain: |
|
||||||||||||
Notes: | Required Versions:
When reporting subscale and total scores use ‘9 - Not stated / Missing’. |
5.4.161. SDQ - Tags¶
List of tags for the measure.
Field name: | sdq_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.162. SDQ - Total Difficulties Score¶
Field name: | sdq_total |
---|---|
Data type: | integer |
Required: | yes |
Domain: | 0 - 40, 99 = Not stated / Missing |
Notes: | See SDQ items and Scale Summary scores for instructions on scoring the Total Difficulties Score. When reporting individual item scores use ‘99 - Not stated / Missing’. |
5.4.163. Service Contact Date¶
The date of each mental health service contact between a health service provider and patient/client.
Field name: | service_contact_date |
---|---|
Data type: | date |
Required: | yes |
Notes: | For Date fields, data 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, 13th March 2008 would appear as 13032008.
|
METeOR: |
5.4.164. Service Contact Key¶
This is a number or code assigned to each service contact. The Service Contact Key is unique and stable for each service contact at the level of the Provider Organisation.
Field name: | service_contact_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | PMHC MDS keys are case sensitive and must have between 2-50 valid unicode characters. Keys must start with A-Za-z0-9 (POSIX :alnum:). Where data is being exported from client systems, these keys can be auto generated, providing that a key does not change once it is assigned. Keys must be generated by the organisation to be unique at the Provider Organisation level and must persist across time. Creation of keys in this way allows records to be merged (where duplicate keys of the same record type have been identified) without having to re-allocate keys since they can never clash. A recommended approach for the creation of keys is to compute random UUIDs. |
5.4.165. Service Contact Practitioner Key¶
This is a number or code assigned to each service contact practitioner. The Service Contact Practitioner Key is unique and stable for each service contact practitioner at the level of the Provider Organisation.
Field name: | service_contact_practitioner_key |
---|---|
Data type: | string (2,50) |
Required: | yes |
Notes: | PMHC MDS keys are case sensitive and must have between 2-50 valid unicode characters. Keys must start with A-Za-z0-9 (POSIX :alnum:). Where data is being exported from client systems, these keys can be auto generated, providing that a key does not change once it is assigned. Keys must be generated by the organisation to be unique at the Provider Organisation level and must persist across time. Creation of keys in this way allows records to be merged (where duplicate keys of the same record type have been identified) without having to re-allocate keys since they can never clash. A recommended approach for the creation of keys is to compute random UUIDs. |
5.4.166. Service Contact Tags¶
List of tags for the service contact.
Field name: | service_contact_tags |
---|---|
Data type: | string |
Required: | no |
Notes: | A comma separated list of tags. Organisations can use this field to tag records in order to partition them as per local requirements. Tags can contain lower case letters (or will get lowercased), numbers, dashes,
spaces, and Tags beginning with an exclamation mark (!) are reserved for future use by the
Department. e.g. |
5.4.167. Service Contact Type¶
The main type of service provided in the service contact, as represented by the service type that accounted for most provider time.
Field name: | service_contact_type |
||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||
Notes: | Describes the main type of service delivered in the contact, selected from a defined list of categories. Where more than service type was provided select that which accounted for most provider time. Service providers are required to report on Service Type for all Service Contacts. Note: NEC is used for ‘Not Elsewhere Classified’. For these records, only use these service types if they cannot be classified by any of the other service options.
|
5.4.168. Source of Cash Income¶
The source from which a person derives the greatest proportion of his/her income, as represented by a code.
Field name: | income_source |
||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||
Required: | yes |
||||||||||||||||||
Domain: |
|
||||||||||||||||||
Notes: | This data standard is not applicable to person’s aged less than 16 years. This item refers to the source by which a person derives most (equal to or greater than 50%) of his/her income. If the person has multiple sources of income and none are equal to or greater than 50%, the one which contributes the largest percentage should be counted. This item refers to a person’s own main source of income, not that of a partner or of other household members. If it is difficult to determine a ‘main source of income’ over the reporting period (i.e. it may vary over time) please report the main source of income during the reference week. Code 7 ‘Not known’ should only be recorded when it has not been possible for the service user or their carer/family/advocate to provide the information (i.e. they have been asked but do not know). |
||||||||||||||||||
METeOR: |
5.4.169. Start Time¶
The start time of each mental health service contact between a health service provider and patient/client.
Field name: | service_contact_start_time |
---|---|
Data type: | time |
Required: | yes |
Notes: | Notes: Indicates the time at which the Service Contact began. Time should be recorded in 24-hour time in the format HH:MM. Leading zeroes are accepted but not required. For example, 8:30 in the morning could be 8:30 or 08:30 and 3:45 in the afternoon would be 15:45. The end-of-day flag “24:00” may be used as a missing time value for any existing Service Contacts that have previously been added to the MDS without a start time. See Service Contact for rules on how the end-of-day value may be used. |
5.4.170. State¶
The state that the provider organisation operates in.
Field name: | organisation_state |
||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||
Required: | yes |
||||||||||||||||||
Domain: |
|
||||||||||||||||||
Notes: |
|
||||||||||||||||||
METeOR: |
5.4.171. Statistical Linkage Key¶
A key that enables two or more records belonging to the same individual to be brought together.
Field name: | slk |
---|---|
Data type: | string (14,40) |
Required: | yes |
Notes: | System generated non-identifiable alphanumeric code derived from information held by the PMHC organisation.
SLK values are stored in sha1_hex format. |
METeOR: |
5.4.172. Suicide Referral Flag¶
Identifies those individuals where a recent history of suicide attempt, or suicide risk, was a factor noted in the referral that underpinned the person’s needs for assistance at intake or entry to the episode, as represented by a code.
Field name: | suicide_referral_flag |
||||||
---|---|---|---|---|---|---|---|
Data type: | string |
||||||
Required: | yes |
||||||
Domain: |
|
||||||
Notes: | Where there is a linked intake and treatment, both the Intake and Episode records must use the same suicide referral flag. |
5.4.173. Value¶
The metadata value.
Field name: | value |
---|---|
Data type: | string |
Required: | yes |
Notes: | Please refer to Metadata file for an example of the metadata file/worksheet that must be used with this specification. |
5.4.174. Venue¶
Where the service contact was delivered, as represented by a code.
Field name: | service_contact_venue |
||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type: | string |
||||||||||||||||||||||||||||
Required: | yes |
||||||||||||||||||||||||||||
Domain: |
|
||||||||||||||||||||||||||||
Notes: | Note that this data item concerns only where the service contact took place. It is not about where the client lives. Thus, if a resident of an aged care residential facility is seen at another venue (e.g., at a GP Clinic), then the Service Contact Venue should be recorded as ‘GP Practice’ (code 3) to accurately reflect where the contact took place. Values other than ‘98 - Not applicable’ only to be specified when Service Contact Modality is ‘Face to Face’.
All other data items would be recorded as per the guidelines that apply to those items – there are no special requirements specific to delivery of services to residents of aged care facilities. For example, any of the episode of care types recorded under the Principal Focus of Treatment Plan may apply; similarly, service contacts delivered to aged care residents may be any of the options available in Service Contact Type field. |
5.4.175. Year of Birth¶
The year the practitioner was born.
Field name: | practitioner_year_of_birth |
---|---|
Data type: | gYear |
Required: | yes |
Domain: | gYear |
Notes: |
|
5.5. Download Specification Files¶
Available for software developers designing extracts for the PMHC MDS, please click the link below to download the PMHC MDS Specification files:
These files conform to the CSV on the Web (CSVW) standard that is defined at https://csvw.org/.
They are used:
- to generate the Record formats and Definitions sections of the data specification documentation
- in the first pass of upload validations