fct_incident_actions


Description

Actions taken in response to incidents.

Columns

Column Type Children Parents Comments
incident_action_id int8

The unique ID of the incident action, e.g. 45.
incident_id int8

The ID of the associated incident, e.g. 12. Maps to fct_incidents.
likelihood varchar

How likely this incident was to occur based on available information. The values are one of the following: rarely: Conceivable but only in extreme circumstances (once every 100 years) unlikely: Hasn’t happened yet but could (once every 10 years) possible: Could happen or known to happen (once a year) likely: Could easily happen (once a month) certainly: Often occurs (once a week).
impact varchar

How serious are the consequences of this incident? The values are one of the following: insignificant: No injuries/minimal financial loss/no personal information exposed minor: First aid treatment/medium financial loss/one person affected with limited personal data moderate: Medical treatment/ high financial loss/one person affected with sensitive data exposed (name, health status) major: Hospital treatment/large financial loss/all personal information for Clients or Workers in one section exposed catastrophic: Death/massive financial loss/all personal information across the company exposed.
severity varchar

This is calculated based off the likelihood and impact columns. One of low, moderate, high, catastrophic.
external_id varchar

The identified of the third party the incident was referred to.
client_review_at date

The date and time at which the client reviewed the incident (in UTC), e.g.: 2021-03-02 00:15:49.996204.
referral_at date

The date and time at which the incident was referred at (in UTC), e.g.: 2021-03-02 00:15:49.996204d.
update_help_plan_at date

The date and time at which the help plan was updated at (in UTC), e.g.: 2021-03-02 00:15:49.996204d
debrief_at date

The date and time at which the relevant parties were debriefed at (in UTC), e.g.: 2021-03-02 00:15:49.996204d.
coaching_at date

The date and time at which the relevant parties were coached at (in UTC), e.g.: 2021-03-02 00:15:49.996204d.
created_at timestamp

The date and time at which the indicent ticket was created at (in UTC), e.g.: 2021-03-02 00:15:49.996204d.
updated_at timestamp

The date and time at which the incident ticket was created at (in UTC), e.g.: 2021-03-02 00:15:49.996204.
reported_to_aged_care_quality_and_safety_commission_at date

Whether the incident was reported to the Aged Care Quality and Safety Commission, e.g. True or False.
reported_to_child_safety_at date

Whether the incident was reported to the Child Safety, e.g. True or False.
reported_to_enduring_power_of_attorney_at date

Whether the incident was reported to the Enduring Power of Attorney, e.g. True or False.
reported_to_ndis_quality_and_safequards_commission_at date

Whether the incident was reported to the NDIS Quality and Safegaurds Commission, e.g. True or False.
reported_to_next_of_kin_at date

Whether the incident was reported to the Next of kin, e.g. True or False.
reported_to_office_of_australian_information_commissioner_at date

Whether the incident was reported to the Office of Australian Information Commissioner, e.g. True or False.
reported_to_police_at date

Whether the incident was reported to the Police, e.g. True or False.
reported_to_whs_safety_authority_at date

Whether the incident was reported to the WHS Safety Authority, e.g. True or False.
reported_to_other_at date

Whether the incident was reported to any other authoritie,. e.g. True or False.
company_id int8

The unique ID associated with the company, e.g. 51.

Indexes

Constraint Name Type Sort Column(s)
fct_incident_actions_pkey Primary key Asc incident_action_id
fct_incident_actions_company_id_idx Performance Asc company_id
fct_incident_actions_incident_id_idx Performance Asc incident_id

Relationships

Close relationships within degrees of separation