Constipation

Constipation records a reported difficulty with bowel movements, graded by subjective severity. It does not count bowel movements or measure stool consistency.

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.

A category entry does not tell you how many bowel movements occurred, whether stool was hard, or whether there was straining or incomplete emptying. Those details need a separate diary or source notes. Counting three saved observations means three records, not three bowel movements or three independent episodes.

Changes in routine, diet and medicines can be useful history to discuss with a clinician. Separately logged Fiber, Dietary Water, Bloating and Abdominal Cramps can provide context when their dates are reliable. A food log can be incomplete, and dietary water entries do not establish hydration status. Alternating constipation and diarrhea does not diagnose irritable bowel syndrome.

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.

Get prompt medical advice for constipation with blood in stool, ongoing abdominal pain, inability to pass gas, vomiting or unexplained weight loss. Persistent symptoms also deserve clinical review; do not use the saved severity code to rule out a problem.

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.