Med-Direct
Your AI-driven powered decision support system for William Osler Health System. Utilizes medical directives to streamline ER processes, reduce wait times and overcrowding, and improve patient satisfaction.
Problem Space
Problem Statement
How can we increase patient satisfaction, reduce overcrowding and long wait times at William Osler Health System Emergency departments.
Problem Background
Emergency departments (EDs) have long struggled with managing patient flow due to high demand, especially as patients seek care in EDs when they cannot access timely services from primary care providers or walk-in clinics. Staffing shortages have further worsened these challenges. Notably, wait times for physician assessments in EDs have increased significantly since the COVID-19 pandemic. In 2022/23, patients waited an average of 118 minutes after triage to see a physician, a 30-minute increase from 2013/14. The longest wait times, for patients in the 90th percentile, reached 257 minutes, up from 183 minutes a decade earlier.
This rise in wait times has led to higher rates of patients leaving EDs without being seen. In 2022/23, 5.3% of patients left without receiving care, with some hospitals experiencing rates as high as 14%. One hospital with an average wait time of 175 minutes saw particularly high abandonment rates. The increase in wait times and patient dissatisfaction has become a persistent issue, highlighting the ongoing strain on the ED system. This problem has worsened over time and remains a significant barrier to improving care delivery and patient satisfaction.
Research Insights
User Pain Points
Emergency Department Patients
- Long Wait Times lead to frustration and discomfort.
- Some patients leave without being seen, with some hospitals seeing even higher rates, leading to unaddressed health concerns.
Emergency Department Staff (Physicians, Nurses, and Support Staff)
- Staffing Shortages: Increased patient demand combined with staffing shortages results in higher workloads, stress.
- Difficulty Managing Overcrowding: Overcrowded EDs create a chaotic work environment, making it difficult for staff to provide timely and effective care.
Hospital Administrator
- Operational Efficiency: Increased wait times and high left-without-being-seen rates put pressure on administrators to improve patient flow and reduce overcrowding.
- Financial and Resource Strain: Overcrowding and staffing challenges lead to inefficiencies, placing financial strain on hospitals and stretching resources thin.
Supporting Data
Based on the publication from the office of the auditor general Ontario,
- In 2022/23, patients waited an average of 118 minutes after triage to see a physician, up from 88 minutes in 2013/14.
- In 2022/23, the average patients left-without-being-seen rate was 5.3%, with some hospitals experiencing rates as high as 14%.
- Staffing shortages have increased pressure on healthcare professionals, contributing to difficulty in managing patient flow.
- Increased patient volumes and longer wait times lead to heightened workloads and stress for staff.
- Operational Strain: The rising wait times and 5.3% left-without-being-seen rate put pressure on administrators to address patient flow issues.
Patient interviewees during the primary research stage also provided supporting data indicating their dissatisfaction and frustrations with long wait times. Some patients even went home and returned at a later time.
Feedback
In order to validate the significance of this problem, we conducted patient interviews and secondary research. From the primary interviews conducted 67% of interviewees were unhappy with the long wait times experienced in the ER. They all acknowledged long wait time to be a symptom of a bigger issue in the ER.
Both Primary research and secondary research from the office of the auditor general of Ontario agreed that shortage of nurses and physicians to be one of the major causes of long wait times. Other causes mentioned by the office of the auditor general of Ontario include lack of beds and delays in lab and imaging results.
Landing on the Solution
From evaluating the root cause of long wait times, we came up with 4 possible solutions. Which included: providing dynamic wait times to patients in attempt to divert patient traffic, making use of AI enhanced triage system to reduce work load of tirage nurse, making use of an AI transcribing feature to help physician with documentation and making use of AI powered medical directives.
Based on criteria such as safety, impact and feasibility, we decided to work on the AI powered medical directives
Med-Direct aims to reduce wait time in ER by increasing consistency, safety and reducing delays in receiving lab and imaging results. Which could save between 30 min to 2 hours of wait time. (Typical estimated average times to receive results of medical imaging, and time between nurse assessment and physician assessment).
User Flows/Mockups
User Flow
Mockup
Here is a link to Figma design page: https://www.figma.com/design/F74lEaAq61u9PsFMgpDZyB/Med-Direct?node-id=0-1&p=f&t=JG5xAVGHURtBhDtx-0
Future Steps
From secondary research, I realised there is still room for improvement with ER triage systems which could reduce wait times even further. The potential of clinical decision support system in the ER is huge. Although I chose to explore medical directives, AI powered Triaging could also provide significant improvement and could be incorporated in the hospital information system to make a bigger impact. I plan to explore this area in future projects.
Images
Learnings
Product Manager Learnings:
Albert Odai
My journey with Co.Lab has been incredibly insightful. I thoroughly enjoyed the ideation phase, where I brainstormed solutions to user pain points and continuously refined them based on user research.
I also gained valuable knowledge about LLMs, NLP, and RAG applications. Additionally, I had the opportunity to explore tools like Figma and Claude for mockups, as well as Bolt for prototyping—all of which I found fascinating.
Designer Learnings:
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
&
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.