JUAN GALAVIS Principal Product & Service Designer · Healthcare · Accessibility · AI-first teams
← All work

Streamlined flows · Healthcare · Accessibility · Forms

Overseas claims, without the paperwork.

Members abroad had to download a PDF, print it, sign it, scan it and upload it with their bills, and only found out what was required halfway through. We turned it into a guided, validated flow inside MyBlue.

A member in Lisbon starts an overseas claim on her laptop, receipt in hand
Role
Lead Product Designer, via Optimity Advisors
Client
BCBS Federal Employee Program, 5M+ members
Worked with
Product managers, engineering, overseas members
Scope
Medical and pharmacy claims MVP, MyBlue web
−0% overseas calls to customer service
0 fields on the paper form
1 guided steps instead
0 patient fields prefilled
0 bills or meds uploaded per claim
2→1 claim forms, one entry point
01 · Discover

More benefits, more calls.

FEP expanded its overseas benefits, and calls from overseas members to customer service climbed with them. The digital self-service program had one KPI that mattered here: reduce calls to the call center.

The claims process was a big driver. Medical and pharmacy claims ran on downloadable PDFs that had to be printed, signed, scanned and uploaded along with every bill. And members didn't see what was required until they were already in the middle of filing a claim.

Disjointed stepsDownload, print, sign, scan, upload. Separate forms for medical and pharmacy, instructions on the back.
Requirements found too lateSignatures, itemized bills and other carriers' paperwork only surfaced once a member was mid-claim.
No validationErrors only surfaced after review. A bad bank detail meant a paper check in US dollars.
Accessibility barriersTiny boxes, dense fine print and a layout built for paper, not screen readers.
The forms we started from
Page one of the FEP Overseas Medical Claim Form, a dense two-page paper form
Issue 01 / 07 Your ID, in 13 tiny boxes

Enrollment code and member ID typed one character per box, with nothing to check them against.

→ Pulled from the member's account, never retyped.
60form fields
2pages, one of fine print
5steps: download, print, sign, scan, upload
02 · Define

Three bets, one restructure.

With product managers and member usability sessions we scoped a first MVP around three hypotheses. Underneath them, the move was restructuring, not adding features: every section of the paper form mapped to a step, a prefill, a condition or an upload. Nothing the plan already knew gets asked twice, and nothing optional is shown until it's needed.

01Replace the downloadable PDFsMedical and pharmacy claims as native forms inside MyBlue. No printing, no scanning.
02Steps, with requirements up frontBreak the process into steps and tell members what they'll need, including document uploads, before they start.
03Prevent errors, don't report themLive field validation plus backend integration, so known data is prefilled and mistakes are caught before submit.
Paper form
Digital flow
1 · Patient information8 items, all typed
Step 1, prefilledPrefilled
2 · Other health insurance11 items, shown to everyone
Step 1, one checkboxConditional
3 · DiagnosisReason, work, accident
Step 2Inline help
4 · ChargesDates, totals, bills scanned separately
Step 3 + uploadUpload
5 · ReimbursementCurrency, check, bank boxes, provider
Step 4, branches by choiceConditional
SignaturePrint, sign, scan, upload
Agree and AuthorizeOne checkbox
Page 2 instructions~900 words of fine print
Helper text at the fieldInline help
Story map: the MVP line Activities across, tasks down. Everything above the line shipped first.
01 · Start
Read what you'll need
Know medical and pharmacy are separate
02 · Confirm email
Keep the email on file
Or add an alternate for receipts
03 · Claim type
Choose medical or pharmacy
04 · Patient info
Review prefilled details
Update mailing address
Add other insurance, if any
05 · Diagnosis or Rx
Describe reason for visit
Flag work or accident
Rx: up to 10 medications
06 · Charges and bills
Dates, count and total
Upload up to 10 bills
07 · Reimbursement
Assign to member or provider
Check or electronic transfer
Agree and authorize
08 · Confirm
Get a confirmation email
Know when it shows up
MVP line
Prefill more from member data
Claims for dependents
Save as draft
Claims dashboard
Native app, camera upload
03 · Develop

One question at a time.

Rough wireframes broke both claims into progressive, multi-step forms. Each one opens with what you'll need, then contact and claim type, then a distinct path per claim type. Required fields are flagged and warnings guide completion. The high-fidelity prototype used MyBlue design system components and became the test bed for usability sessions with overseas members.

Getting Started screen listing what the member will need
01 · Get started Requirements up front

What members used to discover mid-claim is now the first thing they see: policy info, claim info and receipts. Nobody stalls halfway to go find a bill.

Error states

Catch it now, not after review.

On paper, a missing field or signature only showed up after the claim was reviewed, or as a check in the wrong currency. In the flow, validation happens before you can move on, and it's designed to be read by everyone, including screen reader users.

Error summary listing every blank other-insurance field by name
Scenario from the prototype: member has other insurance, all fields left empty.
Fields with red borders and warning icons inline
One summary, every problem namedThe banner lists each blank field by its label, so you know the size of the fix before you scroll.
Each field flags itselfRed border plus an icon, never color alone, so the summary maps straight to the field.
Only what you opted intoOther-insurance fields appear, and validate, only when the member says they have other coverage.

The prototype also covered terminated-member variants of both flows, entry points from across MyBlue, and responsive specs for every step.

04 · Deliver

Built only from what already existed.

For the final design we used components exclusively from the existing MyBlue design system. It kept the new flow consistent with the rest of the portal, inherited its accessibility work, and cut development and QA time, which mattered on an MVP timeline. Annotated, spec'd designs went to the dev team with responsive views for every step.

Desktop view of step 2, Diagnosis, in the MyBlue portalStep 2 in the portal, built on MyBlue design system components.
05 · Results−30%overseas calls to customer service

The self-service program's KPI, moved by a claim form.

And the work kept going: the product owner took the future-iterations backlog to leadership to include in an upcoming PI planning session.

The backlog that went to leadership

Prefill more from what the plan already knows

File claims for dependent members

Save partially completed claims as drafts

A dashboard to track claims and manage drafts

Native mobile, with the camera for document upload

What it taught us

Expanding benefits without a digital path just moves the work to the call center.

Self-service in a regulated product isn't polish, it's capacity. Ship the MVP, measure the calls, and let the numbers fund the next iteration.

WhoWhatWhy redesign on two phones
Next · 05 / 05 · Unified brandsNews & Media Brand Design UX/UI
Read the next case study