Professional Practice and Program Management
Professional Practice and Program Management
This domain tests whether you can run an environmental health program: identify needs, set defensible objectives, deploy limited resources, evaluate honestly and communicate risk without losing public trust.
Planning cycle
Assess needs (data, inspection findings, complaints, disease rates, vulnerable populations) → prioritise using magnitude, severity, equity and preventability → write objectives → design activities → implement → evaluate → reassess. Objectives should be SMART: "reduce critical violations in full-service restaurants by 20% within 12 months" is measurable; "improve food safety" is not.
Logic models make the chain explicit: inputs → activities → outputs → short-term outcomes → long-term outcomes. Outputs count what the program did (inspections completed); outcomes describe change in the population (decline in violations, illness). Confusing the two is the most common evaluation failure. The CDC Framework for Program Evaluation (engage stakeholders, describe the program, focus the design, gather credible evidence, justify conclusions, ensure use and share lessons) is a reliable structure.
Management tools
Risk-based inspection frequency and performance standards; standardised inspection forms and calibrated training to reduce inter-inspector variation; PDSA cycles and root-cause analysis for quality improvement; cost-of-illness, cost-effectiveness and cost-benefit analysis to justify budget; data governance, confidentiality and record retention; workforce competencies and continuing education. Programs also need clear legal authority, an enforcement-discretion policy and due-process safeguards for permits, orders and closures.
Risk communication
Build trust before conveying facts: empathy, competence, honesty, commitment. Give the action first ("use bottled water until further notice"), explain what is known and unknown, state when the next update comes, and use channels the affected audience actually uses. Segment audiences, translate into the languages spoken, and pre-test messages. Crisis principles: be first, be right, be credible.
Worked example
A jurisdiction finds 62% of restaurants had at least one critical violation at routine inspection. It mandates certified food protection managers and re-measures after 12 months: 41%. Before declaring success, check whether there was a comparison jurisdiction, a secular trend or regression to the mean; whether the inspection form or inspector changed; whether violations are counted per inspection or per facility; and whether illness complaints moved. Recommend a difference-in-differences comparison with adequate sample size. Reasoning: a before-after drop is an output-level signal, not proof of outcome improvement.
Traps that cost marks
- Reporting activities as outcomes.
- Objectives with no baseline, target or timeframe.
- Risk messages heavy on reassurance and light on actionable instruction.
- Ignoring equity: aggregate improvement can hide worsening in the highest-risk groups.
- Treating a single pre-post comparison as proof of program effect.