Health Indices troubleshooting

This page addresses common Health Indices questions that arise when API output does not match initial expectations.

Refer first to Overview for the product-level meaning of each index and Integrating Health Indices for the API contract. This page focuses on cases where the result shape, Wellness Score behavior, or custom UI output remains unclear after those pages have been reviewed.

Common Health Indices misunderstandings

computeHealthRisks() does not guarantee that every returned field will be populated. If required inputs are missing, the corresponding index remains null.
The Wellness Score is different from the other health indices. It depends on physiological values from a successful scan, so a standalone risk-factors call without measurement data will not produce a complete Wellness Score.
The Wellness Score is not an arithmetic mean of the individual indices shown in the UI. It is computed from a weighted model that combines measured physiological values with user-provided risk factors.
Wellness Score values can change between measurements. Comparisons should be made between scans taken in similar conditions and, ideally, at a similar time of day.

Common integration pitfalls

Missing inputs lead to partial output. If a given index requires age, blood pressure, cholesterol, HDL, country, or another field that was not passed, the corresponding result will stay null.
When results are rendered in a custom UI, explicit presentation rules for rounding, precision, units, and labels should be defined at the application level. The API returns raw values and does not guarantee byte-for-byte parity with the formatting used by the SDK’s embedded UI.
Unit system management (metric/imperial) must be handled at the application level. Input values should be converted before calling the SDK APIs.