Provider Dashboard (Office-Facing)¶

Source: Call 34 (3-3), Call 35 (3-18) Existing strategy: itheraputix/symlink_docs/plans/dashboards/strategy.md Priority: Tier 3 — Bawa's #1 strategic priority, needs design work at 3/25 visit KB Requirement IDs: #137-#141, #142, #151-#153

Strategic Context¶

On 3-18, when asked to choose between provider dashboard and companion app, Bawa chose dashboard:

"At this point the back end is more important."

This aligns with the existing dashboard strategy (2026-02-12) which defined two dashboards: 1. Protocol Intelligence — for surgeon (cohort-level, protocol versioning) 2. Patient Operations — for care team (individual patients, daily triage)

What Bawa described on 3-18 is the Patient Operations dashboard — the morning workflow tool for staff.

Requirements From Bawa (3-18)¶

Patient list with active monitoring (KB #137)¶

Bawa: "On the back end provider dashboard... if it had the list of patients that are actively being monitored."

Show all patients currently in the system with their status.

Daily conversation summaries (KB #138)¶

Bawa: "Gives you a little summary of what the conversation was like for that patient yesterday."

Each patient row shows a one-line summary of yesterday's AI conversation. Staff can expand for details.

Concerning items flagged (KB #139)¶

Bawa: "If there's anything concerning... a little summary... a one liner or something like that."

Flag conversations that triggered triage, escalation, or concerning patterns. Visual differentiation from routine interactions.

Triage ranking by concern level (KB #140)¶

Bawa: "It also could rank them... you just log in the morning... whoa, what is this? That's concerning. Let's follow up on this person."

Morning workflow: log in, see patients ranked by urgency. Most concerning at top. Staff immediately knows what needs attention.

Action items surface on dashboard (KB #141)¶

Bawa: "It gives us some action items... someone needs a refill they can put it in there and that can show up on the back end provider side."

Refill requests, follow-up needs, and other action items appear as tasks for staff to process.

Refills as office tasks, not patient calls (KB #142)¶

Bawa: "We don't need a phone call in the middle of the night for that."

Medication refill needs surface as dashboard action items during business hours, not as urgent patient escalations.

Requirements From Bawa (3-3)¶

Analytics / FTE savings¶

Bawa (3-3): Prove value by calculating time saved on phone calls and reduced ER visits.

Dashboard should show metrics: conversations handled by AI, estimated calls deflected, time saved.

Monetization visibility¶

Bawa (3-3): Who absorbs cost? Need to demonstrate ROI.

Dashboard metrics feed the business case: cost per case reduction, conversation deflection rate.

HIPAA compliance¶

Bawa (3-3): Patient data handling must be compliant.

Dashboard access requires authentication. Patient data display follows minimum necessary principle.

Existing Strategy Alignment¶

From dashboards/strategy.md — the Patient Operations dashboard concept already covers:

Strategy concept	Bawa's 3-18 requirement	Match
"Which patient needs attention right now?"	Triage ranking by concern	Direct match
"7-day journey briefing"	Daily conversation summaries	Bawa wants daily, strategy says 7-day. Build daily first, expand to weekly trend.
"Suggested Opening"	Not mentioned by Bawa	Nice-to-have, build if time allows
"Inferred Risk" scoring	Concerning items flagged	Direct match
"Deming 1-10-100" prioritization	Ranking patients by urgency	Conceptually aligned

Morning Workflow (Bawa's Vision)¶

Staff arrives → opens dashboard → sees:

┌──────────────────────────────────────────────────────┐
│ 🔴 HIGH CONCERN                                      │
│ ┌─────────────────────────────────────────────────┐  │
│ │ Patient A (Day 4) — Reported increased calf     │  │
│ │ pain, triggered DVT triage. Told to call office. │  │
│ │ ACTION: Follow up on DVT screening result       │  │
│ └─────────────────────────────────────────────────┘  │
│                                                       │
│ 🟡 NEEDS ATTENTION                                    │
│ ┌─────────────────────────────────────────────────┐  │
│ │ Patient B (Day 12) — Projected to run out of    │  │
│ │ Percocet by Saturday. Needs refill.             │  │
│ │ ACTION: Call in refill                          │  │
│ └─────────────────────────────────────────────────┘  │
│ ┌─────────────────────────────────────────────────┐  │
│ │ Patient C (Day 30) — Asked about driving. Still │  │
│ │ using walker, took pain meds 3x yesterday.      │  │
│ │ ACTION: Discuss at next visit                   │  │
│ └─────────────────────────────────────────────────┘  │
│                                                       │
│ 🟢 ROUTINE                                           │
│ ┌─────────────────────────────────────────────────┐  │
│ │ Patient D (Day 8) — Normal check-in. Exercises  │  │
│ │ on track. No concerns.                          │  │
│ └─────────────────────────────────────────────────┘  │
│ ┌─────────────────────────────────────────────────┐  │
│ │ Patient E (Day 45) — Reported knee warmth after │  │
│ │ exercises. AI handled with icing guidance.       │  │
│ └─────────────────────────────────────────────────┘  │
└──────────────────────────────────────────────────────┘

3/25 Visit Plan¶

This is the feature to design IN PERSON with Lauryn: - Walk through her actual morning workflow - What does she check first? - What information does she need to decide who to call? - What action items come up most often? - How does she currently track refill requests?

Lauryn's input will define the dashboard layout and priority signals. Bawa reviews at 5pm and confirms.

Implementation Notes¶

Backend: API endpoints that aggregate patient conversations, triage events, and action items
Frontend: New dashboard view (separate from BCC portal which is developer/protocol-focused)
Data sources: check-in responses, triage events, medication tracking, conversation logs
Auth: staff login (existing auth system)