Walkthrough

This is the landing screen because it answers what caregivers actually need first: a single place to see what's happening across everyone they're responsible for, instead of reconstructing it from memory after a missed call. Caregiving is fragmented by nature — one relative's cardiology referral, another's insurance hold, a third's provider callback — and when the only place those threads live is a caregiver's head, something always slips. The dashboard collapses them into a single glance so nothing has to be remembered in order to be tracked.

Most family caregivers manage care for one person. An estimated 14% manage two or more, roughly 8.8 million people, about 1 in 39 Americans (AARP/National Alliance for Caregiving, Caregiving in the US 2025). That's a minority of caregivers, but a large and specific group that no part of Solace's current caregiver experience is built for. Designing for that harder case also makes the single-relative case trivial by default, one card on the dashboard instead of two.

Entries are written in plain language with a simple status tag instead of medical or insurance jargon, because caregivers aren't medically trained and need to parse an update in seconds, not decode it. A line that reads 'Prior auth pending — cardiology referral' tells a caregiver nothing they can act on. 'Waiting on the insurer to approve the heart-doctor visit — your advocate is following up' tells them exactly where things stand and who's on it, which is the whole point of having an advocate in the first place.

This is the core idea of the demo. Missing a call currently means losing the update entirely — the caregiver either wasn't on the line, or was on the line and is now carrying the whole thing in their head. Turning the transcript into a plain-language summary and action items automatically closes that gap, without the caregiver needing to have been on the call and without the advocate having to manually re-summarize every conversation afterward. The update survives the call, and it lands directly in the timeline where it belongs.

Matching Solace's actual design system instead of building a generic dashboard was deliberate. A demo that looks bolted-on reads as 'I had an idea.' A demo that looks like it could ship inside the existing product tomorrow reads as 'I understand this product well enough to extend it.'

No real integrations, no real patient data, no advocate-side tooling, no real authentication. Solace has almost certainly already solved these problems or is actively solving them, and rebuilding any of it would be wasted effort. The point of this demo is narrow on purpose: show that a real gap exists in the stated product, and show what closing it could look like. Everything outside that claim was deliberately left out.

This demo uses fictional data, but a real version touches protected health information and personally identifiable information directly, medical conditions, medications, insurance details, contact information. Shipping this for real would require HIPAA-compliant infrastructure end to end, not just at the edges. Three risks specifically worth naming: first, PHI and PII protection, encryption, access controls, audit logging, and business associate agreements with any vendor involved. Second, consent granularity, a patient may want one caregiver to see medication details and not a mental health note, and multi-caregiver access has to respect that, not just extend blanket visibility to everyone with access. Third, AI-generated accuracy, a call summary agent that populates a care plan automatically is only as trustworthy as its error rate, and in a healthcare context a wrong or hallucinated action item isn't a minor bug, it's a real risk to someone's care. A production version would need human review in that loop, not full automation.