About Patient Safety

 

About the Patient Safety Assessment

Patient safety reviews of mobile applications are conducted by The Veterans Health Administration (VHA) Informatics Patient Safety Office (IPS), whose purpose is to improve the safety of Health Information Technology (HIT) products used by the VA and Veterans.

How to request an IPS Compliance Review

Project Managers (PMs) designated to a mobile application by Connected Care may request an IPS review. In order to help IPS understand the context of use, identify safety critical tasks, walkthrough realistic scenarios, and manage the review process efficiently and effectively, PMs are asked to complete an IPS Mobile Application Review Request Form (also available to MAE members as an attachment IPS Mobile App Review Request form) in its entirety. The PM should then send the completed form and associated documentation via E-mail to VHA10P2AIPSMobileTeam@va.gov. IPS will respond via E-mail and include the contact information for the person assigned to lead the patient safety review. Note: Requests for a preliminary review before the compliance review stage (i.e. wireframe or preliminary executable) may be granted if sufficient IPS resources are available during the time the review is requested. As much of the review request form as possible should be completed when requesting a preliminary review.

IPS Review Results

When IPS has completed its review the PM will receive an E-mail with an attached document that provides a detailed description of the review conducted and any patient safety issues found. This is presented in a standardized review form, Informatics Patient Safety (IPS) Mobile App Inspection Template. IPS welcomes questions about the review results and also requests that after the PM has discussed the results with the application business owner the response to each issue is communicated back to the IPS person who led the application’s review.

IPS Recommendations for Enhancing Patient Safety

Patient Safety can be enhanced by:

  • Consideration for Patient Safety at all stages in the development life-cycle for mobile applications
  • Certain application characteristics and functionality

Development Process Enhancements

  • Clearly define usage context: Users, Tasks, Technology, Environment of use
  • Identify high-level tasks (clinical/medical tasks) early
  • Connect user stories to high-level tasks
  • Explicitly connect functionality to high-level tasks (this is sometimes called a Conceptual model)
  • Pay particular attention to safety-critical tasks. A safety critical task is any action or decision whose failure could cause patient harm or a significant delay in care delivery
  • Provide support for users needing immediate help during safety critical tasks
  • Employ independent clinical review and usability testing of patient safety critical tasks
  • Develop or utilize a user accessible post-deployment issue reporting system

Application Design Enhancements

When presenting information to the user:

  • Make safety critical information salient
  • Provide context qualifying information near data presented - e.g. units of measure
  • Show deviation from the norm in results
  • Inform the user when system errors/events occur they need to be aware of
  • Provide meaningful error messages
  • Show how to get immediate help
  • Show how to report patient safety issues
  • Show who can see data entered
  • Show the app version/build number
  • User language of the user (especially for safety critical tasks)

When supporting the entry of data by the user Help avoid incorrect action selection & data entry

  • Have a confirmation step in some situations
  • Have an undo capability

References

  1. Bagian, J.P., Lee, C., Gosbee, J., DeRosier, J., Stalhandske, E., Eldridge, N., Williams, R., & Burkhardt, M. (2001). Developing and deploying a patient safety program in a large health care delivery system: You can’t fix what you don’t know about. Joint Commission Journal of Quality Improvement, 27, 522–532.
  2. Chapman R. J., Taylor, L. M., & Wood, S. D. (2012). Cataloging Errors from Reported Informatics Patient Safety Adverse Events. Proceedings of Human Factors and Ergonomics Society Healthcare Symposium, Baltimore, MD. (Available to MAE members as an attachment here).
  3. DeRosier, J., Stalhandske, E., Bagian, J.P., & Nudell, T. (2002). Using Health Care Failure Mode and Effect Analysis™: The VA National Center for Patient Safety’s prospective risk analysis system. Joint Commission Journal of Quality Improvement, 28, 248–267.
  4. Draft Guidance for Industry and Food and Drug Administration Staff - Applying Human Factors and Usability Engineering to Optimize Medical Device Design. http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/default.htm
  5. Johnson, J., ‎ Henderson, A., (2012). Conceptual Models: Core to Good Design. Morgan & Claypool.
  6. NIST EHR Usability Protocol (Lowry, et al. 2012)
  7. (NISTIR 7804) Technical Evaluation, Testing and Validation of the Usability of Electronic Health Records.
  8. Wharton, C. Rieman, J., Lewis, C. and Polson, P. (1994). The Cognitive Walkthrough Method: A Practitioner's Guide. In J. Nielsen and R. Mack (eds.) Usability Inspection Methods (New York: Wiley) 105-140.
  9. Wood, S. D., Chapman R. J., Taylor, L. M., Wright, P., & Scott J. (2014). Identifying Latent Design Issues in Mobile Products to Prevent Patient Harm. Proceedings of Human Factors and Ergonomics Society Healthcare Symposium, Chicago, IL. (Available to MAE members as an attachment here).