ABSTRACT
This chapter presents a process model for developing an incident reporting system that is practical for end users, produces good quality data, and underpinned by the principles of systems thinking. The model describes the core components of an incident reporting system underpinned by systems thinking, and a process for refining them through iterative cycles of end-user testing. The stages of the development process are described, with specific guidance on the optimal design of each component in the process model. The process model is applicable to the development of both internal incident reporting systems, collecting data within a single organization, and sector-wide incident reporting systems, collecting data from multiple organizations. Simply stating 'all incidents should be reported' is unlikely to be sufficient, as a significant barrier to reporting is often the belief that certain types of incidents or injuries are 'normal', and not worth reporting.
