Health Everyware
•Download as PPTX, PDF•
6 likes•882 views
The HIMSS Mobile Design Workgroup is crafting a common sense set of mobile design best practices, specifically tailored for the health market. These exemplars of effective mobile design will serve as an open blueprint that arms engineers, visionaries and designers around the world to craft highly usable and desirable health applications for the various, evolving mobile platforms. In addition, the design patterns will be showcased in a mobile health prototype called hLog (currently on the iPhone platform). This will be used to illustrate, in practical and applied terms, just how these best practices translate into truly remarkable mobile health services.
Report
Share
Health Everyware
- 1. Health EverywareMaking Mobile BeautifulHIMSS Usability WorkgroupJuhan Sonin3.Feb.09
- 8. Ouch.
- 9. We need a simple set of design best practices that … takes a system approach to design…. accelerates good software behavior and interface design pattern adoptionGuidelines will cover: interaction and behavior models,graphic design (including layout, grid, color palette, type and naming conventions),information architecture,technical implementation
- 10. MOBILE DESIGN TENETSLet data screamOnly handle information onceGrid itType less + less typeColor carefullyDate your usersSpeak my signWhat interface?Repeat customers ROCKGet physical
- 11. MOBILE DESIGN TENETSLet data screamOnly handle information onceGrid itType less + less typeColor carefullyDate your usersSpeak my signWhat interface?Repeat customers ROCKGet physical
- 12. Let data scream
- 13. Envisioning Information, E. Tufte
- 17. and the Problem is…Increasingly complex systemsTool and Methodology gapDecision makers are swamped with conflicting dataOur work is increasingly multi-dimensional (not a flat-decision space)Artifacts driving decisions need to be coordinated, presentedMinimal transparency into key health metrics
- 18. How do I (as a patient, nurse, doctor, proxy)make quicker, more accurate decisions?
- 25. Ink and lines screamData disappearsViolates all 5 Tufte principles5 principles produce substantial changes in graphical design:Above all else, show the data.Maximize the data-ink ratio (i.e., the % of ink that shows data)Erase non-data ink.Erase redundant data-ink.Review and edit.
- 29. UnreadableGrid >> DataData as Interface… NOT
- 33. 38%
- 35. 25%20%
- 36. 70%
- 37. 80%
- 38. 80%of the screen space should be for data, the actual workspace
- 39. Let data screamThe data is THE storyLess ink, more bang80% rule
- 40. What interface?
- 41. Over time, you don’t notice the interface
- 43. 50%
- 45. Manipulate the data, not the interface
- 46. What interface?Over time, you don’t notice the interfaceManipulate the data, not the interface
- 47. MOBILE DESIGN TENETSLet data screamOnly handle information onceGrid itType less + less typeColor carefullyDate your usersSpeak my signWhat interface?Repeat customers ROCKGet physical
- 49. When will we see stuff?
- 50. Reference implementationDemonstrate a prototype… then grow advocacyLooking for participation from mobile developerPublic Wikito house UI guidelines, and allow citizens of planet earth to evolve, draft v1 by 4.Mar.10
- 52. HIMSS Celltop Design WorkgroupScott LindJaney BarnesPaul KroftEric MillerRon RibitzkyBruce SklarJuhan Sonin, juhan@mit.eduAlbert VillarinHIMSS CoordinatorsEdna BooneJuanita ThreatAdvisors, ReviewersJeff BeldenDirk Knemeyer
Editor's Notes
- We're all here because the future of health = mobile. I'm here to tell you: that is not nearly enough!
- Is a chair a chair if no one wants to sit in it?Slide credit: designer = HannesGrebin
- For kids and adults under 60, try a fat boy.Practical, light, conforms to many body types, comfortable, multi-use.Pictured here is the FatBoy bean bag w/Udo Sonin, Luka Kirigin, Juhan Sonin
- Is a car a car if no one wants to drive it?The hopped up Gremlin. Only way you’re getting me to take it: pay me $5k to drive that away.Slide credit: therogue (flickr)
- This Bugatti transcendscar-dom. This is an object d’art, inspires other products/ideas, is lovely to drive… you become an apostle.Bugatti Type 57 Atlantic 3… in 1938!
- Apps pictured: Rapid STEMI (left), Stroke Index (right)
- Create a LIGHTWEIGHT celltop health services design pattern library, UI guidelines documentHarmonize the behavior, aesthetics, layout, interaction, and feel across health apps
- Now find the patient.Straight-forward to find.Data screams.
- What’s more important? The UI or the Stroke or Glascow Coma scale results?The Paint vs Data.
- This table is from Wikipedia… and it’s more readable than an app designed just to display this information.And Wikipedia isn’t exactly known for their design… but they are known for their Design.
- What’s more important? The UI or the Stroke or Glascow Coma scale results?The Paint vs Data.
- In contrast to the previous example, the user interface takes a backseat… while the data is front and center.
- Grid lines, labels, UI elements are secondary… they fade into the background because they’re designed to (with smaller, lighter text compared to the data + grid lines are there to help the eye and are light grey, etc).The data pops… as well as the micro trend graph.
- ARDMS Ultrasound Exam app.
- Unreadable labels/global optionsRandomly placed buttonsGrid and labels are same visual priority as dataNo practice exam data… how about an action that allows me to take one, add one, import one. SOMETHING other than that.The data should be part of the manipulation game. Why have 4 options listed and I need to swing down another part of the UI to select one of those options? Make the options selectable.
- Slide credit: Brian Staats
- Slide credit: Brian Staats
- Slide credit: Brian Staats
- App = Tempted by Frog Design (shown here at Pop!Tech 2009)
- Not to mention the data part of the screen is only using 50% of the available real estate….
- Now find the patient.Straight-forward to find.Data screams.
- So those are three important tenets to help design beautiful services. If you are interested in the rest of the tenets or want to take a class, just get in touch with the group. Bottom line: we can't just slap stuff out there for "mobile" and think that will get it done. We need to create things that are usable, that are beautiful, that people enjoy and even look forward to using! Our challenge as people in the industry is to INSIST that the services that we are part of creating or that are created for us are beautiful. Why? People will use them. When people use them, practitioners will embrace them. When practitioner's embrace them, the system will subsidize them. If we have a healthcare system subsidizing beautiful services that practitioner's embrace and people love and use all the time, suddenly we have a peaceful revolution. And it is not a revolution of signing bills on capitol hill or doing other high- profile things. It is a quiet revolution where the care and passion of a few can change the lives of many. It is a revolution that can make lives better, and be led than you and me. My only question to all of us is: why on Earth aren't we busy doing it already?
- The original equation needs to be amplified… to include design, business, technical, behavior, and impact vectors/constraints