Current source-contact matches for the EDS lane.
Use one short, instability-and-support handoff before the next EDS, rehab, pain, or dysautonomia-overlap follow-up conversation.
This page is a public-safe handoff aid for EDS and hypermobility patients, caregivers, PT teams, clinic schedulers, and community moderators who need a cleaner first route before a tracked signup. Start with the public route first, then move to the tracked handoff only when someone wants their own record.
Keep the overdue EDS proof lane attached to the exact packet, handoff page, and overlap-safe support route.
This referral handoff now reads the public-safe community-growth snapshot directly so EDS route copy stays aligned with the current proof queue, overdue review state, and reusable partner assets. It is still a public handoff page, not a proof log.
Public route and page mentions tracked in the latest community snapshot.
The next same-session import or reviewed-zero checkpoint for this route.
Keep traction claims conservative until production-attributable proof exists.
Recent public-safe organizations surfaced for this lane.
This lane is packaging-complete but still waiting on first attributable proof.
Capture the four details that make the next EDS, rehab, or pain visit usable.
Start with the last reliable mobility or function anchor.
Use walking, stairs, time upright, showering, typing, school, work, or driving so the next team can see what changed from a real baseline.
Name the latest event that moved the pattern.
Keep it to one joint event, brace change, PT change, upright-tolerance shift, flare, medication change, or recovery setback.
List what is active right now.
Include braces, taping, PT, mobility aids, pacing, compression, hydration, pain tools, and one or two home supports already in use.
End with the narrowest useful ask.
Examples: what support to change next, whether orthostatic overlap needs its own workup, whether rehab is helping, or what would trigger a different referral path.
Use conservative wording when a clinic, PT team, family helper, or nonprofit asks for one short explanation.
For referral intake or pre-visit routing
For support-group, nonprofit, or family-resource follow-up
Only after someone wants their own record
Keep the framing conservative
Move from public explainer to tracked signup in a fixed order so clinic, community, and booth follow-up stay proof-safe.
Lead with the explainer page before attribution.
Use the public EDS tracking page when someone needs one stable link for instability, support changes, overlap symptoms, and daily function without being asked to sign up yet.
Use this page when one shorter summary is easier to share.
Send the referral handoff page to a scheduler, PT team, pain clinic, moderator, or family helper when the full landing page is more detail than the moment can carry.
Attach attribution only when the person wants their own record.
Move to the tracked signup link only after someone asks to keep their own chronology, prepare for a referral, or preserve the route for later follow-up.
Switch lanes when the thread becomes orthostatic, mast-cell, pain-led, or broadly mixed.
Do not force a narrow EDS label when overlap routing would make the next handoff more accurate and easier for the recipient to use.
Keep the referral handoff tied to the exact proof-safe packet set for the EDS lane.
Use the same source-aware bundle when the handoff becomes real.
Move from the public landing page to this handoff page first. If the person wants their own record after that, switch to the tracked signup and keep any proof logging under community-growth-eds only.
Keep the booth, scheduler, and partner packet language aligned.
Use the same route order across community groups, clinic scheduling notes, and nonprofit resource follow-up so the EDS story stays narrow until overlap routing is clearly needed.
Use the narrow EDS route only when it is still the real story.
- Stay on the EDS route for instability, recurrent joint events, rehab response, mobility supports, and one patient-owned summary before the next visit.
- Use the overlap bridge when the next handoff needs one mixed crash, orthostasis, and function anchor before the full record.
- Switch to POTS and dysautonomia when upright symptoms, hydration strategy, or standing tolerance are doing more explanatory work than instability alone.
- Switch to MCAS when the timing is being driven by trigger-heavy flares, reactions, or environment-linked recovery shifts.
- Switch to Fibromyalgia when pain, sleep disruption, fatigue, and week-long flare patterning are clearer than instability or connective-tissue framing.
- Switch to the overlap hub when no single label is stable enough and the story spans pain, fatigue, dysautonomia, mast-cell-style flares, and practical function loss together.
Load the current public-safe booth, moderator, clinic, and partner copy instead of rewriting the lane by hand.
The companion feed keeps the EDS partner-page blurb, moderator ask, email copy, safe-claim line, and asset links aligned with the broader condition campaign kit. Use these blocks when you need a quick community, clinic, or family-facing explanation that still matches the tracked source.
Keep the public route separate from proof logging.
Share the public page first, then this shorter handoff page if clinic, moderator, or booth follow-up needs a faster summary. If the conversation turns into a real tracked follow-up, keep the source attached with the EDS signup link and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-eds.
If someone only wants a lightweight next step, keep them on the public route or overlap bridge support page. If they need a broader route picker before signup, use the beachhead hub or complex-overlap page instead of attaching EDS attribution too early.
Mito Map is an organization and tracking tool. It does not diagnose EDS, determine subtype, or replace medical care.