Advanced Solutions for Incident Tracking

1
Advanced Solutions for Incident Tracking Data
Analysis
International Incident Database Project (IIDB)
Safety Data
A project from OutdoorEd.com at
www.incidentdatabase.org
2
Objectives

• Identify the role that Incident Data collection
  serves in overall program risk management
• Assess who is currently collecting incident data
  and how you actively use that data in your
  program
• Explore how incident data can inform your program
  
• Present the International Incident Database
  Project
• Gather stakeholders in developing the system

3
Ground Rules

• Confidentiality
• Challenge by Choice
• Sharing incident stories
• Road Crossing example

4
Accident Iceberg
The Accident Ratio Study Tip of the Iceberg
Serious or Major Injury Includes disabling and
serious injuries
1
Minor Injury Any reported injury less than
serious
10
Property DamageAll types
30
Incidents With No Visible Injury or Damage Near
accidents or close calls
600
Accident Ratio Study (Bird Germaine, 1989)
5
Why Does Safety Data?

• Who collects data?
• How is it collected?
• What do you do with it?
• History is important
• Stories educate staff and set the tone for your
  program

6
Exercise Incident Data Collection

• Write up a short incident report
• Identify the Causal Factors

7
How an Incident Database Informs your Program

• What is happening in the field?
• Close Calls/Near Misses
• Incidents
• Risk Assessment
• Protocols
• Staff Training
• Equipment
• Emergency Response Plan

8
History of Data Collection

• Accidents in North American Mountaineering Jed
  Williamson - www.americanalpineclub.org/knowledge/
  publications-acc.asp
• ACA/AW River Safety Task Force Charlie
  Walbridge - US Whitewater Accident Database
  www.americanwhitewater.org/safety/
• National Safety Network Alan Hale
• Wilderness Risk Management Committeewww.nols.edu/
  pti/wrmc/

9
WRMC/AEE
10
American Whitewater
11
National Speleological Society
12
Outdoors New Zealand
13
What is the Problem?

• Programs desperately need to track and analyze
  incidents (accidents and close calls) for risk
  management, insurance, program development and
  training purposes
• Currently there is no standard for how to collect
  and analyze incident/accident data

14
What is the Problem?

• Programs are starting to develop their own
  solutions. This is creating an increasingly
  divided solution which will prevent our industry
  from effectively sharing and analyzing compiled
  data for trends.
• We need to act decisively now to develop an
  comprehensive industry standard.

15
Why Build an Incident Database?

• To create a standard method for collecting
  incident data.
• Creating the standard allows for the development
  of a common approach to incident analysis.
• Having an accepted database standard will allow
  for the collation of data from various sources.
  The more data collected, the better our ability
  to analyze it, identify trends, and make concrete
  recommendations for program improvement across
  the industry.

16
Why International?

• Everybody needs this
• Outdoor education programs are in almost every
  country around the world so an international
  standard will make it easier to integrate program
  data from around the world.
• An international database will help demonstrate
  that the risk levels in outdoor education are
  much less than typical competitive sports
  beneficial both from an insurance and a
  regulation standpoint.

17
International Incident Database System

• Tracking incidents and close calls is essential
  for any outdoor education or recreational
  program. Up to now there hasnt been a good tool
  to do this so Program Risk Managers have
  struggled with inadequate tools to do this
  important job.
• Thats about to change

18
Sample Data
19
Incident Narrative
20
IIDB General Information
21
IIDB Date Time
22
IIDB Course Information
23
IIDB - Location
24
IIDB Activity Environment
25
IIDB Narrative Analysis

• Severity Level
• Equipment involvement
• Detailed narrative
• Optional assessment and follow-up data fields

26
IIDB Person Information

• Allows for data entry about one or multiple
  people per
• Multiple conditions for each person. Person
  status (participant, staff, etc.).
• Detailed data on injury, illness, etc.
  Evacuation, medical care received, lost days,
  returned to the field, etc.
• Person data is optional and can be anonymous

27
IIDB Injury Information
28
IIDB Illness Information
29
IIDB Property Damage
30
IIDB Contributing Factors
31
IIDB Contributing Factors Priority
32
IIDB Related Files
33
IIDB Witness Account
34
IIDB Review/Follow-up
35
Tracking Incident Category in Real Time
36
Tracking Incident Type in Real Time
37
Incident Rate based on Activity
38
(No Transcript)
39
Incident Mapping
40
Drill-down
41
Programs Exploring the Database

• National Park Service
• Australia for a national incident database
• Outward Bound
• National Outdoor Leadership School
• Numerous other programs

42
Development Stages

• Stage 1 - Develop a standard database structure
  for storing outdoor incident data. Completed
• Stage 2 Create a Web version of the database to
  allow programs to test the system and make
  recommendations. Completed
• Stage 3 - Finalize the Database Design first
  quarter 2010

43
Development Stages

• Stage 4 Create Web and Desktop versions of the
  database to allow programs to start using the
  database to collect and analyze their own data.
  first quarter 2010

44
Development Stages

• Stage 5 - Discuss the idea of having a central
  database or several central databases where
  incident information is submitted. Identify and
  work to resolve any issues associated with having
  a centralized data store.
• Stage 6 - Develop a Web-based submission process
  so that data can be submitted to central
  server(s) and analyzed.
• Stage 7 Develop Web-based reporting and data
  analysis of the data

45
International Incident Database

• We want to ensure that this is the best possible
  resource for the broadest program use so we have
  released a Beta of the Web Version for people to
  interact with at www.incidentdatabase.net
• Public Comment is essential to ensure that the
  database covers the broadest spectrum of program
  needs

46
Getting More Information

• Programs interested in becoming part of the Web
  Beta test can access it online.
• Email Staff_at_outdoored.com for Beta Site and
  Password
• Online Videos, Discussion Forum Wiki at
  www.outdoored.com/Community/groups/incidentdataba
  se/

47
Development Stages

• Desktop versions of the database will be built in
  Microsoft Access 2007 and Filemaker Pro 10
• Server Versions will be built for Intranet and
  Internet use
• Web Technology used is ASP.NET 3.5, SQL Server
  2005/2008, third party controls

48
International Incident Database Project (IIDB)
Developed by
www.OutdoorEd.com
The Outdoor Professionals Resource