Companion App (Caretaker) — DEFERRED¶
Source: Call 34 (3-3), Call 35 (3-18) Status: Deferred — build after backend/provider system is settled KB Requirement IDs: #151-#153
Strategic Decision (3-18)¶
Bawa: "At this point the back end is more important."
Bawa: "Getting that sorted out first... once we have a pretty solid app... I think the companion app is gonna be much easier."
Bawa: "Otherwise you're gonna end up having to literally, every time you change one thing on this, you're gonna have to go change it on that... there may be some asymmetry."
Decision: Backend/provider dashboard first. Companion app after the main system is stable. Do not build both in parallel.
This overrides the high excitement Bawa showed on the 3-3 call, where he described the companion app as a significant opportunity. He still wants it — the sequencing just changed.
Requirements Captured (3-3 — Preserved for Future)¶
These requirements were captured on the 3-3 call and remain valid for when the companion app is built.
80% overlap with main app¶
Chris estimated and Bawa agreed — the companion app shares most of its functionality with the main patient app. Building it after the main app is stable means most of the work is already done.
Caretaker-specific features¶
| Feature | Details |
|---|---|
| Time-limited access | Caretaker access expires after recovery period |
| Magic link invitation | Patient invites caretaker via link, no account creation needed |
| Conversation sharing (opt-in) | Patient chooses whether to share their AI conversations with caretaker. Delicate privacy issue. |
| Equipment guidance | Caretaker sees same equipment walkthrough, ice machine instructions, etc. |
| Smart escalation routing | Equipment issues → DME provider, not surgeon |
Privacy constraints¶
Bawa (3-3): Sharing patient-HJ conversations with caretaker should be opt-in by patient.
Patient controls what the caretaker sees. This is a privacy and trust issue.
DME companion (3-3)¶
Another 80% overlap application. Smart escalation routing — equipment issues go to DME provider, not doctor. Example: broken walker → route to DME, not surgeon.
Bridge from onboarding (3-18)¶
Bawa: "The help thing would be then when we do the companion app, you could add that would be a segue at some point later on."
The onboarding question "Will you have somebody helping you after surgery?" is preserved specifically as the future entry point for the companion app invitation.
When to Build¶
Prerequisites before starting companion app: 1. Main patient app stable and validated with real patients 2. Provider dashboard operational 3. Medication management working 4. Protocol gap coverage at acceptable level (Conversation Factory producing results)
Only then does the companion app become the right investment.