Streamlining Search for Faster, Safer Patient Matching

Streamlining Search for Faster, Safer Patient Matching

Care coordinators were spending 2–3 minutes manually matching medical faxes to patient records a slow, error-prone process with privacy risks. I led end-to-end research and design to transform this into a confident ~60-second workflow.

Team Structure

1 PM • 1 Designer • 2 Developers

1 PM • 1 Designer • 2 Developers

Role

Product Designer

Product Designer

Timeline

4 months

4 months

Overview

Overview

Dialogue's care coordinators triage 100+ medical faxes a day, matching each to the right patient. The old search only worked with a full name and birthdate — anything else meant guesswork. I redesigned it to search whatever the fax actually gave you.

Dialogue's care coordinators triage 100+ medical faxes a day, matching each to the right patient. The old search only worked with a full name and birthdate — anything else meant guesswork. I redesigned it to search whatever the fax actually gave you.

66%

66%

faster patient matching
(2–3 min → ~60 sec)

faster patient matching
(2–3 min → ~60 sec)

< 1%

< 1%

mismatch rate
(post-launch QA)

mismatch rate
(post-launch QA)

$15k

$15k

monthly savings
(time saved × CTM hourly cost)

monthly savings
(time saved × CTM hourly cost)

What's the problem?

1

Fax arrives with partial patient info

2

Search returns multiple similar names

3

Manually compare DOB, phone, address info

4

Cross reference profile details in another tab

Why this matters

  • 100+ faxes weekly = 16–25 hours of additional investigation time per week

  • High cognitive load during triage meant less time for patient-facing work

  • Privacy risk: a wrong match = PHI breach with legal and trust implications

Why this matters

  • 100+ faxes weekly = 16–25 hours of additional investigation time per week

  • High cognitive load during triage meant less time for patient-facing work

  • Privacy risk: a wrong match = PHI breach with legal and trust implications

"I wish we could search by phone number at the least. It’d make my life so much easier"

"I wish we could search by phone number at the least. It’d make my life so much easier"

Mariah (Care Coordinator)

Research & Discovery

I embedded with the CTM team for two weeks to see the real workflow, not assumptions — mixing shadowing, interviews, and hard data.

I embedded with the CTM team for two weeks to see the real workflow, not assumptions — mixing shadowing, interviews, and hard data.

8
SHADOWING SESSIONS

12
CONTEXTUAL INTERVIEWS

FULL WORKFLOW MAP

ANALYZED 100+ SUPPORT TICKETS

1

The search fields didn't match the faxes

90% of faxes included a phone number or Health ID — neither was searchable.

2

Disambiguation, not search, was the real problem

Common names returned too many matches — narrowing confidently was the hard part.

3

Anxiety drove behaviour, not speed

Common names returned too many matches — narrowing confidently was the hard part.

The constraint

Phone numbers and Health IDs lived in a separate legacy database the system couldn't interpret. Unifying them was a multi-month backend project — design had to work around that, not wait for it.

Exploration

How might we enable phone and Health ID search without waiting 6+ months for backend changes?

How might we enable phone and Health ID search without waiting 6+ months for backend changes?

I explored three approaches: search-type dropdown, radio button selectors, and prefix-based search — evaluating each against usability, speed, and engineering feasibility.

CONCEPT

Dropdown

Radio

Prefix-Based

USABILITY

Low

Medium

High

SPEED

Slow

Medium

Fast

EFFORT

Low

Low

Low

VERDICT

Prefix-based search was the clear direction: familiar pattern, minimal backend lift, and it supported both novice and power users without adding friction to every search.

The fix

Type phone:, id:, or email: in front of whatever you're searching, and the system knows exactly what to match — no new UI, no backend changes.

Type phone:, id:, or email: in front of whatever you're searching, and the system knows exactly what to match — no new UI, no backend changes.

Prefix search with smart match highlighting and stacked filters

phone: 5551234567 - phone search id: AB123456 - Health ID search
email: sarah@email.com - email search Sarah Johnson - default name search
phone: 555 name: Sarah - stacked filters

Design principles that guided the solution

Design principles that guided the solution

Progressive disclosure

Power features for those who want them, simple defaults for everyone else.

Immediate feedback

Every keystroke shows what matched, and why.

Forgiveness over precision

Typos and syntax slips gracefully fall back to standard search.

WHAT I OWNED, END TO END

  • Interaction specs for every state (empty, typing, results, errors)

  • Reusable "matched field" highlight component for future search features

  • Accessibility — screen readers announce matches

  • Responsive behaviour across desktop and laptop

  • Full developer handoff with edge-case annotations

Did it work?

Did it work?

"You don't know how amazing this is. Our team is blasting through triaging now."

James (Care Coordinator)

HOW WORK CHANGED

  • Phone became the #1 search method (85% of searches)

  • CTMs stopped cross-checking profiles — confidence replaced guesswork

  • 100% adoption within 24 hours, zero critical issues

BUSINESS IMPACT

  • Faster record matching → quicker clinical decisions

  • Est. 2–4 hr improvement in urgent referral response

  • Higher fax volume absorbed with no added headcount

So what's next?

Early OCR tests hit ~95% accuracy for auto-assignment — automation could eventually remove manual triage entirely. Long-term, unifying the databases would let the system auto-detect identifiers with no prefixes at all.

Thanks for reading!

Want to chat about a project? Drop me a line

Want to chat about a project? Drop me a line

Want to chat about a project? Drop me a line