Organizational Context

This case examines public health incident reporting across the Department of Health & Human Services, including CDC surveillance programs, state and local public health partners, healthcare systems, laboratories, and emergency response coordination functions.

Public health incidents enter reporting systems through clinical reports, laboratory confirmations, syndromic surveillance, state notifications, and international health alerts.

• Incident volume fluctuates with seasonality and outbreak dynamics.

• Signals range from isolated clinical cases to emerging public health threats.

• Data quality and timeliness vary widely across jurisdictions.

• Public trust and communication sensitivity are always present.

How the Work Was Intended to Function

From a public health surveillance perspective, incident reporting was expected to function predictably:

• Health events are reported by providers and labs.

• Cases are validated and categorized.

• Trends and anomalies are identified.

• Public health risk is assessed.

• Appropriate response actions are initiated.

Because statutory reporting requirements, surveillance systems, and emergency authorities existed, the system appeared governed at an aggregate level.

What Was Actually Happening

Observed reality diverged materially:

• Low-risk reports consumed analytic bandwidth.

• High-consequence signals were sometimes slow to escalate.

• Volume of data masked emerging patterns.

• Escalation thresholds varied across programs.

• Early uncertainty complicated communication.

The underlying issue was not epidemiologic expertise, but the absence of a shared way to interpret a single public health incident before deciding response posture.

How FLOW Was Introduced

Leadership sought a stabilizing lens that preserved epidemiologic judgment while improving consistency. Specifically, they needed:

• A common language to explain why public health incidents behave differently.

• A method to separate reporting volume from population impact.

• A unit-centered lens rather than aggregate trend intuition.

• Governance aligned to consequence rather than noise.

FLOW was introduced as a classification lens applied early in public health incident assessment.

Identifying the Unit of Effort

The organization anchored reporting on a single, stable unit of work:

• Unit of Effort: one public health incident requiring assessment and response.

• Multiple case reports, lab results, or syndromic signals may inform the same unit.

• Parallel surveillance streams do not create new units.

• The incident remains constant as investigation and response deepen.

How Complexity Was Determined

Complexity was defined as the amount of judgment required to understand cause, transmission, and risk.

• Low complexity: known disease with established response.

• Moderate complexity: incomplete information or evolving clinical picture.

• High complexity: novel pathogen or unclear transmission.

• Very high complexity: conflicting data or cross-border implications.

How Scale Was Determined

Scale was defined as the breadth of public health impact if the incident is mishandled.

• Number of individuals or communities affected.

• Potential for spread or amplification.

• Impact on healthcare system capacity.

• Duration and irreversibility of harm.

Other Measures of Scale Considered

• Media attention and public concern.

• Volume of reported cases.

• Political sensitivity.

• Resource cost of response.

• International attention.

These measures were visible and influential, but were not used as the primary definition of scale in this walkthrough.

Applying FLOW to Public Health Incident Reporting

With complexity and scale definitions fixed, each public health incident was classified consistently. The unit remains constant across all examples — this is still one public health incident.

• Classify complexity first.

• Classify scale second.

• Assign the single FLOW classification.

FLOW A — Localized, Contained Public Health Incidents

This example involves one public health incident. The unit does not change.

Example: isolated case of a known, non-transmissible condition.

• Complexity: low.

• Scale: low.

• Handling implication: routine reporting and monitoring.

Built-out handling: public health officials document the case, verify reporting completeness, and monitor for recurrence.

FLOW B — Coordinated Public Health Response

This example still involves one public health incident. The unit remains the same; coordination expands.

Example: small cluster requiring coordination with state partners.

• Complexity: low.

• Scale: moderate.

• Handling implication: coordinated investigation.

Built-out handling: health departments align case definitions, share data, and coordinate response actions.

FLOW C — Complex, Judgment-Driven Public Health Incidents

This example still involves one public health incident. Judgment requirements increase.

Example: emerging disease with uncertain transmission dynamics.

• Complexity: high.

• Scale: low-to-moderate.

• Handling implication: senior epidemiologic judgment.

Built-out handling: experts test hypotheses, manage uncertainty, and advise leadership on precautionary measures.

FLOW D — System-Level Public Health Impact

This example still involves one public health incident. The unit remains unchanged; dependency becomes enterprise-wide.

Example: outbreak threatening healthcare system capacity.

• Complexity: variable.

• Scale: high.

• Handling implication: department-wide governance.

Built-out handling: HHS leadership coordinates national response, allocates resources, and manages interagency actions.

FLOW S — Exceptional Public Health Emergencies

This example still involves one public health incident. Normal governance is insufficient.

Example: rapidly spreading disease requiring immediate emergency action.

• Complexity and scale vary.

• Handling implication: emergency authority.

Built-out handling: immediate emergency response activation, crisis communication, and executive oversight.

What Changed After FLOW Classification

• Clearer escalation thresholds.

• Reduced analytic noise.

• Faster response to high-impact incidents.

• Improved accountability.

Organizational Implications

• More consistent public health decision-making.

• Better coordination across jurisdictions.

• Improved communication clarity.

• Stronger public trust.