We are a small team of 15 year olds building a simple SMS/USSD tool where communities report a small number of symptoms, clinics send short confirmations, and the system generates early-warning signals (not diagnoses) to help clinics prepare for possible NTD outbreaks.
We are now trying to move from concept to a small, realistic pilot and would really value guidance from those with implementation experience.
We are currently exploring Zimbabwe as a pilot setting, with a deliberately limited scope: 1–2 communities, SMS/USSD only, 1–2 NTD categories, and a short timeframe.
We would particularly appreciate advice on:
• What a responsible and practical pilot should look like in this context
• How to design community reporting incentives that are low-risk and acceptable to ministries
• Common failure points when moving from concept to pilot in similar systems
Our aim is to design something simple, safe, and aligned with existing DHIS2-supported workflows, rather than creating parallel systems.
We would greatly value any guidance or mentoring from those with relevant experience.
Welcome to the DHIS2 Community of Practice! I see that in your other post, @Stefano has offered to join a call which is great and will give you a push forward.
At 15, working on integrations with the open-source DHIS2 to help the world be a better place, good job! It’s great that you’re also sharing this experience with the global community on the CoP. We’re all here to support and learn from each other.
Surveillance, Early Warning & OneHealth pt 1 #dac2023: Event-based surveillance (EBS), “Experience how DHIS2 has revolutionized surveillance systems, enabling real-time data collection, analysis, and response. Explore the seamless integration of early warning systems into DHIS2, empowering proactive measures against potential threats.”