mobieusHealth: food data quality
mobieusHealth keeps the numbers members log honest with a lightweight, AI-assisted quality loop: a one-time sanity check on each food, a member "Report incorrect data" control, and a tenant-admin console to review what members flag. This page covers all three. For the tracker as a whole, see mobieusHealth.
This is a wellness tracker, not medical advice.
The one-time AI check
The first time anyone pulls up a given food to log it, mobieusHealth runs an AI sanity check: does the serving size look typical, and are the calories and macros plausible and roughly internally consistent? Members see the verdict as a small indicator when they set their portion — AI-checked (looks reasonable), serving may be off (atypical serving), or data flagged (numbers look implausible and are worth a second look).
The check runs once per food and the result is cached, so it is instant afterward and never re-spends. It is advisory — it flags what deserves a closer look; it never rewrites the food's numbers on its own, and it never mutates the shared food database seed.
Reporting incorrect data
If a food's data looks wrong, a member taps Report incorrect data and can add a short note about what looks off. Reporting does two things at once:
- Re-checks the food with AI immediately, and
- Escalates the food to the community's admins for review.
To keep it fair, members can have only one open report per food, and there is a daily cap on how many foods one member can flag.
The admin reports console
Community admins review flagged foods at /admin/health/reports (Admin → mobieusHealth → the food reports console). The queue lists each reported food with the member's note and the outcome of the immediate AI re-check, and can be filtered by status (new, rechecking, resolved, rejected).
For each report an admin can resolve it (data fixed or accepted) or reject it (no change), with an optional note. The console requires a super-admin (role 5), and every resolve/reject action is written to the community's audit log. This is a new admin surface — see mobieusHealth for the rest of the admin workflow.
Related
# mobieusHealth: food data quality mobieusHealth keeps the numbers members log honest with a lightweight, AI-assisted quality loop: a **one-time sanity check** on each food, a member **"Report incorrect data"** control, and a **tenant-admin console** to review what members flag. This page covers all three. For the tracker as a whole, see [mobieusHealth](/know/mobieus-health). This is a wellness tracker, not medical advice. ## The one-time AI check The first time anyone pulls up a given food to log it, mobieusHealth runs an AI **sanity check**: does the serving size look typical, and are the calories and macros plausible and roughly internally consistent? Members see the verdict as a small indicator when they set their portion — **AI-checked** (looks reasonable), **serving may be off** (atypical serving), or **data flagged** (numbers look implausible and are worth a second look). The check runs **once per food** and the result is cached, so it is instant afterward and never re-spends. It is **advisory** — it flags what deserves a closer look; it never rewrites the food's numbers on its own, and it never mutates the shared food database seed. ## Reporting incorrect data If a food's data looks wrong, a member taps **Report incorrect data** and can add a short note about what looks off. Reporting does two things at once: 1. **Re-checks the food with AI immediately**, and 2. **Escalates the food to the community's admins** for review. To keep it fair, members can have only **one open report per food**, and there is a **daily cap** on how many foods one member can flag. ## The admin reports console Community admins review flagged foods at **`/admin/health/reports`** (Admin → mobieusHealth → the food reports console). The queue lists each reported food with the member's note and the outcome of the immediate AI re-check, and can be filtered by status (new, rechecking, resolved, rejected). For each report an admin can **resolve** it (data fixed or accepted) or **reject** it (no change), with an optional note. The console requires a **super-admin** (role 5), and every resolve/reject action is written to the community's **audit log**. This is a new admin surface — see [mobieusHealth](/know/mobieus-health) for the rest of the admin workflow. ## Related - [mobieusHealth](/know/mobieus-health) - [mobieusHealth: describe and voice logging](/know/mobieushealth-describe-and-voice-logging) - [mobieusAI: the built-in AI helpers](/know/mobieusai-helpers)
