Richard Kramer / Product Designer
Thumb.png

R1 RCM - R1 Edit Design

Create an MVP Design solution for R1 Edit using WORK CLOSELY WITH PRODUCT Teams to identify opportunities to improve managing incoming claims that can be monetized easily and routed for resubmission. Interviewed current users to understand current tools and users needs. Did comparative anlysis on current tools. Created JTBD Map from current users interviews. Built prototypes for usability testing with users. Shared Design with Product team to get feedback and next steps. Did concept testing with users to validate the design.

Team:  1 Product Designer, 1 Researcher, 2 PM lead and Junior, 2 Front End Developers

Agile:  3 Sprints consecutive user testing and interviews.

Goals: MVP Design Direction and scope

  • Design the MVP R1 Edit App that the R1 Edit team can grow into.

  • Design a valuable MVP feature that helps R1 operators to accomplish tasks faster. 

  • Leverage the R1 Design System to iterate and build faster. 

  • Use rapid research and testing as needed to validate ideas.

Assumptions: Use of R1DS Design System to create prototypes. Developers would be building in Angular with Prime Components.

User Problem

Currently comparing original data to changed data in a claim is done using 3rd party tools. The process is tedious, and users often need to sort through various views of data to find what changed or was updated.

Initial Use Case

Allow R1 Operators to view claims processed through the R1 Edit Rules Engine, validate the updates in a single claim, and route them to next steps.

 

Discovery

Comparative analysis

Completed a comparative analysis on 2 main tools used by R1 Users to scrub Claims.

 

User Interviews

Shadowed 6 R1 Claims Operators to learn about the tools they are currently using to find and compare changed claim data.

  • What tools they use currently and what features are important.

  • Users general workflow when looking for specific types of changes using the tools.

  • Likes and dislikes of the current scrubber tools.

  • Must have vs like to have.

Claim Forms Discovery

We needed to recreate some of the Claim forms used in the current tools. Users are familar with these forms while looking for data.

 

Sketching Ideas

Created initial sketches based on learning from user shadowing and comparative anlysis of current tools

JTBD Mapping

The Design Research team worked with us to synthesize the interview data and create a Jobs To Be Done Map. This gave us a good idea of what our users expected from the UI and which types of information sorting we needed to focus on.

 

Design

Wireframe Concept Testing

Created rough wireframes and prototype based on JTBD Map that was used for concept testing to validate research.

Wireframes were tested with 6 Operators, and helped to validate much of the discovery we had done. This allowed us to move to High Fidelity.

 

High Fidelity

Created high fidelity prototypes using the R1 Design System templates and component libraries. Reviewed prototypes with Product and Engineering teams to get feedback.

 

Outcomes

  • Designed a solid MVP design that my team can use to begin building out a larger set of R1 Edit services and features. 

  • Leveraged the evolving R1 Design System to move faster allowing us to experiment and iterate faster. With the Design System development of working prototypes can be started immediately.

  • Quick user tested helped to move decisions along faster

Claims List

Compare Changes Tab

History Tab