A WA parliamentary question seeks detailed financial information regarding capital works and recurrent expenditure in Laverton under the Southern Inland Health Initiative (SIHI). The response reveals Laverton is not part of the SIHI capital catchment, and provides some recurrent expenditure details.

AnsweredQoN 1384Legislative Assembly
Asked
30 October 2013
Portfolio
Health

QuestionView source ↗

I refer to the Southern Inland Health Initiative, funded by Royalties for Regions and ask for the town of Laverton: (a) how much has been spent in Laverton on capital works for the years: (i) 2010–2011; (ii) 2011–2012; and (iii) 2012–2013; (b) can the Minister please provide a breakdown of projects for the amounts outlined in (a); (c) how much is earmarked to be spent in Laverton on capital works for the years: (i) 2013–2014; and (ii) 2014–2015; (d) can the Minister please provide a breakdown of projects for the amounts outlined in (c); (e) how much has been spent in Laverton on recurrent measures for the years: (i) 2010–2011; (ii) 2011–2012; and (iii) 2012–2013; (f) can the Minister please provide a breakdown of the measures for the amounts outlined in (e); (g) how much is earmarked to be spent in Laverton on recurrent measures for the years: (i) 2013–2014; and (ii) 2014–2015; and (h) can the Minister please provide a breakdown of measures for the amounts outlined in (g)?

AnswerView source ↗

Answered
3 February 2014
Responded by
Minister for Health
Response time
96 days
Answer as at 2 December 2013:
(a-d) Not applicable. Laverton does not fall within the Southern Inland Health Initiative (SIHI) Capital catchment.
(e)(i) Nil.
(ii) $35,000
(iii) Nil.
2011-2012 $109,493  Southern Wheatbelt Health Service
2012-2013 $464,815  Southern Wheatbelt Health Service
(f) Telehealth equipment and outpatients.
(g)(i) $54,600
(ii) $218,659
(h) General Practitioner Primary Health Care Incentive.
Telehealth equipment and outpatients.

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more