Download International Incident Database Project

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
Ground Rules
• Confidentiality
• Challenge by Choice
• Sharing ‘incident stories’
– Road Crossing example
Accident Iceberg
The Accident Ratio Study
Tip of the Iceberg
Serious or Major Injury:
1
10
30
600
Accident Ratio Study (Bird & Germaine, 1989)
Includes disabling and serious
injuries
Minor Injury:
Any reported injury less than
serious
Property Damage:
All types
Incidents With No Visible
Injury or Damage:
Near accidents or close calls
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
Exercise: Incident Data Collection
• Write up a short incident report
– Identify the Causal Factors
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
History of Data Collection
• Accidents in North American Mountaineering
– Jed Williamson www.americanalpineclub.org/knowledge/publicationsacc.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 Committee
www.nols.edu/pti/wrmc/
WRMC/AEE
American Whitewater
National Speleological Society
Outdoors New Zealand
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
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.
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.
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.
International Incident Database System
Tracking incidents and close calls is essential
for any outdoor education or recreational
program. Up to now there hasn’t been a good
tool to do this so Program & Risk Managers
have struggled with inadequate tools to do this
important job.
That’s about to change…
Sample Data
Incident Narrative
IIDB – General Information
IIDB – Date & Time
IIDB – Course Information
IIDB - Location
IIDB – Activity & Environment
IIDB – Narrative & Analysis
• Severity Level
• Equipment
involvement
• Detailed narrative
• Optional
assessment and
follow-up data
fields
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
IIDB – Injury Information
IIDB – Illness Information
IIDB – Property Damage
IIDB – Contributing Factors
IIDB – Contributing Factors Priority
IIDB – Related Files
IIDB – Witness Account
IIDB – Review/Follow-up
Tracking Incident Category in Real Time
Tracking Incident Type in Real Time
Incident Rate based on Activity
Incident Mapping
Drill-down
Programs Exploring the Database
•
•
•
•
•
National Park Service
Australia for a national incident database
Outward Bound
National Outdoor Leadership School
Numerous other programs
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
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
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
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
Getting More Information
• Programs interested in becoming part of the
Web Beta test can access it online.
• Email: [email protected] for Beta Site and
Password
• Online Videos, Discussion Forum & Wiki at
www.outdoored.com/Community/groups/inc
identdatabase/
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