Current source-contact matches for the long COVID lane.
Use one short, post-viral handoff before the next long COVID, rehab, pulmonary, autonomic, or family follow-up conversation.
This page is a public-safe handoff aid for people with long COVID, caregivers, clinic schedulers, rehab staff, 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 long COVID proof lane attached to the exact packet, handoff page, and function-safe support route.
This referral handoff now reads the public-safe community-growth snapshot directly so long COVID 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 long COVID or rehab visit usable.
Start with the last reliable function anchor.
Use walking, stairs, showering, work, school, conversation length, or cognitive load so the next team can see what changed from a real baseline.
Name what happened before the relapse widened.
Keep it to one exertion burst, infection setback, travel day, poor sleep stretch, heat exposure, or therapy change that happened before the function drop.
Show what the setback actually looked like.
Include fatigue, brain fog, breathlessness, dizziness, symptom spread, and how long recovery took before the person got closer to baseline again.
End with the narrowest useful ask.
Examples: what review matters next, what pacing or rehab change to compare, what support to preserve, or what function loss needs to be documented now.
Use conservative wording when a clinic, rehab team, moderator, 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 long COVID tracking page when someone needs one stable link for relapse history, function loss, and visit prep without asking them to sign up yet.
Use this page when one shorter summary is easier to share.
Send the referral handoff page to a scheduler, rehab team, pulmonary follow-up, 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 timeline, prepare for a visit, or preserve the route for later follow-up.
Switch lanes when the thread becomes PEM-led, orthostatic, mast-cell-style, or broadly mixed.
Do not force a narrow long COVID 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 long COVID 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-long-covid 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 long COVID story stays narrow until overlap routing is clearly needed.
Use the narrow long COVID route only when it is still the real story.
- Stay on the long COVID route for post-viral relapse windows, brain fog, breathlessness, fluctuating function, and one patient-owned summary before the next visit.
- Use measured function score when the next handoff needs one compact function anchor before the full record.
- Switch to ME/CFS when delayed payback, crashes, and pacing breakdowns are doing more explanatory work than a general post-viral frame.
- Switch to POTS and dysautonomia when upright intolerance, tachycardia, hydration strategy, or standing tolerance are now the clearest route.
- Switch to MCAS when trigger-heavy flares, food or medication reactivity, or heat-linked reactions are driving the chronology more than the post-viral label.
- Switch to the overlap hub when no single label is stable enough and the story spans crashes, orthostatic burden, 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 long COVID 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 long COVID signup link and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-long-covid.
If someone only wants a lightweight next step, keep them on the public route or measured-function support page. If they need a broader route picker before signup, use the beachhead hub or complex-overlap page instead of attaching long COVID attribution too early.
Mito Map is an organization and tracking tool. It does not diagnose long COVID, prove causality, or replace medical care.