Why Evidence-Based Emergency Guidance Matters More Than Speed

# Why Evidence-Based Emergency Guidance Matters More Than Speed

Draft notice: Draft 1. Sources identified, not yet fully verified. Governance and evidence argument — not clinical protocol.

When an earthquake hits, social platforms fill within minutes with well-meaning lists: induce vomiting, suck snake venom, check pulse for two minutes, pour water on unconscious faces. Some entries are harmless; some accelerate harm. Speed of publication is not virtue if accuracy is unverified.

Virality selects for confidence, not correctness

Information behavior research during crises shows rapid sharing of novel or emotionally charged content — corrections lag [World Health Organization infodemic management framework; academic misinformation during disasters literature summarized in CEP related insights].

Emergency platforms face the same incentive distortion if KPIs reward time-to-publish over time-to-verified-publish.

Myths that speed revives

Documented harmful myths recurring across regions include:

• Poisoning: induced vomiting without professional direction — aspiration risk [poison control center public guidance globally].
• Snake bite: cutting or sucking wound — infection and delayed transport [WHO snakebite envenoming resources].
• Cardiac arrest: pulse-check delays before compressions — reduced survival in chain-of-survival models [ILCOR lay rescuer recommendations].
• Burns: butter, toothpaste, ice directly on wound — tissue damage and infection [burn first aid consensus summaries].

Speed-publishing any of these because "something is better than nothing" is incorrect when slower verified guidance exists.

Evidence governance is a safety feature

CEP's evidence and review protocol distinguishes content banks:

• Bank A: Evergreen design arguments with sourced facts
• Bank B: Medical and technical claims requiring expert review
• Bank C: Event response with heightened verification

Import rules prevent silent promotion of DRAFT fixtures to public APPROVED status. Assets cannot invent steps not in canonical scenarios [CEP Emergency Asset Architecture governance statement].

This is slower. It is intentionally slower.

Simple language ≠ simple sourcing

Plain language saves lives by reducing cognitive load [related CEP insight]. Simplification happens after claim validation — not by skipping validation for readability.

A sixth-grade reading level sentence can still cite ILCOR, WHO, or NDMA. Brevity and rigor are not opposites.

When speed legitimately matters

Speed matters for:

• Event detection and warning (cyclone track updates from IMD)
• Dispatch and resource routing (112/108 systems)
• Clarifying active rumors with pre-reviewed myth-buster cards

Pre-reviewed template content enables fast assembly: "Do not induce vomiting" cards ready before poisoning season — not improvised tweets.

Transparency as trust

Marking content DRAFT, `expertReviewed: false`, and `SOURCES_IDENTIFIED` tells professionals and public where confidence should be calibrated. Hiding review state to look launch-ready destroys long-term credibility faster than missing features.

Withdrawal paths for unsafe approved assets must exist without deleting audit history [CEP asset withdrawal architecture].

Implications for AI-generated content

Generative tools accelerate draft briefs and posters — but generation is not approval. Visual safety checklists and medical review flags exist because image and text models confidently depict wrong CPR hand placement [CEP visual safety checklist].

Human review bottlenecks are real. Solution is prioritized queues (P0 first), not bypass.

Open questions

• Can rumor tracking during Indian disasters feed prioritized review queues automatically?
• What is minimum viable expert review for low-risk preparedness vs P0 medical scenarios?
• How should platforms display "last reviewed" dates without false precision?