A series of feature designs and redesigns for healios — a platform that unifies a person's medical records, then helps them actually understand them.
healios is a white-label digital health platform. It pulls a person's medical records — from providers, labs and insurers — into a single place, so they can monitor and manage their own health instead of chasing paperwork across a dozen portals.
The product already existed. The work here was to design new features and rethink existing ones so the experience matched the promise: not just storing health data, but making it understandable.
This study walks through five connected pieces of work — a trustworthy onboarding flow for connecting sensitive records, a phased Health Summary, and clearer Vitals, Labs and provider search.
Each one started from the same question: where does the experience get in the way of a person understanding their own health?
A person's health history lives in dozens of disconnected systems. Even once healios brings it together, raw data isn't the same as understanding. A few core problems kept surfacing across the app.
Connecting records is what healios does — but data dumped into an interface doesn't help anyone. The harder design problem was turning that data into something a person can trust, read and act on.
Connecting records means handing over deeply private data and verifying identity. Any confusion or unexplained step, and people abandon before they ever see value.
Grey containers and flat hierarchy buried the numbers. Nothing told a user whether a reading was healthy, borderline or worrying.
Lab results were grouped only by date, with no search or filter — so tracking a single result over time meant scrolling endlessly.
The provider database is huge and full of duplicate names, making it easy to accidentally connect to the wrong doctor.
Rather than redesign by taste, each feature moved through the same loop — understand the problem, frame it, explore broadly, then de-risk the hard parts with prototypes and testing before committing.
Reviewed the existing app and talked to stakeholders to map where users got stuck.
Distilled the noise into four clear frictions: trust, legibility, findability, certainty.
Sketched flows and layouts — and made the call to strip out the grey containers entirely.
Turned the highest-risk flow — the ID scan and facial match — into an interactive prototype.
Ran usability tests, watched for drop-off, and refined before anything reached build.
Five pieces of work, each tackling one of the frictions above — built and validated through the loop, then shipped.
Tackling Friction 01. Connecting records means asking for sensitive data, so the north star was a single feeling: this is safe, and here's exactly why we're asking. Three different authorization paths had to share that calm.
The flow narrates what's happening as it happens — choosing what to connect, searching on the user's behalf, and confirming when records land.
The riskiest part — verifying identity with an ID scan and mobile check — was prototyped and user-tested first. Honest waiting states set expectations when a connection takes time.
The result: low drop-off through authorization in testing — a strong signal the reassurance was working.
Health Summary lets users compile a PDF of everything — visits, diagnoses, lab results and more. To get value out fast, it was designed as nine phases, each building on the last, starting from a bare download-only flow.
The exported document — the thing a patient hands to a doctor — was redesigned for clarity, with readable hierarchy and room to breathe.
Tackling Friction 02. The data was already there; it just wasn't legible. Grey containers smothered the content and nothing signalled whether a number was good or worrying.
The most important move was the simplest: remove the grey containers and let white space do the work. A proper type system fixed the hierarchy, and the section instantly felt airier.
Then, to make health legible at a glance, came five clear indicator levels — each with its own colour and icon.
Tackling Friction 03. Everything was grouped by date with no search or filter, so finding a single result was a slog. The goal: make Labs genuinely useful for health monitoring.
On the detail page, the chart now tracks one result over time against its healthy range.
Tackling Friction 04. With a huge database and duplicate names, search had to make it impossible to connect to the wrong person by accident.
Each doctor's office location is prominent and tappable, so people can confirm they've found the right person. A “Request Connection” action lets users ask to join a doctor's health system if they aren't in it yet.
A few lessons that outlasted the individual screens.
Explaining the “why” at each step — and prototyping the scariest flow before building it — kept people moving through identity verification instead of bailing.
Removing the grey containers did more for legibility than any new component. The biggest readability win came from taking things away.
Designing Health Summary as nine incremental releases put value in users' hands immediately and de-risked the build for engineering.
A five-level colour-and-icon system turned raw vitals into something understandable in a second — and was later adopted across the whole platform.