Free worksheet tool

Build a chronic symptom and flare worksheet before your next visit.

Organize symptoms, episode timing, possible triggers, what helped, medication names, and questions. This is visit prep only, not diagnosis, monitoring, or treatment advice.

Open the worksheet Browse tools

Free, no accountSources on the pageNothing is stored

Tool rhythm

Use the tool, then carry forwardthe context that matters.

Each page turns a narrow question into clearer prep: what you entered, what is still missing, and what would be worth discussing with a licensed clinician.

Open the tool

In practice

Start with the numbers, notes, or checklist items you already have.
Treat the result as education and visit prep, not a medical decision.
Use the handoff when your own records can add useful context.

Interactive worksheet

Work the question here, then decide what to carry forward.

Each public tool keeps the input, result, source basis, and safety boundary in one place. When your own records matter, sign in and bring the context into Ojava Coach.

Visit prep tools

Turn loose notes into a worksheet you can actually use.

These tools create a local checklist first, then hand the same context into Ojava Coach when you want a record-aware version after sign-in.

Chronic care tool

Chronic symptom worksheet

Symptom snapshot

Main concernSymptoms or flare notesPossible triggersWhat helpedUrgent symptoms to discuss now

Flare timeline

Episode startPeak dayCurrent statusSeverity or function notesSleep or stress contextExertion contextFood or hydration timingMedication or supplement timingRecovery notesQuestions for the visit

Worksheet for fatigue flaresReady worksheet

What to track before the visit

Main concern: fatigue flares
Symptom to log: fatigue
Symptom to log: brain fog
Symptom to log: post-exertion crash

Pattern clues to bring

Possible trigger: poor sleep
Possible trigger: hard workout
Possible trigger: stress
What helped or changed symptoms: pacing
What helped or changed symptoms: hydration
What helped or changed symptoms: rest day

Medication and record context

Name to review: atorvastatin

Which patterns in my fatigue flares log are worth discussing first?
What record categories would help you understand this pattern better?
Are any of these symptoms or changes reasons to seek care sooner?

This worksheet is education and visit prep only. It does not diagnose, monitor, predict flares, adjust treatment, clear medication safety, or replace urgent care.

Scientific references

The Patient-Reported Outcomes Measurement Information System developed and tested its first wave of adult self-reported health outcome item banksCella, Riley, Stone, et al., 2010.Supports structured patient-reported symptom collection. Ojava does not use PROMIS scoring or claim PROMIS validation.
Improving Diagnosis in Health CareNational Academies of Sciences, Engineering, and Medicine, 2015.Supports structured symptom and record organization as part of a collaborative diagnostic process with clinicians.
QuestionBuilder AppAgency for Healthcare Research and Quality, 2026.Supports preparing questions before appointments and saving those questions for the visit. It is not a substitute for clinician review or emergency care.

Flare and trigger prep for fatigue flaresReady flare prep

Episode timeline

Main topic: fatigue flares
Episode started: Monday morning
Peak day: Wednesday afternoon
Current status: improving slowly
Severity note: fatigue 8/10 at peak
Severity note: brain fog made work difficult

Trigger review prompts

Possible trigger to review: poor sleep
Possible trigger to review: hard workout
Possible trigger to review: stress
Sleep or stress context: two short nights before symptoms
Sleep or stress context: work stress was high
Exertion context: long walk Sunday
Exertion context: errands Monday morning
Food timing context: late dinner Sunday
Food timing context: less water than usual
Medication or supplement context: no medication changes
Medication or supplement context: magnesium at night

Recovery and visit questions

Recovery clue: pacing helped
Recovery clue: extra sleep helped
Question to bring: Which pattern should I track next time?
Question to bring: What would make this worth urgent care?

Which pattern should I track next time?
What would make this worth urgent care?

This flare and trigger prep is education and visit prep only. It does not diagnose a flare, prove causation, predict future flares, adjust treatment, monitor health, triage emergencies, or replace a licensed clinician.

Scientific references

The Patient-Reported Outcomes Measurement Information System developed and tested its first wave of adult self-reported health outcome item banksCella, Riley, Stone, et al., 2010.Supports structured patient-reported symptom collection. Ojava does not use PROMIS scoring or claim PROMIS validation.
Improving Diagnosis in Health CareNational Academies of Sciences, Engineering, and Medicine, 2015.Supports structured symptom and record organization as part of a collaborative diagnostic process with clinicians.
QuestionBuilder AppAgency for Healthcare Research and Quality, 2026.Supports preparing questions before appointments and saving those questions for the visit. It is not a substitute for clinician review or emergency care.

Build in Ojava Coach Build flare prep in Ojava Coach

Research and source basis

The Patient-Reported Outcomes Measurement Information System developed and tested its first wave of adult self-reported health outcome item banksCella, Riley, Stone, et al., 2010. Supports structured patient-reported symptom collection. Ojava does not use PROMIS scoring or claim PROMIS validation.
Improving Diagnosis in Health CareNational Academies of Sciences, Engineering, and Medicine, 2015. Supports structured symptom and record organization as part of a collaborative diagnostic process with clinicians.
QuestionBuilder AppAgency for Healthcare Research and Quality, 2026. Supports preparing questions before appointments and saving those questions for the visit. It is not a substitute for clinician review or emergency care.

Use it well

Enter the values or context you already have.
Review the local result before sign-in.
Use the Coach handoff only when you want a deeper record-aware conversation.

The clinical boundary and source basis stay attached to the result, then repeat once at the page close.

Research and source basis

The Patient-Reported Outcomes Measurement Information System developed and tested its first wave of adult self-reported health outcome item banksCella, Riley, Stone, et al., 2010. Supports structured patient-reported symptom collection. Ojava does not use PROMIS scoring or claim PROMIS validation.
Improving Diagnosis in Health CareNational Academies of Sciences, Engineering, and Medicine, 2015. Supports structured symptom and record organization as part of a collaborative diagnostic process with clinicians.
QuestionBuilder AppAgency for Healthcare Research and Quality, 2026. Supports preparing questions before appointments and saving those questions for the visit. It is not a substitute for clinician review or emergency care.

Back to all free tools

These tools are education and visit prep only. They do not diagnose, prescribe, order labs, determine screening eligibility, clear medication safety, detect conditions, triage emergencies, or replace your clinician.

What Ojava keeps clear

A calm place to understand the pattern before your next step

Ojava organizes health records, wearable trends, medication context, and visit prep in one view. It explains what signals generally mean and keeps clinician decisions where they belong.

Start with your records Read the guides

How the pieces sit togetherThree principles

Your data stays contextual

Daily signals, accepted records, and notes are reviewed together so one lab, symptom, or wearable trend is not treated as an isolated clue.

Education before action

Ojava prepares questions and context. It does not diagnose, prescribe, dose, order labs, or replace licensed care.

One record, many moments

The same structure supports a morning check, a new lab review, and a visit packet when you need it.