Fever

Fever in Apple Health is a symptom category with a reported severity. It contains no temperature value and is separate from the Body Temperature quantity type.

Apple uses HKCategoryValueSeverity for this type. Unspecified is not the same as notPresent, and a missing record is neither. The integers identify labels; numerical averages and physiological reference ranges do not apply.

No. Mild, moderate and severe are symptom labels, not temperature bands. A severe fever entry cannot be converted to degrees Celsius or Fahrenheit. Store a thermometer result as Body Temperature and preserve how and when it was measured.

For adults, NHS guidance commonly describes a high temperature as 38°C or above, while also noting that a user can feel feverish below that reading. That clinical context does not change the HealthKit category codes or create a universal conversion from symptom severity to temperature.

Separate the time a user felt feverish from the time a thermometer reading was taken. Record Chills or other accompanying symptoms independently. A shared reporting day helps organize observations, but does not prove that every record belongs to the same illness.

A numerical temperature trend needs actual temperature measurements. Symptom entries alone cannot show a fever peak, response to treatment or a change in core temperature. If a high temperature is getting worse or not improving, seek medical advice rather than relying on the history chart.

This is a logged symptom, with no fixed sensor sampling schedule. Start-to-start gaps describe when observations were saved. A sample’s start and end times describe the interval supplied by its source; their difference does not establish the full duration of a clinical episode. Repeated or overlapping records need review before counting episodes.

This category is not currently listed in the PulsHealth sync catalog. No observations were present in the reviewed user data, so recorded severity frequencies, source differences and logging intervals could not be measured. That database coverage does not establish whether entries exist in Apple Health.