The Analyze-Err is a software documentation tool designed by ISMP Canada and ISMP (US) for use in institutions to track and analyze medication errors. Definitions, i.e. the Taxonomy of Medication Errors are taken with permission from the National Coordinating Council for Medication Error Reporting and Prevention (NCCMERP). The aim is to create a computerized database of medication events for storage, retrieval, follow-up and analysis.

• The program runs under Windows 98/NT/XP, network-able and supports multiple sites.
• There are two major components to the program. One of which is to record the factual account of the incidents. The other is to analyze the errors to generate root causes of the incidents.
• In keeping with the no-blame, non-punitive principle of error reporting, the two components can be disassociated after the data is entered. This way, we hope to encourage critical analysis of the errors without attaching blame to each incident.
• The user can go back to examine the factual accounts of the events or look at the aggregate root causes to make improvements to the system. Graphs, reports, and search utilities are available to aid the process.
• In addition, mechanism is built in for users to submit data to ISMP Canada. Non-patient specific data can be pooled together to form a "big picture". ISMP Canada will do further analysis and disseminate recommendations so all can learn from past mistakes.
• The software is available in the fourth quarter of year 2001 to licensed users. For more information, please contact info@ismp-canada.org. 

Screen Shots:

Click on each picture to see the full view.

	The Browse Mode This table presents a compressed view off all the records entered so far. It provides a means to browse and organize the records. Records can be sorted by clicking any one of the headers. The contents of this table may be filtered by using the search function. From this table, the user can double click on a record of interest to see or edit the details. Other functions are accessible by pressing one of the icons from the button bar.
	The Event Details The medication error details are divided into 8 pages, accessible by clicking the tabs near the top of the screen. Shown here is the event details tab. The user is encouraged to enter whatever information is available or applicable, i.e., the entire process is voluntary. There are no mandatory fields. With some practice, users should be able to do data entry fairly quickly. Where possible, drop lists and check boxes are used to standardize and facilitate data entry.
	The Outcome Details This is another example of a data entry screen. The Outcome and Interventions are pre-defined. The user will click an appropriate response from the Outcome and Intervention buttons. The outcome categories are taken from the Taxonomy of Medication Errors as defined by the NCCMERP.
	The Patient Details This is another example of a data entry screen. The patient data is entered last because this program places the emphasis on the medication error itself.
	The Analyzer Module This part of the documentation process is not found in most current incident reports. It attempts to ask questions about the event, questions that relate to specific issues and the root causes. Each question requires a yes or no answer, by checking the appropriate boxes.
	The Root Causes This is the main part of the Analyser. There are 10 root cause categories, each with common sub-causes. These are again adapted from ISMP (US). Because there's a perception that we're looking for who or what is at fault, the data gathered here is stored separately from the event itself. In addition, the linkage between the event and the analysis can be broken once the data is entered. This way no blame is permanently attached to the event. However, we can still look at the root causes at a whole to find weakness in the system.
	Graphical Representation The common root causes can be presented graphically. The root causes may be stratified by date, severity, AHFS code or issue. Click on any one of the bars will drill down to the next level of causes, as shown in the graph below.
	Graphical Representation The sub-causes may also be presented graphically. This graph is obtained by clicking on one of the bars from the above graph.
	Graphical Representation Event statistics may be presented graphically also. There are four different type of graphs in this section: Yearly, by type of error Type of error within a time period Outcome Category/Severity Code within a time period Stage of error within a time period.
	Graphical Representation This is another example of the event statistics graphed. This shows the number of different types of error within a time period.
	Search function A comprehensive search function is implemented to quickly find a subset of errors in question. Most data fields can be selected and combined to form the search criteria. The searchable data fields are organized into 5 pages.
	Search function Another example of data fields that can be searched on.
	Reports Hard copy reports can be obtained in various sections of the program. Notice the graphs above each have a Print button This example shows the results of a search function printed (in preview form).
	Reports This is an example of an error report printed (in preview form). The report will span multiple pages if necessary. A blank error report form may also be printed for manual data entry.