Home / Fuzzy / Fuzzy - rx experience
Fuzzy - Rx experience
What was I trying to solve?
Integration of our Rx business
Increase efficiency for our digital health and Rx teams
Ability for Fuzzy members to be able to get a prescription for flea and tick, without having to see a doctor
Access to doctors to easily see prescriptions in one place
Reduce the amount of steps it takes to get a prescription filled
Research: Interviews & user flows
After doing interviews with all the stakeholders and people who would be using the tool, I discovered there were a lot of inefficiencies in our process.
Team was utilizing a spreadsheet for prescriptions
There was no way to keep track of how long each prescription took to fill
There wasn’t a history or activity section to show who did what with the prescription
Doctors would have to copy and paste a prescription request into two Slack channels and the visit document (SOAP)
In order to get final approval from the approving user, the only source of documentation was a Slack message that said “approved”
No ability to export a legal record of the prescription since it was all in a Slack channel
Measurement of Success:
Increased efficiency of the doctors and Rx team by 50%
Functionality:
Allow two levels of approval for the Rx
The Rx team would be the first round of approval and would double check all information is correct and reach out to the member if needed
One approving doctor would have final approval on all prescriptions and could go in and approve easily
Integrate with our automated experience that was being built, allowing members to fill a flea and tick prescription without a doctor visit
Allow for photo integration from member uploads
Include an activity section to have record of who is touching the prescription
Allow for the Rx team and approving doctor to add notes if needed
Include outcomes and doctor notes for each prescription
Allow for doctor to write a prescription in a consult and have it automatically added to the Rx dashboard for processing
Include ability for approving doctor to be able to submit the prescription directly to our prescription vendor
Include prescriber information - only certain states and individuals were allowed to prescribe so if a doctor wrote a prescription in a state they’re not allowed to prescribe in, the prescribing doctor for that state would be the prescriber
Include ability to create a new prescription directly from the dashboard
Ability to have an “admin” view for the approving doctor and another view for those who are actively working on the prescriptions
Blueprint
Pain points
Research
The Rx team didn’t have any integration into our internal systems, they were working from a living Google Sheet and would do all of their work manually.
In order to build out a proper Rx integration into our internal tooling (Kennel), I started the process with defining what the user flows were and how the Rx experience will fit into that. By defining the use cases and interviewing the different teams that use these workflows, I was able to build out a blueprint to identify how the experience should work for maximum efficiency. After this work was at an understandable level, I shared it with the teams to identify anything I may have missed and to get feedback.
Mobile wireframes
MOBILE Rx dashboard - kennel systems
After working with my product manager to identify the opportunities and scope of the project, I started wireframing, to get early feedback from stakeholders. Once wireframes were completed, I moved into the design phase. During the design phase, I worked closely with stakeholders to make sure all legal requirements had been met and all functionality was as expected.
Once the experience was approved, I prepped the file for engineering to take over and be able to develop the full experience.
Wireframes for desktop
Admin dashboard
Desktop Rx dashboard - kennel systems
The team utilized desktop for the majority of these approvals. There were also different views depending on the user permissions. There was the admin view and the team view.