Insurance Verification

Verify insurance before a visit with plan details, member ID, eligibility, coverage status, copay estimate, and missing-information recovery. This example brings Insurance and Member together so patients and care teams can find the next task without losing context.

It includes representative records such as Confirm insurance plan and Enter member information. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Insurance Verification
Use this template in Figr

Template facts

Screen

Form

Primary action

Verify coverage

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Care team members need to verify coverage while keeping status, plan and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Insurance gives users an obvious place to start.
  • Supporting view: Member keeps the related context close.
  • Primary action: Verify coverage stays visible when people need it.
  • First signal: Status shows a useful value (Pending).
  • Second signal: Plan gives additional context (PPO).
  • Sample record: Confirm insurance plan.
  • Next record: Enter member information.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Insurance → Member → Verify coverage → Review outcome

Patterns used

Form, Insurance, Member, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to insurance and member. People need to distinguish Confirm insurance plan from Enter member information. Keep status visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Verify coverage”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Care Team Messaging, Referral Management, Medical Record Detail.

Start from this in Figr

Design a insurance verification screen inside our existing product. Use our current components, tokens and content language. Include Insurance and Member views, credible records like Confirm insurance plan, and a clear “Verify coverage” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr