Creating the CHPSO Database

Post

February 2014

Creating a robust database has been a true challenge at CHPSO, as well as other patient safety organizations (PSO) across the nation. There appear to be some common contributing factors to this problem:

  • Lack of dedicated resources to submit data
  • No regulatory mandate for reporting of incident data to a PSO
  • Legal counsel unfamiliar with legal protections provided for the reporting of patient safety work product to a PSO

We have been told by some members that because of these factors, reporting of incident data to a PSO is not viewed as a priority within their organization.
Fortunately, many organizations understand that the identification of the causal factors of emerging safety risks identified by PSOs is a crucial component to improving the quality of health care delivery and eliminating preventable harm. After all, it’s hard to accomplish these improvements if you do not understand why they occur.

Due to this commitment, CHPSO has experienced a steep increase in data reporting (see Table 1 below). The database now contains approximately 132,000 incident reports which are rich in information. We are currently working on a couple of “deep dives” into safety incidents related to clinical alarms and bar code medication administration to better understand and share the leading causal factors behind incidents involving these technologies.

Table 1: Number of incident reports submitted to CHPSO database



Most of the organizations that are reporting large volumes of incident reports are able to do so through automated modules or services with their risk management incident system (RMIS). We encourage you to contact your RMIS vendor to discuss their ability to automate your incident data to CHPSO. When you are ready to start the process, contact us at CHPSO and we will walk you through the process.