AnalyticsLive · in the productReport

SyndromeWatch

Syndromic counts from every branch in the group, with a heuristic flag and small cells hidden.

Get SyndromeWatch Open the appAvailable nowHow pricing works →

What it is

The syndromic line lists of every branch in a business group, side by side: fever and influenza-like illness, severe respiratory infection, acute diarrhoea, jaundice, encephalitis and fever with rash, per branch per day of onset, from each branch’s own Disease Report cases. Each branch is read inside its own organisation and only counts cross — a count of one to four people shows as fewer than 5, and a group total that would give a hidden count back is hidden too. A day is flagged when a branch saw at least five cases and more than the mean plus two standard deviations of the 28 days before it: a rule of thumb for where to look first. Who sees it is decided by the group’s own grant to the person’s sign-in email.

Who uses it: Built for: Every specialty
Reads: IDSP cases at each branch in the group
Writes: Nothing — the case is IDSPReport’s
Never: It does not declare an outbreak: the flag is a statistical heuristic, and the declaration, the area thresholds and the investigation stay with Disease Report at the branch.
Access: Only people whose role includes it — the clinic owner decides who
Your data: No PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

How it works

Get a grant on the groupThe screen reads across a business group, so the group owner first grants your sign-in email on Group; without a live grant it shows one sentence and no numbers. A manager’s grant can name only some branches, and then only those are read.
Pick 7, 14 or 28 daysEach syndrome — fever and influenza-like illness, severe respiratory infection, acute diarrhoea, jaundice, encephalitis, fever with rash — opens as a table of branches by day of onset, counted from each branch’s own Disease Report cases, with the whole group underneath.
Read <5 as hidden, not smallA count of one to four people is sent as hidden and shows as <5; a group total that would give a hidden count back is hidden too. Zero is shown, because nobody is in it.
Look first where it is flaggedFlags lists each branch-day with at least five cases above the mean plus two standard deviations of the 28 days before it, with that limit. It is a heuristic for where to look — the outbreak itself is declared and investigated on Disease Report at that branch.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not declare an outbreak: the flag is a statistical heuristic, and the declaration, the area thresholds and the investigation stay with Disease Report at the branch.

It never shows a person, an area or a row — counts only — and it does not read clinics outside the business group.

A disease a branch added for itself is not pooled, because its code means something only there.

AI in SyndromeWatch

AskQuestions about what is on screen — “What needs attention in SyndromeWatch today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

SyndromeWatch — Syndrome Watch — See fever, diarrhoea and jaundice counts from every branch, day by day — 01Syndrome Watch — See fever, diarrhoea and jaundice counts from every branch, day by dayCaptured from the running demo clinic

01Syndrome Watch — See fever, diarrhoea and jaundice counts from every branch, day by dayCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 1

IDSPReport

See the whole clinic →

Questions clinics ask

What does SyndromeWatch do?

Syndromic counts from every branch in the group, with a heuristic flag and small cells hidden. The syndromic line lists of every branch in a business group, side by side: fever and influenza-like illness, severe respiratory infection, acute diarrhoea, jaundice, encephalitis and fever with rash, per branch per day of onset, from each branch’s own Disease Report cases. Each branch is read inside its own organisation and only counts cross — a count of one to four people shows as fewer than 5, and a group total that would give a hidden count back is hidden too. A day is flagged when a branch saw at least five cases and more than the mean plus two standard deviations of the 28 days before it: a rule of thumb for where to look first. Who sees it is decided by the group’s own grant to the person’s sign-in email.

What data does SyndromeWatch read and write?

SyndromeWatch reads IDSP cases at each branch in the group 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.

What does SyndromeWatch deliberately not do?

It does not declare an outbreak: the flag is a statistical heuristic, and the declaration, the area thresholds and the investigation stay with Disease Report at the branch. It never shows a person, an area or a row — counts only — and it does not read clinics outside the business group. A disease a branch added for itself is not pooled, because its code means something only there.

What happens to our data if we uninstall SyndromeWatch?

Every record stays; only the workflow leaves.

Is SyndromeWatch available today?

Yes — SyndromeWatch is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see SyndromeWatch running on your own patients?

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.

More in Analytics

All 28 →