Hon Steve Martin asks about the number of Severity Assessment Code 1 (SAC1) events in WA hospitals, including those resulting in death, for the years 2017-2020. The Minister was unable to provide an answer within the timeframe.

AnsweredQoN 218Legislative Council
Asked
2 June 2021
Portfolio
Health

QuestionView source ↗

HOSPITALS —
SEVERITY ASSESSMENT CODE 1 EVENTS
218. Hon STEVE MARTIN to the minister representing the
Minister for Health:
I
refer to the practice within our health system whereby clinical incidents are
classified, specifically those categorised as severity assessment code 1
in which a clinical incident has, or could have, caused serious harm or death
and is attributed to healthcare provision, or lack thereof, rather than the
patient's underlying condition or illness.
(1) For each
metropolitan and regional hospital, how many severity assessment code 1 events
have taken place in the following years —
(a) 2017–2018;
(b) 2018–2019;
(c) 2019–2020; and
(d) 2020 to date?
(2) Of those severity assessment
code 1 events reported each year, how many resulted in death in —
(a) 2017–2018;
(b) 2018–2019;
(c) 2019–2020; and
(d) 2020 to date?

AnswerView source ↗

I thank the honourable member for
some notice of the question.
WA Health has been unable to answer
this question in the time frame provided. The honourable member may wish to
place the question on notice.
If
new honourable members have a question without notice that looks for that level
of detail, it will never be answered within three or four hours. If
members are looking for detail from a number of hospitals or different health
service providers, they might like to consider putting their question on
notice.
Hon Nick Goiran : There must
be a lot of code yellows. It takes a long time to count them up.
Hon STEPHEN DAWSON : How many
hospitals have we got in WA? For goodness sake!
The PRESIDENT : Order! This
is not a free-flowing debate; it is question time.

Explore WA Government Data

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

Explore more