The outbreak seen from the clinics, before the bulletin.
Analytics · No PHI · Every specialtyThe syndromic half ships inside IDSPReport (Disease Report), on its Syndromic tab, rather than as an app of its own: a case is captured off the day’s visits instead of typed twice, with age, sex and village taken from the record and the capture refused — naming the missing field — rather than guessed; the same visit cannot be counted twice for one syndrome; a mid-week cluster scan reads the area thresholds IDSP already holds; and cases are read by area. What is left of this idea is the part that needs data the product does not hold: the cross-clinic aggregation. This product is one organisation’s database, nothing here reads across tenants, and no anonymisation layer exists — a cluster is a cluster inside one hospital’s own line list.
It does not see other clinics — the surveillance view reads one organisation’s own line list, so the district picture still comes from the district. It does not lower a threshold or invent one: the area threshold is the one IDSPReport already holds.
Every app page carries this section. A listing with only benefits is an advertisement.SyndromeWatch reads IDSP cases and area thresholds and writes nothing — the case is IDSPReport’s. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.
It does not see other clinics — the surveillance view reads one organisation’s own line list, so the district picture still comes from the district. It does not lower a threshold or invent one: the area threshold is the one IDSPReport already holds.
Every record stays; only the workflow leaves.
SyndromeWatch is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.