Explore
Flagship studies, sector briefs, and recurring reports, by topic.
Long-form data narratives that walk through an argument.
Recurring advisor series, from weekly reads to annual reviews.
The daily policy prescription, generated each morning.
Seven sector deep-dives: banking, trade, energy, agriculture, and more.
Ask the corpus: answers grounded in published work, with citations.
Grounding verified
Childhood vaccine-preventable / hand-foot-mouth waves
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.
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.
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.
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.
The figures and responsible bodies cited in this prescription are drawn from the platform's own data and the GovTwin registry listed below.
Drafted by an Opus writer grounded in the facts above. Where the prescription cites a figure, it is drawn from those facts. The diagnosis derives from the BDPolicyLab crisis taxonomy; the responsible body and budget from the GovTwin registry. Recommended actions are the think tank's policy judgment.