Why This Page Exists

Community overlap is often the real problem, not a missing symptom list.

People moving between ME/CFS, long COVID, POTS, mitochondrial disease, EDS, MCAS, and fibromyalgia spaces usually need one record that keeps timing, context, and function attached. The goal is not to collapse diagnoses into one theory. The goal is to preserve a usable history when several chronic illness communities are describing pieces of the same lived pattern.

Crash And Flare Review

Track delayed payback and relapse windows.

Useful across ME/CFS, long COVID, fibromyalgia, MCAS, and mitochondrial disease when a bad day is really a sequence.

Orthostatic And Mobility Context

Keep position, instability, and support tactics together.

Useful across POTS or dysautonomia, EDS, and related hypermobility or fatigue stories where standing, bracing, hydration, and compression all matter.

Care Prep

Bring a cleaner multisystem record into appointments.

Useful when symptoms, labs, meds, rehab response, triggers, and function otherwise stay trapped in separate notes or portals.

Build A First Useful Record

Start with the sequence, the function cost, and the overlap context.

Sequence First

Capture the crash, flare, and recovery arc in one place.

Keep exertion, infection history, orthostatic load, meals, rescue meds, sleep loss, and next-day consequences tied to the same timeline so multisystem stories do not split apart.

Function Cost

Use daily anchors instead of vague worse-than-usual notes.

Track walking, upright time, driving, meal prep, work or school blocks, showering, and sensory tolerance so the record shows what the overlap actually changed.

Overlap Context

Keep the bridge between labels visible.

Show when PEM, palpitations, pain, rashes, GI symptoms, instability, or heat intolerance travel together so care prep is based on a pattern instead of disconnected notes.

Measured function score Build a full profile Open overlap tracking Open referral handoff page

Choose A Starting Point

Condition-specific pages for the beachheads already active in community growth.

ME/CFS tracking for PEM, crashes, sleep, and baseline drift.
Long COVID tracking for relapse windows, brain fog, and post-viral function changes.
POTS and dysautonomia tracking for standing intolerance, hydration strategy, and orthostatic symptoms.
Mitochondrial disease tracking for multisystem burden, labs, therapies, and referral prep.
EDS and hypermobility tracking for instability, pain, rehab response, and overlap burden.
MCAS tracking for trigger exposure, flare burden, and rescue-response review.
Fibromyalgia tracking for pain flares, sensory overload, sleep disruption, and daily function.

If you are sharing this page into a broader overlap-heavy community, start with the landing page first and keep the tracked signup route for people who want their own record: /signup.html?next=%2Fmitomap&source=community-growth-complex-chronic-illness.

If the next step is a quicker clinic, caregiver, moderator, or school-facing summary, use the shorter referral handoff page before attaching the tracked signup route.

Mito Map is an organization and tracking tool. It does not diagnose ME/CFS, long COVID, POTS, dysautonomia, mitochondrial disease, EDS, MCAS, fibromyalgia, or any other condition, and it does not replace medical care.

Route Picker

Send the page that matches the conversation instead of forcing one diagnosis frame.

Start Here

Use the overlap hub when the group spans multiple labels.

Best for chronic illness communities where crashes, pain, orthostatic symptoms, allergies, or instability all show up in the same thread and a single page would narrow the story too early.

Bridge Route

Use the crash-and-orthostatic page when PEM and upright intolerance dominate.

For mixed ME/CFS, long COVID, POTS, or dysautonomia conversations, hand off the overlap bridge page first so the shared crash pattern stays visible before a condition-specific follow-up.

Go Specific

Use a condition page when one lane clearly leads.

If the person or moderator is already focused on one primary condition, send the matching beachhead page and keep the source-tagged signup link attached for attribution.

Complex chronic illness overlap hub Crash and orthostatic overlap bridge Referral handoff page Tracked overlap signup

Community Route Matrix

Give advocates one handoff grid for the active beachheads instead of rewriting the same routing advice.

Use the overlap hub when the thread is mixed, then switch to the page below that best matches the lead symptom pattern or community language. Each route keeps a source-tagged signup path ready when someone wants their own record instead of just the explainer page.

PEM and crash lane ME/CFS

Use when post-exertional malaise, delayed payback, crash timing, and baseline compression are the center of the conversation.

Open ME/CFS route Tracked ME/CFS signup

Post-viral lane Long COVID

Use when relapse windows, brain fog, breathlessness, post-viral drift, and activity payback are leading the thread.

Open Long COVID route Tracked Long COVID signup

Orthostatic lane POTS and dysautonomia

Use when upright intolerance, heart-rate shifts, hydration strategy, compression, and standing-time collapse are the clearest entry point.

Open POTS route Tracked POTS signup

Family handoff lane Mitochondrial disease

Use when the need is a cleaner multisystem history for families, specialists, admissions, or referral-prep continuity.

Open mitochondrial route Tracked mitochondrial signup

Instability lane EDS and hypermobility

Use when joint instability, pain, subluxation patterns, rehab response, and orthostatic overlap are driving the discussion.

Open EDS route Tracked EDS signup

Trigger and flare lane MCAS

Use when exposure tracking, flare timing, rescue-med context, rashes, GI swings, or mast-cell-style symptom clustering lead.

Open MCAS route Tracked MCAS signup

Pain and recovery lane Fibromyalgia

Use when pain flares, sensory overload, poor sleep, fatigue, and function loss are present without one dominant orthostatic or post-viral frame.

Open fibromyalgia route Tracked fibromyalgia signup

Routing Rules

Hand off the right tracked route when a mixed thread starts to narrow.

Community moderators, advocates, and partner leads often need one proof-safe script for the overlap lane and one rule for when to switch into a condition-specific tracked signup. Use the overlap source while the thread is still mixed, then move to the dominant condition page only when the handoff is clearly narrower.

Keep The Overlap Source

Stay on `community-growth-complex-chronic-illness` for mixed threads.

Use the overlap hub and tracked overlap signup when a moderator post still spans crashes, pain, orthostatic symptoms, trigger flares, instability, and recovery burden across multiple labels.

Condition-First Handoff

Switch only when one lane becomes dominant.

Move into the ME/CFS, Long COVID, POTS and dysautonomia, mitochondrial disease, EDS, MCAS, or fibromyalgia tracked signup once the conversation is clearly condition-led and you want attribution attached to that narrower source.

Proof-Safe Next Step

Keep claims conservative while giving people a useful route.

Use language like patient-owned tracking for symptom patterns, function changes, and follow-up prep. Avoid diagnostic or treatment claims and let the page plus signup link do the routing work.

Open tracked overlap signup Open crash and orthostatic bridge Open measured function score

Live Community Snapshot

See the current public-safe overlap outreach and proof queue before you share the broad route.

This overlap page reads the aggregate-only community-growth status feed so moderators, advocates, booth leads, and cautious resource editors can confirm whether the broad route is still the safest first share and what proof-safe next step is currently queued behind it.

Matched contacts

-

Public-safe contact matches currently attached to the broad overlap route.

Public mentions

-

Aggregate-only overlap mentions currently surfaced for this route.

Bridge targets

-

Current organizations where the overlap route can hand off into a narrower follow-up.

Proof status

-

Current proof posture for the broad overlap route before another public share.

Updated: -

Route status: -

Proof review: -

Activity origin: -

Starter-Kit Library

Keep reusable overlap assets close to the first public route.

The broad overlap lane should not force operators back into internal notes. Keep the public route, tracked signup, share asset, advocate-facing copy, partner packet, booth materials, and reporting surface together so mixed-label shares stay consistent.

Proof Packet

Keep the overlap route tied to the exact proof-safe packet set before another broad share goes out.

Proof Bundle

Use the same overlap packet path when the route becomes a real tracked follow-up.

Stay on the public overlap hub first. If someone wants their own record after that, switch to the tracked signup and keep proof logging under community-growth-complex-chronic-illness only.

Conference Scan Order

Keep the broad route simple at booths, moderator desks, and resource pages.

Public overlap page first, overlap bridge second when PEM plus orthostatic load becomes the clearer fit, tracked signup only on request, then the proof packet or reviewed-zero route if the next move is an operator checkpoint.

Proof-Safe Rule

Do not over-claim traction before attributable proof lands.

Use the top proof-lane brief and operator snapshot to decide the next same-session move, but keep public community copy on route-safe overlap language until an import or reviewed-zero closeout is recorded.

Open proof packet Open route worksheet Open proof closeout memo Open top proof-lane brief Open operator growth snapshot Partner packet

Clinic And Family Handoff

Use one short overlap summary before the next multispecialty visit, caregiver update, or referral handoff.

Mixed-label chronic illness stories usually lose time at handoff. The problem is not just symptom count. It is that crashes, orthostatic load, pain, trigger windows, and function drift are often explained in separate fragments. This overlap page works best when it becomes the first shared summary before anyone decides which narrower route should lead the next conversation.

Baseline Before The Shift

Start with the last reliable function anchor across systems.

Note the most recent stable walking, upright time, meals, school or work block, sleep pattern, or care routine so the next handoff starts from the right comparison point.

Recent Trigger Or Sequence

Name what changed before the overlap story widened.

Capture exertion, infection, heat, travel, food, medication, hormone timing, stress, or support-stack changes that happened before the crash, flare, orthostatic setback, or pain surge.

Next Visit Ask

End with the narrowest useful question.

State what the next team needs to review now: crash timing, orthostatic burden, trigger patterns, multisystem drift, or which condition-specific route should carry the next tracked handoff.

Tracked overlap signup Crash and orthostatic bridge Build a full profile

Community Share Pack

Copy-ready overlap outreach text for cross-condition moderators, advocates, or group introductions.

Use this route when the conversation spans multiple labels. Keep the tracked signup attached to source community-growth-complex-chronic-illness when someone is ready for their own record.

Attribution source: community-growth-complex-chronic-illness

Keep multisystem chronic illness patterns in one record when the story spans more than one label.