| Course | HLTH 4200 Principles of Epidemiology |
|---|---|
| Week | Week 2 |
| Paper type | Surveillance data source note |
| Length | About 1,080 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | BS in Public Health |
| Updated | October 2026 |
Free sample paper for HLTH 4200 Week 2
School Absence Records as a Signal for Influenza-Like Illness in the Brookfield Unified School District: How the Data Are Collected, What They Can Signal and Who They Never Count
Student Name
Walden University
HLTH 4200: Principles of Epidemiology
Instructor Name
Month Day, Year
School Absence Records as a Signal for Influenza-Like Illness in the Brookfield Unified School District: How the Data Are Collected, What They Can Signal and Who They Never Count
Purpose
This note describes one data source the Brookfield County Health Department, a composite local agency, is considering for influenza surveillance: daily absence records from the twelve buildings of the Brookfield Unified School District, also a composite. It describes how the records are collected, what an illness-related absence can signal about influenza-like illness in the community and which people and illnesses the method never counts. Public health surveillance means gathering and examining health data continuously and on a fixed plan so that the results can guide action (Centers for Disease Control and Prevention, 2012), and any data source should be described in those terms before it is used.
How the Records Are Collected
Each of the district's twelve buildings, eight elementary schools, three middle schools and one high school, enrolls between 350 and 1,600 students, for about 9,200 students in total. Attendance is taken by the homeroom or first-period teacher by 9:15 each morning in the district's student information system. When a parent calls the attendance office, the clerk records a reason code: illness, medical appointment, family or religious reason, or other. Students absent without a call are recorded as unexcused until a reason arrives; many reasons are never recorded.
For surveillance, the district would send the health department, each school day by noon, a file with the count of students enrolled and the count absent for each reason code in each building. No names or student identifiers would be included.
Table 1
Data Elements in the Daily File
| Element | Definition | Who records it | |
|---|---|---|
| Enrollment | Students on the building's roll that day | Student information system | |
| Total absent | Students marked absent at the morning count | Teacher | |
| Absent, illness | Absences with the illness reason code | Attendance clerk, from parent call | |
| Absent, other coded | Absences with any other reason code | Attendance clerk | |
| Absent, no reason | Absences with no reason recorded by noon | Remainder | |
The health department would calculate the percentage absent for illness in each building and across the district each day.
What an Illness Absence Can Signal
Influenza spreads readily among school-age children, and children often become ill early in a community's influenza season. A rise in illness absences across several buildings at once could therefore signal that influenza-like illness is increasing in the community, possibly before rises appear in emergency department visits or laboratory reports. The signal is most useful when it is compared with the same buildings' usual levels for the same time of year, since absence rates vary with weather, holidays and testing schedules.
Evidence on how well this works is mixed. An evaluation in New York City examined three years of daily school attendance data and found moderate increases in absenteeism among children during peak influenza season, suggesting some value for detecting large citywide epidemics (Besculides et al., 2005). The same evaluation found school-level data too noisy to detect localized outbreaks reliably, and the city decided not to adopt prospective monitoring of total absenteeism. That evaluation used total absence, not absence coded for illness; this note proposes using the illness code, which may be more specific but depends on parents calling and clerks coding consistently.
What the Method Never Counts
A surveillance data source is defined as much by what it misses as by what it captures. Several groups and illnesses fall outside this one entirely.
Sick children who attend school. A child with influenza who comes to school, perhaps because a parent cannot stay home, is counted as present. In years when many families cannot afford time off work, illness absences may undercount illness most in the neighborhoods with the most need.
Sick adults. Teachers, staff and parents do not appear in student absence data. If an influenza strain affects older adults more than children, the signal may be weak or late.
Children not enrolled in the district. Children in private schools, homeschooled children and children under school age are outside the data.
Illness on days without school. Weekends, holidays and summer produce no data. A rise in illness that begins over a holiday break would not appear until school resumes, and the first day back may show an artificial spike as illnesses that began during the break are recorded together.
Absences with no reason recorded. Unexcused absences with no call may include many illness absences. If the share of absences without a reason changes over time, the illness count changes for reasons unrelated to illness.
Illness absences coded as something else. A child kept home with a fever but recorded as a family reason is missed. Coding practices may differ between buildings and clerks.
Routine absences coded as illness. Some parents report illness for absences with other reasons, which adds noise unrelated to infection.
Judging the Data Source
Guidelines for evaluating surveillance systems direct attention to attributes such as simplicity, timeliness, data quality, representativeness and sensitivity (German et al., 2001). Against these, the absence data are simple and timely: they already exist and could arrive by noon each school day. Their weaknesses are representativeness, since they cover only enrolled children on school days, and data quality, since the illness code depends on parent calls and clerk coding. Their sensitivity for detecting a citywide or countywide rise may be moderate; for detecting an outbreak in a single building, it may be low, as the New York evaluation found.
How a Signal Would Be Judged
Before the first season, the department should decide what counts as a signal. One approach is to compare each day's district-wide illness absence percentage with the average for the same calendar week in the two previous school years, flagging days that exceed that average by a set margin for two consecutive school days. A building-level flag would require a larger margin, because a single classroom's illness can move a small building's percentage sharply. Writing these rules down in advance prevents the temptation to call any rise a signal after the fact.
Recommendation
The health department should use illness absences as one supplementary signal, not a stand-alone alarm. It should establish a baseline from at least two prior school years, track the share of absences with no reason code alongside the illness code, and compare rises against emergency department and laboratory data before acting. After one season, it should evaluate whether the signal added anything those sources did not already show.
References
Besculides, M., Heffernan, R., Mostashari, F., & Weiss, D. (2005). Evaluation of school absenteeism data for early outbreak detection, New York City. BMC Public Health, 5, Article 105. https://doi.org/10.1186/1471-2458-5-105
Centers for Disease Control and Prevention. (2012). Principles of epidemiology in public health practice: An introduction to applied epidemiology and biostatistics (3rd ed.). U.S. Department of Health and Human Services. https://archive.cdc.gov/www_cdc_gov/csels/dsepd/ss1978/index.html
German, R. R., Lee, L. M., Horan, J. M., Milstein, R. L., Pertowski, C. A., & Waller, M. N. (2001). Updated guidelines for evaluating public health surveillance systems: Recommendations from the Guidelines Working Group. MMWR Recommendations and Reports, 50(RR-13), 1-35. https://www.cdc.gov/mmwr/preview/mmwrhtml/rr5013a1.htm
HLTH 4200 Week 2 instructions, in plain terms
Surveillance notes ask you to describe a single data source well enough that a health department could decide whether to use it. Explain how the data are collected now: who records what, when and with which codes. Describe what you would receive and how you would turn it into a measure. Explain what a change in the measure could signal about the condition of interest, and cite any evaluation of similar data. Then list everything the source cannot count, which is often the most important part. Judge the source against standard surveillance attributes, such as timeliness, simplicity, data quality and representativeness. Decide in advance what would count as a signal. Close with a recommendation that matches the source's strengths and weaknesses, rather than an endorsement or a rejection, and say how you would review the decision after one season.
How the HLTH 4200 Week 2 example is put together
The note opens with the purpose and a definition of surveillance from the CDC primer. A section on collection describes attendance taking, reason codes and the proposed daily file, set out in Table 1. A section on what the data can signal explains why school-age children may show influenza early and reports Besculides and colleagues' findings. A section lists seven groups or situations the method never counts, from children who attend while sick to absences coded as something else. A section judges the source against German and colleagues' attributes. A section sets signal rules in advance, and a recommendation closes the note.
Where the marks sit in the HLTH 4200 Week 2 rubric
Faculty assess a surveillance note on how completely it describes a data source. A clear account of how the data are collected now earns credit. Explaining what the source can signal, with evidence, shows understanding of its purpose. The section on what the source cannot count is often weighted most heavily, since every surveillance system has blind spots and recognizing them is the core skill. Judging the source against named surveillance attributes shows familiarity with evaluation standards. Faculty value recommendations that match the evidence and include a plan for review. Notes that describe the data source only in favorable terms, or that skip its blind spots, earn less. Accurate citation of the evaluation literature is checked.
Common HLTH 4200 Week 2 mistakes, and how to avoid them
Begin by finding out exactly how your data source is produced, ideally by asking the people who record it. Write down each step from the event to the record. Then ask what change in the data would mean and whether anyone has tested that before; search for an evaluation. Make a list of people and situations the source could never capture, and be thorough. Compare the source with the standard attributes from your readings. Decide what a signal would look like before you see any data. A sample note for a data source you are evaluating is something we can prepare. Read your list of what the source misses and ask whether any of those gaps would hide the very people most at risk.
Get a HLTH 4200 Week 2 example written to your instructions
Share the Week 2 prompt with the rubric, and name the data source your section is examining, whether a registry, a survey or a clinic log. The note you receive traces how that source collects its numbers and lists the people it never reaches. First sample free; expect it in 24-48 hours.
More HLTH 4200 papers and BS in Public Health samples
- HLTH 4200 Week 1: Case Definition
- HLTH 4200 Week 3: Rate Calculation
- HLTH 4200 Week 4: Denominator Audit
- HLTH 4200 Week 5: Two-by-Two Table
- HLTH 4200 Week 6: Study Design Comparison
- HLTH 4200 Week 7: Confounding Write-Up
- HLTH 4200 Week 8: Screening Accuracy Write-Up
- HLTH 4200 Week 9: Outbreak Narrative
- HLTH 4200 Week 10: Causal Criteria Essay
- HLTH 4200 Week 11: Applied Epidemiology Paper
- HLTH 3115 Week 2: Measurement Exercise
- HLTH 2500 Week 2: Theory Summary
- HLTH 2110 Week 2: Concept Paper
- HLTH 1000 Week 2: Definition Paper
HLTH 4200 Week 2 questions, answered
Where can I find a free HLTH 4200 Week 2 sample paper?
The surveillance note on school absence records as a signal for influenza-like illness, with references, is free to read here.
What data source does the HLTH 4200 Week 2 example examine?
Daily absence counts, including absences coded for illness, from a composite school district's twelve buildings.
What did the New York City evaluation find?
Absence data showed moderate rises during peak influenza season but were too noisy to detect localized outbreaks reliably.
Who does the method never count?
Sick children who attend school, sick adults, children not enrolled, illness on days without school and absences coded for other reasons.
What does the note recommend?
Using illness absences as one supplementary signal, with a baseline from prior years and a review after one season.