Mitochondrial Disease Referral Handoff

Use one short, family-safe handoff before the next mitochondrial referral or care-transition call.

This page is a public-safe handoff aid for mitochondrial disease families, advocates, clinic schedulers, and community moderators who need a clean first route before a tracked signup. Use the public route first, then move to the tracked handoff only when someone wants their own record.

Live Proof Queue

Keep the due-now proof lane attached to the exact packet, handoff page, and booth path.

This referral handoff now reads the public-safe community-growth snapshot directly so mitochondrial route copy stays aligned with the current proof queue, review date, and reusable partner assets. It is still a public handoff page, not a proof log.

Matched contacts
-

Current source-contact matches for the mitochondrial lane.

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 lane.

Route status
-

This lane is still packaging-complete but waiting on first attributable proof.

Loading the current mitochondrial move-first and proof-focus snapshot.
Three-Minute Family Handoff

Capture the four details that make the next visit usable.

1. Stable baseline

Start with the last reliable function anchor.

Use school, work, walking, feeding, hydration, sleep, or recovery capacity so the next team can see what changed from a real baseline.

2. Recent shift

Name the latest event that moved the pattern.

Keep it to one infection, admission, medication change, supplement change, therapy shift, feeding change, or symptom jump.

3. Current supports

List what is active right now.

Include hydration, feeding support, therapies, medications, mobility help, pacing supports, and the one or two measures families are already using at home.

4. Next question

End with the decision the next team needs to make.

Examples: what to monitor next, whether the referral should widen, whether the current support is helping, or what would trigger a different workup.

Copy-ready caregiver note: Baseline before the change: [last stable function]. What changed: [infection, admission, therapy shift, feeding change, or symptom jump]. Current supports: [hydration, feeding, medications, supplements, therapy, or mobility supports]. What we need from this handoff: [the next question or decision].
Scheduler And Referral Copy

Use conservative wording when a clinic or nonprofit asks for one short explanation.

Clinic scheduler note

For referral intake or pre-visit routing

We are using a patient-owned mitochondrial disease tracking page to keep symptoms, care changes, function drift, and recent supports in one place before the visit. Public route: https://precisionmito.com/mitochondrial-disease-tracking
Moderator or advocate note

For family-support or community-resource follow-up

If mitochondrial disease history keeps getting rebuilt from memory, this page helps keep symptoms, function, labs, and care changes in one record before the next handoff: https://precisionmito.com/mitochondrial-disease-tracking
Tracked follow-up

Only after someone wants their own record

Tracked mitochondrial signup: https://precisionmito.com/signup.html?next=%2Fmitomap&source=community-growth-mitochondrial-disease
Safe claim line

Keep the framing conservative

Patient-owned tracking for symptom patterns, function changes, and follow-up prep. This is not a mitochondrial diagnostic tool, genetics interpreter, or replacement for medical care.
Handoff Ladder

Move from public explainer to tracked signup in a fixed order so family, clinic, and booth follow-up stay proof-safe.

1. Public route first

Start with the mitochondrial explainer before attribution.

Use the public landing page when a family, scheduler, moderator, or conference contact only needs a safe first look at the workflow.

2. Short handoff second

Use this page when someone asks for the smallest usable summary.

Keep the note to baseline, recent shift, current supports, and the narrowest next question so the handoff stays useful and conservative.

3. Tracked signup only on request

Attach attribution only when someone wants their own record.

Switch to the source-tagged signup only after the family or caregiver asks for a personal record they can keep using across visits.

4. Widen when the story stops being narrow

Do not force a mitochondrial frame on mixed overlap threads.

Route out when upright intolerance, MCAS-style flares, or broad chronic-illness overlap become the main organizing problem instead of specialist mitochondrial continuity alone.

Conference scan order: landing page first, referral handoff page second, tracked mitochondrial signup only on request, then wider overlap routes if the conversation is mostly dysautonomia, MCAS-style reactivity, or mixed-label function drift.
Proof Bundle

Keep the referral handoff tied to the exact proof-safe packet set for the mitochondrial 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 family wants their own record after that, switch to the tracked signup and keep any proof logging under community-growth-mitochondrial-disease only.

Conference and clinic reuse

Keep the booth, scheduler, and partner packet language aligned.

Use the same route order across family conferences, clinic scheduling notes, and nonprofit resource follow-up so the mitochondrial story stays narrow until overlap routing is clearly needed.

Proof packet route: public mitochondrial landing page, this referral handoff page, tracked mitochondrial 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 narrow mitochondrial route only when it is still the real story.

  • Stay on the mitochondrial route for specialist prep, care transitions, admissions, feeding or hydration changes, therapy shifts, and one family timeline.
  • Use the measured-function page when the handoff needs one practical function anchor before the next visit.
  • Switch to POTS and dysautonomia overlap when upright tolerance, tachycardia, salt or fluid strategy, and heat sensitivity now explain more than the mitochondrial history alone.
  • Switch to MCAS overlap when trigger-heavy reactivity, food or medication responses, flushing, or flare chronology have become the main handoff problem.
  • Switch to the overlap hub when dysautonomia, MCAS-style flares, pain, or multi-label crash burden become the main organizing problem.
Companion Copy Pack

Load the current public-safe booth, moderator, clinic, and partner copy instead of rewriting the lane by hand.

The companion feed keeps the mitochondrial 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 caregiver, clinic, or community-facing explanation that still matches the tracked source.

Loading the current mitochondrial 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 mitochondrial signup link and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-mitochondrial-disease.

If someone only wants a lightweight next step, keep them on the public route or measured-function support page. If they need a narrower family handoff, send this page. If they need a broader route picker before signup, use the beachhead hub or complex-overlap page instead of attaching mitochondrial attribution too early.

Mito Map is an organization and tracking tool. It does not diagnose mitochondrial disease, interpret genetics on its own, or replace medical care.