decoderHealth brings different kinds of health information into one view: connected records, local observations, and calculated estimates. Keeping those categories clear makes the charts and dashboard easier to interpret.
The challenge of incomplete records
A health record depends on a source having captured and shared it. Food logging may cover only some meals, sleep stages may be missing, and a denied permission can prevent a record from reaching decoderHealth. An empty chart does not prove that the underlying activity did not happen.
Changes in a device, source app, or permission can also change data coverage. Consider those changes before treating a new pattern as a change in your routine.
Measurements, observations, and estimates
Connected records come from permitted Health Connect or Apple Health data. Examples include weight, water, glucose, recorded workouts, and sleep sessions. Some values are platform aggregates rather than individual readings.
Local observations include fasting sessions and Check-Ins. Their times, ratings, notes, and targets come from what you record inside decoderHealth.
Calculated estimates use available records and profile inputs. BMI, BMR, expenditure, and energy balance have defined inputs and fallbacks. They should remain distinct from direct measurements.
A practical review workflow
- Check the period: confirm the chart range and the profile time zone used for daily grouping.
- Review the source: inspect history and available record details when a point is unexpected.
- Check permissions: verify the app can read the metric you expect to see.
- Consider completeness: ask whether the source and logging actually cover the period.
- Compare like with like: an ongoing day and a completed day can have different coverage.
Pull to refresh when you have added or corrected data in another health app. Background refresh is best effort and can be delayed by the platform.
Reading energy balance
decoderHealth subtracts estimated expenditure from recorded intake. Expenditure prefers available total-energy data and uses supported fallback estimates when needed. The calculation does not use a self-selected activity-level multiplier.
A day without nutrition records has zero recorded intake in the calculation. This means there are no intake records to sum; it does not confirm that no food was consumed. Nutrient fields can likewise be absent, rather than measured at zero.
Adding context without inventing causes
Sleep, activity, fasting, and Check-Ins can occur alongside changes in weight or energy. Reviewing them together can identify questions worth exploring. A coinciding event does not prove that one caused the other.
Check-In keeps subjective mood and energy observations separate from connected measurements. Fasting timer phases provide reference information based on elapsed time rather than sensor-confirmed biological readings.
Your next step
Use the dashboard as a starting view, then open the record or calculation you want to understand. The dashboard reference describes the formulas, source windows, and limits. decoderPro chat can add a conversation about selected recorded summaries, while the original charts and local trackers remain available independently.