Spine Harmony can maintain a structured private symptom diary from short check-ins. This is one of the core agent workflows: it preserves daily facts, creates trend summaries, and turns messy symptom history into clinician-ready context.
This workflow is useful for:
A good check-in captures the facts a clinician is likely to ask for:
| Field | Examples |
|---|---|
| Pain score | 0–10 now, on waking, worst today, best today |
| Location/quality | back, leg, neck, arm; sharp/dull/burning/tight if the user reports it |
| Sleep | quality, waking, position issues |
| Medication | type/amount only if the user chooses to record it |
| Activity/function | sitting, standing, walking, work, therapy, exercise, travel, lifting |
| Flares/acute episodes | spasm-like events, sudden worsening, triggers, duration, recovery |
| New symptoms | especially neurological changes or other red-line symptoms |
| Comfort measures | heat, ice, rest, walking, position changes, bracing |
| Comparison | better, same, worse, mixed, or too early to say |
| Clinician questions | questions raised by the trend |
Cadence should match the user’s situation. Examples:
Avoid unnecessary prompting. The goal is useful continuity, not anxiety or obsessive tracking.
When the user provides a short check-in, the agent should:
Good wording:
The last three entries show user-reported pain staying in the 1–2/10 range, with no new symptoms reported. This is encouraging but still needs clinician interpretation and longer follow-up to understand durability.
Bad wording:
The procedure worked and the pain generator is confirmed.
For clinician-directed procedures or interventions, track response durability and side effects without making clinical conclusions. Useful fields include:
The agent may summarize patterns such as “stable low pain,” “mixed response,” “temporary flare,” or “worsening trend,” but should not decide whether the intervention succeeded or failed.
Symptom diaries can contain sensitive health information. Keep real trackers in a private workspace, outside version control. If symptom logs are pasted into hosted LLMs, cloud agents, chat products, or cloud storage, treat that as disclosure of medical information to that provider.