• Scenario
  • Individual design sketches. Each group member should post three of the design sketches they made, along with a few sentences of description for each one.
  • Designs and storyboards
  • Analysis for each of your storyboards

Scenario

Mary is a 70-year-old patient who has type 2 diabetes and high blood pressure, and recently she fell down stairs and broke her leg. She visited her family doctor for all these problems.  The doctor gave her three different medicines to take: red pills for diabetes that she needs to take before every meal; blue pills for high blood pressure that she needs to take before going to bed everyday, green pills (pain killers) for her broken leg in the morning and in the evening. In addition to that, she needs to stretch her leg every day. After the doctor left, she completely forgets the instructions the doctors give to her. She needs to remember the time to take the medications and the doctors need to know whether she has forgotten any.

Individual Design Sketches

  • Jason Yonglin Wu

 

  • Fang (Elaine) Han

  • Yi-An (Morgan) Lai

  

  • Ty Lin 



Designs, Storyboards and Analysis  

  Design 1 

   Storyboard

During her appointment, Mary added all the new medications that the doctor told her to take onto her app right after the doctor gave her the instructions. The app also allows Mary to write down some notes if needed.

It's time for Mary to take her daily vitamin. The app sends out an alarm on her mobile device to remind her. Mary can click "check-in" after she finished taking her medicine or click "snooze" if she wants the app to remind her again 10 minutes later.

Mary can also look at her medication history and future schedules if she opens the app. There will be check marks next to medicines that she has taken on time. If she missed any of her medicines or the medicines were taken at the wrong time, they will be shown in red font on her med calendar.
Mary can also add medications to  her calendar by clicking a time slot and the previous "Add Medication" screen will show up. This is useful if she has taken any over the counter drugs and wants to report to the doctor.

The doctor will have access to all of her patients' medication record on a web application. When she opens the web, there will be notifications on the corner of the screen to indicate abnormal patient activities.

The doctor can look more into details of a particular patient. She will see all of the patient's medications history in a calendar. She can click into a particular day to see the patient's progress for that day. Dates marked with red indicate that the patient has incorrectly taken or missed his/her medication for that day. If the doctor clicks the "Message Patient" button, she will be able to send the patient a message that will show up on the patient's mobile app.

  Analysis

        This user interface focuses the users who doesn’t mind spending time on the app and wants some customizations. The app would be most useful for people who has experience with websites/ mobile apps.

     Learnability

  • The google calendar style user interface makes it very easy to learn for those who are familiar with calendar applications, such as calendar on mac on google calendar.
  • “add new medicine” uses a form, which is also very commonly uses and that helps the users to learn.
  • The way to record taking a pill is by checking the box next to the medicine. It is not very obvious for a novice user so it decreases learnability.

     Efficiency

  • When adding a new medicine, the forum will pre fill in the date and time with the last taking medicine. So if the user wants to add multiple medicine that has similar characteristics, it will be very fast.
  • The “notification” for the doctor makes it very easy for doctors to see which patients have failed to take their medicine correctly, so that the doctor doesn’t check on them on by one.
  • The calendar with highlighted dates, again, allows doctors to go to specific date the user has missed medications instantly.

     Safety

  • When a user enters a medicine that they don’t want, it’s easy to edit and delete it.
  • Since we introduce the functionality of adding medicines that the user has, it is easy to confuse them with the ones the doctor has given to the user
  • When a user accidently click “soonze” instead of “check”, he can instantly corrects his mistake by checking the box next to the medicine in the main interface, but he might think that the only thing he can do is to wait for 10 minutes for the pop up to show again, which can be inconvenient.
  • Overall, this is not a very safe user interface since it has many different options and functionalities

  Design 2

   Storyboard


When the patient click on the app, it will show a list of the drugs that are yet to be taken. Once the drug is taken, the button will disappear. This design is mainly for old user so we don't want
to overwhelm our users with many features. The users are only allowed to log out and click on their profile. When they click on their profile, they will see the list of drugs.


The app will send notification to the users to remind them to take the pill. If the users click on "Remind Me Later" button, the app will send a notification again after 5 mins.


When the doctor search the for the data of the patient, a list of drugs that the patient is currently taking will be shown on the left hand side. The calendar will highlight dates when the patient
misses the medication. On the right hand side, the column is a list of details of patient's missing medication history. 


When the doctor click on "Edit Medication," it will bring the doctor to another page where the doctor can add new medication for the patient. The doctor will be able to add the medication and
the app will synchronize the update immediately with patient's app.

   Analysis

This user interface focuses on users who knows little about new technologies, forgets things very often, and need frequent notifications and clear signs to remind them to take drugs. It has minimal functionality on user side to prevent from errors.

     Learnability

  • The way to check off a medicine is to click on it. This might not be obvious for novice users, but they will know as soon as they try it.
  • This UI is very easy for the user to learn- it only has one main screen and a pop up window. User is very unlikely to get confused when he/she uses the app for the first time.
  • Like the patient interface for Design 1, in this design, there is a form for the doctor to use, which is easy to learn

     Efficiency

  • The user only needs to click once to confirm taking a medicine.
  • There is not a good mechanism for doctor to add multiple new medications (which may have very similar date and time) at the same time, which is not efficient.

     Safety

  • If a user accidently click a medicine when they intend not to, it just disappear and there is no way to bring it back.
  • The application does not check if the user takes the medicine at the right time. For example, if at 3pm, a user clicks on a medicine that is supposed to be taken at 6pm, it will get checked off as well. In this case, a user can cheat the system by clicking away all the medicines at once.
  • The medicine buttons are located near each other and it is easy to accidently click on the wrong medicine.

  Design 3

   Storyboard

    Analysis

This user interface is intended for users who are most self-sufficient, depends less on the application, keeps track of his/her time well. The user mainly uses this as an information board and logging tool.

     Learnability

  • "Taking pill” process is harder to learn in this design, as it doesn’t give very obvious feedback.
  • There are not many options or functionalities, so a user can learn the interface fairly quickly.

     Efficiency

  • The user only needs to click the button once to take the medicine.
  • This user interface is especially useful to check the dosage and time of a certain drug. In a calendar or “list by style” representation for medicines, it is not easy to look up the usage of on particular drug. While in this design, it is very obvious.

     Safety

  • When a user click the wrong button, there is no going back.
  • It is very dangerous to make mistake in this user interface, since the mistake not only affects the current medicine, but the time of the next medicine as well. The user has to be very skilled to use this.
  • No labels

1 Comment

  1. Scenario: Good motivation in the scenario, though it would have been good to give a clear and concise description of the tasks the patient/doctor would be going through in the usage of the system.
    Individual Designs: There was a good variation of designs across the various members, however, there were some designs which were very simillar in terms of the interaction a user would be engaging in when using the system, so some more variation would have been better there. There could have been more stretch in the designs, aside from the mobile interface.

    Storyboards: Great work in synthesizing the best portions of the sketches into your storyboards! Clear descriptions accompanied the designs, so it was easy to see what was going on with each screenshot. It was great to see the mobile/desktop mixed design make it as one of the finalized designs, particularly with its refinements. As mentioned earlier for the individual designs, some stretch in the designs would have really benefitted from outlining the stretches made for the designs (e.g., illiterate users, ultra-efficient, etc.) Also, the analysis for each esign could have benefitted from being very explicit in applying the concepts that we've learnt from class (e.g., learning by exploring, internal consistency and external consistency of widgets used compared to those used in other systems, Fitt's law in some UIs, KLM for those that require combinations of key-presses and clicks, etc.)
    Wiki Presentation: The images were too small! I had to manually look at the attachments to view the sketches clearly. Try to make them zoomable next time (like how Elaine did hers.)