A model view to help you ask better questions.
The Symptom Forecast Report compares your recorded symptoms with estimates from your current Mito Map. It can help you organize what to review and compare modeled scenarios. It cannot tell you which symptoms you will develop, when they will change, or which treatment will work.
What information goes into it?
The report starts with the current saved or autosaved map submitted when you generate it. Its forecast layer uses:
- Tracked symptom ratings: the symptoms you recorded, their severity, and the confidence information attached to those observations.
- The current modeled graph: burden and support signals on mapped mitochondrial subsystems. These are model outputs, not direct measurements of each body system.
- Symptom-to-subsystem mappings: the relationships and weights in Mito Map’s phenotype library.
- A pattern grouping: a model grouping based on the graph and symptom domains, used to contextualize the report.
- Mapped intervention effects, when a scenario is included: the stored effects of a selected intervention are applied to the modeled graph and the symptom estimates are compared again.
Profile details, patient states, recorded interventions, lab information, and measured-function information can inform the map that feeds this report. Having an imported file or a connected wearable does not mean every value in it affects this forecast.
This symptom forecast is not a time-series prediction trained on your daily wearable history. It does not currently provide a validated forecast for a specific number of days or months. Saving data and connecting devices remain Free.
What do the outputs mean?
| In the report | How to read it |
|---|---|
| Current severity | The recorded symptom rating on a 0–5 scale. It represents what was supplied, not an independent clinical measurement. |
| Projected severity | A 0–5 scenario estimate from the current model inputs. It is not a promised future rating or an estimate for a defined date. |
| Risk /100 | A relative model index used to rank symptom patterns. A value of 60 does not mean a 60% chance of developing a symptom. The index is not a clinically calibrated probability. |
| Cluster or pattern | A grouping of the active model signals. Its label and confidence value describe the model’s internal comparison, not a diagnosis or a probability that the biology is correct. |
| Emerging or worsening symptoms | A review list ranked by modeled severity or change. When no symptoms meet the reporting threshold, the report can still return the highest-ranked candidates. Inclusion does not confirm a new symptom or actual worsening. |
| Intervention comparison | The difference between the current model and a scenario with the selected intervention’s mapped effects. It does not establish a treatment effect in you or account for every safety issue, interaction, or contraindication. |
| “Likely to resolve” or “prevented” | Labels for changes that cross the model’s reporting thresholds. They do not establish that a symptom will resolve or that an intervention prevents disease. |
Where does uncertainty come from?
- Your record may be incomplete, out of date, or affected by inconsistent ratings and missing context.
- The map and intervention library simplify complex biology. A mapped relationship does not prove a cause of your symptoms.
- Evidence from a study or population may not apply to your condition or circumstances.
- The symptom forecast does not provide a calibrated confidence interval for the predicted severity or an individualized accuracy estimate.
- Changing an input or the model’s underlying information can change a report even without a measured change in your health.
We do not present this report as a clinically validated prediction of an individual’s course. Scientific references support background evidence; they do not validate the complete Mito Map forecast.
A useful way to use it
- Check the record first. Correct symptom ratings, dates, and treatment details. Missing records are worth noting rather than guessing.
- Compare the model with your experience. Note where the report fits, where it does not, and what is uncertain.
- Choose a few questions. For example: “Does this symptom pattern fit my history?” or “Which measurements would help us check this?”
- Review again after meaningful new information. Compare reports as model outputs alongside actual measurements and visit notes, without treating a model change as proof of benefit or harm.
Do not start, stop, or change a treatment based on a forecast. Use it for discussion with a qualified clinician. A forecast cannot assess urgency; seek appropriate medical help for severe or rapidly worsening symptoms.
You can keep a useful record for Free.
Plus adds these modeled reports and budget and time filters. Your symptoms, map states, measured-function history, labs, imports, wearable connections, and the full intervention library stay in Free.