All studies
Nutrition·November 5, 2026·5 min read

Is My Meal Score Based on What I Ate or My Glucose Response?

HealthOSX meal scores come from what you ate, not your glucose response. The CGM curve is a separate signal that can tell a different story.

HealthOSX gives each logged meal a score from what is in it: the foods, portions and nutrients in the food database, not from your blood sugar. The glucose curve is a separate signal that sits next to that score when a CGM is connected. They answer different questions, and they can disagree.

Two separate signals for one meal
Meal score
From food database: foods, portions and nutrients
Glucose curve
From CGM sensor after eating

Your meal score is calculated from the plate, not the response

The meal score updates as soon as you log a meal by photo, barcode or voice. It uses the food database to evaluate the foods, portions and nutrients in the logged meal, then turns that record into a score. A bowl of lentil soup and a pastry do not get the same score because their contents are different. But the score is not looking at your arm sensor, your blood draw or your glucose curve.

This means the same meal gets the same score on a good glucose day and a bad one, as long as the portion and ingredients stay the same. The score is a property of the food. The glucose curve is a property of you plus the food plus the day.

The meal score grades the plate. The glucose curve grades your body's response to that plate on that day.

Is my meal score based on what I ate or my blood sugar response?

You asked it directly, so the direct answer is: what you ate. If you log a meal with no CGM connected, the score still appears. If your sensor fails after dinner, the score still appears. If your glucose goes higher than usual after a meal, the score does not change. That is the clearest way to know the score is coming from the meal record and the food database, not from the sensor.

Meal score vs glucose curve
Meal scoreGlucose curve
What it measuresFoods, portions and nutrients in the logged mealBlood glucose after eating
InputFood database, meal logCGM sensor readings
UnitsApp scoremg/dL or mmol/L
TimingCalculated from the logged meal; does not move with glucose.Moves after eating
Changed byIngredients and portionsInsulin, sleep, exercise, stress, food order

Scroll the table sideways for the rest →

Two signals, two inputs.

The two signals sit next to each other in the app because that is useful for review, not because they are measuring the same thing.

Why a good score and a big spike can happen in the same meal

A meal can be nutrient dense and still send your glucose up. Fruit, oats, rice and potatoes contain carbohydrate. Some people can eat them at a given portion and stay fairly flat. Another person can eat the same portion and get a sharp rise. The meal score does not know your insulin sensitivity, your sleep, your recent exercise, your stress or the order you ate the food in. Those can all change the glucose curve without changing the foods in the meal.

The reverse also happens. A low scoring meal that is mostly refined carbs and fat can produce a smaller glucose excursion than expected if it is small, eaten after exercise, or eaten with a lot of fat that slows gastric emptying. A flat curve is not proof that the meal was nutrient dense.

What it looks like in real data

In the app, the meal score shows as a score attached to the logged meal. With a glucose sensor on, the curve after that meal shows a separate line or shaded area on the same timeline. The score is calculated from the meal log and does not change from glucose readings. The curve moves over time.

As a general illustration, CGM glucose may start moving around 10 to 20 minutes after eating, peak somewhere between 45 and 90 minutes, and settle over 2 to 3 hours, but the exact timing varies by meal and person. These ranges are illustrative, not product claims. The sensor reads interstitial fluid, so it runs a few minutes behind venous blood. If a meal takes you from 85 mg/dL to 150 mg/dL, that change is visible in the curve and not reflected in the meal score.

What should I compare when the two disagree?

Use them for different jobs.

  • A low meal score tells you to review the meal record and consider ingredient or portion changes.
  • A high glucose curve tells you the meal was metabolically rough that day: look at portion size, carbohydrate amount, sleep, exercise, stress or food order.
  • A high meal score with a high curve means the food itself had useful nutrients but the carbohydrate load or timing may not fit you at that moment.
  • A low meal score with a flat curve can still be a problem if it becomes a pattern, because a flat glucose line does not make a low nutrient meal better.

The common mistake is treating the glucose curve as the truth about food quality. It is not. It is a separate measurement of your response, and that response changes hour to hour.

What the meal score cannot tell you

The meal score is only as good as the food database and what you log. If you leave out the cooking oil or log a different portion, the score changes based on that log, not on what was actually on the plate. The CGM has its own limits: sensor lag, compression lows, placement and calibration can affect the shape of the curve.

Neither signal is a medical diagnosis. A repeated very high post-meal glucose rise, or a very low reading, is worth discussing with a doctor. The meal score is useful for changing what goes on the plate. The glucose curve is useful for seeing how your body handled it.

If you want to see both signals next to your own meals, HealthOSX logs meals by photo, barcode or voice and pairs them with CGM when a sensor is on. You can open it at HealthOSX and watch the two tell their separate stories.

Written by

HealthOSX Research

Keep reading