Dietary Water

Dietary Water stores the volume of water recorded as consumed. A sample is an amount contributed to a cumulative total, usually shown in milliliters. It is not a sensor measurement of hydration, body water or sweat loss. HealthKit accepts volume units; PulsHealth stores this type in mL. Apple's type definition describes the recording semantics.

Water for hydration comes from plain water, other beverages and moisture in food. A drinking-water app or connected bottle may capture only part of that total. Check what the source actually logs before comparing its number with guidance for total water intake. CDC's hydration overview explains that needs vary with activity, age and other circumstances.

Cadence follows the logging method. Entries may appear after a drink, when a bottle syncs or when a daily total is saved. Several samples with the same start time can be separate servings or a batch of retrospective entries; they are not evidence that all water was consumed simultaneously. Inspect sample duration and source before treating a gap as time between drinks.

A logged timestamp does not establish ingestion time. Workout duration alone cannot calculate sweat losses or a fluid prescription. Delayed logging can also shift entries to another reporting day. Compare activity and water only on days with meaningful logging coverage.

The researched 365-day reporting window contained no raw water samples and no stored water aggregates. Recorded ranges, outliers, logging cadence and workout or sleep comparisons were therefore unavailable. No measured chart or intake distribution is presented. This is a data-availability result, not evidence of zero intake or dehydration.

Body-mass changes around exercise can have several explanations, and a water log alone cannot isolate fluid balance. Caffeine entries can help identify beverage logging but do not tell you the beverage's water volume. Avoid replacing recorded amounts with assumed body-weight formulas. If a clinician has given a fluid limit, that individualized plan takes precedence over a generic app goal.

Use consistent units, record the amount actually consumed, and check the source after connecting another app. A daily source-specific sum is a recorded intake total; completeness remains a separate question. Apple's data-source controls help review which apps contribute records.