Matched contacts
-
Current overlap-source contact matches behind the bridge route.
ME/CFS, Long COVID, POTS, And Dysautonomia Referral Handoff
Use one short, crash-and-orthostatic handoff before the next ME/CFS, long COVID, POTS, dysautonomia, rehab, autonomic, or family follow-up conversation.
This page is a public-safe handoff aid for mixed crash, relapse, PEM, upright intolerance, and recovery-burden stories that still need one bridge before a narrower label takes over. Start with the public bridge first, then move to the tracked overlap handoff only when someone wants their own record.
Live Proof Queue
Keep the crash-and-orthostatic proof lane attached to the exact packet, handoff page, and overlap-safe support route.
This referral handoff reads the current public-safe community-growth snapshot directly so the bridge route stays aligned with the latest proof queue, same-day review posture, and overlap attribution rule. It is still a public handoff page, not a proof log.
Public mentions
-
Public route mentions tracked in the latest community snapshot.
Proof review
-
The next same-session import or reviewed-zero checkpoint for this shared lane.
Activity origin
-
Keep traction claims conservative until production-attributable proof exists.
Recent targets
-
Recent organizations and bridge-ready routes surfaced for this overlap source.
Route status
-
This bridge keeps overlap attribution until the story truly narrows.
Loading the current bridge move-first and proof-focus snapshot.
Three-Minute Family Handoff
Capture the four details that make the next crash-and-orthostatic visit usable.
1. Last stable baseline
Start with the last reliable function anchor.
Use walking, stairs, work, school, showering, screen time, or standing tolerance so the next reviewer sees what changed from a real baseline.
2. Recent trigger or load shift
Name the exertion, upright load, infection, heat, or travel change that came first.
Keep it to the one recent sequence that best explains the crash, relapse, or orthostatic loss before the route widened.
3. Crash and upright pattern
Show what travels together.
Capture PEM delay, dizziness, tachycardia, brain fog, heat intolerance, breathlessness, recovery lag, and next-day payback when they move as one story.
4. Narrowest next ask
End with the smallest useful next decision.
Examples: which route should lead next, what support changed function, what visit question matters now, or what documentation needs to stay attached.
Copy-ready family note:
Baseline before the change: [last stable function]. What changed first: [exertion, upright load, infection, heat, travel, or support shift]. Pattern now: [PEM, relapse timing, orthostatic symptoms, and recovery cost]. What we need from this handoff: [the next question, route choice, or support decision].
Clinic And Community Copy
Use conservative wording when a clinic, rehab team, moderator, or family helper needs one short explanation.
Clinic scheduler note
For referral intake or pre-visit routing
We are using a patient-owned crash-and-orthostatic bridge page to keep PEM, relapse timing, upright intolerance, and recovery burden in one place before the visit. Public bridge: https://precisionmito.com/me-cfs-long-covid-pots-dysautonomia-tracking
Moderator or advocate note
For support-group, nonprofit, or booth follow-up
If a thread keeps bouncing between ME/CFS, long COVID, POTS, and dysautonomia language, this bridge helps keep crashes, upright loss, and recovery burden on one route before narrowing: https://precisionmito.com/me-cfs-long-covid-pots-dysautonomia-tracking
Tracked follow-up
Only after someone wants their own record
Tracked bridge signup: https://precisionmito.com/signup.html?next=%2Fmitomap&source=community-growth-complex-chronic-illness
Safe claim line
Keep the framing conservative
Patient-owned tracking for crash patterns, upright intolerance, function changes, and follow-up prep. This is not a diagnostic sorter, triage engine, or replacement for medical care.
Handoff Ladder
Move from public explainer to tracked signup in a fixed order so clinic, community, and booth follow-up stay proof-safe.
1. Public route first
Lead with the bridge page before attribution.
Use the public bridge when crashes, relapse windows, and upright loss clearly belong together but a single-condition route would still be too narrow.
2. Short handoff second
Use this page when one shorter summary is easier to share.
Send the referral handoff page to a scheduler, autonomic or rehab team, moderator, or family helper when the full bridge page is more detail than the moment can carry.
3. Tracked signup only on request
Attach attribution only when the person wants their own record.
Switch to the tracked overlap signup only after someone asks to keep their own timeline, prepare for a visit, or preserve the route for later follow-up.
4. Narrow when the story finally settles
Move into one condition page only when that framing now helps more.
Switch into ME/CFS, Long COVID, or POTS and dysautonomia only when the narrower route clearly improves the next handoff instead of shrinking the story too early.
Conference scan order:
public bridge first, referral handoff second, tracked bridge signup only on request, then ME/CFS, Long COVID, or POTS once the route is clearly narrower than the overlap source.
Proof Bundle
Keep the referral handoff tied to the exact proof-safe packet set for the crash-and-orthostatic bridge.
Proof packet route
Use the same source-aware bundle when the handoff becomes real.
Move from the public bridge page to this handoff page first. If the person wants their own record after that, switch to the tracked overlap signup and keep any proof logging under community-growth-complex-chronic-illness only.
Community and clinic reuse
Keep booth, moderator, and clinic copy aligned.
Use the same route order across support groups, booth follow-up, and clinic notes so the mixed crash-and-orthostatic story stays broad until one narrower route is clearly better.
Proof packet route:
public bridge page, this referral handoff page, tracked bridge signup only on request, then the proof packet, route worksheet, and closeout memo if a real tracked follow-up or reviewed-zero check needs to be logged.
Route Choice
Use the bridge route only when it is still the real story.
- Stay on the bridge route when PEM, relapse windows, standing intolerance, tachycardia, and recovery lag still belong on the same page.
- Use the complex chronic illness overlap route when the thread gets broader than crash-plus-upright-load.
- Switch to ME/CFS when delayed payback, crashes, and pacing breakdowns clearly lead the next handoff.
- Switch to Long COVID when post-viral relapse timing and symptom drift now explain more than the bridge framing.
- Switch to POTS and dysautonomia when upright intolerance, hydration strategy, compression, and standing tolerance are the clearest route.
Companion Copy Pack
Load the current public-safe booth, moderator, clinic, and partner copy instead of rewriting the bridge by hand.
This page loads the public-safe community-growth status plus the companion feed so the bridge route keeps the same proof posture and share language as the rest of the community-growth stack.
Loading the current crash-and-orthostatic companion copy pack.
Proof-Safe Follow-Up
Keep the public route separate from proof logging.
Share the public bridge 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 overlap source attached with the tracked bridge signup and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-complex-chronic-illness.
If someone only wants a lightweight next step, keep them on the public bridge or the broader overlap hub. If one condition clearly leads now, switch into that narrow route only after the bridge has already done its job.
Mito Map is an organization and tracking tool. It does not diagnose ME/CFS, long COVID, POTS, or dysautonomia, and it does not replace medical care.