top of page

Developing an Electronic Incident Report Feature for Behavioral Health Users

The following project is a summary of the research methods, insights, and actions taken to develop an incident reporting feature in an electronic medical records system.

Background

Role

  • ​Chief Clinical Officer

Duties​

  • Conduct research on user needs to for incident reporting feature in electronic medical records system

Collaborators

  • Stakeholders

  • Website developer

  • Clinical Leadership team

The Challenge

The organization's strategic plan included clinical quality as an initiative to align with healthcare quality standards.

  • Organization did not have any established user flows for incident reporting.

    Organization did not know what insights to prioritize

​

Project Goal

  1. Develop a feature in electronic medical records system for users to document and store incidents that occur on-site.

Secondary Research

I first conducted secondary research reviewing records of incident report templates and payor, legal, and ethical requirements for the field.

Incident report template_edited.jpg

User Interviews

Conducted interviews with users representative of all possible user personas about clinical quality and web-based EMR.

​

Participants

  • Regional Clinical Director

  • Administrative Staff 

  • Supervising Clinician

ABA EMR User Interviews pg1.jpg

Contextual Inquiry

Conducted contextual inquiries with users representative of all possible user personas about incident reporting.

 

Participants

  • Regional Clinical Director

  • Administrative Staff 

  • Direct-Care Clinician

  • Supervising Clinician

Beta Testing

Due to immediate necessity of feature, incident reporting feature was Beta tested.

  • Beta version of feature was distributed to 10% of users.

Insights

Gathered key insights about Beta Version via usability testing.

Insights.jpg

Actionable Insights

Disseminated findings to development team and provided recommendations for actionable insights

  1. Create a save and exit button for users to return for signature from caregiver later.

  2. Create signature section for caregiver.

  3. Create user flow and capability for incidents that require caregiver contact.

User Flow

Created a user flow for incident reporting to alert users to obtain supervisor signature.

Incident Report SOP User Flow.jpg

Conclusion

The methods used in this project resulted in the following changes to the incident reporting feature:

  1. 100% User engagement for incident reporting feature that documented and stored incidents across the entire organization

  2. Iterations that included the following:

    • Sign and save feature​

    • Signature section for caregivers

    • User flow to include alert to contact a caregiver based on incident type

© 2023 by Ashley Lugo. Powered and secured by Wix

bottom of page