OuraWHOOPGarminApple
Start with the member's device
Target ecosystems are shown as design context; production compatibility and the final permission model remain to be confirmed.
Python Water for Clinics
Python Water for Clinics · A workflow in development
One clinic view. Across wearables.
Help us shape a source-aware workflow that brings member routines and wearable trends into one clear place—without pretending different devices measure the same thing.
No clinic cohort is currently enrolling. The group layer and routine/adherence model are in development and are not clinical hydration measurements or diagnostic products.
Connected hardware testingWe are testing device behavior and BLE reliability.
Group layer in developmentOpt-in cross-wearable groups are not yet a production clinic workflow.
General wellness scopeNo diagnosis, verified ingestion or clinical hydration measurement.
The design problem
Every device speaks a slightly different language.
Clinic members may arrive with Oura, WHOOP, Garmin or Apple devices. Their definitions and proprietary scores differ. We are exploring how a clinic could see routine adherence and within-person trends without pretending those scores are interchangeable.
→
Source stays visible
Use personal baselines
The proposed approach preserves the data source and emphasizes change within each person rather than a false universal readiness score.
→
Workflow hypothesis
Summarize, then discuss
We want clinic partners to help define what a concise, useful weekly summary should contain—and what it should leave out.
What partners would shape
Designed with clinics, not around them.
The immediate goal is not a longevity claim. It is a practical specification that clinics, members and engineers can evaluate before any cohort is proposed.
01
Permission
What should members understand before connecting a device, and what controls should remain visible?
02
Routine
Which hydration behaviors are simple enough to follow without turning a wellness program into medical monitoring?
03
Summary
Which trends deserve a coach's attention, and which belong only in the member's personal view?
04
Success
What evidence would show that the workflow is understandable, usable and worth further evaluation?
Evidence boundary
Wellness guidance. Clear boundaries.
- A routine/adherence model is not a clinical hydration measurement.
- A pressure event can indicate device activity; it does not verify who drank or how much was ingested.
- Different wearable scores should not be treated as directly equivalent.
- The concept does not diagnose, treat or prevent disease, and no longevity outcome is being claimed.
Questions to resolve
Before anything ships, the hard questions.
Is the cross-wearable clinic workflow available today?
No. Opt-in groups and the clinic-facing workflow are in development. These conversations are intended to shape requirements before any clinic cohort is offered.
Will proprietary readiness scores be compared directly?
That is not the proposed approach. Data sources should remain explicit, and interpretation should focus on documented shared measures and within-person changes.
Does the concept measure clinical hydration status?
No. The proposed model concerns routines, adherence and wearable-derived trends. It is not a diagnostic measure of hydration status.
What happens to member data?
Consent, revocation, deletion, security and clinic access controls are requirements to resolve before a clinic workflow can be considered ready. Do not submit patient or health information through this page.
Clinic design conversations
Build the right workflow with us.
We are looking for U.S. longevity and performance clinics willing to pressure-test the workflow, evidence boundaries and member experience.
