Alcoholic Beverages

Apple HealthKit stores the number of standard alcoholic drinks as a cumulative quantity in count units. It is a logged amount, rather than beverage volume, a count of containers or a blood-alcohol reading.

The writing source determines how a serving becomes a standard-drink count. Check that convention before comparing apps or converting counts to grams of alcohol. The identifier and count unit do not carry a region, alcohol-by-volume percentage or serving size.

No. Glass size, recipe and alcohol concentration matter. The U.S. NIAAA definition uses 14 grams of pure alcohol per standard drink. Approximate examples under that convention are:

These are explanatory examples, not measured user data or a recommended intake. A larger pour or stronger drink can represent multiple equivalents. Retain fractional counts when a source uses them. The NIAAA drink-size calculator illustrates how strength and serving size change the count. Do not apply the U.S. conversion to every source without checking its normalization.

The 365-day example coverage review found no raw alcoholic-beverage samples or stored aggregates. It therefore provides no measured value range, outlier distribution, source pattern, cadence or workout/sleep comparison. An empty history does not establish abstinence, zero consumption or complete tracking.

The reviewed PulsHealth sync catalog does not include this identifier. Database absence therefore does not establish what is present in the phone’s HealthKit store.

No measured graph is shown because there are no observations for this type in the selected window. The source guidance here explains how to interpret records when they are available.

A source can write a point entry for a drink, an interval for several drinks or a retrospective daily total. Apple’s example uses a point sample. Repeated timestamps and batch imports can reflect logging behavior rather than a drinking schedule.

Sum compatible contributions within a source after checking corrections and duplicate imports. Show how many days have records, keep unrecorded days unknown, and distinguish an explicitly logged zero from a missing entry. Do not divide a count by a zero-duration timestamp to estimate a consumption rate.

Such comparisons require reliable consumption times and sufficient logging coverage. A log timestamp during a workout or asleep interval does not prove alcohol was consumed then. Bedtime, exercise, illness and recording behavior can change alongside reported intake, so an aligned trend is descriptive rather than evidence of an alcohol effect.

Sleep Analysis, Heart Rate and HRV SDNN have separate measurement and coverage rules. No empirical relationship was estimated here because alcohol records were absent.

Use a log as context for a discussion, with serving definitions and missing days visible. A recorded count does not measure impairment, establish a safe personal intake or diagnose alcohol use disorder. It cannot be converted to Blood Alcohol Content from count alone.

Health interpretation depends on timing, medications, pregnancy, medical history and individual circumstances. Avoid labeling a logged day “healthy” simply because its count falls below a generic threshold; the data type provides no such certification.