Edustories
Case reports

What's in a case report

A section-by-section tour of a case report — Case Description, Anamnesis, the user's solution, AI-powered solutions, and the author-only tools.

Not verified yet

Every case report follows the same shape, so once you know one you know them all. This page walks through each part in the order you meet it.

A note on wording. Two everyday Edustories terms come from clinical practice: what is technically a "disorder" is shown throughout the app as "Challenging behavior", and the Anamnesis section is labelled "Student's background" (sometimes "Student's medical history"). This guide uses the labels you actually see on screen.

Title and summary

Every case opens with a Title and a short Summary — a one- or two-sentence blurb. These are what you see first on a case card while browsing, so they're written to tell you at a glance what the case is about.

Case Description

The Case Description is the factual core of the case, in two parts.

Basic student info

A compact, structured profile of the student and situation. These are the same fields that power the catalog filters and the grey tags on each case card.

FieldWhat it capturesTypical options
AgeThe student's ageA number of years (for example, "12 years"); may be "age unknown"
GenderThe student's genderMale / Female / Other
DiagnosisAny formal diagnosisOne or more diagnoses, where known
Challenging behaviorThe behaviour that made the situation hard (the "disorder" field)One or more behaviours
HobbiesThe student's interestsOne or more hobbies, where known
FrequencyHow often the challenging behaviour happensA frequency level
SeverityHow intense the challenging behaviour isA severity level
Family statusThe student's family situationA family-status value
GradesSchool performanceWhere provided
CountryWhere the situation/idea originatedA country
OtherAutomatically detected sensitivity flagsSee note below

The Other field holds content-sensitivity flags that Edustories detects automatically (for example, mentions of harassment, self-harm, or violence). They help readers know what to expect and let you filter cases accordingly — they are not something the author types in.

Detailed Description

Below the basic info comes the Detailed Description — the long, narrative account of the situation in the author's own words. This is where the story lives: the context, what happened, and how it unfolded.

Anamnesis ("Student's background")

The Anamnesis section — shown as "Student's background" — gives relevant history: the student's background and, where appropriate, medical history. It is collapsible, so you can expand it when you want the fuller picture and keep it tucked away otherwise.

User solution

This is the educator's own approach — what they actually tried — in two parts:

  • Detailed Solution Description — the approach the author took, step by step.
  • Solution Result — the outcome.

A badge marks the result as Successful or Unsuccessful. If the author hasn't filled this in yet, you'll see a "User has not filled in" note instead.

The full User solution and the AI-powered solution designing below require you to be logged in. Logged out, you'll see a prompt to sign in.

AI-powered solution designing

For each case, Edustories drafts suggested approaches automatically, organised into tabs based on established frameworks (such as proactive and reactive strategies, SEL, PBIS, and more). This is a feature in its own right — see AI-suggested solutions for the full tour.

Intervention & Monitoring (author only)

The final section, Intervention & Monitoring, is visible only to the case's own author. It's a personal tool for tracking a real intervention over time — recording behaviour ratings, choosing a strategy, and seeing whether things improve. Read more in Intervention tracking.

Where to go next

On this page