Skip to content
Healthcare · Integrations2025

PromptEMR Activation

A custodian activation experience that turns a technical EMR integration into a guided, confident setup.

Role
Product Designer
Timeline
4 weeks
Platform
Web · Activation Flow
Year
2025

PromptEMR Activation is the flow that gets a record custodian connected to an EMR integration. It moved from a Vercel prototype into a production integration-activation repo. The goal: make a technical connection feel like a guided, reassuring setup.

The Problem

What wasn't working

Activating an integration involved API keys, verification and steps that felt intimidating to non-technical custodians. Drop-off happened where the process felt risky.

Goals

What success looked like

  • Turn a technical connection into a confident, guided flow.
  • Reduce anxiety around API keys and verification steps.
  • Make success, and any error, completely unambiguous.
Research

What I learned first

  • Traced every technical step a custodian must complete to activate.
  • Found the moments where uncertainty caused people to stop.
Challenges

The hard parts

  • Explaining technical concepts without condescending or overwhelming.
  • Designing error and success states that leave no room for doubt.
Design Process

How I worked through it

  1. 01

    Sequence

    Broke activation into ordered steps, each with a single clear objective.

  2. 02

    Reassure

    Added plain-language guidance and confident success/error states.

  3. 03

    Ship

    Moved from prototype to the production activation repo with the same design intact.

Wireframes

Structure before surface

Laid out the activation as a checklist-style flow before refining the visual language.

User Flow

The path a user takes

  1. 1Custodian starts activation
  2. 2Completes guided, one-at-a-time steps
  3. 3Verifies the connection with clear feedback
  4. 4Lands on an unambiguous success state
Final UI

Where it landed

An activation flow that makes a technical integration feel guided and safe, with success and errors you can't misread.

Impact

What changed

Prototype→Prod
Shipped into the activation repo
Guided
Step-by-step technical setup
Confident
Success and error states
Lessons Learned

What I took away

  • Technical flows need more reassurance, not less explanation.
  • The success state is part of the product, not an afterthought.
Reflection

Helping a non-technical person confidently finish a technical task is one of my favourite design problems, it's pure translation.

Next project

Another Store

E-commerce · Editorial Web

View case study