Case Study 02

Statement of Health

Designing a guided online health form that combines dependent logic, required questions, medical communication rules, and a clear multi-step journey.

RoleUX/UI Designer
FocusComplex forms
MethodsFlow design, IA, UI
PlatformMember-facing web form
Statement of Health homepage mockup
Overview

Turning a rules-heavy health form into a guided digital experience.

The online Statement of Health needed to support employee information, identification of proposed insureds, health history, health questionnaires, lifestyle questions, and signatures while keeping users aware of progress and required completion.

Goals

  • Transform a rules-heavy health form into a guided digital experience.
  • Support employee, spouse, and dependent logic without overwhelming users.
  • Make required sections, progress, and completion status easier to understand.
  • Clarify medical communication, privacy, and verification expectations.

Expectations

  • Allow users to move through the form with confidence and clear status feedback.
  • Support conditional follow-up questions when users answer yes.
  • Use system-pulled data where appropriate while allowing required user input.
  • Provide a structure that can scale across health, lifestyle, and signature sections.
Primary Users

Members and dependents completing sensitive coverage-related forms.

Primary users included employees applying for coverage, spouses or dependents included in the application, and internal administrative staff who configured who needed to complete the Statement of Health before the email link was sent.

MVP Strategy

The MVP emphasized the most critical form behaviors first: section status, required completion, dependent-specific responses, and conditional follow-up inputs. This helped make the workflow testable before expanding into later enhancements such as mobile support.

Data-Driven Decisions

Decisions were informed by known business rules, certificate data availability, dependent selection rules, and auto-approval assessment requirements. The structure prioritized fields and sections that directly affected completion, verification, and processing accuracy.

The challenge

  • Conditional yes/no questions with follow-up inputs
  • Dependent-specific responses and verification
  • System-pulled employee/dependent information
  • Medical information messaging and privacy sensitivity

UX structure

  • Landing page with bilingual option and privacy link
  • Left-hand dashboard with status states
  • Progressive step-by-step sections
  • Required completion before submission
Key UX Decision

The form needed to guide users through complexity without hiding the overall structure of the journey.

The section dashboard and progress indicators helped users understand what was not started, in progress, and complete.

Selected Screens

Outcome

A clearer architecture for a sensitive, multi-step application.

The design clarified section grouping, status visibility, conditional question behavior, and how users verify information before submission.