Community and Public Health Practice

01Purpose and scope

• This manual supports the course Community and Public Health Practice. It is written as a working reference for people who plan, deliver, or evaluate health work for a defined population, such as a county health department staff member, a community health worker supervisor, a nonprofit coordinator, or a clinic team member who takes on population-level responsibilities.
• The scope covers the routine sequence of community health work: learning what a population needs, choosing where to act, designing interventions with partners, delivering them, checking quality, and reporting results. It does not cover individual clinical care, which follows different standards, and it does not replace the protocols your organization or health authority has adopted. Community health practice also varies a great deal with local governance, funding rules, and the presence or absence of a formal health department, so the examples here describe common patterns rather than any single system.
• Guidance in this manual does not replace qualified professional judgment, approved procedures, or required authorization. Where a decision involves protected health information, legal obligations, emergency response, or the use of public funds, confirm the current requirements with your supervisor, legal counsel, or the authoritative body for your jurisdiction.

02Core principles

• Community health work starts from the population rather than the service. A program designed around what an agency already offers often misses the people with the greatest need. Begin with questions about who experiences a problem, where they live and work, what they already do about it, and what barriers stand in the way.
• Equity is a working requirement, not a slogan. Look at outcomes by neighborhood, age, language, income, disability, and other characteristics that the data allow you to examine, and be honest about groups you cannot see well because their information is missing or underreported.
• Interventions should be matched to the level of the problem. Individual education, policy change, environmental modification, and system redesign each have different reach, cost, and time to effect. Many programs fail because they choose the most familiar tool rather than the one that fits the cause.
• Community participation shapes what is feasible and what is trusted. Residents and local organizations know which messages land, which hours work, and which past efforts left a bad impression. Treat their input as a source of design decisions, not as a formality at the end.
• Practice is accountable to evidence and to the community. Use established frameworks and the best available data, but also state plainly what you do not know and how you will find out.

03Planning and preparation

• Start with a defined problem statement that names the population, the health issue, and the geographic area. A statement such as high rates of emergency department visits for asthma among children in two census tracts with older rental housing is far more useful than a general goal to improve respiratory health. Confirm that the problem is within your mandate and resources before committing staff time.
• Gather existing data before collecting new data. Common sources include vital statistics on births and deaths, hospital discharge data, state or county surveillance reports, census and American Community Survey estimates, school health records, and local surveys. Check each source for its time coverage, geographic resolution, and suppression rules for small counts. Where data are restricted or require a data use agreement, begin that process early because it often takes longer than the program work itself.
• Map the community assets and the stakeholders. List the organizations, faith communities, schools, clinics, employers, elected officials, and resident groups that touch the issue. Note which have authority, which have influence, and which have a direct stake. A simple matrix with these three columns is often enough to plan outreach.
• Use a planning model to structure decisions. Frameworks such as PRECEDE-PROCEED, the Mobilizing for Action through Planning and Partnerships approach, and logic models are widely used to link problems, determinants, objectives, activities, and outcomes. Pick one that your funders or partners already recognize, and document how each element connects.
• Set aside the budget, staffing, and timeline before you choose activities. Many plans assume capacity that does not exist. Identify who will do the work, how much time they have, and what happens if a key person leaves mid-project.

04Recommended workflow

1. 1
   : Conduct a community health assessment. Combine secondary data with at least one primary method, such as key informant interviews, focus groups, a short resident survey, or a walking audit of the neighborhood. Record who was included and who was missing from each method, because gaps in participation are themselves findings.
2. 2
   : Prioritize problems. Use a transparent method to rank issues. Criteria often include the size and severity of the problem, the feasibility of change, the likelihood that work will reduce inequity, and the availability of partners. Write down the ranking and the reasons for it so that later decisions can be traced.
3. 3
   : Set objectives and select interventions. Write objectives that are specific, measurable, time bound, and tied to a determinant you have identified. Choose interventions with evidence of effectiveness where it exists, and say clearly when you are adapting a model or testing something new. Consider the population's preferences and the setting in which the intervention will run.
4. 4
   : Build the partnership and agree on roles. Draft a memorandum of understanding or a simpler working agreement that states what each partner contributes, what they receive, how decisions are made, how data will be shared, and how the partnership will end or be revised.
5. 5
   : Implement the program and track activity. Keep a simple activity log with dates, locations, numbers reached, staff time, and any deviations from the plan. Activity records are the foundation for process evaluation and for explaining results to funders.
6. 6
   : Evaluate, report, and decide what happens next. Compare results to the objectives, look at implementation fidelity, and gather feedback from participants and partners. Share findings in a format the community can use, then decide whether to scale, modify, pause, or stop the work.

05Quality checks, risk controls and compliance

• Quality in community health work has several layers: the accuracy of the data, the fidelity of the intervention to its design, the appropriateness of the materials for the audience, and the safety of participants and staff. Build a short review step into each stage rather than relying on a final check. For example, have a second person verify a data extraction before it is used in a report, and have a community member read printed materials before they are distributed.
• Protect privacy and confidentiality. Small populations can be identified from aggregated data, so apply suppression thresholds and avoid publishing counts below the level your data governance policy sets. If you collect personal information, know which rules apply. In the United States, the HIPAA privacy rule governs certain health information held by covered entities and their business associates, but many community programs fall outside it, and state laws or local policies may impose stricter requirements. Check with your privacy officer before sharing identifiable data across partners.
• Manage risk for participants and staff. Screening events, home visits, and outreach in unfamiliar neighborhoods carry physical, emotional, and reputational risks. Write a risk register, assign an owner to each risk, and define what triggers escalation. Confirm consent procedures for surveys and interviews, and explain how participants can withdraw.
• Follow applicable regulations for funding, procurement, human subjects research, and emergency response. Requirements depend on the funding source, the jurisdiction, and whether the work is classed as research or program evaluation. Where a project may meet the definition of research, consult your institution's review board or the authoritative body in your jurisdiction before collecting data.

06Collaboration and documentation

• Most community health work depends on partners who do not report to you. Agree early on a single point of contact for each partner, a regular meeting rhythm, and a shared place to keep documents. Meeting minutes that record decisions, owners, and due dates prevent the common problem of the same issue being discussed repeatedly without resolution.
• Document decisions as well as activities. A decision log that notes what was decided, by whom, on what evidence, and what alternatives were considered is invaluable when staff change or when a funder asks why a particular approach was chosen. Keep the log current rather than reconstructing it at the end of the grant period.
• Adapt communication to each audience. Partners need technical detail and timelines. Elected officials need a short summary with the cost and the community impact. Residents need plain language, adequate translation, and channels they already use, such as community radio, schools, or trusted local leaders. Test materials with the intended readers when possible.

07Measures and continuous improvement

• Define indicators at three levels. Process indicators track whether activities happened as planned, such as the number of sessions delivered or the percentage of target households reached. Output indicators count direct products, such as the number of screenings completed. Outcome indicators measure change in the health problem or its determinants, such as the proportion of households reporting reduced exposure to mold, or the rate of emergency visits for the target condition. Outcome change usually takes longer to appear and is influenced by factors outside the program.
• Use baseline and comparison data where possible. Without a baseline, you cannot show change, and without a comparison group you cannot easily separate program effects from broader trends. When a comparison is not feasible, say so and describe the limits of the conclusions you can draw.
• Build in regular review points. A quarterly review of process data allows corrections while there is still time to change course. An annual or end-of-cycle review supports larger decisions about continuation or redesign. Record what was changed and why so that the next cycle starts from a clear record.
• Be cautious with small numbers. A change from two cases to three can represent a fifty percent increase while meaning very little. Report counts alongside rates, show confidence intervals when the method supports them, and avoid claiming success from a single small cohort.

08Common mistakes and how to prevent them

• Starting with a solution. Teams often adopt a popular program before defining the problem. Prevent this by writing the problem statement and the determinants analysis before any intervention is chosen, and by asking partners to challenge the link between the two.
• Treating partners as audiences. Organizations that are only informed of decisions tend to disengage or withdraw resources. Give partners a real role in design and governance, and record their input and what happened to it.
• Ignoring implementation data. Teams sometimes report only outcomes and cannot explain failure. Keep activity logs from the start, and review them alongside outcome data so that you can tell whether an intervention did not work or was not delivered as designed.
• Underestimating time for data access and approvals. Data agreements, privacy reviews, and institutional approvals can add months. Start these processes during planning and include them in the timeline with realistic durations.
• Losing the thread when staff change. Turnover is common in public health agencies and nonprofits. Maintain written protocols, decision logs, and shared folders so that a new person can understand the project within a few days.

09Practical checklist

• Write a problem statement that names the population, the health issue, and the place.
• Confirm the problem falls within your mandate, budget, and staffing capacity.
• List data sources, check their suppression rules, and start any data use agreements early.
• Map stakeholders by authority, influence, and direct stake, and note who is missing.
• Set specific, measurable objectives tied to identified determinants.
• Draft a partnership agreement covering roles, decisions, data sharing, and exit terms.
• Build an activity log and a risk register before implementation begins.
• Confirm privacy, consent, and review requirements with the responsible office for your jurisdiction.
• Schedule regular review points and record every change to the plan and the reason for it.

★Learning sources

• Micro Degree: Community and Public Health Practice
• Micro Degree: Healthcare Administration Practice
• Micro Degree: Physiotherapy Assistant Operations
• Micro Degree: Cardiac Care Support