Overview: The Merit-based Incentive Payment System (MIPS) is a new way by which eligible clinicians will be measured by U.S. Dept. of Health Services to determine if they are providing quality patient care in an economically efficient way.
This consolidation will reduce the aggregate level of financial penalties physicians otherwise could have faced, and it also provides a greater potential for bonus payments. More about MIPS.
The Solution: A customizable web based application which can record data, generate scorecard and conduct what-if analysis to save time & provide meaningful insights.
Client: Regenstrief Institute, Inc.
Timeline: 4 Months
I worked as the UX Designer on this project. Some of my responsibilities included:
Currently used by Quality Improvement Advisors (QIA) to guide 15,000+ clinicians across universities, health systems and independent provider-practices in five Midwestern states.
The users of this tool are Quality Improvement Advisors (QIA). QIA's acts as an internal consultant and resource to a health organization with the goal of driving improvement in quality, cost efficiency and patient satisfaction. They gather, compile and analyze clinical reports, identify gaps / strengths & make appropriate recommendations for corrective actions.
I collaborated with the researchers and domain experts in the team to understand our core users, their environment, and majors tasks to accomplish. We interviewed few participants and gathered data on their current workflow and major challenges. This data helped us in finding opportunites to solve the problems.
We chose four Quality Improvement Advisors to interview.
Interviews conducted were semi- structured in nature.
All from different health organizations such as IU Health, Purdue Health etc.
What's the context?
What are your major tasks?
How do you report & analyze data?
What are the major problems faced?
How do collaborations happen?
What tools do you currently use?
Observations were conducted to get and understanding the QIA's process of data collection from various pysicians and providers and to study the tools / mediums used in their current workflow.
After conducting interviews and observations I created user personas with information about their behaviors, technologies used, pain points & their needs. View Persona
1. Long reports and high error rates
3. Organizing & searching data in reports
2. Tedious process to analyze the data
4. Time consuming calculations in Excel
How might we empower Quality Improvement Advisors to gather, compile, and analyze clinical reports, so that they can quickly make appropriate recommendations for corrective actions?
We brought together our research data and ideated solutions based on the user's problems, behavior, goals and priority.
A dashboard which shows all the important and frequently used features at one place to help users navigate faster
Create new reports and save previous ones at one common place to search and compare anytime they want
Showing meaningful visualizations for the user to glance and understand the reports in an much efficient way
Give users opportunity to rework and check different scores without affecting the original scores in the report
As we moved on to designing the interface of the application, I wireframed all the UI screens and conducted an intial user testing session.
Shown below are different versions of dashboard page explored and tested early with expert users.
Repetitive links and buttons on dashboard
Not showing scores of report
Long dashboard page with too much data
Users probably switch between 2-3 reports
Side navigation leaves less space for long tables
Scores are the not user’s first priority
The three main components of the overall user interface are the Dashboard, Data Reporting and the scorecard. Some key screens the application are illustrated below.
2. Create Report
3. All Reports
4. View ACI Data
5. What-if Analysis
This was the first project where I was not only responsible for UX design but also project management, strategy, and team leadership. It was a great experience collaborating with developers, product owners and other stakeholders which helped me in developing a holistic idea about feasibility of the design. I learned that every problem looks difficult initially, but with the right approach and design mindset we can solve any issues and achieve great results. Designing effectively means bridging business needs, technical constraints & finally providing user satisfaction.
Points which are not covered in this case study but could be worth discussing in person:
Thanks for making this far. Here's a gif for you.
Have any suggestion or interested in working together on a project?
Go ahead, I'd love to connect with you.
© Designed and Coded by Rahul Jain