From the Health & Human Services edition of November 9, 2026
APHA 2026 session: about a third of health departments still use no AI, two-thirds of state health departments have AI-use policies, mostly imposed from above
American Public Health Association (session with ICF, WashU, Dallas County HHS) · State and local public health departments · United States
- Publisher
- APHA Public Health Newswire
- Original publication
- 2026-11-09
- Source retrieved
- 2026-11-10
- Event date
- 2026-11-04
What happened
At APHA 2026, panelists citing a 2025 ASTHO survey said about one-third of state and local health departments do not use AI at all, use elsewhere is mostly administrative or report writing, and about two-thirds of state health departments have an AI-use policy, most handed down at the state level. Dallas County HHS described uses from COVID-19 outbreak prediction to translation and raised concerns about mental health chatbots and data center effects on residents.
Why it matters
Public health departments are being asked to move from whether to how on AI, but policy often comes from the state CIO level and workforce training is the stated gap, which shapes what local health departments can buy and deploy.
Evidence and measured results
APHA Newswire (Nov. 9, 2026) reports panel remarks by John Auerbach (ICF), Jennifer Layden (WashU) and Philip Huang (Dallas County HHS), citing the ASTHO 2025 survey figures.
Limitations and uncertainty
Session reporting, not the ASTHO survey itself; figures are panelists’ summaries of a 2025 survey; the Dallas County uses are described without outcome data.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-09; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Health departments face pressure to adopt AI but lack training, leadership readiness and department-specific policy.
- Stakeholders
- State and local health officers
- Health department informatics leads
- State CIO AI governance offices
- Discovery questions
- Which AI policy applies to your department, and who wrote it?
- Which reports or translations take the most staff time today?
- What training have staff and leaders received on AI use?
- Value hypothesis
- Policy-aligned training plus one administrative pilot can move a department from no use to measured, governed use.
- Potential engagement
- Four-to-six-week readiness and policy-adaptation engagement with one reporting or translation pilot.
- Unsupported claims
- AI improves outbreak prediction accuracy
- Every health department is ready to adopt AI
- Inherited state policy covers public health data needs
Pre-sales engineering
Role takeaway
- Fit
- Administrative, reporting and translation assistance within approved environments; analytics later.
- Architecture and integration
- Enterprise-approved assistant for drafting and translation, with document stores for templates; surveillance analytics only with defined data pipelines.
- Prerequisites
- Confirmed applicable AI-use policy
- Approved tool environment
- Staff training plan
- Constraints
- State-imposed policy may restrict tools and data
- Limited department IT and data staff
- Equity and hallucination concerns require review
- Security
- Keep identifiable surveillance and case data out of unapproved tools; apply state data classification to every pilot.
- Proof of value
- Staff hours per named report before and after
- Translation quality reviewed by fluent staff
- Policy compliance audit of pilot uses
Delivery
Role takeaway
- Work
- Assess policy, train staff, run one administrative pilot, document results and update governance.
- Dependencies
- State CIO or AI governance approvals
- ASTHO or peer policy templates
- Department leadership sponsorship
- Ownership
- Health officer or deputy, with informatics lead as day-to-day owner.
- Skills and adoption
- Training for both staff and leadership is the stated demand, so budget for it before tools.
- Governance checkpoints
- Policy gap check before pilot
- Equity and accuracy review of outputs
- Leadership report after pilot
- Acceptance criteria
- Pilot report shows measured time change on named tasks (proposed)
- All pilot uses logged against policy (proposed)
- Staff trained before access (proposed)
- Risks
- Falling further behind other sectors
- Uneven adoption across departments
- Public concern about chatbots and data centers
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Administrative and reporting uses dominate, suggesting low-integration assistants first; outbreak prediction and translation need data pipelines and language-quality checks.
Governance
Who approves, reviews and stays accountable for outcomes?
Health departments often inherit state AI policy rather than writing their own; ASTHO template policies are offered for under-resourced departments.
Security and privacy
What data, permissions and controls need testing?
Health departments handle surveillance and identifiable health data; inherited enterprise policies may not address public health data-sharing specifics.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Workforce and leadership training is the main stated need; translation uses may improve language access if quality-checked.
Procurement
What should contracts, pricing and exit terms secure?
Departments may be limited to state-approved tools; template policies lower drafting costs.
Operating model
Which teams own the service once it runs?
Governance frequently sits above the department, so local leaders need a clear internal owner for AI use.
Publication history
- 2026-11-09Health & Human Services · Issue 105 resources
Stable resource ID: apha-2026-public-health-ai-how-not-if-astho-policy-gaps-20261109