Wireframe draft — for discussion, not final visual design

Care Coordinator for Lilly Access & Value

Patient and physician experience, powered by Cognesity, for employer-sponsored Lilly Access & Value enrollees. Cogni supports patients between visits; their treating physician — added during enrollment, not already on file — is kept updated and can respond back. This walks through both sides of that loop.

v0.1 · adapted from Cognesity's care-coordination model for the employer-sponsored channel · click a step below, or use Prev / Next
Patient journey
Physician view — different persona, referenced for context
For our discussion — not a product screen
Step 1 of 11
9:41●●●

Care Coordinator

POWERED BY COGNESITY, WITH LILLY ACCESS & VALUE

Continuous support between visits — included as part of your employer's Lilly Access & Value benefit.

Activate my Care Coordinator
Already have an account? Log in
Screen 1 of 11

Activate

Entry point for an employer-sponsored enrollee. Unlike LillyDirect, there's no existing physician referral record to draw on — the patient is coming in through their employer's benefit, so the app has to establish who's treating them, not just confirm it.

Backend tie-in
  • Deep-link entry from an employer HR/benefits portal should land here with the employer/Group ID pre-filled — see Screen 2, where it's now a required field, not optional.
  • No physician pre-fill here (contrast with the LillyDirect version) — Screen 2 adds a "treating physician" field instead of assuming one's already on file.
9:41●●●
← Back

Let's confirm it's you

We verify identity before any health information is shared — the same check Cogni runs before every check-in.

Jordan
Alvarez
MM / DD / YYYY
Required
Your treating physician
Required
Required
Required
Continue
Screen 2 of 11

Identity verification

Confirms the patient matches an existing chart or employer enrollment record before any clinical content is shown or discussed.

Backend tie-in
  • Mirrors the voice channel's Identity Verification state (Architecture v3 §6) — same two core fields (name + DOB), so a patient starting a check-in later is asked exactly what they already confirmed here, not re-interrogated.
  • This record becomes the patient_id key the Memory Layer (v3 §17) is built around.
Dev notes
  • Failed match should not reveal *why* it failed (existing account vs. no record) — same non-disclosure principle as the phone channel.
  • Treating physician is now three required fields (name, email, phone), not one — Care Alerts and Care Team assume a physician is on file to notify, and email specifically is what makes delivery work at all; phone is captured for potential future use (e.g. SMS alerts) even though nothing reads it yet. Needs a lookup/verification step of its own (spelling variants, multiple physicians, clinic vs. individual name) that isn't designed yet.
Viewing: First-time Steady-state
9:41●●●

Welcome, Jordan

Let's set up your care plan
A quick conversation with Cogni — covers your current medication, weight goals, and how you're feeling. About 5–10 minutes.
Start now
Medication
Not set up yet
Weight trend
Not set up yet
Message care team
Recent activity
Nothing yet — this fills in after your first check-in.
Home
Trends
Alerts
Learn
Care team
Screen 4 of 11

Home — two states, same screen

Toggle above switches between them directly, rather than describing the second one in prose. A brand-new patient has no medication or weight data yet — showing "On track" or a future-dated check-in would be false, so the first-time state prompts starting that first conversation now instead.

Backend tie-in
  • "Start now" / "Talk to Cogni now" both lead into Screen 5, same mechanism either way — but the first session is where the baseline actually gets established. Medication and Weight Loss are mandatory every check-in (v3 §9.1–9.2), and their first-call phrasing variants (built for exactly this moment) ask "What medication are you currently taking?" cold, rather than "Last time you were on X — still the case?"
  • No separate intake form exists or is planned — Cogni's own pathway questions are the single source of this data, in the exact wording the pathway tables specify. A typed form asking a similar-but-not-identical question would just create a second, uncontrolled copy of the same fields.
  • Symptoms are covered without adding a third mandatory pathway — Medication and Weight Loss stay the only two, deliberately, so calls don't bloat into a checklist. Instead, the existing TRIAGE opener (v3 §7) gets a first-call-specific version: rather than a generic "How can I help today?", the first session asks something more pointed — "How have you been feeling since starting your medication — any side effects?" — so the trigger-cue system (v3 §10) has something concrete to scan and route from on the one call where missing something matters most.
  • Timing (5–10 min) is a rough estimate, not a tested number: MED (7 questions) + WL (5 questions) + the mandatory closing sequence puts a quiet first call around 5–6 minutes; a symptom that triggers a pathway (e.g. Digestion, 6–7 more questions) pushes the long end toward 10–13. Treat this range as a placeholder to revisit once a real conversation gets timed.
  • Which state renders is driven by whether a first check-in has happened yet — not a setting the patient controls; the toggle here is a wireframe device only, not part of the product itself.
9:41●●●
← Back to Home

Checking in with Cogni

Scheduled check-in · can also be started anytime from Home

Cogni is listening
Speak naturally — Cogni waits for you to finish before responding.
End session
Screen 5 of 11

Voice session with Cogni

Corrected from earlier drafts, which modeled this as an incoming phone call — that's not right. Telephony (clinic calling a patient, or a patient calling a clinic) is Provider Portal territory. This app's voice interaction happens entirely in-app: a scheduled check-in, or started on demand from Home ("Talk to Cogni now").

Backend tie-in
  • Same Turn Cycle and pathway engine as the rest of this architecture (v3 §2, §8) — the interaction model doesn't change, only the transport does (in-app audio session vs. a phone call).
  • Scheduled entry: a push notification/reminder opens directly into this screen at the scheduled time. On-demand entry: tapping "Talk to Cogni now" on Home does the same.
  • First session specifically: TRIAGE's opener is more pointed than usual ("How have you been feeling since starting your medication — any side effects?") rather than a generic "How can I help today?" — see Screen 4's annotation for why.
9:41●●●
← Back to Home

Here's what we covered

Thursday, Aug 14 · 2:04–2:13 PM

You're taking your medication as prescribed.
Your weight has continued trending down since last month.
You mentioned some mild nausea — we'll keep an eye on that.
✓ Shared with your care team
Share this with my care team now
Ask a question about this session
Screen 6 of 11

Session summary

Plain-language recap in the patient's own app — not the clinical transcript, not a tier label, just what was actually discussed.

Backend tie-in
  • Generated from the session's answered_questions and DDM state (v3 §4), rewritten in plain language.
  • The mild-nausea line is a good example of an Escalation-Relevant field (Escalation Logic §3) that's Follow-up-weighted, not alarming — patient sees a calm reflection of it, not a clinical severity score.
  • "Shared with your care team" (green, already sent) and "Share this with my care team now" (button, patient-initiated) are two different triggers into the same delivery mechanism — one automatic per the tiering logic, one on demand. Neither depends on the provider having set up anything beyond receiving email.
9:41●●●

Care alerts

We'll only post here when your care team needs to follow up — not for routine check-ins.

Care team notified
Aug 12 — Your care team was notified about symptoms you shared and may reach out.
Follow-up completed
Aug 3 — We recommended you seek immediate care. Your care team followed up the same day.
Home
Trends
Alerts
Learn
Care team
Screen 8 of 11

Care alerts

Patient-friendly reflection of Urgent/Emergency events — deliberately does not expose internal tier names or clinical scoring.

Backend tie-in
  • Maps to the four-tier model in Escalation Logic §1/§5 — the amber card reflects an Urgent tier, the red card reflects a past Emergency escalation, written as a calm, past-tense, reassuring log entry rather than re-surfacing crisis language.
9:41●●●

For you

Suggested based on what you've shared in your check-ins.

Managing mild nausea on GLP-1 medications
4 min read
Staying on track with your dose schedule
3 min read
Understanding your weight trend
3 min read
Home
Trends
Alerts
Learn
Care team
Screen 9 of 11

Learn

Education surface — content selection can be personalized by which pathways a patient's check-ins have actually triggered, not generic content for everyone.

Backend tie-in
  • Candidate signal: completed/triggered pathways this check-in and last (v3 §10 trigger cues) — the nausea article above follows directly from a Digestion pathway trigger.
9:41●●●

Your care team

Dr. Priya Nair
Your treating physician
Last summary shared: Aug 1
Aug 2New care instructions from Dr. Nair — view
Send a message
We've let Dr. Nair know you're using Care Coordinator and will keep her updated — nothing extra for either of you to set up.
Home
Trends
Alerts
Learn
Care team
Screen 10 of 11

Care team

Shows who's treating the patient and closes the loop the proposal describes — adapted here since the physician wasn't already known the way a LillyDirect referral would be; they were added on Screen 2 and notified for the first time as a result.

Backend tie-in
  • "New care instructions from Dr. Nair" is the patient-side landing point for the physician's "Respond to Patient" action shown in Screen 12 (the physician's Clinical Summary view).
9:41●●●
← Back

Settings

Profile
Jordan Alvarez · DOB on file · (617) 555-0148
Program
Lilly Access & Value — via Acme Co.
SMS reminders
App notifications
Privacy & data
Log out
Screen 11 of 11

Settings

Standard account management, plus a visible confirmation of the employer program and the treating physician added during enrollment.

Inbox — Dr. Priya Nair
🔴 Urgent — Jordan Alvarez
Reported a symptom meeting urgent-review criteria — for your awareness.
Lilly Access & Value Care Coordinator
Clinical Summary: Jordan Alvarez — open below
Lilly Access & Value Care Coordinator — Clinical Summary
Patient: Jordan Alvarez  |  DOB: on file  |  Physician: Dr. Priya Nair
Jordan Alvarez, your patient, enrolled in the Lilly Access & Value Care Coordinator through their employer's benefit and listed you as their treating physician. This is Cogni's encrypted email channel — you'll receive care summaries and urgent alerts here going forward. No action is required to keep receiving updates.
Current medication / dose
Tirzepatide 5 mg — Week 7 of titration
Adherence score
92% (11 of 12 doses)
Weight trend
↓ 9.4 lbs since initiation
Side effects
Mild nausea, improving
Engagement
8 of 8 check-ins completed
Tier
Follow-up
Suggested discussion topic
Consider reviewing readiness for escalation to 7.5 mg at next visit.
No urgent alerts this period — Jordan will be escalated immediately if severe symptoms are reported
View Jordan Alvarez's Progress Portal →
Respond to Patient →
This summary supplements — not replaces — clinical judgment. No diagnosis or treatment change is recommended by the Lilly Access & Value Care Coordinator.
Screen 12 — physician view

Clinical summary & urgent alert

Adapted from the Cognesity → LillyDirect proposal's example (p.5–6) — reused the same patient (Jordan) and physician (Dr. Nair) from the patient-side screens so the two views read as one continuous story. The teal intro card is the one substantive addition versus the LillyDirect version: since this physician has no prior relationship with Cognesity or Lilly Access & Value, the email opens by explaining why they're receiving it at all, rather than assuming that context is already understood.

Backend tie-in
  • This is the periodic, non-urgent side of the loop — maps to the Follow-up / Routine tiers in the Escalation Logic doc (§1, §5). "Suggested discussion topic" is a good example of a Follow-up-weighted field surfacing inside a routine summary rather than as its own alert.
  • The urgent inbox item (left) is the Urgent tier's near-real-time alert (Escalation Logic §5) — independent of the physician ever opening it, matching the proposal's central safety claim: "patient safety escalation is independent of physician review." Jordan already got directed to appropriate care before this email was even sent — true regardless of channel.
  • Tier badge now uses our real vocabulary: Emergency, Urgent, Follow-up, Routine (Escalation Logic §1, §5) — replacing "AI Risk Score" from the proposal's original example. Color-coded consistently: red = Emergency, amber = Urgent, blue = Follow-up, green = Routine. This example is Follow-up.
  • No separate "Provider Onboarding" screen here (removed from an earlier draft) — the physician's actual first notice comes from LillyDirect or the employer health plan, outside this product's scope. This banner is simply the first thing they see once Cogni's own encrypted-email updates start.
Not a product screen

Discussion Topics for Our Design Workshop

Six things we'd like to align on together before finalizing. Each links back to the screen it came from.

Screen 1 — Activate
Physician introduction framing
Unlike LillyDirect, this physician may be hearing from Cognesity and Lilly Access & Value for the first time — no existing referral trust to lean on. Worth a joint pass on how Screen 12's first-contact messaging is framed.
Screen 3 — Check-in preferences
Consent & disclosure language
Exact wording for check-in consent will need a pass from your legal/compliance team before this ships.
Screen 8 — Care alerts
Escalation tier wording
Patient-safe phrasing for each alert tier is a first pass from us — worth a review from your clinical/medical affairs team.
Screen 9 — Learn
Education content source
Should this be Lilly Access & Value-provided content, co-branded, or sourced independently?
Screen 12 — Clinical summary & alert
Provider Portal scope
Is deeper physician access — full patient timelines via the Progress Portal — part of this phase, or a later one?
Screen 12 — Clinical summary & alert
Safety-independence disclaimer
Exact wording confirming patient safety guidance never waits on physician review needs your legal/clinical sign-off.
Draft wireframes for internal review and partner discussion — layout and copy are illustrative, not final. Patient screens (1–11), the physician view (12), and our discussion topics (13) are intentionally kept low-fidelity so the conversation stays on flow and content, not visual polish. Built for the employer-sponsored Lilly Access & Value channel.