Started With An Identity Crisis
Too Many Options I started today off by reviewing Rebecca and Evan's blogs. I figured it would be nice to catch up on what they have been up to and learn from what they discovered, From Rebecca I learned everything Hep C. There is no doubt in my mind that within the next few weeks she will have the knowledge necessary to be considered a regional expert on the virus! Reviewing Evan's blog, I really enjoyed his link to the Health Design Challenge that showcased innovative new ways to design electronic medical records.
As I scrolled through some of the winning designs, I began to second guess an earlier decision. When first designing the home screen, I realize that the app can be created in one of two ways. It can be designed for inputting information (how I have been working so far) so the primary purpose for a user is to record information. Or it can be designed as a an app that presents information, and simply notifies a user when and where they need to update their inputs. As I looked at these Electronic Health Records, I felt that it is too difficult on our app for users to get to their information. We constantly ask for information but do we take the information and provide something with obvious value to the patient?
I began mocking up designs of a new home screen to replicate what I saw for the electronic health records.
As I scrolled through some of the winning designs, I began to second guess an earlier decision. When first designing the home screen, I realize that the app can be created in one of two ways. It can be designed for inputting information (how I have been working so far) so the primary purpose for a user is to record information. Or it can be designed as a an app that presents information, and simply notifies a user when and where they need to update their inputs. As I looked at these Electronic Health Records, I felt that it is too difficult on our app for users to get to their information. We constantly ask for information but do we take the information and provide something with obvious value to the patient?
I began mocking up designs of a new home screen to replicate what I saw for the electronic health records.
As I began thinking up different ways to portray information, I was having trouble deciding which information is most important to include. I realized the patient report card was the summary I was trying to produce and so I shrunk down the picture from the grant and opened it up on my iphone.
The screen was too crowded; a big NO-NO in home screen design. While everything fit and was legible, the screen could not function as a "terminal leading to information inputs." I settled down. For now, it will have to be fine that the information is two clicks away (About me --->My Charts--->). Identity crisis over and time to move on.
Next, I began reviewing the designs that I have so far and attempted to go deeper into the app. I drew up sample screen shots for the "my care" and "resource utilization" components of the app. While I knew from the start that I would not have enough information to complete these pages, I am happy I explored them. I gained an understanding of what decisions need to be made to complete these deeper layers of the app. Do we want to have our Users undergo a large scale data extraction or do we want to ask the minimal amount of questions-just enough so we can fill up the patients report card?
No matter how we answer the question, we will have to decide what the "minimal" or "crucial" questions" are so that I can mock up the final screen shots.
No matter how we answer the question, we will have to decide what the "minimal" or "crucial" questions" are so that I can mock up the final screen shots.
RSS Feed
