Data Model and Specifications

TWB is an extension of the Primary Mental Health Care Minimum Data Set (PMHC MDS); the current PMHC MDS Data model and specification rules may apply. These are available to be viewed at https://docs.pmhc-mds.com/data-specification/index.html.

Data model

TWB & PMHC data model

Fig. 1 TWB data model within the PMHC MDS

Note: TWB Collection Occasion data model for more details about Collection Occasion records.

TWB Collection Occasion data model

Fig. 2 TWB Collection Occasion data model

Note: See TWB data model within the PMHC MDS for more details about how Collection Occasion records fit into the overall structure.

Record Formats

PMHC MDS Record formats

As TWB is an extension of the Primary Mental Health Care Minimum Data Set (PMHC MDS), the current PMHC MDS Data model and specification record formats are available to be viewed at https://docs.pmhc-mds.com/data-specification/data-model-and-specifications.html#record-formats.

The following data items have TWB business rules:

Episode

Episode - Additional Diagnosis

For TWB only episodes the response 000: No additional Diagnosis must be used.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range of Additional Diagnosis responses allowed for standard PMHC MDS episodes is available.

Episode - Medication - Antidepressants (N06A)

For TWB only episodes the response 9: Unknown must be used.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range Medication - Antidepressants (N06A) of responses allowed for standard PMHC MDS episodes is available.

Episode - Medication - Antipsychotics (N05A)

For TWB only episodes the response 9: Unknown must be used.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range Medication - Antipsychotics (N05A) of responses allowed for standard PMHC MDS episodes is available.

Episode - Medication - Anxiolytics (N05B)

For TWB only episodes the response 9: Unknown must be used.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range Medication - Anxiolytics (N05B) of responses allowed for standard PMHC MDS episodes is available.

Episode - Medication - Hypnotics and sedatives (N05C)

For TWB only episodes the response 9: Unknown must be used.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range Medication - Hypnotics and sedatives (N05C) of responses allowed for standard PMHC MDS episodes is available.

Episode - Medication - Psychostimulants and nootropics (N06B)

For TWB only episodes the response 9: Unknown must be used.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range of Medication - Psychostimulants and nootropics (N06B) responses allowed for standard PMHC MDS episodes is available.

Episode - Principal Focus of Treatment Plan

For TWB only episodes the following value must be used:

8 - Psychosocial support

Episodes of care should be classified as Psychosocial Support (code 8) where the treatment plan for the client is primarily based around the delivery of psychosocial support services. Psychosocial support services are defined for PMHC MDS purposes as services that focus on building capacity and stability in one or more of the following areas:

  • social skills and friendships, family connections;

  • managing daily living needs;

  • financial management and budgeting;

  • finding and maintaining a home;

  • vocational skills and goals, including volunteering;

  • educational and training goals;

  • maintaining physical wellbeing, including exercise;

  • building broader life skills including confidence and resilience.

These services are usually delivered by a range of non-clinical providers including peer support workers with lived experience of mental illness

Services delivered to clients receiving episodes of care classified as Psychosocial Support may receive the full range of services as described in the Service Contact Type data item, for example, assessment, care coordination and so forth. However, in general, where the Principal Focus of Treatment Plan is coded as Psychosocial Support there should be an expectation that the majority of services provided will be of a psychosocial support nature. Further details on the relationship between the episode of care concept and service contacts is available at https://docs.pmhc-mds.com/faqs/concepts-processes/data-definitions.html#episode-one-at-a-time

PHNs may wish to advise specific commissioned organisations solely funded from their Psychosocial Support Schedule that all episodes of care should be coded as Psychosocial Support, or leave it to the discretion of service providers.

Clients who are recorded as NDIS recipients would not usually be recorded as receiving a Psychosocial Support episode of care. The National Psychosocial Support guidance material states explicitly that these services are designed for individuals who have significant psychosocial disability but do not meet NDIS eligibility criteria.

Episodes of care delivered to individuals who are recorded as Continuity of Support clients (see below) may be reported as Psychosocial Support.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full range of Principal Focus of Treatment Plan responses allowed for standard PMHC MDS episodes is available. The 8: Psychosocial Support response has been removed from the Principal Focus of Treatment Plan in PMHC MDS Version 4.0 even though it is an allowed valued in the TWB extension for TWB only episodes.

TWB Record formats

The Way Back adds the following records on top of PMHC MDS current specifications:

When uploading PMHC clients at the same time as TWB clients, the following records will also need to be supplied. NB. These record specifications are different to the standard PMHC specifications. The TWB upload format separates collection occasion data into a separate Collection Occasion worksheet so that multiple measures can be collected at a single collection occasion. The TWB upload format aligns with a future PMHC MDS Version 3.0 file format. No date has been set for the release of the PMHC MDS Version 3.0 upload file format.

Metadata

The Metadata table must be included in file uploads in order to identify the type and version of the uploaded data.

Table 1 Metadata record layout

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

WAYBACK

version

3

Provider Organisation

Same as standard PMHC MDS Provider Organisation.

Practitioner

Same as standard PMHC MDS Practitioner.

Client

Same as standard PMHC MDS Client.

Episode

Same as standard PMHC MDS Episode.

TWB Episode

See Episode for definition of an episode.

TWB Episodes are managed by the provider organisations via upload or data entry.

Table 2 TWB Episode record layout

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 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.

TWB Episode - Veteran (twb_veteran)

string

yes
1:

Identifies as a veteran

2:

Does not identify as a veteran

9:

Not stated/Inadequately described

TWB Episode - Sexual Orientation (twb_sexual_orientation)

string

yes
1:

Straight or heterosexual

2:

Lesbian, gay or homosexual

3:

Bisexual or pansexual

4:

Asexual

5:

Questioning

6:

Other

9:

Not stated

TWB Episode - Transgender Status (twb_transgender_status)

string

yes
1:

Yes

2:

No

3:

Does not want to disclose

9:

Not stated / Unknown

TWB Episode - Intersex Status (twb_intersex_status)

string

yes
1:

Yes

2:

No

3:

Does not want to disclose

9:

Not stated / Unknown

TWB Episode - Eligibility Type (twb_eligibility_type)

string

yes
1:

Primary Criteria

2:

Secondary Criteria

98:

Other

99:

Not stated/Inadequately described

TWB Episode - External Evaluator Contact Consent (twb_external_evaluator_contact_consent)

string

yes
1:

Consented to be contacted by external evaluators

2:

Not consented to be contacted by external evaluators

9:

Not stated/Inadequately described

TWB Episode - Primary Nominated Professional (twb_primary_nominated_professional)

string

yes
1:

Aboriginal and Torres Strait Islander Health Practice

2:

Medical

3:

Nursing and Midwifery

4:

Occupational Therapy

5:

Psychology

6:

Mental Health Social Worker

98:

Other

99:

No one nominated

TWB Episode - Primary Nominated Professional Consent Date (twb_primary_nominated_professional_consent_date)

date

yes

The date that the client consented to having their Primary Nominated Professional contacted.

TWB Episode - Primary Nominated Professional Contact Entry Date (twb_primary_nominated_professional_contact_entry_date)

date

yes

The date that the client’s Primary Nominated Professional was contacted after entry.

TWB Episode - Primary Nominated Professional Contact Exit Date (twb_primary_nominated_professional_contact_exit_date)

date

yes

The date that the client’s Primary Nominated Professional was contacted after client’s exit.

TWB Episode - Previous suicide attempts (twb_previous_suicide_attempts)

string

yes
1:

No

2:

Previous attempt(s) made in the past 12 months

3:

Previous attempt(s) made prior to the last 12 months

4:

Previous attempts made both within and prior to the last 12 months

7:

Not known

9:

Not stated/Inadequately described

TWB Episode - Method of suicide attempt (twb_method_of_suicide_attempt)

string

yes
1:

Intentional self-poisoning

2:

Intentional self-harm by hanging, strangulation and suffocation

3:

Intentional self-harm by drowning and submersion

4:

Intentional self-harm by sharp object

5:

Intentional self-harm by Firearm

6:

Intentional self-harm by jumping from a high place

98:

Other

99:

Not stated/Inadequately described

TWB-Critical Incident

Critical Incidents are managed by the provider organisations via upload or data entry.

Table 3 Critical Incident record layout

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.

TWB Critical Incident Key (twb_critical_incident_key)

string (2,50)

yes

This is a number or code assigned to each critical incident. The Critical Incident Key is unique and stable for each Critical Incident 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.

TWB Critical Incident - Type (twb_critical_incident_type)

string

yes
1:

Suicide attempt of an active client

2:

Suicide death of an active client

3:

Death by other cause of an active client

9:

Not stated/Inadequately described

TWB Critical Incident - Date (twb_critical_incident_date)

date

yes

The date the critical incident was reported to the Service Provider.

TWB-Recommendation Out

Recommendation Outs are managed by the provider organisations via upload or data entry.

Table 4 Recommendation Out record layout

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.

TWB Recommendation Out Key (twb_recommendation_out_key)

string (2,50)

yes

This is a number or code assigned to each recommendation out. The Recommendation Out Key is unique and stable for each recommendation out at the lvel 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.

TWB Recommendation Out - Provider Type (twb_recommendation_out_provider_type)

string

yes
1:

GP/Medical Practitioner

2:

Hospital

3:

Psychiatric/mental health service or facility

4:

Alcohol and other drug treatment service

5:

Other community/health care service

6:

Correctional service

7:

Police diversion

8:

Court diversion

9:

Legal service

10:

Child protection agency

11:

Community support groups/agencies

12:

Centrelink or employment service

13:

Housing and homelessness service

14:

Telephone & online services/referral agency e.g. direct line

15:

Disability support service

16:

Aged care facility/service

17:

Immigration department or asylum seeker/refugee support service

18:

School/other education or training institution

19:

Community based Drug and Alcohol Service

20:

Youth service (non-AOD)

21:

Indigenous service (non-AOD)

22:

Extended care/rehabilitation facility

23:

Palliative care service

24:

Police (not diversion)

25:

Public dental provider - community dental agency

26:

Dental Hospital

27:

Private Dental Provider

28:

Early childhood service

29:

Maternal and Child Health Service

30:

Community nursing service

31:

Emergency relief

32:

Family support service (excl family violence)

33:

Family violence service

34:

Gambling support service

35:

Maternity services

36:

Peer support/self-help group

37:

Private allied health provider

38:

Sexual Assault service

39:

Financial counsellor

40:

Sexual health service

41:

Medical specialist

97:

No Recommendation

98:

Other

99:

Not stated/Inadequately described

TWB Recommendation Out - Status (twb_recommendation_out_status)

string

yes
1:

Client declined to take up recommendation

2:

Service commenced

3:

Service completed

4:

Waitlisted

5:

Client deceased prior to service commencement

98:

Other

99:

Not stated/Inadequately described

Service Contact

See Service Contact for definition of a service-contact.

Service Contacts are managed by the provider organisations via upload or data entry.

TWB adds an extra field Service Contact - Funding Source to the standard PMHC Service Contact.

Table 5 Service Contact record layout

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 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.

Practitioner Key (practitioner_key)

string (2,50)

yes

A unique identifier for a practitioner within the provider 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
0:

No contact took place

1:

Assessment

2:

Structured psychological intervention

3:

Other psychological intervention

4:

Clinical care coordination/liaison

5:

Clinical nursing services

6:

Child or youth specific assistance NEC

7:

Suicide prevention specific assistance NEC

8:

Cultural specific assistance NEC

9:

Psychosocial support

Service Contact - Postcode (service_contact_postcode)

METeOR: 429894

string

yes

The Australian postcode where the service contact took place.

Service Contact - Modality (service_contact_modality)

string

yes
0:

No contact took place

1:

Face to Face

2:

Telephone

3:

Video

4:

Internet-based

Service Contact - Participants (service_contact_participants)

string

yes
1:

Individual client

2:

Client group

3:

Family / Client Support Network

4:

Other health professional or service provider

5:

Other

9:

Not stated

Service Contact - Venue (service_contact_venue)

string

yes
1:

Client’s Home

2:

Service provider’s office

3:

GP Practice

4:

Other medical practice

5:

Headspace Centre

6:

Other primary care setting

7:

Public or private hospital

8:

Residential aged care facility

9:

School or other educational centre

10:

Client’s Workplace

11:

Other

12:

Aged care centre - non-residential

98:

Not applicable (Service Contact Modality is not face to face)

99:

Not stated

Service Contact - Duration (service_contact_duration)

string

yes
0:

No contact took place

1:

1-15 mins

2:

16-30 mins

3:

31-45 mins

4:

46-60 mins

5:

61-75 mins

6:

76-90 mins

7:

91-105 mins

8:

106-120 mins

9:

over 120 mins

Service Contact - Copayment (service_contact_copayment)

number

yes

0 - 999999.99

Service Contact - Client Participation Indicator (service_contact_participation_indicator)

METeOR: 494341

string

yes
1:

Yes

2:

No

Service Contact - Interpreter Used (service_contact_interpreter)

string

yes
1:

Yes

2:

No

9:

Not stated

Service Contact - No Show (service_contact_no_show)

string

yes
1:

Yes

2:

No

Service Contact - Final (service_contact_final)

string

yes
1:

No further services are planned for the client in the current episode

2:

Further services are planned for the client in the current episode

3:

Not known at this stage

Service Contact - Funding Source (funding_source)

string

yes
0:

PHN funded

7:

TWB

Service Contact - Tags (service_contact_tags)

string

—

List of tags for the service contact.

Collection Occasion

See Collection Occasion for definition of a collection occasion.

Collection occasions are managed by the provider organisations via upload or data entry.

Table 6 Collection Occasions record layout

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
1:

Episode start

2:

Review

3:

Episode end

Collection Occasion - Tags (collection_occasion_tags)

string

—

List of tags for the collection occasion.

TWB Plan

Table 7 TWB Plan record layout

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.

TWB Plan Key (twb_plan_key)

string (2,50)

yes

This is a number or code assigned to each instance of a TWB Plan. The TWB Plan 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.

TWB Plan - Plan Type (twb_plan_type)

string

yes
1:

Safety

2:

Support

TWB Plan - Tags (twb_plan_tags)

string

—

List of tags for the collection occasion.

TWB NI

Table 8 TWB NI record layout

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.

TWB NI Key (twb_ni_key)

string (2,50)

yes

This is a number or code assigned to each instance of a TWB NI. The TWB NI Key is unique and stable for each instance of a TWB NI 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.

TWB NI - Type (twb_ni_type)

string

yes
1:

Health (Physical)

2:

Self-esteem

3:

Mental Health Condition

4:

Home

5:

Education/Employment

6:

Sexual/Physical/Emotional Abuse

7:

Marital/De facto Relationship

8:

Financial Problems

9:

Sexual Identity/Orientation

10:

Sense of Self

11:

Loss of Hope

12:

Drugs/Alcohol

13:

Family History Mental Health Problems

14:

Family History Suicide /Attempt

15:

Other knowledge of suicide

16:

Grief and Loss

17:

Social support/sense of belonging

18:

Coping/problem solving ability

19:

Cultural identity

20:

Child rearing or care taking responsibilities

21:

Help-seeking behaviour

22:

Religion

23:

Self Care

24:

Daily Structure

98:

Other

99:

Not stated/Inadequately described

Multiple space separated values allowed

TWB NI - Tags (twb_ni_tags)

string

—

List of tags for the collection occasion.

K10+ Measure

For TWB, either the K10+ needs to be supplied or in the case of Aboriginal and Torres Strait Islander clients the K5 can be supplied instead.

Please note: The format for reporting the K10+ in TWB uploads is different than for standard PMHC MDS as explained at Files or worksheets to upload.

Table 9 K10+ record layout

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
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 2 (k10p_item2)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 3 (k10p_item3)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 4 (k10p_item4)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 5 (k10p_item5)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 6 (k10p_item6)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 7 (k10p_item7)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 8 (k10p_item8)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 9 (k10p_item9)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Question 10 (k10p_item10)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

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
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K10+ - Score (k10p_score)

integer

yes

10 - 50, 99 = Not stated / Missing

K10+ - Tags (k10p_tags)

string

—

List of tags for the collection occasion.

K5 Measure

For TWB, either the K10+ needs to be supplied or in the case of Aboriginal and Torres Strait Islander clients the K5 can be supplied instead.

Please note: The format for reporting the K5 in TWB uploads is different than for standard PMHC MDS as explained at Files or worksheets to upload.

Table 10 K5 record layout

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
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K5 - Question 2 (k5_item2)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K5 - Question 3 (k5_item3)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K5 - Question 4 (k5_item4)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K5 - Question 5 (k5_item5)

string

yes
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

K5 - Score (k5_score)

integer

yes

5 - 25, 99 = Not stated / Missing

K5 - Tags (k5_tags)

string

—

List of tags for the collection occasion.

SDQ Measure

For TWB only episodes the SDQ is not required.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider an SDQ may be collected.

Please note: The format for reporting the SDQ in TWB uploads is different than for standard PMHC MDS as explained at Files or worksheets to upload.

Table 11 SDQ record layout

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
PC101:

Parent Report Measure 4-10 yrs, Baseline version, Australian Version 1

PC201:

Parent Report Measure 4-10 yrs, Follow Up version, Australian Version 1

PY101:

Parent Report Measure 11-17 yrs, Baseline version, Australian Version 1

PY201:

Parent Report Measure 11-17 yrs, Follow Up version, Australian Version 1

YR101:

Self report Version, 11-17 years, Baseline version, Australian Version 1

YR201:

Self report Version, 11-17 years, Follow Up version, Australian Version 1

SDQ - Question 1 (sdq_item1)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 2 (sdq_item2)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 3 (sdq_item3)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 4 (sdq_item4)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 5 (sdq_item5)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 6 (sdq_item6)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 7 (sdq_item7)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 8 (sdq_item8)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 9 (sdq_item9)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 10 (sdq_item10)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 11 (sdq_item11)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 12 (sdq_item12)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 13 (sdq_item13)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 14 (sdq_item14)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 15 (sdq_item15)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 16 (sdq_item16)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 17 (sdq_item17)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 18 (sdq_item18)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 19 (sdq_item19)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 20 (sdq_item20)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 21 (sdq_item21)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 22 (sdq_item22)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 23 (sdq_item23)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 24 (sdq_item24)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 25 (sdq_item25)

string

yes
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 26 (sdq_item26)

string

yes
0:

No

1:

Yes - minor difficulties

2:

Yes - definite difficulties

3:

Yes - severe difficulties

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

SDQ - Question 27 (sdq_item27)

string

yes
0:

Less than a month

1:

1-5 months

2:

6-12 months

3:

Over a year

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 28 (sdq_item28)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 29 (sdq_item29)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 30 (sdq_item30)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 31 (sdq_item31)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 32 (sdq_item32)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 33 (sdq_item33)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 34 (sdq_item34)

string

yes
0:

Much worse

1:

A bit worse

2:

About the same

3:

A bit better

4:

Much better

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 35 (sdq_item35)

string

yes
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 36 (sdq_item36)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 37 (sdq_item37)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 38 (sdq_item38)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 39 (sdq_item39)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 40 (sdq_item40)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 41 (sdq_item41)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

SDQ - Question 42 (sdq_item42)

string

yes
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

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 collection occasion.

WHO-5 Measure

Table 12 WHO-5 record layout

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.

WHO-5 - Question 1 (who5_item1)

string

yes
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

WHO-5 - Question 2 (who5_item2)

string

yes
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

WHO-5 - Question 3 (who5_item3)

string

yes
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

WHO-5 - Question 4 (who5_item4)

string

yes
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

WHO-5 - Question 5 (who5_item5)

string

yes
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

WHO-5 - Tags (who5_tags)

string

—

List of tags for the collection occasion.

SIDAS Measure

Scoring the SIDAS

Total SIDAS scores are calculated as the sum of the five items, with controllability (item 2) reverse scored (10=0, 9=1, …, 0=10). Total scores range from 0 to 50.

Respondents who respond “0 – Never” to the first item skip all remaining items and score a total of zero. Refer to SIDAS Current Validations for information about how this is enforced in the PMHC MDS.

If any item has not been completed, other than those who respond “0 – Never” to the first item (that is, has not been coded 0-10), 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.

Table 13 SIDAS record layout

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.

SIDAS - Question 1 (sidas_item1)

string

yes

0 - 10, 99 = Not stated / Missing

SIDAS - Question 2 (sidas_item2)

string

yes

0 - 10, 98 = Not required, 99 = Not stated / Missing

SIDAS - Question 3 (sidas_item3)

string

yes

0 - 10, 98 = Not required, 99 = Not stated / Missing

SIDAS - Question 4 (sidas_item4)

string

yes

0 - 10, 98 = Not required, 99 = Not stated / Missing

SIDAS - Question 5 (sidas_item5)

string

yes

0 - 10, 98 = Not required, 99 = Not stated / Missing

SIDAS - Tags (sidas_tags)

string

—

List of tags for the collection occasion.

TWB Definitions

Definitions

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.

See Collection Occasion Current Validations for validation rules.

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:
1:

Episode start

2:

Review

3:

Episode end

Notes:

At a minimum, collection of outcome measures and plans are required at the Episode Start, Review and End.

TWB will allow the following data records to be collected at a collection occasion:

  • Safety Plan

  • Support Plan

  • Needs Identification

  • Outcome Measures (K10, WHO-5, SIDAS )

1 - Episode start

Refers to a service activity undertaken at the beginning of an Episode of Care. For the purposes of the PMHC MDS protocol, episodes may start at the point of first Service Contact with a new client who has not been seen previously by the organisation, or a first contact for a new Episode of Care for a client who has received services from the organisation in a previous Episode of Care that has been completed.

2 - Review

Refers to a service activity undertaken during the course of an Episode of Care that post-dates Episode Start and pre-dates Episode End. A service activity may be undertaken at Review for a number of reasons including:

  • in response to critical clinical events or changes in the client’s mental health status;

  • following a client-requested review; or

  • other situations where a review may be indicated.

3 - Episode end

Refers to the service activities collected at the end of an Episode of Care.

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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

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:

See Identifier Management

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.

A recommended approach for the creation of Episode Keys is to compute random UUIDs.

See Identifier Management and Managing Practitioner, Episode and Service Contact Keys

Key

A metadata key name.

Field name:

key

Data type:

string

Required:

yes

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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’

K5 - Tags

List of tags for the collection occasion.

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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

K10+ - Question 4

In the past 4 weeks, how often did you feel hopeless?

Field name:

k10p_item4

Data type:

string

Required:

yes

Domain:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

K10+ - Question 7

In the past 4 weeks, how often did you feel depressed?

Field name:

k10p_item7

Data type:

string

Required:

yes

Domain:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

K10+ - Question 10

In the past 4 weeks, how often did you feel worthless?

Field name:

k10p_item10

Data type:

string

Required:

yes

Domain:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

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.

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.

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.

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:
1:

None of the time

2:

A little of the time

3:

Some of the time

4:

Most of the time

5:

All of the time

9:

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.

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 with the proviso that a competed K10 with more than one missing item is regarded as invalid.

If more than one item of items 1 to 10 are missing, the Total Score is set as missing. Where this is the case, the missing value used should be 99.

When reporting individual item scores use ‘99 - Not stated / Missing’.

K10+ - Tags

List of tags for the collection occasion.

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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

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:

See Identifier Management

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:

Organisation Key

Organisation Name

Organisation Type

Commissioning Organisation

Organisation Path

PHN999

Test PHN

Primary Health Network

None

PHN999

PO101

Test Provider Organisation

Private Allied Health Professional Practice

PHN999

PHN999:PO101

Practitioner Key

A unique identifier for a practitioner within the provider organisation.

Field name:

practitioner_key

Data type:

string (2,50)

Required:

yes

SDQ Collection Occasion - Version

The version of the SDQ collected.

Field name:

sdq_version

Data type:

string

Required:

yes

Domain:
PC101:

Parent Report Measure 4-10 yrs, Baseline version, Australian Version 1

PC201:

Parent Report Measure 4-10 yrs, Follow Up version, Australian Version 1

PY101:

Parent Report Measure 11-17 yrs, Baseline version, Australian Version 1

PY201:

Parent Report Measure 11-17 yrs, Follow Up version, Australian Version 1

YR101:

Self report Version, 11-17 years, Baseline version, Australian Version 1

YR201:

Self report Version, 11-17 years, Follow Up version, Australian Version 1

Notes:

Domain values align with those collected in the NOCC dataset as defined at https://webval.validator.com.au/spec/NOCC/current/SDQ/SDQVer

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’.

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’.

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’.

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’.

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’.

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’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not True

1:

Somewhat True

2:

Certainly True

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

No

1:

Yes - minor difficulties

2:

Yes - definite difficulties

3:

Yes - severe difficulties

7:

Unable to rate (insufficient information)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Less than a month

1:

1-5 months

2:

6-12 months

3:

Over a year

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: - PC101 - PY101 - YR101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions: All

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Much worse

1:

A bit worse

2:

About the same

3:

A bit better

4:

Much better

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • PC201

  • PY201

  • YR201

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

Not at all

1:

A little

2:

A medium amount

3:

A great deal

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • PC201

  • PY201

  • YR201

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • PC101

  • PY101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • PC101

  • PY101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • PC101

  • PY101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • YR101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

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:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • YR101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

SDQ - Question 41

Does your family complain about you being awkward or troublesome?

Field name:

sdq_item41

Data type:

string

Required:

yes

Domain:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • YR101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

SDQ - Question 42

Do your teachers complain about you being awkward or troublesome?

Field name:

sdq_item42

Data type:

string

Required:

yes

Domain:
0:

No

1:

A little

2:

A lot

7:

Unable to rate (insufficient information)

8:

Not applicable (collection not required - item not included in the version collected, or SDQ Item 26 = 0)

9:

Not stated / Missing

Notes:

Required Versions:

  • YR101

When reporting subscale and total scores use ‘9 - Not stated / Missing’.

SDQ - Tags

List of tags for the collection occasion.

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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

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’.

Service Contact - 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:
1:

Yes

2:

No

Notes:

Service contacts are not restricted to in-person communication but can include telephone, video link or other forms of direct communication.

1 - Yes

This code is to be used for service contacts between a mental health service provider and the patient/client in whose clinical record the service contact would normally warrant a dated entry, where the patient/client is participating.

2 - No

This code is to be used for service contacts between a mental health service provider and a third party(ies) where the patient/client, in whose clinical record the service contact would normally warrant a dated entry, is not participating.

Note: Where a client intended to participate in a service contact but failed to attend, Service Contact - Client Participation Indicator should be recorded as ‘1: Yes’ and Service Contact - No Show should be recorded as ‘1: Yes’.

METeOR:

494341

Service Contact - 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.

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.

  • The service contact date must not be before 1st January 2014.

  • The service contact date must not be in the future.

METeOR:

494356

Service Contact - Duration

The time from the start to finish of a service contact.

Field name:

service_contact_duration

Data type:

string

Required:

yes

Domain:
0:

No contact took place

1:

1-15 mins

2:

16-30 mins

3:

31-45 mins

4:

46-60 mins

5:

61-75 mins

6:

76-90 mins

7:

91-105 mins

8:

106-120 mins

9:

over 120 mins

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.

0 - No contact took place

Only use this code where the service contact is recorded as a no show.

Service Contact - Final

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:
1:

No further services are planned for the client in the current episode

2:

Further services are planned for the client in the current episode

3:

Not known at this stage

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:

  • the date of the final Service Contact should be recorded as the Episode End Date

  • the Episode Completion Status field should be recorded as ‘Treatment concluded.

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.

Service Contact - Funding Source

The source of funding for a service contact

Field name:

funding_source

Data type:

string

Required:

yes

Domain:
0:

PHN funded

7:

TWB

Notes:

A client may be receiving care from both The Way Back and another service in the same episode. For all Service Contacts provided under The Way Back please select “TWB” for all other types of service please select “PHN Funded”.

Service Contact - Interpreter Used

Whether an interpreter service was used during the Service Contact

Field name:

service_contact_interpreter

Data type:

string

Required:

yes

Domain:
1:

Yes

2:

No

9:

Not stated

Notes:

Interpreter services includes verbal language, non-verbal language and languages other than English.

1 - Yes

Use this code where interpreter services were used during the Service Contact. Use of interpreter services for any form of sign language or other forms of non-verbal communication should be coded as Yes.

2 - No

Use this code where interpreter services were not used during the Service Contact.

9 - Not stated

Indicates that the item was not collected. This item should not appear as an option for clinicians, it is for administrative use only.

Service Contact - Modality

How the service contact was delivered, as represented by a code.

Field name:

service_contact_modality

Data type:

string

Required:

yes

Domain:
0:

No contact took place

1:

Face to Face

2:

Telephone

3:

Video

4:

Internet-based

Notes:
0 - No contact took place

Only use this code where the service contact is recorded as a no show.

1 - Face to Face

  • If ‘Face to Face’ is selected, a value other than ‘Not applicable’ must be selected for Service Contact Venue

  • If ‘Face to Face’ is selected a valid Australian postcode must be entered for Service Contact Postcode. The unknown postcode is not valid.

4 - Internet-based

Includes email communication, that would normally warrant a dated entry in the clinical record of the client, involving a third party, such as a carer or family member, and/or other professional or mental health worker, or other service provider.

Note: If Service Contact Modality is not ‘Face to Face’ the postcode must be entered as unknown 9999.

Service Contact - 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:
1:

Yes

2:

No

Notes:
1 - Yes

The intended participant(s) failed to attend the appointment.

2 - No

The intended participant(s) attended the appointment.

Service Contact - Participants

An indication of who participated in the Service Contact.

Field name:

service_contact_participants

Data type:

string

Required:

yes

Domain:
1:

Individual client

2:

Client group

3:

Family / Client Support Network

4:

Other health professional or service provider

5:

Other

9:

Not stated

Notes:
1 - Individual

Code applies for Service Contacts delivered individually to a single client without third party participants. Please refer to the Note below.

2 - Client group

Code applies for Service Contacts delivered on a group basis to two or more clients.

3 - Family / Client Support Network

Code applies to Service Contacts delivered to the family/social support persons of the client, with or without the participation of the client.

4 - Other health professional or service provider

Code applies for Service Contacts that involve another health professional or service provider (in addition to the Practitioner), with or without the participation of the client.

5 - Other

Code applies to Service Contacts delivered to other third parties (e.g., teachers, employer), with or without the participation of the client.

Note: This item interacts with Service Contact - Client Participation Indicator. Where Service Contact - Participants has a value of ‘1: Individual’, Service Contact - Client Participation Indicator must have a value of ‘1: Yes’. Service Contact - No Show is used to record if the patient failed to attend the appointment.

Service Contact - 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.

  • If Service Contact Modality is not ‘Face to Face’ enter 9999

  • If Service Contact Modality is ‘Face to Face’ a valid Australian postcode must be entered

  • As of 1 November 2016, PMHC MDS currently validates that postcodes are in the range 0200-0299 or 0800-9999.

METeOR:

429894

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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

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:
0:

No contact took place

1:

Assessment

2:

Structured psychological intervention

3:

Other psychological intervention

4:

Clinical care coordination/liaison

5:

Clinical nursing services

6:

Child or youth specific assistance NEC

7:

Suicide prevention specific assistance NEC

8:

Cultural specific assistance NEC

9:

Psychosocial support

Notes:

Describes the main type of service delivered in the contact, selected from a defined list of categories. Service providers are required to report on Service Type for all Service Contacts.

For TWB only service contacts one of the following values must be used:

0 - No contact took place

Only use this code where the service contact is recorded as a no show.

9 - Psychosocial Support

Where the client attends, this code must be used for Way Back services.

Where a client is being delivered TWB services and accessing another support service within the same Service Provider the full ranges of responses allowed for standard PMHC MDS service contacts is available.

Service Contact - Venue

Where the service contact was delivered, as represented by a code.

Field name:

service_contact_venue

Data type:

string

Required:

yes

Domain:
1:

Client’s Home

2:

Service provider’s office

3:

GP Practice

4:

Other medical practice

5:

Headspace Centre

6:

Other primary care setting

7:

Public or private hospital

8:

Residential aged care facility

9:

School or other educational centre

10:

Client’s Workplace

11:

Other

12:

Aged care centre - non-residential

98:

Not applicable (Service Contact Modality is not face to face)

99:

Not stated

Notes:

Values other than ‘Not applicable’ only to be specified when Service Contact Modality is ‘Face to Face’.

Note that ‘Other primary care setting’ is suitable for primary care settings such as community health centres.

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 organisation.

Field name:

service_contact_key

Data type:

string (2,50)

Required:

yes

Notes:

See Identifier Management and Managing Practitioner, Episode and Service Contact Keys

SIDAS - Question 1

In the past month, how often have you had thoughts about suicide?

Field name:

sidas_item1

Data type:

string

Required:

yes

Domain:

0 - 10, 99 = Not stated / Missing

Notes:

0 = Never, 10 = Always

Respondents who respond “0 – Never” to the first item skip all remaining items and score a total of zero. Refer to SIDAS Current Validations for information about how this is enforced in the PMHC MDS.

SIDAS - Question 2

In the past month, how much control have you had over these thoughts?

Field name:

sidas_item2

Data type:

string

Required:

yes

Domain:

0 - 10, 98 = Not required, 99 = Not stated / Missing

Notes:

0 = No control, 10 = Full control

Controllability is reversed scored (10=0, 9=1, …, 0=10), however responses must not be reversed before entering data into the PMHC MDS. The PMHC MDS will reverse this item when calculating the total score.

SIDAS - Question 3

In the past month, how close have you come to making an attempt?

Field name:

sidas_item3

Data type:

string

Required:

yes

Domain:

0 - 10, 98 = Not required, 99 = Not stated / Missing

Notes:

0 = Not close at all, 10 = Made an attempt

SIDAS - Question 4

In the past month, to what extent have you felt tormented by thoughts about suicide?

Field name:

sidas_item4

Data type:

string

Required:

yes

Domain:

0 - 10, 98 = Not required, 99 = Not stated / Missing

Notes:

0 = Not at all, 10 = Extremely

SIDAS - Question 5

In the past month, how much have thoughts about suicide interfered with your ability to carry out daily activities, such as work, household tasks or social activities?

Field name:

sidas_item5

Data type:

string

Required:

yes

Domain:

0 - 10, 98 = Not required, 99 = Not stated / Missing

Notes:

0 = Not at all, 10 = Extremely

SIDAS - Tags

List of tags for the collection occasion.

Field name:

sidas_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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

TWB Critical Incident - Date

The date the critical incident was reported to the Service Provider.

Field name:

twb_critical_incident_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.

Requires services to record the date of when a critical incident was reported.

If the reported date of the critical incident is unknown, 09099999 should be used.

  • The critical incident date must not be before 1st January 2019.

  • The critical incident date must not be in the future.

TWB Critical Incident - Type

The type of critical incident.

Field name:

twb_critical_incident_type

Data type:

string

Required:

yes

Domain:
1:

Suicide attempt of an active client

2:

Suicide death of an active client

3:

Death by other cause of an active client

9:

Not stated/Inadequately described

Notes:

Reporting requirements Mandatory where a critical incident is reported.

Guide for use It is acknowledged that due to the nature of the project and the reporting of suicide, Beyond Blue and stakeholders may not be advised of all critical incidents. It is also acknowledged that each Service Provider will have the appropriate management strategies in place for handling Critical Incidents.

TWB Critical Incident Key

This is a number or code assigned to each critical incident. The Critical Incident Key is unique and stable for each Critical Incident at the level of the organisation.

Field name:

twb_critical_incident_key

Data type:

string (2,50)

Required:

yes

Notes:

See Identifier Management

TWB Episode - Eligibility Type

The criteria by which a client is assessed as being eligible for the Way Back Support service, as represented by a code.

Field name:

twb_eligibility_type

Data type:

string

Required:

yes

Domain:
1:

Primary Criteria

2:

Secondary Criteria

98:

Other

99:

Not stated/Inadequately described

Notes:
1 - Primary Eligibility Criteria

The primary eligibility criteria are met when a person is referred to The Way Back after presenting to a hospital emergency department or community mental health service following a suicide attempt. A suicide attempt is defined as a “non-fatal self-directed potentially injurious behaviour with any intent to die as a result of the behaviour”. A suicide attempt may or may not result in physical injury and may or may not result in a hospital admission.

2 - Secondary Eligibility Criteria

The secondary eligibility criteria are met when a person is referred to The Way Back after presenting to a hospital emergency department or community mental health service in or following a suicidal crisis and whose risk of suicide is identified as imminent. A suicidal crisis is defined as a person experiencing distress, suicidal thoughts and articulating an intent to die. A suicidal crisis may or may not result in a hospital admission.

TWB Episode - Intersex Status

An indication of whether the client has an intersex status, as represented by a code.

Field name:

twb_intersex_status

Data type:

string

Required:

yes

Domain:
1:

Yes

2:

No

3:

Does not want to disclose

9:

Not stated / Unknown

Notes:

Guide for use The term intersex is used to describe people who are born with sex characteristics, including genitals, gonads and chromosome patterns, that do not fit typical binary notions of male and female bodies

TWB Episode - Method of suicide attempt

Identifies the method of the most recent suicide attempt, as represented by a code.

Field name:

twb_method_of_suicide_attempt

Data type:

string

Required:

yes

Domain:
1:

Intentional self-poisoning

2:

Intentional self-harm by hanging, strangulation and suffocation

3:

Intentional self-harm by drowning and submersion

4:

Intentional self-harm by sharp object

5:

Intentional self-harm by Firearm

6:

Intentional self-harm by jumping from a high place

98:

Other

99:

Not stated/Inadequately described

TWB Episode - Previous suicide attempts

Indicates whether the client has attempted suicide prior to this episode, as represented by a code.

Field name:

twb_previous_suicide_attempts

Data type:

string

Required:

yes

Domain:
1:

No

2:

Previous attempt(s) made in the past 12 months

3:

Previous attempt(s) made prior to the last 12 months

4:

Previous attempts made both within and prior to the last 12 months

7:

Not known

9:

Not stated/Inadequately described

Notes:

A suicide attempt is described as a non-fatal, self-directed, potentially injurious behaviour with an intent to die as a result of the behaviour; might not result in injury.

TWB Episode - Primary Nominated Professional

Identifies the profession of the primary professional nominated by the client, as represented by a code.

Field name:

twb_primary_nominated_professional

Data type:

string

Required:

yes

Domain:
1:

Aboriginal and Torres Strait Islander Health Practice

2:

Medical

3:

Nursing and Midwifery

4:

Occupational Therapy

5:

Psychology

6:

Mental Health Social Worker

98:

Other

99:

No one nominated

Notes:

The primary nominated professional of the client is the professional or support worker that the client consents to be advised of their participation in The Way Back Support Service.

If a client does not wish for anyone to be advised then code 99 indicates no consent in conjunction with 09099999 for TWB Episode - Primary Nominated Professional Consent Date indicates no consent.

TWB Episode - Primary Nominated Professional Contact Entry Date

The date that the client’s Primary Nominated Professional was contacted after entry.

Field name:

twb_primary_nominated_professional_contact_entry_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 a client does not wish for anyone to be advised please use the date 09099999.

  • The entry date must not be before 1st January 2019.

  • The entry date must not be in the future.

Written advice (email or letter) advising of the client’s participation in The Way Back Support Service must be sent to the primary nominated professional on commencement of the service. The Contact Entry Date is the date the service provider initiates the communication with the primary nominated professional, the date the email or letter is sent. There is a KPI requirement for this to take place within 3 business days of client consent.

TWB Episode - Primary Nominated Professional Contact Exit Date

The date that the client’s Primary Nominated Professional was contacted after client’s exit.

Field name:

twb_primary_nominated_professional_contact_exit_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 a client does not wish for anyone to be advised please use the date 09099999.

  • The exit date must not be before 1st January 2019.

  • The exit date must not be in the future.

  • The exit date must not be before the entry date.

Written advice (email or letter) advising of the client’s exit from The Way Back Support Service must be sent to the primary nominated professional on exit of the service. The Contact Exit Date is the date the service provider sends this information to the primary nominated professional, the date the email or letter is sent. There is a KPI requirement that this occurs within 3 business days of client exit.

TWB Episode - Sexual Orientation

Identifies how the client describes their sexual orientation, as represented by a code.

Field name:

twb_sexual_orientation

Data type:

string

Required:

yes

Domain:
1:

Straight or heterosexual

2:

Lesbian, gay or homosexual

3:

Bisexual or pansexual

4:

Asexual

5:

Questioning

6:

Other

9:

Not stated

Notes:

Sexual orientation encompasses several dimensions of sexuality including sexual identity, attraction and behavior, and refers to a person’s emotional, physical and/or sexual attraction to another person.

Definitions of terms

Lesbian

The term lesbian is used to describe a person identifying as a woman who is romantically and/or sexually attracted to other women.

Gay

The term gay is used to describe a person identifying as a man who is romantically and/or sexually attracted to other men.

Bisexual

The term bisexual is used to describe a person of any gender who is romantically and/or sexually attracted to people or more than one gender. Some people who fit this description prefer the terms ‘queer’ or Pansexual, in recognition of more than two genders. It may also be defined as romantic or sexual attraction to people of any sex or gender identity, which is also known as pansexuality.

Asexual

Asexual is a sexual orientation defined by a lack of sexual attraction to any person of any gender.

Questioning

Is a process of exploration by people who may be unsure, still exploring, and concerned about applying a social label to themselves for various reasons.

More information on collecting LGBTI inclusive data collection can be found at: https://meridianact.org.au/wp-content/uploads/LGBTIQ-Inclusive-Data-Collection-a-Guide.pdf

TWB Episode - Transgender Status

An indication of whether the client has a transgender history, experience or identity , as represented by a code.

Field name:

twb_transgender_status

Data type:

string

Required:

yes

Domain:
1:

Yes

2:

No

3:

Does not want to disclose

9:

Not stated / Unknown

Notes:

The term transgender is used to describe people whose gender identity does not align with the sex they were assigned at birth.

Non-binary genders also fit under this umbrella term, as well as under the term gender diverse.

TWB Episode - Veteran

An indication of whether the client identifies as a veteran, as represented by a code.

Field name:

twb_veteran

Data type:

string

Required:

yes

Domain:
1:

Identifies as a veteran

2:

Does not identify as a veteran

9:

Not stated/Inadequately described

TWB NI - Tags

List of tags for the collection occasion.

Field name:

twb_ni_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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

TWB NI - Type

The identified needs of the client at commencement or review of the service.

Field name:

twb_ni_type

Data type:

string

Required:

yes

Domain:
1:

Health (Physical)

2:

Self-esteem

3:

Mental Health Condition

4:

Home

5:

Education/Employment

6:

Sexual/Physical/Emotional Abuse

7:

Marital/De facto Relationship

8:

Financial Problems

9:

Sexual Identity/Orientation

10:

Sense of Self

11:

Loss of Hope

12:

Drugs/Alcohol

13:

Family History Mental Health Problems

14:

Family History Suicide /Attempt

15:

Other knowledge of suicide

16:

Grief and Loss

17:

Social support/sense of belonging

18:

Coping/problem solving ability

19:

Cultural identity

20:

Child rearing or care taking responsibilities

21:

Help-seeking behaviour

22:

Religion

23:

Self Care

24:

Daily Structure

98:

Other

99:

Not stated/Inadequately described

Multiple space separated values allowed

Notes:

Reporting requirements The Needs Identification (NI) is a screening process where the psychosocial needs of a client are identified. It provides the basis for the creation of a Support Plan and is considered a useful way to help understand client support needs and service goals. The needs identified through this process should inform the client’s goals and recommendations to community-based services.

The NI must be administered at a minimum at the following points of service participation:

  • At the start of The Way Back

  • At the six-week or mid-point of the expected support period

  • At exit from the service

TWB NI Key

This is a number or code assigned to each instance of a TWB NI. The TWB NI Key is unique and stable for each instance of a TWB NI at the level of the organisation.

Field name:

twb_ni_key

Data type:

string (2,50)

Required:

yes

Notes:

See Identifier Management

TWB Plan - Plan Type

The type of plan.

Field name:

twb_plan_type

Data type:

string

Required:

yes

Domain:
1:

Safety

2:

Support

Notes:

1 - Safety Plan

Clients referred to The Way Back may have commenced the process of safety planning as part of their discussions with Emergency Department or Ward staff. Any existing safety plans completed by hospital or staff should be shared with or requested by The Way Back service provider and updated as part of preliminary discussions with The Way Back clients. Where clients referred to The Way Back have not completed any safety planning prior to their referral this should be completed as a priority once the client has consented to participate in The Way Back.

Safety Plans must be updated/developed within the first contact with the client. Safety plans should be reviewed with a client as needed. Each instance of the review and update of a safety plan should be recorded.

Service Providers should choose the most appropriate Support Plan template for their service. The TWB Tools and Templates provide a sample of one and there is also the BeyondNow app.

2 - Support Plan

All Way Back service providers must work collaboratively with their clients to develop a Support Plan that articulates:

  • the client’s needs as assessed using the Support Tools

  • the client’s goals of participating in The Way Back

  • proposed actions and interventions planned to address identified needs and goals including referrals to be made

In developing a Support Plan, discussion with clients should consider warning signs, strengths, support mechanisms and strategies that have enabled them to take the next steps. Needs Identified in this process are to be grouped and reported in the TWB NI data collection.

A Support Plan must be completed with a client within two weeks of their consenting to participate in the service. To identify a client’s needs and build an understanding of what support will be of benefit, all Support Tools and Measures should be completed prior to completing the Support Plan. Support Plans are also required to be reviewed at 6 weeks, or a regular basis throughout the support period to ensure that strategies are current and upon Service Exit. Each review must be documented.

TWB Plan - Tags

List of tags for the collection occasion.

Field name:

twb_plan_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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

TWB Plan Key

This is a number or code assigned to each instance of a TWB Plan. The TWB Plan Key is unique and stable for each instance of a measure at the level of the organisation.

Field name:

twb_plan_key

Data type:

string (2,50)

Required:

yes

Notes:

See Identifier Management

TWB Recommendation Out - Provider Type

Identifies the type of external service(s) that the client has been recommended to from the Way Back during their Episode of care, as represented by a code.

Field name:

twb_recommendation_out_provider_type

Data type:

string

Required:

yes

Domain:
1:

GP/Medical Practitioner

2:

Hospital

3:

Psychiatric/mental health service or facility

4:

Alcohol and other drug treatment service

5:

Other community/health care service

6:

Correctional service

7:

Police diversion

8:

Court diversion

9:

Legal service

10:

Child protection agency

11:

Community support groups/agencies

12:

Centrelink or employment service

13:

Housing and homelessness service

14:

Telephone & online services/referral agency e.g. direct line

15:

Disability support service

16:

Aged care facility/service

17:

Immigration department or asylum seeker/refugee support service

18:

School/other education or training institution

19:

Community based Drug and Alcohol Service

20:

Youth service (non-AOD)

21:

Indigenous service (non-AOD)

22:

Extended care/rehabilitation facility

23:

Palliative care service

24:

Police (not diversion)

25:

Public dental provider - community dental agency

26:

Dental Hospital

27:

Private Dental Provider

28:

Early childhood service

29:

Maternal and Child Health Service

30:

Community nursing service

31:

Emergency relief

32:

Family support service (excl family violence)

33:

Family violence service

34:

Gambling support service

35:

Maternity services

36:

Peer support/self-help group

37:

Private allied health provider

38:

Sexual Assault service

39:

Financial counsellor

40:

Sexual health service

41:

Medical specialist

97:

No Recommendation

98:

Other

99:

Not stated/Inadequately described

Notes:

It is best to record the recommendation information as soon as the client is recommended to an agency/community service as it may be difficult to track this information later.

To assist staff, service providers may find it useful to make a list of the agencies from which they most frequently send recommendations and note the corresponding Source of Recommendation code. Report the Recommendation starting with the most relevant or urgent one first.

TWB Recommendation Out - Status

Identifies the final status of external service recommendations made to the client, as represented by a code.

Field name:

twb_recommendation_out_status

Data type:

string

Required:

yes

Domain:
1:

Client declined to take up recommendation

2:

Service commenced

3:

Service completed

4:

Waitlisted

5:

Client deceased prior to service commencement

98:

Other

99:

Not stated/Inadequately described

Notes:

It is only necessary to complete this field when initially recommending and again, when closing the episode. There is no requirement to keep it updated as a recommendation progresses.

TWB Recommendation Out Key

This is a number or code assigned to each recommendation out. The Recommendation Out Key is unique and stable for each recommendation out at the lvel of the organisation.

Field name:

twb_recommendation_out_key

Data type:

string (2,50)

Required:

yes

Value

The metadata value.

Field name:

value

Data type:

string

Required:

yes

WHO-5 - Question 1

I have felt cheerful and in good spirits

Field name:

who5_item1

Data type:

string

Required:

yes

Domain:
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

WHO-5 - Question 2

I have felt calm and relaxed

Field name:

who5_item2

Data type:

string

Required:

yes

Domain:
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

WHO-5 - Question 3

I have felt active and vigorous

Field name:

who5_item3

Data type:

string

Required:

yes

Domain:
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

WHO-5 - Question 4

I woke up feeling fresh and rested

Field name:

who5_item4

Data type:

string

Required:

yes

Domain:
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

WHO-5 - Question 5

My daily life has been filled with things that interest me

Field name:

who5_item5

Data type:

string

Required:

yes

Domain:
0:

At no time

1:

Some of the time

2:

Less than half of the time

3:

More than half of the time

4:

Most of the time

5:

All of the time

9:

Not stated / Missing

Notes:

When reporting total score use ‘9 - Not stated / Missing’

WHO-5 - Tags

List of tags for the collection occasion.

Field name:

who5_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 !. Leading and trailing spaces will be stripped. e.g. priority!, nurse required, pending-outcome-1 would all be legitimate.

Tags beginning with an exclamation mark (!) are reserved for future use by the Department. e.g. !reserved, ! reserved, !department-use-only.

Download Specification Files

Available for software developers designing extracts for TWB, please click the link below to download TWB Specification files for the PMHC MDS: