RxtoMe Pharmacy Portal 2.0
Information Architecture | UI Design
This desktop app allows pharmacies to connect to the RxtoMe 2.0 mobile app. Through this platform, pharmacists are able to manage subscriptions, patients and prescriptions.
Project Details
My Role: UX/UI Designer
Client: RxtoMe / Prizm Media Inc.
Developers: Matthew Chan & Sean Park
Duration: 3 Months
Tools: Balsamiq Mockups, Adobe Illustrator, Adobe XD, Invision App
Problem
The users of the Pharmacy Portal 1.0 are pharmacists that are already subscribed to the RxtoMe 2.0 mobile app services.
As opposed to the RxtoMe 2.0 mobile app which was being updated and tested, the RxtoMe Pharmacy Portal 1.0 had not been updated, tested or reviewed in a long time and was missing new features.
The Marketing team started working on the RxtoMe 3.0 mobile version and the Pharmacy Portal had not been updated to even match RxtoMe 2.0.
The two interfaces did not look like they belonged to the same product.
Discovery
Product Description
B2C
RxtoMe is a mobile app for users to order prescriptions online with free delivery and cash rewards.
B2B
RxtoMe Pharmacy Portal is a desktop app for pharmacists in the RxtoMe network to manage subscriptions, patients and orders.
The development of RxtoMe 1.0 and Pharmacy Portal 1.0 started with a team of developers, no designers participated in this phase.
RxtoMe 2.0
As the product progressed, the company hired a Marketing director to improve the engagement and increase sales and downloads.
This lead to the development of RxtoMe 2.0, which included:
-
- Order Prescriptions
- Transfer to Pharmacy Network
- Cashback Rewards
RxtoMe 3.0
While the development team was working on shipping and testing RxtoMe 2.0, the marketing director and his team started working on RxtoMe 3.0.
For the latest version, the marketing team decided to make the UI dark and to include these new features:
-
- Transfer Medication
- Upload Prescription
- Order Refill
- Medication Reminders
- Calendar
- Trackers
- Insurance Wallet
- Tutorial
- Rewards System
Pharmacy Portal 1.0
While the mobile app was being worked on, the Pharmacy Portal hadn’t been updated and neither the features or the user interface matched.
The Development team was not aware that the Marketing team was working already on the 3.0 version.
Challenge: Feature Integration
The stakeholders approved the creation of the Pharmacy Portal 2.0 desktop app. However, due to time constraints and resources, the portal should have the following characteristics:
- Be shipped before RxtoMe 3.0 mobile app
- Include the features of the 3.0 version
- Match both RxtoMe 2.0 and 3.0 user interfaces.
Decision: No Pharmacy Portal 3.0 in the near future.
Challenge: Team Communication
There was a big disconnect between the Development team and the Marketing team. The only communication happened between directors, who would later share their findings with the rest of the team. The developers did not know what the designers were working on, and vice versa. No meetings, no collaboration, pure silos.
Communication was a big challenge at the beginning of this project and it was also a problem for the development of the RxtoMe User Portal project.
Research
Pharmacy Portal 1.0 Features
The original Pharmacy Portal was created to match the RxtoMe 1.0 mobile app. So it had a very basic user flow.
It included the following features:
- Change status of prescription orders.
- Buy credits (users) from the RxtoMe network.
- Send an email to their representative.
Pharmacy Portal 1.0 sitemap
Competitors’ Analysis
In order to find the best way to integrate the new features to the Pharmacy Portal 2.0, I had to compare and contrast with the competition.
RxtoMe’s main competitors are PrescribeWellness, Speed Script and SimplePractice. I created accounts for each one of the platforms to navigate their product and assess their user flow, compare features and study their user interface.
PRescribeWellness
This platform had the most valuable information for our research. Same as RxtoMe, PrescribeWellness has a B2B (community pharmacies) and B2C (patients with chronic diseases) business models.
- Help clients reach more patients
- Improve medication adherence and loyalty
- Increase maintenance prescription revenue
- Increase daily scripts
- Provide the patients with a Pharmacy Directory
- Home Delivery
To view the full 2018 competitor’s analysis report,click here.
SpeedScript
|
|
SimplePractice
SimplePractice
Features:
- Secure Messaging
- Therapy Notes
- Client Portal
- Autopay
- Appointment Reminders
- Simple booking
Portal:
- Calendar
- Clients
- Billing
- Insights
- Activity
- Reminders
Research Results
Possible Features:
|
RxtoMe 3.0 Features:
|
Outcomes
Integrating Features
After further discussion with the team, we decided to include the following features to the Pharmacy Portal 2.0.
|
|
The reasons why these features where included is that they meet the basic needs of the user (Pharmacies and Pharmacists) to connect properly with both RxtoMe 2.0 and RxtoMe 3.0 in the fastest time and without ignoring any of the features of the latest product release.
Ideation
Pharmacy Portal 1.0 Site Map
This is the sitemap of the original Pharmacy Portal. Including the following features:
- Account Settings
- My Inquiries
- Contact My Representative
- Purchase Credits
Pharmacy Portal 2.0 Site Map
This is the sitemap of the original Pharmacy Portal. Including the following features:
- Orders
- Patients
- Memberships
- Payment Method
- Inbox (Messaging)
- Account Settings
Content Outline
1. Orders 1.1 Order Number 1.1.1 Prescription Image 1.2 Change Status 1.2.1 Rejected by Patient 1.3 Notes 2. Patients 2.1 Patient Profile 1. Orders (Sorted by Name) 3. Memberships 3.1 Membership Type 3.1.1 Terms and Conditions 3.1.2.1 Pay Per Order |
3.1.3 Payment Method 3.2 Purchase History 4. Payment Method 4.1 Credit Card 5. Inbox 5.1 Message 5.3.1 Send Email to a Patient 6. Account Settings 6.1 Pharmacy Services 6.2.1 Edit 6.2.1.1 Edit Hours 6.3 Shipping Information |
Solution
Team Communication
Lack of communication was one of the primary set backs for the product.
There was a gap between the teams, even during lunch break. I was the newbie, and since I am very extroverted and talkative. I wanted to get to know the teams. I heard that the developers were joining the BC Game Jam Hackathon, and coincidentally they needed a designer. So I joined! My participation in this hackathon made it possible for us to create a bridge between developers and designers.
We started meeting up on Thursdays. We would share the progress of our different progress and we were able to learn from each other. This definitely helped out bridgning the gaps in communications and the deliverables surely improved after we instated the Thursday meetings.
Prototype
Medium Fidelity Mockups
Using Balsamiq Mockups app, I created medium fidelity screens based on the new approved user flow and site map. I used these screens later to create a prototype that was used for testing.
These are some examples of the screens:
Medium Fidelity Prototype
Using InVision App, I put together the medium fidelity prototype to test the new proposed features and user flow. Due to lack of resources, the protype was only tested by volunteer employees of Prizm Media who helped us figure out if the proposed flow was usable and navigable.
Desktop Version High Fidelity Mockups
After testing the medium fidelity prototype internally and after considering the Product Owner’s business model, the results made us made little changes to the labelling and position of certain elements. However the user flow worked.
These are some of the screens of the high fidelity mockups for the RxtoMe Pharmacy Portal 2.0 Desktop version. You can view all the screens in the prototype.
High Fidelity Prototype – Desktop Version
Unfortunately, due to resources and time, the only testing we were able to do was internal with company volunteers. I put together this high fidelity prototype for their use. Any feedback was added to the developer’s notes and implemented in the final product.
Mobile Version High Fidelity Mockups
I had to create a few high fidelity screens for the developers to use as a guide for the responsive version. Some of those screens are the following:
Log In
Mobile Menu
Order List
Memberships
New Message
Message Active Patient
Implementation
Front End Development
All the implementation for this project was under the responsibility of Mattew Chan and Sean Park. I was resposible to share with them the Adobe XD export file that includes all the specs for developers. I was available for any communication with them regarding any doubts or questions they may have.