Product UI/UX

Designing the trust layer for home healthcare

Home healthcare has no shortage of demand. What it lacks is the infrastructure for trust: verified identity before anyone enters a home, payment held until the service is confirmed complete, and documented accountability across all three parties in the transaction simultaneously.

+35%

projected checkout conversion (form reduction + progressive disclosure)

0

payments released without confirmed service

3

trust tokens · chain of custody from booking to payment

Role

Product Designer

Platform

iOS · Android

Users

3 simultaneous

Status

Portfolio rebuild · NDA

MedMe app screens

Current state · before this project

Wants home visit No platform exists Googles or asks No filter, no trust Calls / WhatsApp No record, no audit Gets a quote No escrow guarantee Professional arrives Unverified. No recourse.

The on-demand product didn't exist. Ecommerce existed for products, but not for professional services at home.

01

The problem

Home healthcare has a trust problem, not a demand problem. Friction is the symptom. The root cause is simpler and harder to fix.

A patient opens their front door for a stranger. This isn't a food delivery. This is someone touching your body, drawing your blood, vaccinating your child.

MedMe had a working pharmaceutical ecommerce. What didn't exist was an on-demand product with verified professional identity, payment protection, and accountability covering all three sides of the transaction simultaneously: patient, professional, and clinic.

The original screens stayed with the company. Everything here is a reconstruction from scratch for the portfolio.

02

Three users, three fears

Three actors are active simultaneously during every appointment. Each has a different set of concerns. Designing for one without the others produces a system that fails at the seams.

Patient

Identity & money

Is this person who they say they are? What if the service doesn't happen? Who holds my payment until it does?

Professional

Equipment & coverage

Will the gear be ready at the clinic? Am I legally covered if something goes wrong at the patient's home?

Clinic

Quality & reputation

Someone represents my brand at a stranger's home. I can't be there. I need documented accountability.

Every design decision in this product is a response to at least one of these fears. The token system and the matching logic each address all three simultaneously: that's where most of the complexity landed.

Complete user flow: Patient, Professional, and Clinic across 8 steps from service selection to payment
03

The scheduling decision

Most healthcare platforms show all units upfront. You pick one based on distance or name recognition. Then you find a time and discover the slot you wanted is gone. You go back. You pick another unit. You try again.

This loop isn't just frustrating. It's the structural failure behind most scheduling abandonment in digital health. The form isn't broken. The information architecture is.

27% of patients switched providers specifically because of digital friction (McKinsey, 2025). They didn't abandon the process. They went to a competitor.

MedMe inverts this. Time first. Unit second.

The patient selects when they want the service. The system only shows clinics that have confirmed availability at that specific time. Slots that can't be fulfilled don't exist in the UI. They're never offered.

Standard model MedMe Browse all units Select unit Select time slot Slot unavailable Go back · pick another unit Frustration loop Select service type Select desired time View confirmed units Only available at that slot Select unit Confirmed · no loop Unit shown regardless of availability Units filtered to confirmed slots only

Before selecting time, the patient chooses visit type: at-home or at-clinic. This single toggle filters everything downstream: which clinics appear, what equipment lists apply, what the professional card shows. At-home visits carry the full token protocol. At-clinic visits use a simplified check-in. The scheduling IA is the same in both cases.

The time selection itself breaks into three sub-steps: month picker, then day, then available slots. Each step narrows the choice space before the next opens. The patient never faces a grid of every open slot. They arrive at a short, filtered list for the specific day they already committed to.

Rejected approach We considered inverting only one step: showing all units, but filtering the time picker per unit. Rejected: this still requires the user to pick a unit before knowing availability. The frustration loop persists, just one click later.
Month picker, step 1 of 3
Month picker · step 1 of 3
Day picker, step 2 of 3
Day picker · step 2 of 3
Time picker with confirmed slots only
Time picker · confirmed slots only
Scheduling complete, time selected and continue button unlocked
Time selected · continue unlocked
Unit list filtered by selected slot
Unit list · filtered by selected slot
Addresses 27% switched providers due to digital friction, not clinical quality (McKinsey, 2025)
04

Matching with regulatory competence

The patient doesn't choose the professional. The clinic does. This is the only model that holds given how liability actually works in healthcare.

The clinic's certification and reputation are what the patient is trusting when they book. If the clinic assigns the professional, accountability stays in one place. If the patient chooses, accountability fragments and no one owns the outcome.

Standard model

Patient browses a list of professionals. Chooses one. Accountability is diffuse: the platform, the professional, and the clinic all share partial responsibility with no clear chain.

MedMe

Clinic receives the booking. Assigns the professional internally. Patient sees credentials after assignment. The clinic owns the outcome. Liability is clear, trust is verifiable.

Information architecture: service-first filter logic and pool overflow

When a clinic has no available professional, a pre-approved pool of third-party professionals fills the gap. Same certifications: ANVISA-registered clinics, CRBM-licensed professionals. Same vetting. To the patient, the card looks identical. To the clinic, the pool assignment is flagged in the operational dashboard. The answer is never "unavailable."

After service, all three actors rate each other. The patient rates the professional. The professional rates the patient. The clinic rates the professional's execution. A three-sided rating creates accountability at every point in the chain, not just at the end where the patient leaves a review.

One thing this doesn't fully resolve: when a pool professional delivers the service instead of the clinic's own staff, the clinic is rating someone they didn't hire. Whether operators engage with that feedback the same way for pool assignments as for their own team was a question that stayed open.

05

The time logic

Every slot shown to the patient already includes 60 minutes of lead time built in: the window the professional needs to collect equipment at the clinic before traveling. If that window collapses due to a last-minute booking or a late confirmation, the slot disappears from the picker before it's ever offered. The patient never sees unavailable time.

This is where most on-demand healthcare products fail. They optimize for showing availability. MedMe optimizes for fulfillment. Showing a slot that can't be executed is worse than showing no slot. It creates a confirmed appointment followed by a cancellation, which destroys trust faster than saying the time is unavailable.

Edge cases
Professional late (>10 min) Patient notified. Slot extended or cancellation with full refund.
Equipment not collected by T–45min Clinic alerted. Slot flagged at risk. Pool assignment triggered.
Last-minute booking (<1h lead) Slot not offered. Removed from picker before patient sees it.
Waiting state with professional en route, credentials visible, status timeline
Waiting state · professional en route, credentials visible, status timeline
Credentials expanded, full professional card with license details
Credentials expanded · full professional card
06

The token system

Three tokens. Three problems solved independently. Together they form an unbroken chain of custody from booking to payment release.

Token system: three-phase chain of custody
Token system: chain of custody in three phases with bilateral flows

The bilateral check-in references a pattern that already exists in services patients use daily: the bilateral PIN in Uber, ID verification in Airbnb. The difference is the context: this is a private home and a medical procedure.

Rejected approach We considered a single token passed from clinic to patient at booking, used by the professional on arrival. The question that killed it: how does the patient know the person at the door is the same person whose credentials they received? A unilateral token protects the system. It gives the patient nothing to verify with.
Token 2 empty state, waiting for both codes
Empty · waiting for both codes
Token 2 error state, wrong code entered
Error · wrong code entered
Token 2 confirmed, both parties verified
Confirmed · both parties verified
Addresses identity verification gap + payment protection (no release without service confirmation)
07

Checkout and payment

Checkout abandonment in healthcare peaks at the point where users realize how many steps remain. A persistent 6-step progress indicator makes the endpoint visible from the first screen. The form breaks into three sub-steps that open sequentially, each unlocking only when the current one is valid. Fewer fields visible at once, no information actually hidden. The reduction to 12–14 fields follows Baymard's benchmark for the field count at which abandonment drops meaningfully.

Multi-method payment lets the patient split the total between their MedMe balance and a second method: Pix or card. The coupon input sits on the same screen as payment method selection. Entering a code updates the total immediately, before committing to a method. A visual split bar shows how much each method covers. No mental arithmetic.

57% of patients say price transparency influences where they seek care (McKinsey, 2025). The escrow note at confirmation shows the patient what they're paying, to whom, and that the money is held until Token 3 is confirmed. Below that, the token protocol is restated in plain language: "Vita Clinic assigns a professional", "Credentials sent for review", "Do digital check-in on the day". Price visibility is a selection criterion before the patient even books.

Checkout with 6-step progress indicator and order review
Checkout · 6-step progress indicator
Payment screen with MedMe balance and method selector
Payment · balance split + method selector
Payment with MedMe balance active and payment method selected for remaining amount
Payment · method selected, total split
Confirmation screen with escrow note and token protocol summary
Confirmation · escrow note + token protocol
Addresses 74% decision-stress abandonment · 80.2% mobile abandonment · hidden cost as #1 exit factor
08

Outcome

The on-demand product didn't exist before this project. The numbers below are projections grounded in published benchmarks, not post-launch data. The product was built for a company that couldn't share results.

+35%

Projected checkout conversion: form reduction to 12–14 fields + progressive disclosure

Baymard, 2026

60%

Patients reporting friction in digital scheduling, addressed by time-first IA

McKinsey, 2025

74%

Users abandoning due to decision stress, mitigated by 6-step progress indicator

Accenture, 2024

19%

Abandonment from forced account creation, removed from both flows

Baymard, 2024

Three trust patterns from services patients already use, adapted for a medical context:

Airbnb · ID verification Uber · bilateral PIN TaskRabbit · Happiness Pledge

Hidden cost is the number-one exit factor in ecommerce (McKinsey, 2025). Escrow makes the cost structure transparent: the patient knows exactly what they're paying, to whom, and when it releases.

Let's talk

Got a project?
Let's make it work.