Opposition questions the Minister for Health on the handling of a sterilisation failure at Fiona Stanley Hospital by Serco, specifically regarding transparency and financial repercussions. The Minister defends the response, prioritising patient safety and adherence to contractual obligations.

AnsweredQoN 72Legislative Assembly
Asked
25 February 2015
Portfolio
Health

QuestionView source ↗

FIONA
STANLEY HOSPITAL — SERCO CONTRACT — STERILISATION PROCEDURES
72. Mr M. McGOWAN to the Minister for
Health:
I have a supplementary question. If
the minister has known about this since December, why did he not reveal that
information then; what are the exact details of the reimbursement of the cost
to the Department of Health for this failure; and what will the amount be?

AnswerView source ↗

There is no way of knowing that at
present, because the only reimbursement required at present is the cost of
staff, and they have only just been transferred across, so there is no detail
in that space. The details of the fine will be determined as part of the
contract. There is a clear contract in place that has requirements within it to
deal with fines, and that will continue as part of the contract.
Several members interjected.
The
SPEAKER : Members!
Dr
K.D. HAMES : This is a $2 billion hospital that has just opened with 5 000
staff altogether. Serco itself has large numbers of staff in this space across
a whole range of different parts of the contract. All of the other parts are
going fine. This is an area of failure and it is being dealt with. Yes, I did
know about this in December, but I do not know why I would want to come out and
announce that because our job is to make the hospital work and to make it safe
for patients, and we have done that. My people in the Department of Health at
Fiona Stanley Hospital have done an incredible job in making sure that the
safety of the patients is paramount, and we have been doing that job.

Explore WA Government Data

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

Explore more