Timeline Redesign

 

Overview

As a care manager, I need to track care plan changes and write notes to describe a clinical encounter in one place.

My Role

  • Research:

  • Wireframes:

  • Prototypes:

Overview

As a care manager, I need to track care plan changes and write notes to describe a clinical encounter in one place.

Problem: Before the redesign of the care plan, users had to open a timeline event in order to access the care plan at all. I had to figure out how to let users access the care plan at all times and track what they’re doing in the care plan and link those actions to timeline events.

We had to deliver quickly during our first iteration so we tried to reduce the amount of inputs needed from our users and keep as much of the current functionality as possible. With such a new concept and tight turnaround, we built in time and made it a priority to respond to feedback in the next release.

After hearing from our clients, we spent the second iteration focusing on locking notes so that they become a part of the permanent medical record, making it so that users can write  a note without having to click a button to do so, and really improving the reschedule workflow to more easily add and report on attempts to contact patients.


Approach:
Relying on knowledge from my first site visit, I sketched some wireframes which also included user scenarios and alternative options. Since I was still new, this helped to visualize the UI, but also get validation on my assumptions of the user’s workflow and intentions. I then explored options with my team, designed, prototyped the solution, and used a journey map to articulate all the scenarios a user could go through and make sure we covered everything.

In the second iteration, we were able to do some concept validation with multiple clients around locking notes and will be doing more validation around rescheduling events and billing workflows in January 2019.




 

 
Dandelion.001.jpeg

Approach

In two weeks, I found, studied, and interpreted curriculum data in government sites, district websites and blogs to push the previous design.

Problem: …
Solution: …

Deliverables: While “Timeline event redesign” sounds pretty straightforward, there were a lot of elements to it which had to be improved to deliver this experience. I created a journey map, decision map, prototypes, and concept validation videos for research (denoted with *)

  • Tracking care plan changes

  • Add & edit event details

  • *Billing workflows

  • Re-assigning to another user

  • Documentation events

  • Auto save

  • Filtering

  • Notes tab

  • *Locking a note

  • Logging attempts to contact patient

  • Needs review” permissions

  • Event statuses & reporting

  • Who performed the last action

 

 

Learning Progressions

I attended a workshop with SME's where I discovered that learning progressions show Jamie where a student is having trouble and - why. We would need to create a model that used learning progressions so that Jamie could view prerequisite standards in prior grade levels to determine where a student first started having trouble and begin re-teaching from there. 

Outcomes: Jamie thought the "Dandelion" was overwhelming, so I needed to figure out how to make this design more simple.

  • This workshop included a representative from design, development, delivery, offering management, data architecture and data science - half of which I had no idea existed before!

  • I created a design that would show Jamie her students' knowledge levels and how they build on one another and what the root cause of the problem was.

  • I met the data team halfway by researching and piecing together and mapping out learning progressions from the Texas Curriculum..

 

 

Simplify the Data

After months of struggling with this problem, I finally received help and support from Elayna Spratley who brought a new perspective and saved me from having to go it alone. We constantly updated and tested the data we were showing on cards to identify what was important enough to show because we didn't want to put too much cognitive load on our teachers. 

Outcomes: Jamie could get a quick overview and investigate, but she still had no context of when a standard should be taught.

  • We told Jamie what she needed to know instead of giving her a graph she needed to figure out.

  • When we tested this option, the teachers realized they really needed the ability to prioritize the standards they see, otherwise they would be overwhelmed. They teach standards in groups and it would be nice to understand which standard should be taught first, or which standard will give them the most trouble ahead of time.