Matched contacts
-
Current source-contact matches for the POTS lane.
POTS And Dysautonomia Referral Handoff
Use one short, orthostatic-first handoff before the next POTS, autonomic, cardiology, school, or family follow-up conversation.
This page is a public-safe handoff aid for people with POTS or broader dysautonomia, caregivers, clinic schedulers, school-support helpers, 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.
Live Proof Queue
Keep the overdue POTS proof lane attached to the exact packet, handoff page, and orthostatic-safe support route.
This referral handoff now reads the public-safe community-growth snapshot directly so the POTS 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 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 packaging-complete but still waiting on first attributable proof.
Loading the current POTS move-first and proof-focus snapshot.
Three-Minute Family Handoff
Capture the four details that make the next POTS or autonomic visit usable.
1. Stable baseline
Start with the last reliable upright anchor.
Use standing time, shower tolerance, school, work, walking, driving, or errands so the next team can see what changed from a real function baseline.
2. Recent trigger or support shift
Name the change that tilted the day.
Keep it to one heat event, infection, travel day, meal shift, hydration miss, medication change, exertion burst, or compression change before symptoms escalated.
3. Current orthostatic picture
Show what upright burden looked like.
Include dizziness, tachycardia, presyncope, nausea, heat intolerance, walking limits, rescue steps, and whether the episode stayed short or rolled into the next day.
4. Next question
End with the narrowest useful ask.
Examples: what support to test next, whether the route should widen, what accommodation is needed now, or what the next visit should clarify.
Copy-ready family note:
Baseline before the flare: [last stable standing or walking capacity]. What changed: [heat, infection, travel, meds, hydration, meals, or exertion]. Orthostatic picture: [upright symptoms, rescue steps, and next-day cost]. What we need from this handoff: [the next question, support change, or accommodation review].
Scheduler And Referral Copy
Use conservative wording when a clinic, school support lead, or nonprofit asks for one short explanation.
Clinic scheduler note
For referral intake or pre-visit routing
We are using a patient-owned POTS and dysautonomia tracking page to keep orthostatic symptoms, support changes, recovery burden, and daily function in one place before the visit. Public route: https://precisionmito.com/pots-dysautonomia-tracking
Moderator or advocate note
For support-group, school, or family-resource follow-up
If a POTS or dysautonomia story keeps getting rebuilt from memory, this page helps keep standing tolerance, symptom spikes, rescue steps, and next-day function on one record before the next handoff: https://precisionmito.com/pots-dysautonomia-tracking
Tracked follow-up
Only after someone wants their own record
Tracked POTS signup: https://precisionmito.com/signup.html?next=%2Fmitomap&source=community-growth-pots-dysautonomia
Safe claim line
Keep the framing conservative
Patient-owned tracking for orthostatic symptoms, function changes, and follow-up prep. This is not a POTS diagnostic tool, autonomic testing substitute, 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
Start with the POTS explainer before attribution.
Use the public landing page when a patient, caregiver, moderator, school lead, or clinic contact only needs a safe first look at the orthostatic workflow.
2. Short handoff second
Use this page when someone asks for the smallest usable summary.
Keep the note to baseline, trigger or support shift, current orthostatic picture, 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 person asks for a personal record they can keep using across visits, school notes, or accommodation follow-up.
4. Widen when the story stops being narrow
Do not force a POTS frame on mixed overlap threads.
Route out when hypermobility, PEM, MCAS-style reactivity, or broad chronic-illness overlap becomes the main organizing problem instead of orthostatic load alone.
Conference scan order:
landing page first, referral handoff page second, tracked POTS signup only on request, then wider overlap routes if the conversation is mostly hypermobility, PEM, MCAS-style flares, or mixed-label function drift.
Proof Bundle
Keep the referral handoff tied to the exact proof-safe packet set for the POTS 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-pots-dysautonomia only.
School, booth, and clinic reuse
Keep the event, scheduler, and partner packet language aligned.
Use the same route order across school accommodation notes, conference booths, clinic scheduling, and nonprofit resource follow-up so the orthostatic story stays narrow until overlap routing is clearly needed.
Proof packet route:
public POTS landing page, this referral handoff page, tracked POTS 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 POTS route only when it is still the real story.
- Stay on the POTS route for orthostatic symptom reconstruction, support-stack review, school or work accommodation prep, and one patient-owned summary before the next visit.
- Use Crash Decoder when the next handoff needs one fast upright-trigger-to-payback sequence before the full record.
- Switch to EDS and hypermobility when instability, joint events, bracing, or injury burden are doing more explanatory work than upright symptoms alone.
- Switch to ME/CFS when delayed payback, PEM, or crash timing is now the more useful organizing frame.
- Switch to MCAS when food, medication, environmental, heat, or hormone-linked reactions are dominating the flare chronology.
- Switch to the overlap hub when no single label is stable enough and the story spans orthostatic burden, crashes, mast-cell-style flares, and practical function loss together.
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 POTS 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 school, clinic, or community-facing explanation that still matches the tracked source.
Loading the current POTS 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 school, 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 POTS signup link and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-pots-dysautonomia.
If someone only wants a lightweight next step, keep them on the public route or Crash Decoder support page. If they need a broader route picker before signup, use the beachhead hub or complex-overlap page instead of attaching POTS attribution too early.
Mito Map is an organization and tracking tool. It does not diagnose POTS, dysautonomia, or any other condition, and it does not replace medical care.