outcomeId, outcomes[]). In Health Yourself product language the same concepts are often called assessments — this page uses both terms where helpful.
What wellbeing means
Wellbeing describes how supportive a subject’s submitted profile is for day-to-day functioning and comfort over roughly the next 10 years. It focuses on everyday capacity: steady energy, comfort during activity, clear thinking for daily tasks, and normal recovery after typical effort. Wellbeing is forward-looking, practical, changeable over time, separate from disease diagnosis, and informational — not a diagnosis or treatment recommendation.Wellbeing outcome ids
Request these inoptions.requestedOutcomes on submission. The same ids appear on GET /v1/results/{resultId}.
Synonyms such as
wellbeing.kidney or renal.wellbeing normalize to wellbeing.renal.
Requesting outcomes on submit
requestedOutputs is required and controls pipeline artefacts (scores, JSON report, HTML report, PDF).
Outcome fields in GET /v1/results
Each outcome summary uses partner-safe vocabulary only (no model codes or internal warning ids).
Example single outcome:
outcomes[] (array) in addition to outcome (primary / first).
Older integration drafts described
assessments[] with 0–100 scores.globalPopulation fields. The live partner API uses outcomes[], a single score in 0–1, and band.tier instead of group: optimal | suboptimal.Marker contributions and reports
Detailed per-marker explanations and reference-range display appear in generated HTML/JSON report artefacts (when requested inoptions.requestedOutputs), not as a separate structured contribution array on GET /v1/results.
The structured GET response is intentionally minimal: correlation ids, outcome summaries, notices, and signed artifact URLs.
Artifacts
Whenjson, html, or pdf is in requestedOutputs, artifacts.items[] may include:
See Get result for a full response example.