Disease programs
People can join the disease program that fits them, or start broader and narrow later if a more specific path becomes clear.
Research
Broader participation makes the data network more useful.
MDA can include people at different points in the journey: confirmed diagnoses, suspected diagnoses, caregivers, family advocates, people in different geographies and care settings, and comparison volunteers when a program allows it. The goal is a richer, more representative dataset that can support aggregate, longitudinal evidence without moving raw health records into public forms. When people return clear updates over time, researchers can compare group patterns more fairly, design better studies, publish clearer reports, and return plain-language findings later. If you already use Mito Map, coming back with a short update when symptoms, care, tests, or goals change helps keep the longitudinal picture current. A few words are enough.
Start with a basic account and the smallest useful set of details. If you later want to add private health information, Mito Map keeps that part separate and under your control.
Who can help
Different participation paths make the network more complete.
Suspected diagnoses
People still working toward a diagnosis can help surface early patterns and keep the network from being limited to only the most complete records.
Caregivers and family advocates
Caregivers can help tell the story, reduce burden, and keep updates current when the patient wants support.
Geography and care settings
Participation from more places and care settings makes the public picture less local and more useful to the community.
Comparison volunteers
Some programs may invite non-mito comparison volunteers so researchers can compare patterns carefully when the program says that is appropriate.
Different backgrounds and life stages
A dataset is stronger when it reflects different ages, backgrounds, and care histories instead of only one narrow slice of the community.
What MDA asks for
Ask for the minimum information needed to route someone into the right public path.
Start with the smallest useful set of details for joining, routing, or study review.
Use broad program choices first, then add detail only when a program truly needs it.
Keep raw charts, lab files, genetics, and detailed symptom histories in Mito Map or another governed system.
Use public forms to guide people, not to collect a patient record.
Why it matters
More breadth and more follow-up make aggregate, real-world evidence easier to trust and easier to review for biomarker and endpoint planning.
More programs and more people reduce the chance that one disease path dominates the picture.
Repeated updates from the same people show what changed over time, which gives aggregate models, prediction checks, and research reviews a better chance of reflecting the current reality.
When the same consented pattern keeps showing up, teams can review whether a model, cohort screen, or follow-up cue is still useful without guessing from one old snapshot.
Broader participation helps the network spot blind spots before they distort planning or review.
That can help teams rule out weak fits earlier and avoid some avoidable protocol rework, but it does not promise lower spend, faster enrollment, or trial success.
Real-world evidence grows from reviewed, aggregate results over time, not from a single snapshot or a promise about individual care.
Those same aggregate summaries can help collaborators judge whether a biomarker or endpoint idea is ready for a closer review, still exploratory, or needs more data before protocol work starts.
Consent-aware summaries can support aggregate analysis without exposing individual records or personalized recommendations. If Mito Map ever surfaces a follow-up prompt from those summaries, that prompt is a review cue for the person and care team, not a diagnosis, treatment plan, or personal recommendation from MDA.
How results return
Reviewed evidence can become a milestone note, a publication, or the next question to study.
Public summaries should explain what changed, what was measured, and what still needs follow-up.
Milestone notes and publications belong on the public side, not in raw record exports.
Mito Map stays the private home for detailed records, consent choices, and patient-level follow-up.
What people control
Join the public path first, then add private details only if you want to.
You can start with a basic account and keep medical records out of public forms.
Mito Map is where detailed health information, consent choices, and follow-up live.
Any request to share more should explain why it is needed before you decide.
Coming back with a short update after symptoms, care, tests, or goals change helps the network stay useful, but you choose the pace and the details you share.
Privacy boundary
Broader participation is not the same as broader data exposure.
Public side
MDA explains the path, the purpose, and the next step in plain language.
Private side
Mito Map holds detailed health information, consent controls, and patient-level workflows.
Review side
Research and partner requests are reviewed before any governed data work moves forward.
Returned value
When appropriate, the community should get back plain-language summaries, updates, or publications.
MDA is the Alliance's public website. It should help more people participate without becoming a patient record or a direct-access data warehouse.
Next step