Skip to main content

For hospitals and health systems

Food logging for hospital patient apps.

BiteRight helps a hospital care team see what outpatients eat between appointments, and act when a day goes off plan instead of finding out at the next visit. Patients log meals by photo, voice or text inside the hospital's own patient app, the BiteRight API returns the recognised foods and nutrient estimates, and the patient is alerted when a day crosses a sugar, carbohydrate, fat or protein limit the care team set. Dietitians can review the meals in the BiteRight dietitian portal.

Last updated:

BiteRight photo logging screen with a meal in the camera frame
BiteRight result for a photographed meal with estimated calories, protein, carbohydrate, fat and sugar

What happens between appointments?

Outpatient care for diabetes, IBS, kidney disease or recovery after surgery depends on what patients eat at home. Most of that is invisible to the care team until the next visit, and paper food diaries are incomplete or forgotten.

Building food recognition and a nutrient database yourself is a big project. BiteRight adds both to your patient app, and the app keeps its own design.

How it works, step by step.

Example: Example Health, a fictional hospital.

  1. Step 1

    The care team sets a limit

    A patient in a diabetes outpatient programme gets a daily sugar limit of 30 g in the hospital app.

  2. Step 2

    The patient photographs lunch

    They take a photo of a slice of spinach pie in the app they already use for appointments.

  3. Step 3

    BiteRight returns the estimates

    The API recognises the dish and returns its estimated weight, ingredients, carbohydrate, protein and sugar.

  4. Step 4

    The day crosses the limit

    The hospital app shows the meal in its own design and alerts the patient that today's sugar is above the limit.

Example Health

Your plan

Daily sugar limit: 30 g

Set by your care team · example value

Logged before lunch: 27 g

Lunch

Logged with a photo

Spinach pie, 1 slice

Carbs
24 g
Protein
11 g
Sugar
6 g
Sugar today33 / 30 g

Today's sugar is above the limit your care team set.

Behind the scenes

BiteRight API

Receives the meal, returns food and nutrient estimates, and flags when the day crosses a limit your organisation set.

5. The day crosses the limit, so your app alerts

Illustrative workflow in a fictional partner app, with example values. Your app keeps its own design; BiteRight supplies the estimates and the limit check.

What BiteRight gives your team.

  • Food logging without redesigning your app

    Photo, voice and text logging through the API, shown in your own screens

    Nutrition API

  • Targets set by the care team

    Daily maximums for sugar, carbohydrate and fat, and a daily protein minimum, with an alert when one is crossed

    API and dietitian portal

  • Dietitian review between visits

    A workspace to review each patient's logged meals, rules and alerts, with export of meal logs

    Dietitian portal

  • Patients who don't speak English

    Arabic input for photo, voice and text; app interface in English, French, Arabic and Spanish

    API and app

  • Local food in the Gulf

    A Bahraini food-composition database and localised Middle Eastern dishes, alongside 2.5M+ food records from national databases

    Food data

  • Procurement and data protection review

    Oracle Cloud hosting, regional hosting, encryption in transit and at rest, and a DPA

    Platform

  • Oracle Cloud Infrastructure
  • Regional hosting
  • Encrypted in transit and at rest
  • DPA for business customers
  • Arabic and English input
  • 2.5M+ food records

Read more about the nutrition API, the dietitian portal and how data is protected.

What BiteRight does not do.

  • Nutrient values are estimates, not measurements. Your clinical team decides how they are used.
  • BiteRight does not diagnose or treat conditions, and limits should be set by a qualified clinician.
  • BiteRight does not monitor inpatient meal trays and does not connect to electronic health records.

Questions we hear.

Does the hospital app have to change its design?

No. Your app keeps its own screens, branding and flows. It sends the meal to the BiteRight API and shows the results however your team chooses.

Who sets the daily limits?

Your organisation or your clinicians can set daily maximums for sugar, carbohydrate and fat and a daily minimum for protein. Patients can also set their own limits in the BiteRight app.

Can patients log meals in Arabic?

Yes. The API accepts Arabic for photo, voice and text logging, and the food data includes a Bahraini food-composition database and localised Middle Eastern dishes.

Can a dietitian review what patients logged?

Yes. The BiteRight dietitian portal shows each connected patient's logged meals with foods, servings and estimated nutrients, highlights entries that break a rule, and can export meal logs.

Where is patient data hosted?

BiteRight runs on Oracle Cloud Infrastructure. Data is encrypted in transit and at rest, hosting can be regional, and a data processing agreement (DPA) is available for business customers.

How do we get access?

The API is available to approved partners. Request a demo and the team will discuss your programme, data requirements and sandbox access.