Prepare better visit questions. Browse conditions
Condition prep

The crash comes later.

The pattern that matters here is delayed, which makes it almost impossible to describe from memory in a short appointment. Ojava holds what you did, what followed, and how long recovery took, on one line, so the delay itself is visible.

Free to start, no card. Everything you import stays exportable and deletable.

Visit brief
Crashes logged
7 in 12 weeks
Usual delay
18 to 36 hours
Longest recovery
5 days

3 questions ready to ask, and 3 gaps named rather than filled in.

Read together
  • Activity notes
  • Crash and recovery
  • Sleep data
  • Prior visit notes
One brief
What this page prepares

Four lanes,and four clear limits

Each lane turns something you already have into something you can hand over. None of them decides anything. The line under each card is the specific thing that lane refuses to do, written the same way on all nineteen condition pages.

Start your record
  • Crash and recovery timeline

    Every crash you logged with the day before it and the days after, so the delay and the recovery length are both on the page.

    No condition is identified and no cause is assigned.

  • Your own baseline

    What an ordinary week looks like in your record, so a bad week is compared against you rather than against anyone else.

    No activity limit, exertion target or pacing plan is prescribed.

  • Sleep and function

    Connected sleep data and the function notes you kept, on the same axis as the crashes.

    Device data is context, never a sleep study or a measurement.

  • Questions to bring

    About evaluation, documentation and what to keep recording, written from your own record.

    Questions only. Diagnosis and referrals are your clinician.

The brief it builds

What is on it,and what is missing

Every figure below was computed from a record you imported or entered, the same way each time. Nothing here is estimated to fill a hole, and where the record is thin the page says so instead of smoothing it over.

Build yours
ME/CFS briefDraft, updated today
Crashes logged7 in 12 weeks
Each with the day before it recorded
Usual delay18 to 36 hours
From your own timestamps, across six of the seven
Longest recovery5 days
Following the week you noted travel

Example screen, with illustrative values.

Still missing
  • Two crashes have no note of the preceding day
  • No record of what a good week looks like for comparison
  • No prior specialist notes imported
Questions to bring
  • The delay is consistently a day or more. Does that shape matter to you?
  • What would you want me to record that I am not recording?
  • Which referrals or tests, if any, would change how this is approached?
How it works

Three steps,then it is quiet

Setup is a file and a permission, not a project. After that the work is invisible: things arrive, get read, wait for you, and become a page you can hand to someone in the ten minutes you actually get.

ImportedPDF, XML, CSV, ZIPIn reviewyou accept or correctOn the briefdated, with its source
  1. Bring in what you already have

    A lab PDF, a records file, a health export, or the food and training you are already logging. The type is detected from the file itself and each type has its own parser.

  2. Review it before it counts

    Extracted values are checked back against the source text and the result waits in review. Nothing joins your record until you have seen it, and anything wrong can be corrected by hand.

  3. Walk in with the page, not the memory

    The brief is a summary of what happened, what is missing, and what to ask. You take it to your own clinician, who makes every decision that follows.

Worth writing down between visits
  • What you did on the day before a bad day
  • When the crash started, and how long it ran
  • Sleep, and whether it felt restorative
  • The ordinary weeks too, since they are the baseline

References

What this page is built on

Published guidance and reference sources behind the education on this page. Ojava uses them to explain and organize, never to diagnose or treat.

Review sourcesHide sources
Improving Diagnosis in Health Care

National Academies of Sciences, Engineering, and Medicine, 2015.

Supports structured symptom and record organization as part of a collaborative diagnostic process with clinicians.
QuestionBuilder App

Agency 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.
Laboratory Tests

MedlinePlus, U.S. National Library of Medicine, 2025.

Supports lab-prep reminders that food, medicines, instructions, and timing can affect results. It does not support ordering tests or changing medicines.
Where the line is

General wellness,stated plainly

Ojava brings your own data together, explains what markers generally mean, shows how yours have moved, and helps you write down questions before an appointment. That boundary is not a limitation being worked around. It is the design, and it is why the product can be honest about what it knows.

  • Name a condition, or tell you what you have
  • Prescribe, dose, or change a medication
  • Order a test, or read one as safe or unsafe for you
  • Suggest you delay or skip seeing a clinician

If something concerns you, speak to a clinician. In an emergency, call your local emergency number.

Next

Start with one file you already have.

A lab PDF, a records export, or the food and training you are already logging. The brief gets more useful with each thing you add, and the first one costs nothing.