Reporting system, incident investigation

The initial incident report is very important. This document captures the initiator s firsthand knowledge of what occurred in the moments after the specific event. Example 5-2, Sample Toller Initial Incident Report, is an example of the data that should be documented as soon as possible. Note that it should be modified using the company s management system procedure and incident investigation procedure, which should describe the type of data needed, and level of detail desired. 

In addition to incident reporting systems, root cause analysis techniques can be used to evaluate the causes of serious incidents where resources are usually available for in-depth investigations. A practical example of root cause investigation methods is provided in Chapter 7. 

Workforce Support for Data Collection and Incident Analysis Systems Few of the incident investigation and data collection systems reviewed provide any guidelines with regard to how these systems are to be introduced into an organization. Section 6.10 addresses this issue primarily from the perspective of incident reporting systems. However, gaining the support and ownership of the workforce is equally important for root cause analysis systems. Unless the culture and climate in a plant is such that personnel can be frank about the errors that may have contributed to an incident, and the factors which influenced these errors, then it is unlikely that the investigation will be very effective. 

Given the low incidence of severe withdrawal symptoms and the modest effects on the mesolimbic dopamine (reward) system, most investigators have found that cannabis has a low abuse or addiction potential. However, it has been argued that if cannabis is a non-addictive substance, why is its use so widespread and why are there so many longterm and heavy users Finally, contrary to the evidence that cannabis can produce chronic tolerance, some regular users report that they require less drug to achieve the same high, or sensitisation (Chapter 3). Three possible explanations may account for this. First, chronic users may focus on the effects that they wish to achieve. Second, the... 

Consider having one incident reporting system with one approach for teaching employees the definition of a near miss and with one approach for doing incident investigations including one approach for root cause analysis. 

An incident has just been reported. How is a team activated The team activation segment of a company s incident investigation management system should guide the user to assemble a team based upon the following two areas of concern ... 

Trend analysis can be confused or invalidated by a sample that is too small. If the charting or analysis is limited only to major incidents, there will often be too few within a period to arrive at meaningful conclusions. For example, a facility with one thousand employees may experience only one or two serious incidents per year, and several years worth of data would be needed to make any meaningful statistical analysis. Minor incidents and near misses can be as useful in trend analysis and preventive prediction as major incidents. All process incidents should be reported, classified, and investigated as appropriate. The severity of an incident is frequently more a function of chance than actual fundamental system differences among accidents and near misses. 

The following case study describes the investigation work process for a hypothetical occurrence using a logic tree based multiple root-cause systems approach. An example incident investigation report follows the work process description. The example is intended for instructive purposes only descriptions of process equipment and conditions are not intended to reflect actual operating conditions. 

Every laboratory should have an internal accident-reporting system. This includes provisions for investigating the cause of an injury as well as any potentially serious incident that does not result in injury. The primary aim of such investigations should be to make recommendations to improve safety, not to assign blame for an incident. Local legal regulations may require reporting procedures for accidents or injuries. 

The typical incident report will be maintained in the technical report system, unless the team chairman or legal council recommends that it is inappropriate for this incident. The original signed incident report is filed in the technical report system. Copies are sent to the affected plant manager, production superintendent, second-level supervisor, process safety manager, the investigation team chairman, and others as deemed appropriate by the chairman. 

---