What’s real in this build, and what we assumed
This is an evaluation build: a working front end with every journey clickable, running entirely in your browser. Nothing is sent anywhere. Here is exactly where the edges are.
Real in this build
- Every screen, control and state on phone, web, Mac, clinic and admin.
- One shared record across all of them. Open two tabs and they update each other live.
- Insights computed from the patient’s logs, with n-counts and evidence thresholds.
- The companion’s guardrails and grounding: it only cites published articles.
- Safety detection for crisis language and red-flag symptoms, on logs, messages and questions.
- RTM data-day and minute counting against the 2026 code rules.
- Print-ready report, CSV and JSON exports, offline queue, audit trail.
Scripted or simulated
- Denise’s 90 days of logs are generated from a fixed seed, counted back from today, with planted sleep, activity and weather effects.
- Voice logging types a scripted transcript; production uses on-device speech recognition.
- The AI is deterministic lexicons and statistics; production uses an LLM with retrieval over reviewed content and the same guardrail contract.
- Weather and Apple Health data are simulated. Other panel patients have weekly summaries only.
- Sign-in, Epic hand-off, e-prescribing and OARRS checks raise a message instead of calling out.
Assumptions we made
- Market: United States first, English, USD. Spanish is a phase-2 option.
- Model: patients join directly (Free, or Ebb Plus at $8.99/mo, $69.99/yr); clinics pay $14 per enrolled patient per month and clinic patients get Plus included.
- Name: “Ebb” is a working name; no trademark search has been done.
- Regulatory: no FDA claim. Insights and the outlook are positioned as general wellness, not diagnosis. RTM billing requires data from a device meeting the FDA definition; the regulatory pathway needs confirming with counsel.
- Billing: RTM rates shown are estimated national averages for 2026; each clinic must confirm with its Medicare contractor and payers.
- Privacy: HIPAA applies to clinic-linked data under a BAA; consumer data follows the FTC Health Breach Notification Rule and state consumer-health-data laws.
- Clinical content: the lessons are illustrative and would be written or reviewed by your clinicians before launch.
- Safety detection deliberately errs toward false positives.
- Browser: best demoed in Chrome or Edge. Date fields follow your computer’s region.
What we need from you
- The scope document, so we can reconcile this build against every requirement in it.
- Your brand name and any existing identity, or approval of the Cold compress direction.
- The clinical partner and the conditions to launch with.
- Your preferred EHR integrations (Epic, Oracle Health, athenahealth) and wearables.
- A decision on the regulatory position: wellness only, or a path to FDA clearance.
How this becomes the product
- Mobile: React Native (iOS and Android) sharing the design tokens and components shown here.
- Web and desktop: one React web app, wrapped with Tauri for Mac and Windows (menu-bar log, notifications, offline store).
- Backend: HIPAA-eligible cloud with encrypted storage, audit logging, FHIR integration, and an AI service with retrieval, evaluation sets and human review.