ROLE AND TEAM:

Product Designer Full-Stack Engineer Medical Team (Domain Expertise) QA

TIMELINE:

August-September 2024

SKILLS:

User Interviews Prototyping OOUX System Mapping Visual Design Design System

PROBLEM:

Patients answered risk assessments in the room, making consultations longer and the answers less reliable.

ROLE AND TEAM:

Product Designer Full-Stack Engineer Medical Team (Domain Expertise) QA

TIMELINE:

August-September 2024

SKILLS:

User Interviews Prototyping OOUX System Mapping Visual Design Design System

PROBLEM:

Patients answered risk assessments in the room, making consultations longer and the answers less reliable.

01

01

Why the project existed?
Why the project existed?

Nuumad runs pharmacist consultations with digital PGDs. The risk assessment could only run in the room, live, during the appointment and it was eating consultation time.

Nuumad runs pharmacist consultations with digital PGDs. The risk assessment could only run in the room, live, during the appointment and it was eating consultation time.

02

02

Why does it matter?
Why does it matter?

Users lingered on the RA page longer than any other; check-ins kept surfacing the same friction. 14 structured interviews with healthcare professionals (HCPs) + patients turned a long-standing annoyance into an evidenced, sized problem.

Users lingered on the RA page longer than any other; check-ins kept surfacing the same friction. 14 structured interviews with healthcare professionals (HCPs) + patients turned a long-standing annoyance into an evidenced, sized problem.

03

03

What was the problem?
What was the problem?

Time pressure, recall and privacy looked like three problems.They shared one root: patients answer at the worst possible moment. The when and where of answering mattered more than the questions.

Time pressure, recall and privacy looked like three problems.They shared one root: patients answer at the worst possible moment. The when and where of answering mattered more than the questions.

04

04

What the interviews said?
What the research said?

Three findings:

  • the patient answers cold with no time to think,

  • no access to records,

  • no privacy for intimate questions.

Three findings:

  • the patient answers cold with no time to think,

  • no access to records,

  • no privacy for intimate questions.

Time pressure

Recall

Privacy

the when and where of answering

Lengthy and possibly inaccurate consultations

Design decisions
Decision 1: Hypothesis

We were looking at the problem from the HCP's point of view.

The risk assessment was treated as HCP data-entry, so every fix focused on the appointment. This was until we spoke to the patients.

vs

vs

Reframe to the patient's.

Hypothesis: let them answer before & outside → more confident, shorter consultations. We also established conditions that would prove we were wrong.

Decision 2: Approach

Killed

Option A: Pre-fill & verify

Riskiest assumption

The info the RA needs actually lives in a record you can pull

Bets the cause is:

Missing information: patients can't recall what isn't in front of them

Patient experiences:

Form pre-filled from their record; they confirm, correct, or flag

Rests on:

Most RA answers already exist in records; verifying beats recalling

Cheapest test:

Desk audit: what % of RA questions are answerable from records? No build.

Build: heaviest

Selected

Option B: Private async form

Riskiest assumption

Patients actually complete it ahead of the appointment

Bets the cause is:

Pressure and setting: rushed, watched, in the room

Patient experiences:

Blank form on their own device, at home, untimed, private

Rests on:

Patients have the answers; only time and privacy are missing

Cheapest test:

Wizard-of-Oz: send RA to a few patients ahead via existing channel; watch completion + quality

Build: lightest

Parked

Option C: Guided prep

Riskiest assumption

Comprehension is the bottleneck: and a guide can explain safely

Bets the cause is:

Comprehension and confidence: unclear what's asked or what's "right"

Patient experiences:

Guided flow explains each question; "not sure" is a valid answer

Rests on:

Questions are opaque or intimidating, not unknown or rushed

Cheapest test:

Human walks a few patients through verbally; does confidence jump?

Build: heaviest

Decision 3: Process

selected

selected

discarded

Version 1

  • Lets users answer Yes / No / Unsure in a single click per vaccine without changing the page state.

  • Shows every vaccine and its current answer state at a glance.

Version 2

  • Requires toggling each card open, which adds an extra step and increases time-on-task

  • Cards stack vertically with more padding, pushing items off-screen and making it harder to verify completeness

discarded

Version 2

  • Requires toggling each card open, which adds an extra step and increases time-on-task

  • Cards stack vertically with more padding, pushing items off-screen and making it harder to verify completeness

Decision 4: Service redesign

Blueprint both states across every lane — what moves, what stays. Patient answering shifts before the visit; HCP shifts from entry to review; clinician keeps authority over the record

Today — risk assessment answered live, in the room

LaneBeforeDuring appointmentAfter
PatientBooks visit, no prepAnswers cold, on the spot — rushed, unsure, exposed on intimate itemsLeaves; some answers were guesses
Frontstage HCP—Reads questions aloud, types answers, waits while patient thinksProceeds on possibly shaky data
BackstageVisit scheduledRA module open in EHR, clinician-enteredRA stored in record
SystemsSchedulingEHR RA form; clock running in-roomRecord updated

Proposed — patient-led, private, clinician-reviewed

Shaded cells mark what changed from today.

LaneBeforeDuring appointmentAfter
PatientGets a private link, fills RA at home, untimed — can check records, flag "not sure"Reviews with HCP; time spent only on flagged or sensitive items—
Frontstage HCPSystem sends invite + reminderSees pre-filled answers; edits, comments, confirms — stays the authorityFinalises record
BackstageRA generated + sent; responses held as draftDraft surfaced in EHR for review, not re-entryConfirmed RA committed, edit trail kept
SystemsSecure patient form + draft storageEHR shows patient draft with edit/commentAudit trail of clinician edits

Shaded = changed from current state

Today — risk assessment answered live, in the room

LaneBeforeDuring appointmentAfter
PatientBooks visit, no prepAnswers cold, on the spot — rushed, unsure, exposed on intimate itemsLeaves; some answers were guesses
Frontstage HCP—Reads questions aloud, types answers, waits while patient thinksProceeds on possibly shaky data
BackstageVisit scheduledRA module open in EHR, clinician-enteredRA stored in record
SystemsSchedulingEHR RA form; clock running in-roomRecord updated

Patient

Before
Books visit, no prep
During appointment
Answers cold, on the spot — rushed, unsure, exposed on intimate items
After
Leaves; some answers were guesses

Frontstage HCP

Before
—
During appointment
Reads questions aloud, types answers, waits while patient thinks
After
Proceeds on possibly shaky data

Backstage

Before
Visit scheduled
During appointment
RA module open in EHR, clinician-entered
After
RA stored in record

Systems

Before
Scheduling
During appointment
EHR RA form; clock running in-room
After
Record updated

Proposed — patient-led, private, clinician-reviewed

Shaded cells mark what changed from today.

LaneBeforeDuring appointmentAfter
PatientGets a private link, fills RA at home, untimed — can check records, flag "not sure"Reviews with HCP; time spent only on flagged or sensitive items—
Frontstage HCPSystem sends invite + reminderSees pre-filled answers; edits, comments, confirms — stays the authorityFinalises record
BackstageRA generated + sent; responses held as draftDraft surfaced in EHR for review, not re-entryConfirmed RA committed, edit trail kept
SystemsSecure patient form + draft storageEHR shows patient draft with edit/commentAudit trail of clinician edits

Patient

Before
Gets a private link, fills RA at home, untimed — can check records, flag "not sure"
During appointment
Reviews with HCP; time spent only on flagged or sensitive items
After
—

Frontstage HCP

Before
System sends invite + reminder
During appointment
Sees pre-filled answers; edits, comments, confirms — stays the authority
After
Finalises record

Backstage

Before
RA generated + sent; responses held as draft
During appointment
Draft surfaced in EHR for review, not re-entry
After
Confirmed RA committed, edit trail kept

Systems

Before
Secure patient form + draft storage
During appointment
EHR shows patient draft with edit/comment
After
Audit trail of clinician edits

Shaded = changed from current state

Decision 5: Interface and edge cases

Where the logical states become real screens: the patient's private entry, the "not sure" option on each question, and the ability to add more comments. Below you can find the annotated screens with decisions behind them. Click the right arrow to view more screens.

The final flow
The final flow

Create a free website with Framer, the website builder loved by startups, designers and agencies.