> ## Documentation Index
> Fetch the complete documentation index at: https://help.visualcare.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# SIRS incidents

> Create and manage Serious Incident Response Scheme incidents in Visualcare

The Serious Incident Response Scheme (SIRS) is a requirement under the NDIS Quality and Safeguards Commission. NDIS providers must report certain types of serious incidents, including abuse, neglect, unauthorised restrictive practices, serious injury, and death. Visualcare supports SIRS reporting by letting you flag incidents as SIRS records, which adds the fields and tracking needed to meet your reporting obligations.

## What counts as a SIRS incident

Under the NDIS (Incident Management and Reportable Incidents) Rules, reportable incidents include:

* The death of a person with disability
* Serious injury of a person with disability
* Abuse or neglect of a person with disability
* Unlawful sexual or physical contact with, or assault of, a person with disability
* The use of a restrictive practice that is unauthorised or not in accordance with a behaviour support plan

When an incident falls into one of these categories, it needs to be recorded as a SIRS incident in Visualcare so it can be tracked separately and reported to the NDIS Commission within the required timeframes.

## Where to find SIRS incidents

SIRS incidents are accessible from two places:

* **Operations** → **Incidents** → **SIRS** tab for a centralised view of all SIRS incidents across your organisation
* The **Incidents** tab on the individual client's profile, where SIRS incidents appear alongside other incident records

<Tip>Use the **SIRS** tab under **Operations** when you need to review all SIRS incidents in one place, for example during an audit or when preparing a report for the NDIS Commission.</Tip>

## Creating a SIRS incident

SIRS incidents follow the same creation process as standard incidents. When creating or editing an incident, flag it as a SIRS incident to add the additional reporting fields. See [Creating an incident](/incidents/creating-an-incident) for the full creation process.

Once flagged as SIRS, the incident appears in the **SIRS** tab and any assigned users receive a notification.

## Restricting visibility

SIRS incidents often involve sensitive information. You can restrict an individual SIRS incident to a specific user group using the **User Access Control** option on the incident form. This makes the incident visible only to members of the selected group, for example the Administration group.

See [User access control](/getting-started/user-access-control) for how to enable and use this feature.

<Warning>If you're reporting a SIRS incident to the NDIS Commission, keep in mind the reporting timeframes: notify the Commission within 24 hours for the most serious incidents and provide a full report within five business days. Use the [SIRS register](/incidents/sirs-register) to track your reporting status.</Warning>

## Running into issues?

See [Incidents troubleshooting](/troubleshooting/general) for common errors and fixes.

## Related articles

<CardGroup cols={2}>
  <Card title="SIRS register" icon="list-check" href="/incidents/sirs-register">
    Track and report on all SIRS incidents in one place
  </Card>

  <Card title="Creating an incident" icon="plus" href="/incidents/creating-an-incident">
    How incidents are created and where to find them
  </Card>

  <Card title="Editing incidents" icon="pen-to-square" href="/incidents/editing-incidents">
    Review and update incident details after submission
  </Card>

  <Card title="Incident settings" icon="gear" href="/incidents/incident-settings-configuration">
    Control incident visibility and form behaviour
  </Card>
</CardGroup>
