Creating an electronic version of a paper medical record is very challenging for the UI designer.
A UX/UI designer has a tremendous challenge when she is assigned the duties of translating a real-world process in to an electronic or digital process. The UX designer must keep the user’s mental model in mind when designing an electronic system.
When working on EMR, or electronic medical records, it is a completely different set up and system than the paper recording method the user has been using. They key to designing a successful EMR, is to closely match the work flow and system that the user is used to. That success has not really been achieved in most EMR systems. Often, software designers get too excited and caught up in the features and flash of digital possibilities. When working on any electronic system, it is crucial to always understand how the user works, and make your system as similar to that work flow as possible.
If you have any suggestions on how to bridge the gap between the real world and electronic world, please leave them in the comments. Thanks!
Wireframes are not for everyone. I understand there might not be time to create wireframes. Some people don’t see the value of this middle step. “Just sketch out some ideas. Once you like something just code it up.” Others may not have it in the budget to create some deliverables.
Wireframes can be created in a variety of programs. I chose Adobe Illustrator to create these first drafts of the dashboard.
I have to admit, I am guilty of not always creating wireframes. To me, they can be a luxury. There are times I don’t really have the time or the patience to go beyond sketches (if I have even created those) to going to the middle step of creating wireframes.
I strongly suggest that if you do have the time, and the budget, that you should make the effort to create some static wireframes. Here are a few advantages of creating wireframes:
Get the concepts out of your head and on to a page/layout
Visualize how your designs might work
Get early feedback on your designs before it goes in to code
Allow for quick changes before too committed to design
Facilitate discussion across the team and with stakeholders
Provides clarity for communication
For developers to understand the functionality of the site
To show the information architecture and navigation structure of websites
Cost-effective level of fidelity for quick changes
Jennifer Blatz explores the world of UX through words and imagery
