IncidentAnalytix ®

Order Cloud Services

Incident Reporting & Data Analytics: Implementing a Risk Management Information System for Youth Protection Workshop at the HEPNet 2020 Conference

Managing risk in youth programming means understanding the factors that either lead to incident events or to safe programming. Your best defense against risk is data collection and analysis of incidents and close calls to be able to quickly identify and mitigate hazards.

In this workshop we’ll start by exploring the traditional Safety I approach to risk management which focuses on what went wrong and takes a ‘control mistakes’ approach to identify weaknesses or failures in the system. Safety I is often used as a framework for post-incident review to identify and address the contributing factors that led to the event. This is a critical risk management step after any serious incident.

While post-incident analysis is critical, far more of our programming is safe and successful. The Safety II framework looks proactively at those factors which create success and work to ensure that those are present in all programming. Any comprehensive risk management approach requires using both Safety I and Safety II frameworks.

The Systems Theory approach to risk management (Rasmussen, 1997) allows us to combine the Safety I Safety II frameworks to create a comprehensive risk management approach. Rasmussen identified that accidents are not the result of a failure at a single point, but that any failure point is related to multiple other aspects of the entire system. Government, regulatory agencies, organizations, parents, providers, staff, participants, work setting, etc. all interact to create either safe or unsafe environments. Managing safety means understanding the relationships between factors at each level and determining the most effective methods of intervention.

The essential element in implementing a Systems Approach to Safety I & Safety II is data collection. Information on incidents and close calls must be collected in a consistent manner to allow organizations to identify trends both in the hazards contributing to incident events and the mitigating factors that create safe and successful programming. A Risk Management Information System (RMIS) provides a structured data collection and analysis for both Safety I and Safety II frameworks. We will use the IncidentAnalytix data collection and analysis system as a sample RMIS for analyzing your program through both a Safety I and a Safety II lens.

How to build an AcciMap

  1. Create a blank AcciMap with the Taxonomy headings on the left sidebar in hierarchical order
  2. Identify the outcome(s) and enter at the bottom
  3. Identify Causal Factors on a sticky note
  4. Enter the Causal Factors at each Taxonomy Level
  5. Identify the Relationships between Factors
    • Had A not occurred, B would (probably) not have occurred
    • AND
    • B is a direct result of A (no other factor in between, otherwise link A to C and C to B)
  6. Check causal logic
  7. Determine:
    • What is In Scope?
    • What is Out of Scope
  8. Create an Action Plan based on what is In Scope

Resources from the Workshop:

Key Literature:

Other Resources:

 
 

Learn More

Order Cloud Services

Technology

Products

Getting Started

Contact Us