
Situation Statement
ICD coding logic that is defined in the ICD10 coding manual. ICD10 coding rule prohibits the use of ICD codes that cannot be used together. Example: A condition cannot be both acquired and congenital.
Task Statement

Acceptance Criteria
During the ordering flow for insurance bill orders that are enabled for the Excludes 1 functionality, when there are at least 2 diagnosis codes on the order, a web service call will be made to determine if the diagnosis codes are conflicting. If the diagnosis codes are conflicting, a message will be displayed to the user and the order will be blocked. User will have to remove one of the conflicting diagnosis codes or indicate there is an exception in order to place the order.
Action Solution
The challenge was to design a workflow that would visually help the user identify the diagnosis codes that are conflicting before user to submit the order. To solve this I designed the appropriate conflicting diagnosis codes to display in red underline font. When hover over the 2 conflicting diagnoses codes display a red border. Then provided a delete icon so the user would not have to return to previous page to find and remove. The user can also select the Exception checkbox and provide a fax on the reason. Once the user selects the exception checkbox or removes one of the conflicting codes the CTA Buttons become active allowing the user to move forward and submit the Lab Order completing the users task.
Result Statement
This feature provided up front transparency while also reducing trailers to clients using Quanum Application. Increasing performance measures that include our ability to reduce write-off’s associated with denials on orders, and improve metrics by reducing the denial rate. By enabling this editing logic we will be reduced the order errors at the time or the order and educating our clients regarding payer editing/denial practices.
My Role
Design Thinking Process

User Research
User Interview
Journey Map
Goal Statement
Empathy Map

Brainstorm
Card Sorting
User Flow
Paper Prototyping
FigJam Templates

Wireframes
Visual Design
Mockups
Prototype

Usability Testing
dTeam Approved
Improvements

Define Phase
As a Primary Physician doctor he uses laboratory testing to diagnose the patients current acute issues and needs to submit the Lab Order with no errors so that Quest Diagnostics can be paid.

Goals
• Simplified lab ordering
• Enhanced results
Frustations – Pain Points
• Conflicting diagnosis codes
• Not able to complete order.
• Having to go back to previous screen
• Having to call help-desk.
• Quest not getting paid.
Needs
• User-friendly dashboard for a single view of • Quest interactions, including orders, results, and action items
• New orders completed in as few as 3 clicks
• Eliminate paper test requisitions
• Alert user and prevent ordering if there are conflicting diagnosis codes on the order