← Sword Health
Something new at Sword Health

Ship a resume path for paused members without exposing stale state

You’re the software engineer. Your team is in the room. Printed Oct 15, 2026.

A returning member needs continuity, while enrollment state must remain trustworthy.

The re-entry path protects a member’s momentum without sending them into a stale or incorrect care journey.

Who you’d be doing this for

“I keep getting asked why people enrolled, then never seemed to reach care.”

Parth Mishra · Population Health Manager

Oversees engagement with the covered cardiometabolic benefit for an employer population.

What is at stake

Members who return after account creation are being sent back to the beginning instead of toward care. You must weigh a faster return path against reliable account and entitlement state.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • member continuity vs. state correctness
  • fast experiment learning vs. durable navigation
  • cross-platform consistency vs. localized implementation
  • activation lift vs. trustworthy attribution

Why Sword Health

Pulse depends on covered members reaching an early care interaction that population health managers can recognize as engagement.

Written with these in mind

Product-minded mobile engineerGrowth platform builderFull-stack journey engineer

Not your kind of problem? 30 more at Sword Health, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.