Identifying Project Topics and Requirements in a CitizenScience RareDisease Study

Introduction

Rare diseases affect fewer than 200000 individuals in the United States, yet more than 7000 distinct conditions have been identified worldwide. Because each condition is uncommon, the research community often lacks sufficient data, funding, and expertise. Citizenscience initiatives can fill these gaps by mobilising patients, families, clinicians, and advocacy groups to generate and share data that would otherwise remain hidden.

This page outlines a systematic approach for selecting project topics and establishing functional requirements for a participative citizenscience study focused on rare diseases. The guidance is intended for researchers, program managers, and patientled organisations that wish to codesign projects with the communities they serve.

Why Citizen Science Matters in RareDisease Research

• Scale of data collection: Patients can contribute symptoms, diagnostic timelines, and treatment outcomes directly from home.
• Contextual insight: Community members provide nuanced explanations of disease impact that clinicians may overlook.
• Trust and engagement: Involving patients early builds confidence that research addresses realworld needs.
• Accelerated hypothesis generation: Large, openly shared datasets enable rapid identification of patterns and therapeutic targets.

Identifying Project Topics

1. Conduct a Stakeholder Landscape Analysis

Map all relevant actors patients, caregivers, raredisease organisations, clinicians, genetic counsellors, and policy makers. Use surveys, focusgroup workshops, and socialmedia listening to capture emerging concerns.

2. Prioritise Gaps Using a Weighted Scoring Matrix

Develop criteria such as clinical relevance, data scarcity, feasibility, and community interest. Assign scores (15) and calculate a composite priority index for each potential topic.

3. Validate with a Delphi Process

Invite a panel of experts and patient representatives to iteratively rank topics. Anonymised rounds reduce bias while converging on a consensus list.

4. Align with Existing Initiatives

Check for overlap with ongoing registries, biobanks, or international consortia. Complementarity ensures that resources are leveraged rather than duplicated.

Illustrative Topics

• Longitudinal symptom tracking for mitochondrial disorders.
• Selfreported treatment sideeffects in rare autoimmune diseases.
• Genotypephenotype correlation in ultrarare neurodegenerative disorders.
• Barriers to diagnostic testing in lowresource settings.

Defining Project Requirements

Functional Requirements

• Secure data capture: Mobile/web forms that allow anonymous or pseudonymous entry of clinical variables.
• Interoperability: Export formats compatible with FAIR standards (e.g., CSV, JSONLD, HL7 FHIR).
• Realtime analytics dashboard: Visualisations for contributors to see aggregated trends.
• Feedback loops: Automated emails summarising personal data contributions and emerging findings.

NonFunctional Requirements

• Privacy & Ethics: GDPRcompliant consent workflow, dataencryption at rest and in transit.
• Accessibility: WCAG2.1 AA compliancescreenreader support, adjustable font sizes, and language localisation.
• Scalability: Cloudbased architecture able to handle spikes in participation during awareness campaigns.
• Usability: Usercentred design tested with at least 20 patients representing diverse literacy levels.

Technical Stack Overview

Frontend: React with MaterialUI for responsive forms. Backend: Node.js/Express API linked to a PostgreSQL database with rowlevel security. Hosting: Managed Kubernetes service with automatic backups.

Participative Study Methods

CoDesign Workshops

Facilitate virtual workshops where participants sketch mockups of data entry screens, propose questionnaire items, and discuss incentive structures. Capture decisions in a shared backlog.

Iterative Piloting

Launch a 4week pilot with 50100 volunteers. Monitor completion rates, abandonment points, and feedback. Refine interfaces and wording before full rollout.

Gamified Engagement

Introduce optional challenges (e.g., Complete 5 weekly logs) and award digital badges. Gamification can increase adherence without compromising data quality.

Community Governance

Establish a steering committee comprising patient advocates, clinicians, and dataethicists. The committee reviews datasharing policies, publication plans, and any amendments to the protocol.

Key Recommendations

1. Start with the community: Topic selection must be driven by lived experience rather than purely academic curiosity.
2. Document every decision: Transparent records of scoring matrices, Delphi rounds, and design choices support reproducibility.
3. Invest in training: Offer short tutorials on data privacy, symptomreporting standards, and use of the platform to reduce entry barriers.
4. Measure impact early: Define quantitative metrics (e.g., number of unique symptom entries, participant retention) and qualitative outcomes (e.g., participant satisfaction) at the projects outset.
5. Plan for sustainability: Identify longterm funding sources, integrate with national raredisease registries, and design modular code that can be repurposed for other conditions.

Conclusion

Identifying meaningful project topics and building clear requirements are foundational steps for any citizenscience initiative in the raredisease arena. By systematically engaging stakeholders, applying transparent prioritisation tools, and cocreating an accessible digital platform, researchers can harness the collective expertise of patients and professionals alike. The resulting data not only enriches scientific understanding but also empowers the community with insights that directly affect their everyday lives. When these practices are embedded into a participative study design, the likelihood of sustained engagement, highquality data, and actionable outcomes increases dramatically.