Vomiting

Vomiting records a reported symptom with subjective severity. Its integer value is not the number of times someone was sick, the volume lost or an estimate of dehydration.

Apple uses HKCategoryValueSeverity for this type. Unspecified and notPresent mean different things. The codes identify labels; an average such as 2.5 is not a symptom measurement or a validated clinical score. Missing entries are unknown, not automatically notPresent.

No. One saved entry may summarize repeated vomiting, and several entries may describe the same period. Keep record count distinct from event count unless the writing source explicitly provides an event diary. The type also does not encode the appearance of vomit or whether fluids could be kept down.

Nausea and Diarrhea are separate reported symptoms. Their overlap can help describe an illness history but does not establish an infectious cause. Logged Dietary Water describes entered intake, which may be incomplete; it cannot establish what fluid was retained or replace an assessment of dehydration.

This is a logged observation, with no guaranteed recording frequency. Gaps between start times describe the saved logging history, not symptom-free intervals. Source changes, retrospective entry and overlapping records can change the apparent pattern. A sample's start and end describe the interval the source saved; they do not establish a distinct clinical episode or continuous symptom duration.

When summarizing a history, keep the category labels, reporting dates and source visible. Count explicitly absent observations separately from missing days. Review unexpected labels or repeated overlapping records before treating them as changes in health.

Seek urgent advice if vomiting continues and fluids cannot be kept down or dehydration develops. Vomiting blood, material resembling coffee grounds, or green vomit in adults requires emergency assessment. Sudden severe abdominal pain also needs emergency help.

No records of this type were found in the database research window, so severity frequencies, source differences and logging patterns could not be measured. This HealthKit type is not listed in the current PulsHealth sync catalog. Database coverage therefore cannot establish whether corresponding records exist in Apple Health, and an empty timeline does not establish symptom absence.