fct_incidents


Description

Incidents are a ticket add-on. There are 4 steps to an incident. 1. An incident ticket is created. 2. The incident is then categorised. 3. The incident is actioned. 4. Summary of the incident. The fct_incidents model combines the base incident with the categorisation. Incidents do not include archived tickets.

Columns

Column Type Children Parents Comments
incident_id int8
fct_incident_actions.incident_id Implied Constraint R

The unique ID of the incident, i.e. 14.

ticket_id int8
fct_tickets.ticket_id Implied Constraint R

The associated ticket ID of the incident, i.e. 59.

reporter_profile_id int8

The profile ID that reported the incident, i.e. 10.

subject_profile_id int8

The profile ID of the subject of the incident, i.e. 3283.

state text

Whether the incident is open or closed.

incident_occurred_at timestamp

When the incident occured at (in UTC), e.g. 2021-03-02 00:12:59.996101.

incident_reported_at timestamp

When the incident occured at (in UTC), e.g. 2021-03-02 00:12:59.996101.

incident_created_at timestamp

When the incident was created by the staffer (in UTC), e.g. 2021-03-02 00:12:59.996101.

incident_updated_at timestamp

When the incident was last updated (in UTC), e.g. 2021-03-02 00:12:59.996101.

primary_category varchar

The main category the incident was categorised as. These 22 categories were set by lookout. E.g. abuse_emotional.

secondary_categories _varchar

Any other relevant categories for the incident. It contains all values in the primary_category plus a few others. Multiple can be selected. E.g. {fall, injury}

recommended_level varchar

This is selected by the lookout decision support tool, and selects the level based on what the primary category is. It is based of the SIRS framework. One of 3 values: non_reportable, priority_one, priority_two.

selected_level varchar

The level that is selected by the staffer who is overlooking the incident. One of 4 values non_reportable, reportable, priority_one, priority_two.

caused_injury bool

Whether this incident caused or could reasonably expect to have caused physical, or psychological injury or discomfort that requires treatment. E.g. True or False

reportable_to_police bool

Whether there is reasonable grounds to notify the police or not. E.g. True or False

unlawful_conduct_occurred bool

Whether unlawful sexual conduct or inappropriate sexual conduct has occured. E.g. True or Fals.e

unexplained_absence_or_death bool

Whether an unexpected death has occured or the client has an unexplained absence during the incident. E.g. True or False

cognitive_impairment varchar

What is the persons cognitive status? One of 4 possible values: none: No cognitive impairment mild: Mild cognitive impairment moderate: Moderate cognitive impairment severe: Severe cognitive impairment

incident_category_created_at timestamp

When the incident category was created at (in UTC), e.g. 2021-03-02 00:12:59.99610.1

incident_category_updated_at timestamp

When the incident category was updated at (in UTC), e.g. 2021-03-02 00:12:59.99610.1

company_id int8
dim_companies.company_id Implied Constraint R

The company ID, e.g.: 345.

location varchar

Where the incident took place, one of 5 values: client_home, outisde_home, hospital, respite, other.

community_id int8
dim_communities.community_id Implied Constraint R
community_name text
membership_id int4

The ID of the membership associated with the incident, e.g. 1989.

Indexes

Constraint Name Type Sort Column(s)
fct_incidents_pkey Primary key Asc incident_id
fct_incidents_company_id_idx Performance Asc company_id
fct_incidents_ticket_id_idx Performance Asc ticket_id

Relationships