Joint History
Keep recurrent events on one timeline.
Track subluxations, sprains, pain spikes, headaches, and mobility setbacks beside the activity or context that preceded them.
EDS And Hypermobility Tracking
Make EDS and hypermobility patterns easier to capture across joints, fatigue, and daily function.
EDS and hypermobility-related illness can sprawl across pain, instability, injuries, dysautonomia, GI symptoms, fatigue, sleep disruption, and long recovery after basic activity. Mito Map helps keep those patterns in one longitudinal record so patients can show what is recurring, what overlaps, and what actually changes function.
Why This Beachhead Fits
EDS care often breaks down when multisystem patterns are documented in fragments.
Mito Map is useful when you need more than a list of painful joints. The question is usually how instability, fatigue, dysautonomia, GI symptoms, pacing limits, therapy, bracing, medications, and recovery interact over time. The goal is not to diagnose EDS or determine subtype. The goal is to make the pattern easier to organize and review.
Overlap Review
Show when EDS is not just a musculoskeletal story.
Connect pain and instability with fatigue, orthostatic symptoms, GI burden, sleep disruption, and cognitive load.
Visit Prep
Bring a cleaner pattern into referrals and therapy.
Organize PT response, braces, mobility aids, medication shifts, and day-to-day function before rheumatology, genetics, cardiology, or rehab visits.
Build A First Useful Record
Start with the pieces that usually get lost between PT, specialists, and daily life.
Function Anchors
Pick two or three daily tasks that show real capacity.
Use stairs, showering, errands, school or work hours, walking tolerance, typing time, or time upright so each flare has a practical baseline.
Support Stack
Keep braces, mobility aids, PT changes, and recovery supports together.
Log compression, hydration, pacing, braces, taping, strengthening work, pain tools, or medication changes beside the outcome they were meant to change.
Referral Handoff
Make the next multispecialty visit less repetitive.
Bring one record that shows instability, pain, dysautonomia overlap, GI burden, fatigue, and function instead of retelling separate fragments in each clinic.
Send The Right Next Link
Use the EDS page when instability and support-stack context lead, then widen or narrow the handoff on purpose.
Moderator Or Support Thread
Lead with EDS when recurrent joint events, pain, and function drift are the shared problem.
Best for hypermobility communities where braces, PT response, mobility aids, pain flares, and overlap burden need one cleaner pattern before another route takes over.
Clinic Or Care Prep
Switch to the tracked signup when someone wants their own handoff-ready record.
Use the source-tagged signup when the next move is genetics, cardiology, rehab, pain, or multispecialty follow-up and the person needs the EDS lane attached to their own account.
Overlap Spillover
Route out when orthostatic symptoms, mast-cell flares, or a wider multisystem picture become primary.
If the story is now mostly upright intolerance, trigger-heavy flares, or one broad mixed-illness timeline, move to the narrower or wider route that fits the lead pattern instead of forcing everything into EDS copy.
Community Route Matrix
Give moderators and advocates one hypermobility handoff grid instead of rewriting the same route logic.
Start with the EDS page when instability, pain, rehab response, and daily-capacity drift are doing the most explanatory work. Move to a different route below when the record is really being led by orthostatic, trigger-heavy, fatigue-crash, or broader overlap patterns.
Instability lane
EDS and hypermobility
Use when joint instability, pain spikes, mobility supports, PT response, and practical function loss are central and one wider overlap route would be too vague.
Orthostatic lane
POTS and dysautonomia
Use when time upright, heart-rate shifts, hydration strategy, heat intolerance, and compression or salt support changes are now doing more explanatory work than instability alone.
Trigger and flare lane
MCAS
Use when food, medication, environmental, heat, or hormone-linked reactions are making the story hard to read and flare chronology is more actionable than a pain-first frame.
Pain and recovery lane
Fibromyalgia
Use when widespread pain, sleep disruption, fatigue, sensory overload, and practical recovery burden are doing more explanatory work than recurrent joint events.
Mixed multisystem lane
Complex chronic illness overlap
Use when no single label is clearly leading and the best handoff is one shared hub before narrowing back down to a condition-first route.
Community Share Pack
Copy-ready EDS outreach text for hypermobility moderators, advocates, or referral-prep follow-up.
Start with the landing page when someone needs a clearer instability-and-overlap resource first. Use the tracked signup when they are ready for their own record with source community-growth-eds.
Attribution source: community-growth-eds
Live Community Snapshot
See the current public-safe EDS outreach and proof queue before you share the narrow route.
This route reads the same aggregate-only community-growth status feed used by the public hub, but filters it to the EDS lane so moderators, support-group leads, clinic-prep partners, and cautious resource editors can see whether the route is stale, where first attributable proof is still missing, and which recent organizations matched this page.
Matched contacts
-
Public-safe contact matches currently attached to the EDS beachhead.
Public mentions
-
Aggregated public mentions currently surfaced for the route, kept below proof-release detail.
Recent targets
-
Recent organizations surfaced for this instability, pain-overlap, and referral-handoff lane.
Updated: -
Route status: -
Proof review: -
Activity origin: -
Proof Packet
Keep the due-now EDS proof lane attached to the exact packet, handoff page, and operator-safe shortcut set.
Proof Bundle
Use the same packet path when the route becomes a real tracked follow-up.
Move from the public landing page to the EDS referral handoff first. If someone wants their own record after that, switch to the tracked signup and keep proof logging under community-growth-eds only.
Conference Scan Order
Keep the booth path simple.
Public landing page first, referral handoff second, tracked signup only on request, then the proof packet or reviewed-zero route if the next move is an operator proof checkpoint.
Proof-Safe Rule
Do not over-claim traction before attributable proof lands.
Use the proof brief and operator snapshot to decide the next same-session move, but keep community-facing copy on public-safe route language until import or reviewed-zero closeout is recorded.
Clinic And Family Handoff
Use one short hypermobility summary before the next PT, cardiology, pain, genetics, or family-support handoff.
EDS friction often shows up at handoff time: a patient needs to explain instability and orthostatic overlap, a family member needs to summarize what function actually changed, or a rehab team needs one compact record before deciding what to review next. This page works best when it becomes the stable first summary for that conversation.
Baseline Before The Flare
Start with the last useful mobility and function anchor.
Note the most recent stable walking, stairs, showering, typing, school, work, or time-upright baseline so the next handoff starts from the right comparison point.
Support Shift
Name what changed in the brace, PT, pacing, or hydration stack.
Capture new braces, taping, compression, PT adjustments, mobility aids, medication changes, or recovery supports that happened before the instability or pain pattern changed.
Next Visit Ask
End with the narrowest useful question.
State what the next team needs to review now: recurrent joint events, orthostatic spillover, rehab tolerance, pain control, or whether current supports are preserving practical capacity.
Booth And Community Routing
Use one proof-safe hypermobility handoff script for support groups, resource pages, and event follow-up.
EDS outreach gets noisy when the next person receives a broad symptom list without a clear route. Keep the handoff short: what instability or support-stack problem is actually leading, whether the public explainer is enough for now, and when a tracked signup is justified because the person wants their own record.
Support Group Or Booth
Lead with the public page before you ask for signup.
Use the landing page first when someone needs a cleaner hypermobility, instability, pain, and overlap explainer for a thread, meetup, or booth conversation.
Clinic Or Resource Follow-Up
Switch to tracked signup only when the record itself is the next step.
Use the source-tagged signup when the person wants a handoff-ready record for PT, cardiology, rehab, pain, genetics, or family coordination.
Proof-Safe Next Step
Route out fast if another pattern is doing more explanatory work.
Move to POTS for upright-intolerance-led stories, to MCAS for trigger-heavy flare chronology, or to the overlap hub when no single condition-first script is stable enough yet.
What To Capture
Questions that help an EDS or hypermobility record hold together.
- Which joints or body systems flare together, and what does recovery from those periods actually look like?
- Did PT, strength work, bracing, hydration, compression, pacing, or medication changes improve function in a repeatable way?
- Are pain, dysautonomia, GI symptoms, fatigue, and sleep disruption moving together or on separate clocks?
- What details would make the next specialist visit shorter, clearer, and less dependent on memory?
Dysautonomia tracking
Fibromyalgia tracking
Complex chronic illness overlap
Sleep and recovery tracking
Mito Map is an organization and tracking tool. It does not diagnose EDS, hypermobility spectrum disorders, connective tissue disease, or any other condition, and it does not replace medical care.