Nausea

Nausea records feeling sick, graded by subjective severity. It is distinct from Vomiting: nausea can occur without being sick, and its category does not count vomiting events.

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.

Keep them as separate symptom histories. Nausea describes a sensation; Vomiting records a different reported symptom. Their timestamps may overlap, but this does not mean both occurred throughout the saved interval. One can be present while the other is explicitly notPresent.

A useful diary can capture recurrence, meal context, medicines and accompanying symptoms in source notes. The nausea code contains none of those details. Headache, Dizziness or Heartburn entries may add history when independently reported, but co-recording does not identify migraine, pregnancy, motion sickness or another cause.

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.

Arrange medical review for nausea that keeps returning or does not improve after a few days. Sudden nausea with tight or heavy chest pain, pain spreading to the arms, back, neck or jaw, or shortness of breath 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.