M-EHR

Progressive WebApp

Mantle

Mantle is a web hosted platform for clinicians in the psychotherapy space.

Improvements to the experience, information architecture as well as HIPAA+GDPR compliance were required to undertake a v2 of the project.

ERP/EHRs are widely known to be clunky, expensive, hard to use, and their users hate them. But more notably, The users & Buyers of ERP software usually have varying goals.

Features

> Client Management
> Claims management
> Payments system
> Clinical notes
> Tasks
> Reports

Website

Public Beta

Jhool, UK 🇬🇧

Mantle, US 🇺🇸

Figma, Fullstory,
Visual electric

Web (Responsive)

User research, UX Audit, Design system governance (development+Maintenance),
Internal marketing

2025

Context

Goal

Create a product that improves the affinity of Clinical therapists towards their daily driver software by improving how quickly they can complete tasks and find information.

Outcome

We re-built onboarding, billing and content management features that improved task completion time & efficiencies for billers, auditors, providers & coders & their use-cases.
‍
Launched in private beta to over 100 US clinicians, Q2 2024.

10+

Happy institutional providers

32k+

Session notes written

16,000+

Claims processed

100%

Provider retention rate

5,000+

Patients helped

Goal-Outcome

Solutions

Intuitive Session Notes

+ Note-taking is a frequently undertaken activity in administering care.

+ Mantle's simplifies note-taking with AI assistance, ensuring comprehensive, accurate, and compliant documentation.

Session Notes details

- With a Mouse enter-to-scroll microanimation, clinicicians are saved multiple clicks

mobile responsiveness*

designops/Strategy peek-through

Internal Marketing Dev Mode

I used the Figma community files to market dev mode for smoother handoffs between design and engineering, prompting leadership to scale up our Figma team plan (By saving time and $$ spent on other software & longer handoff tools)

Component Matrix 1

As part of our UI Library(Design system) refresh, I employed the use of a component matrix to keep track of component versions & their documentation.
This helped us keep track of what was to be done and when as well as help the devs with reference.

Component Matrix 2

Changelogs

i introduced the use of changelogs and decision notes for handoff cases where figma comments might be insufficient.

Context Goal-Outcome Solutions Strategy