AZMedAppzSign inSet up a practice

SyndromeWatch

◦ in design

The outbreak seen from the clinics, before the bulletin.

Analytics · No PHI · Every specialty

What SyndromeWatch does

Bottom-up syndromic surveillance: anonymised, aggregated symptom patterns across consenting clinics watched for unusual clusters — fever spikes in one locality, diarrhoeal clusters after a festival — flagged to public-health teams days before formal channels, feeding IDSPReport rather than replacing it.

What it reads

aggregated anonymised patterns

What it writes

cluster alerts
Same patient record as every other app — nothing is copied into a silo. Data class: No PHI.

What it does not do

It does not track individuals — aggregates only, k-anonymity enforced, and a cluster alert names a place, never a person.

Every app page carries this section. A listing with only benefits is an advertisement.

Questions clinics ask

What data does SyndromeWatch read and write?

SyndromeWatch reads aggregated anonymised patterns and writes cluster alerts. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.

What does SyndromeWatch deliberately not do?

It does not track individuals — aggregates only, k-anonymity enforced, and a cluster alert names a place, never a person.

What happens to our data if we uninstall SyndromeWatch?

Every record stays; only the workflow leaves.

Is SyndromeWatch available today?

SyndromeWatch is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.

More analytics apps