Stand Up a Standing Outbreak-Response System for Measles and HFMD Before the Next Wave

Diagnosis

The note characterizes the problem plainly: recurring childhood vaccine-preventable waves (measles) alongside hand-foot-mouth-disease (HFMD) waves. These are episodic events, not a steady-state condition, which is why the engine here is event-driven and the horizon is short. Two features make this urgent now. First, measles is vaccine-preventable, so every wave that occurs is a signal of an immunity gap that routine immunization should have closed, and the gap compounds across birth cohorts if left unaddressed. Second, the context records no current-state indicator value for either disease (current_state is null, data_status is needs_collector), which means the responsible body is operating without a live surveillance feed. You cannot manage a wave you cannot see in time. The lead body is the Directorate General of Health Services (DGHS), with the Department of Public Health Engineering (DPHE) named as a supporting body, the latter relevant because HFMD transmission is tied to hygiene and water access in childcare and school settings.

The core failure is not a single missed campaign. It is the absence of a standing system that detects a cluster early, confirms it, and triggers a pre-agreed response. Without that, each wave is fought from a cold start.

Recommended actions

1. Close the surveillance blind spot. Owner: DGHS. Mechanism: a measles-and-HFMD event collector feeding a weekly case-cluster line list from upazila health complexes and sentinel hospitals into the DGHS surveillance system, with a defined cluster-alert threshold. Observable signal: a populated weekly case feed where current_state is no longer null, and alerts firing on real clusters rather than on press reports.
2. Pre-position a measles outbreak-response protocol. Owner: DGHS. Mechanism: a standing circular that defines, in advance, the trigger (a confirmed cluster), the catch-up vaccination radius, and the cold-chain and staffing call-up, so a response launches in days, not after committee formation. Observable signal: time from cluster confirmation to first catch-up vaccination day falling wave over wave.
3. Map and close routine immunization coverage gaps by sub-district. Owner: DGHS. Mechanism: use the new case feed to rank upazilas by recurring measles clusters, then direct routine immunization micro-planning and supplementary campaigns to the lowest-coverage pockets first. Observable signal: clusters concentrating in fewer upazilas over successive seasons as the worst gaps are filled.
4. Attach the HFMD hygiene response to DPHE. Owner: DPHE, supporting DGHS. Mechanism: a school-and-childcare hygiene protocol (handwashing access, surface cleaning, temporary closure guidance) activated when an HFMD cluster alert fires, since HFMD has no vaccine and is controlled by transmission breaks. Observable signal: HFMD clusters resolving faster after the hygiene protocol is triggered.
5. Publish a short post-wave review after each event. Owner: DGHS. Mechanism: a standardized one-page after-action note recording detection lag, response lag, and coverage gaps found, fed back into the protocol. Observable signal: each successive review showing shorter lags than the last.

Sequencing (first 12 months)

Start with action 1: the surveillance feed is the binding prerequisite, because actions 2 through 5 all depend on seeing clusters in time. Stand up the case feed and alert threshold first. Once data flows, issue the standing measles protocol (action 2) and the DPHE hygiene protocol (action 4) so the next wave meets a prepared system. Use the first season of feed data to rank upazilas (action 3). The after-action review (action 5) closes the loop only once there has been a wave to review. The feed unlocks everything downstream.

Risks and constraints

The binding constraint is institutional, not technological: a surveillance feed and standing circular are cheap, but they require DGHS to commit upazila staff time to weekly reporting and to accept pre-authorized triggers that fire without fresh sign-off. That pre-authorization is the politically hard part, since it cedes case-by-case discretion. Fiscally, catch-up campaigns and cold-chain call-ups draw on immunization budget lines that compete with routine coverage. DPHE coordination adds a cross-agency seam where ownership can blur. Each risk is managed by writing the trigger, owner, and budget line into the circular in advance.

Bottom line

Measles and HFMD waves recur, yet the responsible body currently has no live indicator to see them coming, which is the gap to close first. DGHS should pre-position a standing detect-confirm-respond protocol, fed by a real case surveillance feed, so the next wave meets a prepared system instead of a cold start.