To help new users recall and understand key information, I included tool tip micro interactions and considered best UX practices for dashboard design.

Dashboard design calls for prioritizing the data elements by location so I placed most important data at the top left and incorporated checklists in the dashboard interface to aid improving user's memory of important information.

Low levels of health care work related accident reporting is caused by a lack of staff awareness and the rigid accident reporting process.

Nurse admins tend to be unaware of accidents that happen in the workplace and tend to be less informed about preventing work-related accidents. Often low levels of reporting accidents is due to factors such as long process time of OSHA 300 reports, unreliable documentation, and the need to stay in HIPPA compliance.

The existing process for submitting OSHA 300 reports is lengthy and complex.

To understand the current landscape of incident reporting, I reviewed academic articles and industry reports. I learned that the existing process for submitting OSHA 300 reports often taking up to 30 days to turn an incident into a case. I created a user journey map of the reporting process to accurately understand where an admin responsibilities plays into each step in order to find the biggest bottleneck to a case closing.

This research highlighted key challenges:

• Privacy Concerns: Employers must balance accurate logging with protecting employee privacy, sometimes needing employee consent to disclose identifying details.
• Busy Schedules: Healthcare workers are often too busy or overwhelmed with their other responsibilities to report incidents promptly.
• Long Turnaround Times: The extended process of closing OSHA reports discourages timely and accurate reporting.

Pinpointing key players in the reporting process

I found that Registered Nurses (RNs) frequently initiate accident reports, while roles such as the Assistant Director of Nursing (ADON), Director of Nursing (DON), and administrators are responsible for reviewing and converting these reports into cases.

Understanding these multiple roles and touch points highlighted the necessity for my solution to be versatile and accommodating for not only the tracking of accidents and staff but also the submission of relevant files as needed.

I aimed to create a dashboard and reporting that delivers precise data to users that they would want to see in a clear, non-overwhelming manner while also being customizable for each user and their specific need.

I created wireframes of the solution to address the lack of awareness in company wide incident reports. To improve report transparency, the dashboard must have  an overview of the amount of reports being reporting by specific time periods, monthly incident report trends, and easy access to attend to open cases that are high priority, features to easily track their daily tasks.

[wireframes and sketches]

‍

Prioritizing use cases for Nurse Administrative roles

Given the constraints of time and resources, we decided to concentrate on the Nurse Administrative roles—those responsible for monitoring and reviewing incident reports in order to address the most critical pain points impacting reporting success.

Key pain points:

• Awareness and monitoring: Admin staff need to be constantly aware of issues within their department and track the number of incidents reported.
• Reporting duties: Admins must review and create workers' compensation reports and OSHA 300 reports for specific incident cases.
• Long wait time in processing: Admins need to be informed about the reports process, but often a lack of communication and updates after it is submitted occurs.

I enhanced the system's trust, readability and accessibility through visual design tokens.

I worked closely with my partner to unify the nursing staff's portal view by harmonizing icons, language, colors, and components, ensuring consistency across the system's interface.

By using an official WCAG color contract checker tool to check the accessibility of interface's background color and content font color, I improved the readability of key data points in the software.

‍

‍

Viewing submitted reports and monitoring the progress of incident report cases can be an overwhelming task due to the sheer volume of information and the need for consistent oversight.

A well-organized reports page that displays a table of all reports can significantly reduce administrators cognitive load and improve the oversight of submitted accident reports

By incorporating filtering controls, this solution ensures users can swiftly locate the reports they need, facilitating a more streamlined and efficient process for tracking and managing incident cases.

Maintaining awareness of accident cases for each team member and overseeing their well-being presents a substantial difficulty, as it requires constant vigilance and the capacity to respond to issues as they arise.

Enhancing the software to prioritize team communication can help administrators stay updated on staff members' well-being and accidents

By enabling admin users to swiftly connect with their employees, this approach not only facilitates immediate attention to any concerns but also fosters improved trust within the team.

Nurse administrators are faced with the demanding task of managing their daily responsibilities while simultaneously keeping tabs on newly reported incidents, a challenge that can be overwhelming due to the complexity and volume of information.

Implementing a notification center and a reminder feature can help nurse administrators manage their daily tasks while keeping track of newly reported incidents

By simplifying the managerial tasks of nursing administrators with daily notifications and check lists, they can efficiently handle their tasks and stay informed about new incidents without getting overwhelmed.

I've learned that when developing data-intensive products, it's important to understand and manage both data inputs and the system outputs.

In this design process, I needed to recognize the types of data entering the system and the various scenarios that could affect this data and anticipating issues that might disrupt user's workflows to ensure that users can navigate and interact with the system efficiently.

Collaboration and Feasibility:

‍If I were to revisit this project, I would go out my way to collaborate with developers, security experts, and health SaaS experts to discuss the feasibility of the system. It would've been important to know if my proposed solution was technically viable, secure, and scalable.

User Testing and Feedback:

‍Due to time constraints and the nature of this student project, feedback was primarily focused on the overall UX of the system from my professor and grad student peers. Ideally, I would have liked this solution to be tested with real nursing administrators to gather more practical insights and make further improvements.

Low levels of health care work related accident reporting is caused by a lack of staff awareness and the rigid accident reporting process.

Nurse admins tend to be unaware of accidents that happen in the workplace and tend to be less informed about preventing work-related accidents. Often low levels of reporting accidents is due to factors such as long process time of OSHA 300 reports, unreliable documentation, and the need to stay in HIPPA compliance.

Navigating ambiguity to design a simplified reporting system to improve transparency in the error reporting process.

Understanding the current reporting process was essential to empathize with the roles involved in tracking an OSHA 300 report in a Nursing home organization. This empathy drove the design of a B2B SaaS solution aimed at simplifying the process while ensuring accuracy and compliance.

In 6 weeks, my responsibilities included:

Week 1: Conducting extensive secondary research and developed a comprehensive design brief to understand challenges faced by healthcare staff.

Week 2-3: Translating pain points into system goals and user tasks and facilitated team brainstorming sessions.

Week 4-5: Creating sketches, wireframes, and prototypes for 11 user flows for features like the dashboard, report repository, profile settings, and communication tools. Conducted design review sessions.

Week 6: Iterating on designs to address any unsolved challenges and optimize the solution and designed micro-interactions to enhance the prototype.

The existing process for submitting OSHA 300 reports is lengthy and complex.

To understand the current landscape of incident reporting, I reviewed academic articles and industry reports. I learned that the existing process for submitting OSHA 300 reports often taking up to 30 days to turn an incident into a case. I created a user journey map of the reporting process to accurately understand where an admin responsibilities plays into each step in order to find the biggest bottleneck to a case closing.

This research highlighted key challenges:

• Privacy Concerns: Employers must balance accurate logging with protecting employee privacy, sometimes needing employee consent to disclose identifying details.
• Busy Schedules: Healthcare workers are often too busy or overwhelmed with their other responsibilities to report incidents promptly.
• Long Turnaround Times: The extended process of closing OSHA reports discourages timely and accurate reporting.

Maintaining awareness of accident cases for each team member and overseeing their well-being presents a substantial difficulty, as it requires constant vigilance and the capacity to respond to issues as they arise.

Enhancing the software to prioritize team communication can help administrators stay updated on staff members' well-being and accidents

By enabling admin users to swiftly connect with their employees, this approach not only facilitates immediate attention to any concerns but also fosters improved trust within the team.

Nurse administrators are faced with the demanding task of managing their daily responsibilities while simultaneously keeping tabs on newly reported incidents, a challenge that can be overwhelming due to the complexity and volume of information.

Implementing a notification center and a reminder feature can help nurse administrators manage their daily tasks while keeping track of newly reported incidents

By simplifying the managerial tasks of nursing administrators with daily notifications and check lists, they can efficiently handle their tasks and stay informed about new incidents without getting overwhelmed.

Pinpointing key players in the reporting process

I found that Registered Nurses (RNs) frequently initiate accident reports, while roles such as the Assistant Director of Nursing (ADON), Director of Nursing (DON), and administrators are responsible for reviewing and converting these reports into cases.

Understanding these multiple roles and touch points highlighted the necessity for my solution to be versatile and accommodating for not only the tracking of accidents and staff but also the submission of relevant files as needed.

Designing a software for multiple roles

My partner and I collaborated to create a comprehensive site map in order to map out the system requirements and features we came up with for the robust system that includes tools for incident management and improves team communication. I then defined key assumptions to ensure the system met the needs of all users and streamlined the reporting process while remaining compliant with HIPPA regulations.

Key design assumptions included: ‍

• Role-Based Customization: Dashboard data are to be customizable based on the logged-in user's role (e.g., admin staff vs. nursing staff).
• Priority Organization: Reports and cases are automatically organized from low to high priority based on the type of incidents recorded.
• Case Management: Reports are entered by nursing staff and must be manually converted into open cases by admin users.
• Real time updates: the incident reports in the system is updated in real time.

Prioritizing use cases for Nurse Administrative roles

Given the constraints of time and resources, we decided to concentrate on the Nurse Administrative roles—those responsible for monitoring and reviewing incident reports in order to address the most critical pain points impacting reporting success.

Key pain points:

• Awareness and monitoring: Admin staff need to be constantly aware of issues within their department and track the number of incidents reported.
• Reporting duties: Admins must review and create workers' compensation reports and OSHA 300 reports for specific incident cases.
• Long wait time in processing: Admins need to be informed about the reports process, but often a lack of communication and updates after it is submitted occurs.

I faced the challenge of presenting key information in a limited layout without overwhelming users with excessive data.

I was tasked with addressing 25 software requirements for this project but my focus was on designing solutions and user flows for critical tasks within the home dashboard, accident reports page, cases page, employees page, user settings page, and staff messaging page. It was essential to showcase relevant information clearly and concisely across all screens.

Key user tasks:

• View assigned cases: Users can view and filter assigned cases by progress status and date.
• Monitor staff activities: Users can view staff members' work status, accident reporting activity, and message them directly.
• Monitor open cases and submitted reports: users can view current, closes and pending cases and review recently submitted reports at a glance.

There are significant concerns regarding the security of incident reports, emphasizing the need for a platform that can safeguard sensitive information effectively.

A secure profile management feature that lets users update their profiles and use industry standard verification methods can greatly reduce security concerns and protect sensitive information

This design decision can not only addresses privacy and data protection concerns but also reinforces the integrity and confidentiality of incident reports, ensuring a secure environment for all users.

I aimed to create a dashboard and reporting that delivers precise data to users that they would want to see in a clear, non-overwhelming manner while also being customizable for each user and their specific need.

I created wireframes of the solution to address the lack of awareness in company wide incident reports. To improve report transparency, the dashboard must have  an overview of the amount of reports being reporting by specific time periods, monthly incident report trends, and easy access to attend to open cases that are high priority, features to easily track their daily tasks.

[wireframes and sketches]

‍

I enhanced the system's trust, readability and accessibility through visual design tokens.

I worked closely with my partner to unify the nursing staff's portal view by harmonizing icons, language, colors, and components, ensuring consistency across the system's interface.

By using an official WCAG color contract checker tool to check the accessibility of interface's background color and content font color, I improved the readability of key data points in the software.

Nurse administrators are not aware of company wide incident report analytics that may inform action items that need to be taken to move the process of case.

To improve report transparency and efficiency for nurse administrative staff responsible for monitoring and reviewing incident reports, the dashboard needed key data analytics such as overview of the amount of accident reports, the frequency of the reports, and the overall yearly and monthly trend of the accidents occurring in order.

To help new users recall and understand key information, I included tool tip micro interactions and considered best UX practices for dashboard design.

Dashboard design calls for prioritizing the data elements by location so I placed most important data at the top left and incorporated checklists in the dashboard interface to aid improving user's memory of important information.

‍

‍

In the end, a comprehensive system was created to support nursing administrators in their daily tasks and provide them with easy solutions to keep up with accident reporting.

Metrics I'd love to measure are:

• Efficiency: If the streamlined user flows and optimized dashboards can enable faster and more accurate reporting, reducing the time spent on administrative tasks.
• Accuracy: if features like case filtering and detailed staff profile views can ensure that all relevant information is accurately recorded and monitored.
• Engagement: If enhanced communication tools and notifications keep can keep users informed and connected, promoting better collaboration and oversight.

Low levels of health care work related accident reporting is caused by a lack of staff awareness and the rigid accident reporting process.

Nurse admins tend to be unaware of accidents that happen in the workplace and tend to be less informed about preventing work-related accidents. Often low levels of reporting accidents is due to factors such as long process time of OSHA 300 reports, unreliable documentation, and the need to stay in HIPPA compliance.

Navigating ambiguity to design a simplified reporting system to improve transparency in the error reporting process.

Understanding the current reporting process was essential to empathize with the roles involved in tracking an OSHA 300 report in a Nursing home organization. This empathy drove the design of a B2B SaaS solution aimed at simplifying the process while ensuring accuracy and compliance.

In 6 weeks, my responsibilities included:

Week 1: Conducting extensive secondary research and developed a comprehensive design brief to understand challenges faced by healthcare staff.

Week 2-3: Translating pain points into system goals and user tasks and facilitated team brainstorming sessions.

Week 4-5: Creating sketches, wireframes, and prototypes for 11 user flows for features like the dashboard, report repository, profile settings, and communication tools. Conducted design review sessions.

Week 6: Iterating on designs to address any unsolved challenges and optimize the solution and designed micro-interactions to enhance the prototype.

I've learned that when developing data-intensive products, it's important to understand and manage both data inputs and the system outputs.

In this design process, I needed to recognize the types of data entering the system and the various scenarios that could affect this data and anticipating issues that might disrupt user's workflows to ensure that users can navigate and interact with the system efficiently.

Collaboration and Feasibility:

‍If I were to revisit this project, I would go out my way to collaborate with developers, security experts, and health SaaS experts to discuss the feasibility of the system. It would've been important to know if my proposed solution was technically viable, secure, and scalable.

User Testing and Feedback:

‍Due to time constraints and the nature of this student project, feedback was primarily focused on the overall UX of the system from my professor and grad student peers. Ideally, I would have liked this solution to be tested with real nursing administrators to gather more practical insights and make further improvements.