Table 1.
Key characteristics for error reporting system design
Purpose | System improvement |
Organizational accountability | |
Clinician education | |
Patient education | |
Administrative education | |
Public assurance | |
Process solution development | |
External (e.g. drug companies) entity education | |
Content | Form |
Elements such as situational characteristics, contributing factors, tips for prevention, tools involved, mitigating factors | |
Limited identification of both clinician and patient | |
Format | |
Blend of checkboxes and free-flow narrative sections | |
Design | Non-punitive |
Secured access | |
Optional identification | |
Flexibility (reporting medium, anonymity, etc.) | |
Easy to use | |
Pilot testing before implementation | |
Tactics employed to ensure clinician buy-in | |
Continuous feedback | |
Partial protection from consequential events for reporting | |
Solutions availability (e.g. for common errors) | |
Professional analysis of the data | |
Presence of an intermediary (e.g. editor, consultant) | |
Positive terminology (e.g. “Care Improvement System” vs. “Error Reporting System”) | |
Processing entity | Separate from the state |
Diverse mix of professionals (clinical and non-clinical) | |
No punitive power | |
Instructions | Information distributed to impart when to use, system goals, protections offered, and system limitations |
Training options: on-site expert, help desk, auto tutorials, help icons |