The parliamentary question seeks information on ambulance patient distribution from Royal Perth Hospital's catchment area to other hospitals. The answer clarifies St John Ambulance's protocols, which prioritise clinical appropriateness and proximity, with a tertiary hospital distribution agreement.

AnsweredQoN 3421Legislative Council
Asked
16 February 2011
Portfolio
Health

QuestionView source ↗

(1) Are patients requiring an ambulance service located in the catchment area for Royal Perth Hospital (RPH) ever taken to a hospital other than the RPH?
(2) If yes to (1), why?
(3) How many patients were taken to a different hospital in 2010 ,and what was the reason?

AnswerView source ↗

Answered
15 March 2011
Responded by
Minister for Mental Health representing the Minister for Health
Response time
27 days
(1) St John Ambulance Australia (SJAA) does not define catchment areas for particular public hospitals in the metropolitan area for the purposes of determining patient distribution. The clinical protocols under which SJAA operates provide that patients who need hospital treatment will be taken to the nearest clinically appropriate public hospital. Where tertiary hospital treatment is assessed as being required, the nearest available tertiary hospital will usually be chosen, subject to a requirement in SJAA's contract to distribute patients to the three adult tertiary hospitals on a percentage basis in any 24 hour period - 40% to Royal Perth Hospital, 35% to Sir Charles Gairdner Hospital and 25% to Fremantle Hospital. Patients not requiring tertiary care will normally be delivered to the nearest available public hospital emergency department.
(2-3) Not applicable.
Notice: This document is created or edited using unregistered or evaluation copy of rtLib valid for testing or development purposes only. To use it for productive or any other purposes please register it. You may purchase the license on
http://www.rtlib.com

Explore WA Government Data

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

Explore more