See the whole picture.
What matters, what to check, and where to go from here.
- 01A LITTLE MORE CLARITY
Start with an organizational problem
ONU’s business routes cover employers, partners, healthcare and developer discussions. Choose the problem before choosing a package: participant engagement, organizing information, integrating a workflow or evaluating a partnership. A public service description is not a commitment to every feature or delivery model.
See how to get started - 02A LITTLE MORE CLARITY
Define a pilot people can evaluate
Specify participants, countries, expected workflow and the outcome to assess. Agree on support, onboarding, accessibility and a review date. Avoid calling a wellness score proof of clinical benefit or using individual health readings as employee-performance measures. A useful pilot needs a clear decision at the end.
- 03A LITTLE MORE CLARITY
Clarify data access and consent
Document who provides information, who can see it, what reports are produced and when data are deleted. Discuss aggregation and safeguards before collecting sensitive records. Individual health information should not be attached to a general sales enquiry; proposed uses need security and legal review.
Review your data choices - 04A LITTLE MORE CLARITY
Request scope and commercial terms
Ask for current capabilities, documentation, pricing basis, dependencies and service responsibilities. Confirm what is available now versus a proposal. API credentials, clinician coverage and enterprise reporting are not activated by reading this website; they require the relevant agreement and setup.
See how connected wellbeing works for teams.
