01Weekly reports
Clusters flagged against baseline, every day.
- Cases by block compared with the baseline for the season
- Each cluster arrives with an action and an owner
Seen in days, not weeks
OperationsHealthWatch · public-health command centre
Data exists everywhere. Command exists in one place.
For health secretaries, mission directors and district health officers. Surveillance, hospital capacity, helpline cases, ambulances and stock on one verified picture — so outbreaks are seen in days, not weeks, and no patient is sent to a full ICU.
- Every district on one screen
- < 5 min exception to owner
- Diversion before beds run out
WhySound familiar?
Three things we hear in every first conversation.
From health secretaries, mission directors and district health officers. Composite quotes from discovery calls — the problems are real; the names are left out.
-
“We see the outbreak in the weekly report.”
Cases, lab results and helpline calls are in different systems, so a cluster is visible only after it has grown.
Mission directorOutbreaks seen a week late
-
“The ICU was full before anyone told us.”
Capacity is reported by phone, so ambulances arrive at hospitals that cannot admit.
District health officerPatients sent to full ICUs
-
“Every district has a different number.”
Reconciling systems by phone takes the hours that decisions need.
Health secretaryDecisions waiting on data
HowWhat changes with HealthWatch
The same three problems, on the screens that solve them.
Product screens with illustrative data. In a briefing we replay one of your peak weeks.
02Full ICUs
Diversion suggested before the beds run out.
- ICU, oxygen and ventilators refreshed every 15 minutes
- A diversion plan that notifies ambulance dispatch in one click
Every patient to a bed that is free
03Numbers by phone
A morning brief with decisions that close in one tap.
- Each district gets its own numbers and exceptions on WhatsApp
- Approvals are logged with time and owner
One verified picture
FieldHealthWatch in the field
The people, the phone, the place.
The workplace it runs in, the person who uses it on a phone, the team at the desk and the detail it reads.
Photographs are illustrative — real customer sites are not shown.
- 36Districtson one picture in a typical state rollout
- < 5 minTo an ownerfor every exception
- 15 minCapacity refreshICU, oxygen, ventilators
- 2.4×Clusters flaggedagainst baseline, by block
- Helpline+ ambulanceon the same record
- DailyDistrict briefon WhatsApp
01The screens
From a fever cluster to a decision before beds run out.
State command, hospital capacity, surveillance and the district brief.
autowhat · HealthWatch / State command
Illustrative data
Disease index, ICU load, helpline volume and the exceptions that need a decision.
Product screens with illustrative data — every name, place and figure is a placeholder.
02Before and after
Systems report. Nobody reconciles them in time.
Surveillance, hospital, helpline and ambulance systems already exist — reconciled by phone, after the fact.
| Area | Today | With HealthWatch |
|---|---|---|
| Outbreaks | Seen in weekly reports | Clusters flagged against baseline daily |
| ICU | Full before anyone knows | Diversion suggested hours ahead |
| Helpline & ambulance | Separate dashboards | On the same exception queue |
| Districts | Calls and spreadsheets | A morning brief with one-tap decisions |
| Review | Memory and minutes | Every exception with owner, time and closure |
03One verified picture
Eight steps, from signal to closed exception.
Every number keeps its source and timestamp, so the command centre never hides stale or estimated data.
-
01
Collect
Surveillance · HMIS
Cases, lab results and facility reports pulled per district.
-
02
Capacity
Hospitals
ICU, oxygen and ventilator availability refreshed every 15 minutes.
-
03
Calls
Helpline · ambulance
Helpline cases and ambulance response joined to the same districts.
-
04
Detect
Clusters
Cases compared with baseline by block; clusters raised with evidence.
-
05
Rank
Exceptions
Capacity, clusters and delays ranked by risk to life.
-
06
Route
Owners
Each exception assigned to a district or hospital owner in minutes.
-
07
Brief
Districts
A morning brief on WhatsApp with decisions that close in one tap.
-
08
Review
Replay
Every exception with owner, time and closure for the weekly review.
04The platform
Command, capacity and surveillance together.
Monsoon season first; heat waves, vaccination drives and mass gatherings run on the same centre.
Command · 4
- State command
- Facility map
- Exception queue
- District desks
Capacity · 4
- Hospitals & ICU
- Diversion planner
- Ambulances
- Stock & cold chain
Surveillance · 4
- Disease index
- Cluster detection
- Lab results
- Helpline triage
Review · 4
- Daily brief
- Replay
- Scorecards
- Audit trail
05How we deliver
One season, then every season.
Built on the health systems the state already runs.
- Weeks 1–4 · ConnectFacility map, surveillance and capacity feeds connected for pilot districts.
- Weeks 4–8 · OperateException queue and district briefs live in the pilot.
- Months 3–4 · ScaleEvery district; helpline and ambulance desks joined.
- Then · ExtendHeat, vaccination and event health on the same centre.
FAQQuestions we get about HealthWatch
Straight answers, before the call.
HealthWatch is a public-health command centre. Short, factual answers for buyers, procurement and the assistants people ask first.
In short. HealthWatch is a public-health command centre. It is built for health secretaries, mission directors and district health officers. It exists to remove the problems those teams describe in almost every first conversation: outbreaks seen in the weekly report; patients sent to ICUs that are already full; and district numbers reconciled by phone. With HealthWatch, teams get clusters flagged against baseline by block, daily, capacity every 15 minutes and a diversion plan before beds run out, and a morning WhatsApp brief per district with one-tap decisions. It connects to Surveillance & HMIS, Hospital systems, Helpline & ambulance and Cold chain, is used by State · districts · hospitals, and runs on web + whatsapp. Like every Autowhat AI product, HealthWatch goes live on one site, lane or process first, usually within weeks, on managed cloud, in your own VPC or on-premises, and shares one operational record with the other products, so the second deployment reuses the data and integrations of the first.
Who is HealthWatch for?
Health secretaries, mission directors and district health officers. A public-health command centre.
What problems does HealthWatch remove?
outbreaks seen in the weekly report; patients sent to ICUs that are already full; district numbers reconciled by phone.
What do we get with HealthWatch?
clusters flagged against baseline by block, daily; capacity every 15 minutes and a diversion plan before beds run out; a morning WhatsApp brief per district with one-tap decisions.
What does HealthWatch connect to, and who uses it?
It connects to Surveillance & HMIS, Hospital systems, Helpline & ambulance, Cold chain. Users: State · districts · hospitals. Channel: Web + WhatsApp.
How do we start with HealthWatch?
With a 30-minute working session on your own data — an engineer from the relevant sector, not a sales queue. The first wave is scoped in that call; most products go live on one site, lane or process within weeks and then scale.
Where does HealthWatch run, and who owns the data?
On managed cloud, in your own VPC (AWS, Azure or GCP) or on-premises, with your keys. SOC 2 Type II and ISO 27001 controls, India data residency when required, and local or open-weight models when policy demands it. The data stays yours.
06Briefing
Bring last monsoon’s peak week. We’ll show you the day it could have been seen.
A working session: your districts mapped, a past peak replayed, and the decisions it would have surfaced.