symptom-documentation-guide

# Symptom Documentation Guide > **Disclaimer:** This skill provides general wellness and health information for educational purposes only. It does NOT constitute medical advice, diagnosis, or treatment recommendations. The information provided is not a substitute for professional medical judgment. Always consult a qualified healthcare professional before making decisions about your health. If you are experiencing a medical emergency, contact emergency services immediately. --- ## When to Use **Use this skill when:** - A user wants to build a symptom diary or health journal and needs a structured framework for what to observe and record - A user has a recurring symptom (headaches, fatigue, stomach discomfort, joint pain, skin flares, dizziness) and wants to identify patterns before a medical appointment - A user says their doctor asked them to "keep track" of symptoms and they are not sure what information to capture - A user wants to improve how they describe their symptoms in appointments -- moving from vague descriptions ("I just feel off") to precise, actionable observations - A user is tracking symptoms that are tied to potential triggers -- food, activity, sleep, stress, menstrual cycle, weather, or environmental exposures - A user is preparing for a first specialist appointment and wants to arrive with organized documentation rather than relying on memory - A user has been living with a chronic condition and wants to detect whether their symptom pattern is changing over time **Do NOT use when:** - The user asks what their symptoms might mean or indicate -- this requires clinical interpretation and falls outside this skill's scope; acknowledge the question and advise them to raise it with their provider - The user asks whether their symptoms are serious or whether they should see a doctor -- do not assess urgency; advise consulting their healthcare provider promptly and, if symptoms feel severe or sudden, contacting emergency services - The user asks for treatment recommendations, home remedies, or medication guidance -- defer entirely to their provider; see the medication-tracking or treatment-adherence skills for related but distinct workflows - The user describes symptoms consistent with acute emergency (chest tightness, shortness of breath, sudden severe headache, one-sided weakness, sudden vision change, high fever with stiff neck) -- stop all other guidance and advise contacting emergency services immediately - The user wants to interpret patterns they have already documented -- pattern interpretation is clinical reasoning; help the user formulate their observations as questions for their provider instead - The user is seeking a specific diagnosis through a different framing ("I don't want a diagnosis, I just want to know if this sounds like X") -- this is still diagnostic reasoning; redirect to documentation and provider consultation --- ## Process ### Step 1: Clarify the Documentation Goal Before Building Anything Begin by understanding what the user actually needs. The right documentation structure depends entirely on context. - Ask whether they are tracking a single symptom or multiple concerns simultaneously -- multiple symptoms require correlation tracking in addition to individual logs - Determine how long the symptom has been present: new (days to 2 weeks), subacute (2--6 weeks), or chronic/recurring (months to years) -- this shapes how long they need to track before the appointment - Find out whether they have an upcoming appointment (and when) -- if the appointment is in 3 days, help them create a retrospective summary from memory; if it is in 4 weeks, build a prospective daily log - Ask whether a provider has given them specific instructions about what to track -- if yes, build the template to match those instructions exactly; provider-specified tracking always takes priority - Ask what tool or format they prefer for recording: handwritten notebook, phone notes app, a spreadsheet, printed template -- format matters for actual compliance; the best documentation system is the one the user will actually use ### Step 2: Teach the OPQRST Observation Framework OPQRST is the gold-standard clinical framework used by healthcare professionals to characterize any symptom. Teaching users to apply it produces documentation that directly maps to how providers think. - **O -- Onset:** When did the symptom first appear? Was the onset sudden (appearing in seconds to minutes) or gradual (building over hours or days)? What were you doing when it started? - **P -- Provocation/Palliation:** What makes it worse? What makes it better? Specific positions, foods, activities, temperatures, stress levels, time of day, medications taken - **Q -- Quality:** What does the sensation feel like? Teach a vocabulary of descriptors: - Pain descriptors: sharp, stabbing, dull, aching, burning, cramping, throbbing, pressure-like, squeezing, shooting, gnawing, tearing - Non-pain descriptors: tingling, numbness, heaviness, tightness, fullness, fluttering, pulsing, crawling, itching, warmth, cold - **R -- Region/Radiation:** Where exactly is the symptom located? Does it move or radiate to another area? Ask the user to point to the specific location on their body and note whether it stays fixed or travels (e.g., "starts in my lower back and moves down my right leg") - **S -- Severity:** Use the 0-10 numeric scale consistently -- 0 means the symptom is completely absent, 5 means it is present and noticeable but not preventing activity, 10 means the worst imaginable version of that sensation. Record both the typical severity and the peak severity experienced - **T -- Timing:** How long does each episode last (seconds, minutes, hours, constant)? Is it continuous or intermittent? How frequently does it occur (daily, several times per week, weekly)? Is there a time-of-day pattern? ### Step 3: Build the Right Log Structure for the Symptom Type Different symptom categories warrant different logging emphases. Apply domain-specific column configurations: **For pain symptoms (headache, back pain, joint pain, abdominal pain):** - Location specificity (point location vs. regional) and radiation pattern are critical - Include a body map field -- instruct users to mark the location on a simple front/back body outline - Add a functional impact column: "What did this prevent you from doing?" -- this is clinically meaningful beyond intensity alone - Track position-dependency: does lying down, sitting, or standing make it better or worse? **For gastrointestinal symptoms (nausea, cramping, bloating, changes in bowel habits):** - Track the prior 2-hour food and beverage intake for every episode - Include a bowel habits column if relevant -- frequency, consistency using Bristol Stool Scale descriptors (formed, loose, watery) without asking the user to interpret what this means clinically - Note whether onset is related to eating: before meals, immediately after, 30-60 minutes post-meal, 2+ hours after - Track stress and sleep quality on the same day as high-impact variables **For fatigue, mood, or cognitive symptoms:** - Intensity alone is insufficient -- add functional impact: "Could not drive / could not work / rested for 2 hours" - Track sleep the prior night (hours and perceived quality on a 1-5 scale) - Note hydration and caffeine intake as baseline variables - Track time of day carefully -- fatigue that is worst in the morning has different pattern implications than late-afternoon crashes **For skin symptoms (rash, hives, itching, flares):** - Track location AND spread over time (did it appear in one spot and spread?) - Note any new products used in the prior 72 hours: detergents, lotions, soaps, foods, medications - Environmental exposures: outdoor time, animals, dust, pollen levels - Temperature and moisture: hot shower before onset? Sweating? Cold exposure? **For cyclical or hormonal-pattern symptoms:** - Build the log to track cycle day if the user tracks their menstrual cycle - Note whether symptoms correlate with the week before menstruation, during, or after - Track 2 full cycles minimum to detect a cyclical pattern ### Step 4: Establish Consistent Intensity and Impact Scaling Numbers without calibration are unreliable across time. Help users establish personal anchors for their own scale: - **0-10 Pain/Intensity Scale Calibration:** Help the user define their personal anchors before they begin: - Their personal 10: "Think of the most severe version of this symptom you have ever experienced -- that is your 10" - Their personal 5: "Present but you can carry on with normal activity with moderate effort" - Their personal 3: "You notice it but it does not interrupt what you are doing" - Their personal 7-8: "You are modifying your behavior because of it -- skipping activities, resting" - **Functional Impact Scale (1-4):** Use this alongside the intensity number for a more meaningful picture: - 1 = Noticeable but no activity change - 2 = Modified one or more activities (chose not to exercise, took a break) - 3 = Stopped a planned activity or required rest - 4 = Unable to perform daily tasks (work, childcare, self-care) - Consistency rule: encourage the user to always record intensity and impact at the same point in an episode -- e.g., "record when symptoms are at their worst" or "record 30 minutes after onset" -- rather than retrospectively ### Step 5: Build the Trigger Tracking Layer Trigger identification is the highest-value output of a symptom diary because it gives the provider actionable clinical hypotheses. Build this layer deliberately: - Create a standardized list of potential trigger categories based on the symptom type, then help the user check them against each episode: - **Dietary:** specific foods, alcohol, caffeine, skipped meals, large meals, eating time - **Activity:** exercise (intensity and type), prolonged sitting, prolonged standing, specific movements - **Sleep:** hours the prior night, sleep quality (1-5), unusual sleep schedule - **Stress:** work stress, social stress, significant events -- rate stress level 1-5 for that day - **Environmental:** weather changes (barometric pressure drops are a documented trigger for certain headache types), temperature extremes, air quality, seasonal allergens - **Medications and supplements:** what was taken in the prior 24 hours, including timing - **Hormonal:** menstrual cycle day if relevant - **Postural and positional:** body position at onset, recent physical activity, screen time duration - Teach the user not to pre-assume which triggers matter -- the goal is to record broadly for the first 2 weeks, then identify patterns from data rather than assumption - True trigger identification requires seeing a symptom occur AND NOT occur relative to a potential trigger. Advise recording potential trigger exposure even on symptom-free days ### Step 6: Design the Weekly Pattern Summary Raw daily logs are data. The weekly summary converts data into patterns that are communicable to a provider in a 10-15 minute appointment: - At the end of each week, calculate or estimate: - Total episode count for the week - Average intensity and peak intensity - Episode duration range (shortest to longest) - Most consistent trigger across episodes (appears in 3 or more episodes) - Most effective relief method (reduced intensity by at least 2 points or resolved episode) - Any new associated symptoms that appeared this week - Add a qualitative "Pattern Notes" field -- this is where the user writes in plain language what they noticed: "All 4 episodes this week happened within 1 hour of eating" or "The three worst episodes were all Monday/Tuesday -- high-stress workdays" - Compare week-over-week: Is frequency increasing, decreasing, or stable? Is intensity changing? Are new symptoms emerging? A clear trend direction is clinically valuable even if the user cannot explain it ### Step 7: Build the Provider Communication Summary Before the appointment, help the user compile all tracking data into a one-page summary structured around how clinicians receive information. Most appointments are 15-20 minutes; a well-organized one-page summary maximizes the value of that time: - **Structured summary format (OPQRST-aligned):** - Symptom name (descriptive, not diagnostic): "Recurring cramping sensation in the left lower abdomen" - Tracking duration: "Tracked for [X] weeks, [Y] total episodes recorded" - Frequency: "[X] episodes per week on average" - Intensity: "Typical [X]/10, peak [Y]/10" - Timing pattern: "Onset most common [time of day / day of week / relationship to meals or activity]" - Identified triggers: listed in order of consistency - Identified relief: what has worked and to what degree - Functional impact: "Caused me to stop activity / rest / miss work on [X] occasions" - Trend: "Frequency has [increased / decreased / remained stable] over the tracking period" - **Questions section:** Help the user convert their observations into specific questions: - Format: "I noticed [observation] -- is that significant?" - Format: "The symptom seems to [pattern] -- does that point to anything I should know about?" - Format: "Is there a specific trigger or pattern you would like me to track more precisely before our next visit?" - Advise the user to bring both the one-page summary AND the raw daily log to the appointment -- the provider may want to see the raw data ### Step 8: Establish a Maintenance and Review Protocol If the tracking is long-term (for a chronic condition or ongoing monitoring), build in a review structure: - **Daily:** Record within 30 minutes of an episode when possible -- retrospective recording at end-of-day is acceptable but same-day recording is more accurate - **Weekly:** Complete the pattern summary every Sunday (or whatever day works consistently) while the week is fresh - **Monthly:** Review 4-week trends, note any changes in baseline, update the trigger list based on new observations - **Before appointments:** Compile the provider summary 2-3 days before the appointment -- not the morning of, when there is no time to organize clearly - **After appointments:** Record what the provider said in response to the tracking data -- this creates continuity if the symptom recurs or the provider changes --- ## Output Format ``` ## Symptom Documentation System **Created:** [Date tracking begins] **Tracking for:** [Appointment date or "ongoing monitoring"] **Primary symptom(s) being tracked:** [Descriptive name -- e.g., "Recurring pressure sensation behind eyes"] --- ### Daily Symptom Log | Date | Time | Symptom Description | Location | Radiation | Intensity (0-10) | Functional Impact (1-4) | Duration | Onset Context | Potential Triggers | Relief Attempted | Relief Effect | Associated Symptoms | |------|------|---------------------|----------|-----------|-------------------|--------------------------|----------|---------------|-------------------|-----------------|---------------|---------------------| | | | | | | | | | | | | | | **Intensity Scale Anchors (set at start of tracking):** - My 10: [User-defined worst experience] - My 5: [User-defined -- present but manageable] - My 3: [User-defined -- noticeable, not disruptive] **Functional Impact Scale:** - 1 = Noticeable, no activity change - 2 = Modified an activity - 3 = Stopped a planned activity / rested - 4 = Unable to perform daily tasks --- ### Trigger Checklist (Review After Each Episode) **Dietary (prior 2 hours):** - [ ] Specific food: ___________ - [ ] Alcohol: ___________ - [ ] Caffeine: ___________ - [ ] Skipped meal / fasting - [ ] Large meal - [ ] Other: ___________ **Activity and Posture:** - [ ] Exercise type/intensity: ___________ - [ ] Prolonged sitting (>2 hours): ___________ - [ ] Prolonged standing - [ ] Specific movement or position: ___________ **Sleep (prior night):** - [ ] Hours slept: ___________ - [ ] Sleep quality (1-5): ___________ - [ ] Unusual schedule (shift, travel, disruption) **Stress:** - [ ] Stress level today (1-5): ___________ - [ ] Significant stressor: ___________ **Environmental:** - [ ] Weather change (temperature drop, storm, barometric change) - [ ] Allergen season / outdoor exposure - [ ] New product (detergent, soap, lotion, food) - [ ] Temperature extreme (heat, cold) **Medications / Supplements:** - [ ] Taken in prior 24 hours: ___________ - [ ] Timing relative to symptom: ___________ **Other:** - [ ] Menstrual cycle day (if tracking): ___________ - [ ] Other notable context: ___________ --- ### Weekly Pattern Summary | Week | Episodes | Avg Intensity | Peak Intensity | Avg Duration | Functional Impact (episodes at level 3-4) | Most Consistent Trigger | Most Effective Relief | Trend vs. Last Week | Pattern Notes | |------|----------|---------------|----------------|--------------|-------------------------------------------|------------------------|-----------------------|---------------------|---------------| | 1 | | | | | | | | (baseline) | | | 2 | | | | | | | | | | | 3 | | | | | | | | | | | 4 | | | | | | | | | | --- ### Symptom-Free Day Log (Optional but Valuable) On days with NO symptom, note which potential triggers were present but did NOT cause a symptom. This helps distinguish true triggers from coincidental patterns. | Date | Potential Triggers Present | Symptom Occurred? |