Redesigning patient scheduling and management for nurse coordinators
How might we provide a calendar view of case days and facilitate not only scheduling but also task mangement of cases via the calendar?
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
This work sample is about optimization of workflow management software in digital health.
Hawkeye is a web-based product whose customers manage the patient journey from post-referral through post-procedure milestones.
The product’s primary users are nurses who coordinate AFib therapies within cardiovascular programs supported by Hawkeye.
As lead designer, I collaborate with my peers and conduct design activities in pursuit of viable solutions.
We operate on a balanced team model (à la the product trio) with continuous discovery and regular user check-ins.
Medical procedures are referred to as cases. For any day on which a case is scheduled, that day is a case day.
Hawkeye launched with case day scheduling functionality but the MVP feature required the end user to first 1) select a day and the number of cases for that day, and then 2) select patients for the resulting day and empty case slots.
The experience was suboptimal in that it led with abstract rather than purposeful scheduling—nurses do not schedule sets of cases so much as they schedule individual patient procedures.
Additionally, the original experience lacked a calendar view and provided a relatively static list of cases.
From continuous discovery we learned that our customers wanted 1) improved means to schedule individual procedures, 2) improved means to manage cases, and 3) a calendar view à la Outlook for scheduling cases and other patient touch points.
Providing calendar functionality is straightforward enough but like any general ask, the result can differ from what was originally envisioned.
Hawkeye’s first iteration was in part understandably built without detailed requirements, whether in the form of business rules or functional specifications. My first step was to not redesign the existing functionality but rather, clarify the requirements underlying that feature.
I then looked at obvious examples, specifically Apple Calendar, Google Calendar, and Microsoft Outlook and for our purposes crafted the best thereof in coordination with our lead engineer.
With a design system already in place, I augmented that system with components appropriately and then tested high-fidelity wireframes with real users.
As far as challenges go, the addition of a feature to the initiative pushed our timeline but proved to be worthwhile.
Cases are about patients and although the type of attributes for each case is the same, the patients vary. We learned from our research that nurses attach notes, typically stickies, to cases as they schedule them. Notes in this context are invaluable for they serve as reminders to everyone.
Similar to the existing case days functionality, Notes was a legacy and rudimentary feature. So, per the strategy above, I clarified requirements and proceeded accordingly.
Users can now effortlessly manage cases within a calendar and also manage tasks per patient in the calendar for seamless efficiency.
Calendar functionality was a long desired feature by users who manage multiple applications.
"AWESOME updates!!! Love it! Great work team :)."
—Nurse Coordinator
Within 24 hours, the first case was scheduled using the calendar.