I designed a post-purchase patient portal end to end, giving people who bought an at-home sleep test one clear place to track their order, act on next steps, and stay cared for after the sale.
The portal in action. Upload an insurance card and the next step marks itself complete. Open the live, interactive prototype to click through the full flow: the order timeline, next steps, support, and the device shop.
The company sells at-home sleep tests and devices. The purchase was handled, but everything after it was not. Where is my test, what do I do next, is my care on track, all of it lived nowhere. That gap is where post-purchase anxiety and support tickets come from.
I started this one from almost nothing. I was handed a set of product requirements and little direction, so I mapped the entire post-purchase journey myself and filled in the blanks: the information architecture, the dashboard, the order and treatment timeline, the insurance-and-benefits step, and the device cross-sell. Ownership from the first journey map to the final UI.
There was no map to start from, so I drew the whole thing. A bird's-eye view of the end-to-end path, and a full patient journey from discovery through the sleep test, diagnosis, device, and ongoing progress. Every screen in the portal traces back to a decision on one of these two maps.
The bird's-eye view I mapped: every stage of the at-home sleep health path on one board, so the whole team could see where the portal had to do work.
The full patient journey I built, from discovery and the sleep test through diagnostics, device, and progress. Mapping it end to end is how the blanks in the requirements got filled.
This is the counterweight to the buy-flow work. Not conversion, not a funnel, but the account experience that keeps a customer feeling cared for after the sale, where trust is kept or lost.
Post-purchase is the part teams forget and patients feel the most. The portal's job was to replace uncertainty with the feeling of being looked after.