Generalized Body Ache

Generalized Body Ache records a reported overall aching sensation. It is a subjective symptom category, not a muscle-damage measurement, pain map or recovery score.

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.

This type describes a generalized experience. Lower Back Pain and Pelvic Pain have separate HealthKit identifiers for more localized reports. The code does not identify affected muscles, injury mechanism, inflammation or whether discomfort began after physical activity. Additional notes about location and impact are often more informative than comparing raw category numbers.

Fever, Chills and Fatigue can provide useful accompanying symptom history. The NHS lists aching as one possible flu symptom, but this pattern is not specific enough to diagnose flu. A high Body Temperature quantity and a Fever symptom report are also different kinds of evidence. Summaries should preserve each source rather than convert one into another.

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.

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.