MobileODT - Web app and admin tools
Type: Healthcare / Medical devices
Role: Lead UX/UI
Platform: Web application
Scope: Product design, Information/Data design.
Timeline: 2015-2017
www.mobileodt.com
“Bringing user management to the user.”
The mobileODT web portal is a suite of tools used by client administrators for user management, data analysis, reporting, and alerts. Administrators can view new cases as they are recorded in the EVA mobile app, as HIPPA compliant documents (patient’s personal information is omitted), and add annotations and messages to the examining nurse in real-time.
Admin portal
Users
User research highlighted two types of potential users.
The main persona for this feature is an Organization administrator. I talked to existing client organization administrators and used them model personas, since they also agreed to be our beta-testers for this feature.
The secondary persona type is a customer-support team member, since they would be providing support for our clients and will be creating profiles for customers as part of their daily work.
Primary personas
Organizational hierarchies
It was important for the product team to understand user’s hierarchy within client organization, in order to assign different permissions, features and profiles types to different members.
Organizational hirarchy and profiles.
The web portal content changes according to the user-type.
Some profiles have the option to view patient details they created in the app, but also provide feedback on other patient’s cases. This called for a creation of permissions system, that block some types of content (mainly P.I.D) from some users in the same organization.
Patient case with annotations - “Profile B”/ own case view
Patient case with a conversation - “Profile B”/ other nurse’s case view
Data tracking and reporting - “Profile C” view
“Case study - “Add new user” feature”
As MobileODT was growing, the company wanted to give more autonomy to clients, and include the ability to add and create user profiles in their accounts.
Challenges
A profile creation process was initially put in place by company engineers without client considerations. I decided to use the existing process as a starting point for the redesigned Profile creation feature. A discovery phase highlighted several usability issues that were to be addressed in the redesign:
The layout and order of actions needed to create a new profile in the system was confusing.
The terminology the developers used was vague and misleading.
Some features were obsolete.
Since the initial workflow was intended for internal propose only, it was created with a raw, schematic interface that created further confusion. The UI needed to be aligned with MobileODT's visual language.
Original UI
Objectives
After user research and observations I defined the wanted outcomes of the redesign:
Profile creations should be a simple, self-explanatory process.
Admins will be able to create several types of profiles for different roles in the organization, and
duplicate profiles if needed.Profile data access will be clear and understandable.
The workflow should work for very large organizations or single user organizations.
The workflow should be modular, and features should be easily added or removed according to the clients' membership plan.
Prototypes
Basic hierarchies were ideated on white-boards. I iterated with wireframes and prototypes to reach my objectives. I tested prototypes with users at different points during the process, using screen sharing tools.
Some of the earlier layouts incorporated "profile presets", but these versions were not implemented in the final release.
Permissions
One challenge I focused on was defining profile access permissions. Setting up the permissions wrong could potentially expose sensitive patient information to the wrong user. Originally, the engineers created a permissions presets list that quickly proved unsustainable - it was too long and the definitions were too confusion for external users. Working directly with our users, I iterated on solutions until a I reached small selection with a manageable amount of options. For reassurance, the interface was accompanied by a natural language description of the selected permissions.
Permission iterations
Final permissions layout
Outcomes
Working closely with our engineers and sympathetic clients made it possible to "work Lean" and iterate quickly on UX.
It was proven in testings that a progressive, segmented task flow simplified the process - features were collected into groups in navigable sections. This guaranteed that all mandatory details were entered, but some sections could be skipped, which made the workflow much quicker for some users.
A great realization from the user testing sessions was that minimizing the number of security permissions clarifies both the process and the understanding of the outcome. Users expressed in their feedback that they now have a better understanding of hierarchies, and confidence in the security and ownership in the system.
Users list and “Add new user” call to action
Feature design - new step by step profile setup tool with tooltips, contextual fields and more.
Feature design - The last step of the setup allows for quick duplication of the profile.
You can see the entire feature flow here:
