Security incidents in Safety Learning System
The reporting and review of both emergency and non-emergency security incidents
Definition - A security incident is any event or circumstance that resulted in a request for emergency or non-emergency security attendance. These include when any of the Emergency Codes are called.
Who will record security incidents?
For health service organisations employing Security officers, these officers will be the usual notifiers. For other
- How to record a security incident into SLS (PDF 589KB)
Quickguide to recording a security incident into SLS (PDF 87KB)
Who will be responsible for
review of these incidents?
Staff responsible for
For example, in metro
- How to manage a security incident in SLS (PDF 758KB)
Quickguide to managing a security incident in SLS (PDF 88KB)
How are security incidents classified in SLS?
All security incidents are classified by selecting from a series of questions with several options. There are additional questions and space to record comments. The diagram Security incidents – level 1, 2, and 3 classifications (PDF 90KB) illustrates the hierarchy of classification options in the Security incident module.
The Topic Guide – Security incident module (PDF 147KB) provides definitions for terms used when recording a security incident into the SLS. Definitions of common terms are provided to ensure that reporting is consistent and accurate.
Emergencies include all of the emergency codes. Code Blue reporting will commence in the near future. These are:
|Code Black||Personal threat, for
|Code Blue||Medical emergency, for
|Code Brown||External emergency, for
|Code Purple||Bomb threat, for
|Code Red||Fire and/or smoke|
|Code Yellow||Internal emergency, for
What are non-emergency security assists?
This is a non-emergency request made by clinical staff for Security officers to
- Security officer attending while nursing staff change a catheter, for a patient with dementia who was quite aggressive last time this occurred.
attenda difficult family meeting,when it is anticipated that there may be verbalor physical confrontation.
attendto re-apply a mechanical restraint after its scheduled release, to allow for limb movement. Clinical staff are unable to reapply safely because the consumer becomes combative and likely to harm themselves and/or staff.
Some incidents may escalate into an emergency, leading to a Code Black call to request the full Emergency Response team to attend.
Routine practice is not required to be reported as it is not an incident, for example, escorting a patient to
What is a Code Black call and how is it made?
The SA Health Preventing and Responding to Challenging Behaviour policy directive (PDF 547KB) and toolkit provides further information. See also:
- How to report an incident involving challenging behaviour (PDF 60KB)
This diagram is an overview of the SLS incident reports required if a patient affected, if a worker is affected, and/or if security is involved
- Preventing and responding to challenging behaviour by a consumer/patient (PDF 67KB)
This diagram explains the options for resolving a situation of challenging behaviour including calling for emergency assistance (Code Black)
- Preventing and responding to challenging behaviour by a person who is not a current
consumer / patient(PDF 69KB)
This diagram explains the options for resolving the situation or getting assistance when a
non patientis exhibiting challenging behaviour
- Quick guide – Components of a stepped response to challenging behaviour by a
consumer / patient(PDF 91KB)
A table to guide
selectionof the type of assistance required in a range of situations.
Updates and outages
For a list of recent and upcoming SLS updates and outages, see the Safety Learning System Notice page.
For further information or enquiries, please contact:
Cameron Hussey / Ruta Errington
Information Officers, SLS Management Team
Telephone: (08) 8226 6177 / (08) 8226 6196