HH OASIS Mobile App is a companion tool to Decision Health's Home Health Coding Center SaaS tool.
I was responsible for creating a mobile user interface for iOS and Android with reference to high level requirements documentation. I also created further assets and branding materials for the length of the project.
UI, UX, Mobile App Branding, Email Design, Landing Page Design
Sketch, Symplii, Invision, Illustrator
Pre-Production Customer Feedback,
Live Customer Alpha Testing, Invision
The HH OASIS mobile app was intended to meet the needs of nurses on the go. Specifically, Home Health nurses that are required to submit reports measuring home health care quality. What is an OASIS code? Well, to put it better than I can:
"The instrument/data collection tool used to collect and report performance data by home health agencies is called the Outcome and Assessment Information Set (OASIS)."
Since the data set these nurses are collecting is used to measure the quality of patient care, to fulfill insurance reimbursement, and to ensure many other Medicare/Medicaid standards, the information itself was important for the nurses to be accurate with. However, the M-Items themselves can be quite complex, and contain extremely similar codes, with the most subtle of differences.
This sort of complexity begged the need of a way for nurses to reference something more than a guidebook, or even more than clunky, outdated (quite literally without new code updates) websites.
Decision Health's team did a LARGE amount of work preparing scope and high level documentation very early on in the project, way before I was brought on to help. The purpose of their original documentation was to seek approval from stakeholders, while also outlining the necessary steps, estimated budget, and time frame for the project moving forward.
Once the project was approved, further documentation was created to describe each screen as well as the current user flow for the website. Since they currently had a web-based tool available to 4,375 users, they had a significant brand-standard that their users were familiar with, as well as an expected experience while using the product.
Using all the information available, we had had a launching point for me to get involved at. I poured through the entirety of the documentation and met with the team to describe the project, walk through interactions, and to talk through potential problems that I could see us running into, especially since the information we were presenting was so dense.
We still found it somewhat necessary to be able to quickly navigate in several ways throughout the app, but we were very hesitant to implement actions such as swipes and sliding menus without a way to inform the user intelligently. The Mitems were especially requested from users to be able to swipe between, since they tended to use a few similar ones in a row. This, being information we didn't understand before, was certainly something we added as small header bar up top.
Essentials to Success:
• Get the user's attention quick
• Quick/relatable content
• Subtle branding
• Above the fold matters!
• Build simple designs
• Everything is basically a box
• Images are a LUXURY
• Most people won't even scroll