Initial Notes and Ideation:
I wanted to be as transparent as possible in the way that I work. I usually start out by jotting down everything that is of like category which allows me to visualize patterns and understand how to tackle the UI.
Wire framing and Layout:
The next step I usually like to do is understand user flow and sitemap the product. After that I jump into the wire-framing portion of the project and begin to flesh out some of the sketches that I had done above.
Taking the wireframe and layout elements and bringing them to life is the next step. At this step of the process I usually allow myself to be fairly agile and adjust to certain layouts as most problems are found at this stage.
I wanted to create a portal-like system that both the Nurses and Physicians could use. The front end check in desk would sign in the patient (or the patient on their own) while the Physician would be able to log in and see her appointments for the day. By doing this it allows both the Nurse and the Physician to see what patients still need data to be entered.
Collection Phase (Bottom Right):
I broke down the narrative/brief into a six part process so that the patient can follow along with the Nurse as they enter in the relevant, needed, information. Ned T. Helm is the active profile using this page and is walking through Marsha’s profile with her.
Ned is given indicators with each section that allows him, at a glance, to see what he needs to enter in or adjust with Marsha’s profile.
Invalid Entry Error
It looks like Ned is entering a new event for today under Marsha’s Medical History tab. However, it looks like he used an invalid date so when he went to save the system gave him an error.
Ned would like to add some recent medication that Marsha has been on. Since the infrastructure is tile based he can simply click on a new tile to enter in new data. Once Ned feels that he his finished updating Marsha’s profile he can save and submit it. This sends Patty (our physician) a notification that Ned is complete with his steps.
Physician to Patient
In comes Patty L. Kay (our physician). Her job is to quickly review and assess patterns in the patients history.
When Patty logs into her account and opens up her patient she sees that she has some notifications that appear in the top of her screen. This is where all the important information is. Before beginning, the system validated all the data that Ned entered and tracked it for patterns. It also noted that Marsha has a latex allergy so Patty knows this before making contact with her. It looks like there has been an anomaly detected within the medical history. Marsha is complaining about lower hip pain. However, there is also a pattern that has been detected in her medication dosage. Marsha is taking more medication than is prescribed which is nulling the obvious pain that she is now feeling in her hip - this is not solving the problem. Patty’s actions Seeing these notifications, Patty can assess whether they are serious or not. If she decides to do more digging she can see multiple patterns ontop of eachother (shown in image) and how they correlate. If she agrees with the notifications she can close out of them. When she feels that she is finished with her assessment she can submit it and continue onto her next appointment.