RESUMO
INTRODUCTION: An electronic checklist has been designed with the intention of reducing errors while minimizing user effort in completing the checklist. We analyze the clinical use and evolution of the checklist over the past 5 years and review data in an incident learning system (ILS) to investigate whether it has contributed to an improvement in patient safety. METHODS AND MATERIALS: The checklist is written as a standalone HTML application using VBScript. User selection of pertinent demographic details limits the display of checklist items only to those necessary for the particular clinical scenario. Ten common clinical scenarios were used to illustrate the difference between the maximum possible number of checklist items available in the code versus the number displayed to the user at any one time. An ILS database of errors and near misses was reviewed to evaluate whether the checklist influenced the occurrence of reported events. RESULTS: Over 5 years, the number of checklist items available in the code nearly doubled, whereas the number displayed to the user at any one time stayed constant. Events reported in our ILS related to the beam energy used with pacemakers, projection of anatomy on digitally reconstructed radiographs, orthogonality of setup fields, and field extension beyond match lines, did not recur after the items were added to the checklist. Other events related to bolus documentation and breakpoints continued to be reported. CONCLUSION: Our checklist is adaptable to the introduction of new technologies, transitions between planning systems, and to errors and near misses recorded in the ILS. The electronic format allows us to restrict user display to a small, relevant, subset of possible checklist items, limiting the planner effort needed to review and complete the checklist.
