Matched contacts
-
Current source-contact matches for the overlap lane.
Complex Chronic Illness Referral Handoff
Use one short, overlap-first handoff before the next multispecialty visit, caregiver update, school plan, or community follow-up conversation.
This page is a public-safe handoff aid for people whose story spans ME/CFS, long COVID, POTS or dysautonomia, mitochondrial disease, EDS, MCAS, fibromyalgia, and related chronic illness overlap. Start with the public route first, then move to the tracked handoff only when someone wants their own record.
Live Proof Queue
Keep the overlap proof lane attached to the exact packet, handoff page, and bridge route before another broad share goes out.
This referral handoff reads the public-safe community-growth snapshot directly so overlap-route copy stays aligned with the current proof queue, review posture, and reusable outreach assets. It is still a public handoff page, not a proof log.
Public mentions
-
Public route and page mentions tracked in the latest community snapshot.
Proof review
-
The next same-session import or reviewed-zero checkpoint for this route.
Activity origin
-
Keep traction claims conservative until production-attributable proof exists.
Recent targets
-
Recent public-safe organizations surfaced for this overlap lane.
Route status
-
This lane stays broad and proof-safe until one narrower handoff is clearly warranted.
Loading the current overlap move-first and proof-focus snapshot.
Three-Minute Family Handoff
Capture the four details that make the next overlap-heavy visit or support handoff usable.
1. Last stable baseline
Start with the last reliable function anchor across systems.
Use walking, upright time, school or work block, meals, sleep, showering, sensory load, or support needs so the next handoff starts from a real baseline.
2. What changed next
Name the trigger, infection, load, or support shift that widened the story.
Keep it to one recent change such as exertion, travel, heat, food, medication, infection, hormone timing, rehab shift, or stress spike.
3. Cross-system pattern
Show what traveled together instead of listing isolated symptoms.
Capture crash timing, orthostatic burden, pain, GI symptoms, rashes, palpitations, cognition, and recovery lag when they move as one sequence.
4. Narrowest next ask
End with the smallest useful decision.
Examples: which route should lead next, what specialist question matters now, what support changed function, or what the next visit should review first.
Copy-ready family note:
Baseline before the change: [last stable function]. What changed next: [crash, flare, infection, upright load, trigger, or support shift]. Pattern now: [what symptoms and function costs are traveling together]. What we need from this handoff: [the next question, route choice, or support decision].
Clinic And Community Copy
Use conservative wording when a clinic, caregiver team, school helper, or community moderator asks for one short explanation.
Clinic scheduler note
For referral intake or pre-visit routing
We are using a patient-owned overlap tracking page to keep crashes, triggers, function changes, and cross-system symptom patterns in one place before the visit. Public route: https://precisionmito.com/complex-chronic-illness-tracking
Moderator or advocate note
For support-group or resource follow-up
If a chronic illness history keeps getting split across several labels, this page helps keep symptom patterns, function drift, and follow-up prep in one record before the next handoff: https://precisionmito.com/complex-chronic-illness-tracking
Tracked follow-up
Only after someone wants their own record
Tracked overlap 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 symptom patterns, function changes, and follow-up prep across mixed-label chronic illness stories. 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 overlap landing page before attribution.
Use the public overlap page when the story still spans several labels and the first need is one stable explainer.
2. Short handoff second
Use this page when one smaller summary is easier to share.
Send the referral handoff page to a scheduler, caregiver, school helper, moderator, or family helper when the full landing 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 source-tagged signup only after someone asks to keep their own chronology, prepare for visits, or preserve the route for later follow-up.
4. Narrow when one route finally leads
Move into a condition page only when it helps the next handoff.
Switch into ME/CFS, Long COVID, POTS and dysautonomia, mitochondrial disease, EDS, MCAS, or fibromyalgia only when that framing now improves the next visit or support step.
Conference scan order:
public page first, referral handoff second, tracked overlap signup only on request, crash and orthostatic bridge next if PEM plus upright loss dominate, then condition-specific routes when one lane clearly leads.
Proof Bundle
Keep the referral handoff tied to the exact proof-safe packet set for the overlap lane.
Proof packet route
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-complex-chronic-illness only.
Community and clinic reuse
Keep the moderator, booth, and caregiver route aligned.
Use the same route order across resource pages, clinic notes, conferences, and nonprofit follow-up so the overlap story stays broad until one narrower route is clearly useful.
Proof packet route:
public overlap landing page, this referral handoff page, tracked overlap 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 overlap route only while a broad frame is still the right story.
- Stay on the overlap route when crashes, pain, orthostatic symptoms, trigger windows, and function drift are still crossing labels.
- Use the crash and orthostatic bridge when PEM plus upright intolerance now explain more than a fully broad mixed-label frame.
- Switch to ME/CFS when delayed payback, crash timing, and recovery burden are clearly leading.
- Switch to POTS and dysautonomia when upright loss, tachycardia, hydration strategy, and standing tolerance are leading.
- Switch to mitochondrial disease, EDS, MCAS, fibromyalgia, or Long COVID when a narrower route now produces a better next handoff than the overlap summary alone.
Companion Copy Pack
Load the current public-safe booth, moderator, clinic, and partner copy instead of rewriting the overlap lane by hand.
The companion feed keeps the overlap 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 caregiver-facing explanation that still matches the tracked source.
Loading the current overlap companion copy pack.
Proof-Safe Follow-Up
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 overlap signup link 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 route or the crash and orthostatic bridge. If one condition clearly leads, switch into the matching lane only after the broad overlap explanation has already done its job.
Mito Map is an organization and tracking tool. It does not diagnose complex chronic illness, sort overlapping diagnoses on its own, or replace medical care.