BLAMMO Error Reporting
Transcription
BLAMMO Error Reporting
BLAMMO Error Reporting A system to report and track equipment issues Benjamin (BJ) Sintay, Ph.D., DABR Cone Health Cancer Center Greensboro, NC Cone Health at a glance Logistical challenges 1. Tracking minor issues or issues that “appear to be minor” 2. Contacting the right person for system issues quickly 3. Quickly determining issue response and follow-up 4. Communication with vendors 5. Learning from past issues UCSD able to achieve significant reductions in downtime and treatment cancellations; better response from vendor BLAMMO Initial Goals 1. Meet regulatory requirements of documentation/follow-up 2. Meet the Joint Commission standards of documentation/follow-up 3. Quickly notify individuals that need to respond 4. Communicate issues to vendor BLAMMO Origins Responders Notifications based on preferences, severity, type/serial number of system Weekly email to vendor (regional service manager) Designed for mobile Evolving Goals 1. Centralizing service reports 2. Track and predict solutions to problems 3. Manage PMI program 4. Communicate solutions to other users 5. Tie end-user issues to predictive/automated QA processes 6. Integrate vendor documentation / safety notices 7. Track QA results and provide trending / statistical analysis against database Thank you to Cone Health physics and IT team David Wiant, Ph.D. Caroline Vanderstraeten, M.S. Jackie Maurer, Ph.D. Han Liu, Ph.D. Lane Hayes, M.S. Keith Pearman, B.S. Jeff Wilson, Alex Tomalski, Cameron Necko