Episource · Optum
Episource
Senior, then Lead Product Designer at Episource, now part of Optum, from 2021 to 2024. User research across the suite, a design system, an integration with hospital record systems and an AI medical-coding interface taken from alpha to production.
Healthcare · AI · Design System · Enterprise · NLP
The visuals on this page are simplified reproductions, deliberately different from the real products and built with royalty-free elements. They show how the product is used, they are not the actual software, out of respect for intellectual property.
User research across the suite
Led user research across several products of the suite.
A design system for the whole suite
Built the Figma component libraries and integrated design tokens into production for the design-system rollout across the whole product suite (Q4 2021 - Q2 2022). With the design system developer, it then grew from Angular to a multi-stack library (React, Angular, Vue) built on Stencil JS web components, on top of Google Material 2. I owned the Figma side, the developer the code.
Promoted to Lead after 12 months
Promoted to Lead Product Designer after 12 months.
Provider Direct Messaging
Owned Provider Direct Messaging, a two-way integration with hospital record systems (EHR), built with UnitedHealthcare, with a pilot targeted for Q1 2024.
Click to Code, from alpha to production
Led the Click to Code medical autocoding project, an NLP-based AI coding interface, from alpha to production (Q1 2022). A major V2.0 redesign, validated with 897 users, reached 88% of suggested medical codes accepted and 80% of users rating it 8 to 10 on NPS, and became a core part of Episource's autocoding strategy, targeting 500,000-750,000 charts a year.
Use case: Click to Code
One screen to show the work: a coder reviewing an encounter in Click to Code, with the evidence in the note, the confidence on each code and the guidance beside the decision.
Reviewing an encounter
- Evidence in the note
Need. A coder trusts a code only when the note visibly supports it.
Solution. Each code points to the exact sentences in the PDF, highlighted and tagged with the code.
- Confidence and validation
Need. Time should go to the uncertain codes, not the obvious ones.
Solution. A confidence level on every suggestion, the likely ones checked, and one action to validate the selection.
- Guidance beside the decision
Need. Checking a rule should not mean leaving the screen.
Solution. Documentation checks and the relevant guideline, with its source, next to the codes.
- Flag and escalate
Need. A doubtful code should be neither guessed nor left blocking the queue.
Solution. Flag it with a reason, send it to a senior coder or query the provider, and keep the discussion on the code.
Illustrative recreation of a Click to Code screen, not the actual Episource product. All content is fictional.