Assessment is the first of the core functions and surveillance is the machinery that makes it possible, so an introductory systems course reaches this territory in the second half of the session. The written work is usually a description or evaluation of a surveillance system rather than an analysis of data, and it is graded on whether you can describe a flow of information between organizations, judge its quality against named attributes, and treat the legal and ethical basis for collection as part of the system rather than as a footnote. Your section may print this as MPH 500 or MPH500; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What MPH-500 Week 6 asks for
A long-term care administrator opens a state reporting portal every Wednesday and enters the week's respiratory illness numbers. She types how many residents had symptoms and how many tested positive. The form does not ask how many residents were in the building, does not ask how many were tested, and does not distinguish a unit that tests everyone weekly from one that tests only the symptomatic. Two hundred miles away, an analyst builds a map from those submissions. The map is the system's product, and everything doubtful about it was determined by the design of that form. Surveillance analysis is the study of how an artifact like that map comes to exist and what it can honestly support.
The vocabulary is precise and you are expected to use it precisely. A surveillance system has a purpose, a case definition, a population under surveillance, a reporting source, a legal basis for collection, a transmission route, an analytic function and a defined set of people to whom the output is returned for action. Passive systems wait for reports and are cheap and incomplete; active systems go out and ask and are expensive and more complete. Syndromic systems trade specificity for speed. Registries follow defined conditions over time. Vital statistics are a near-census with legal machinery behind them and a known lag. Laboratory reporting has been substantially automated in many jurisdictions, which changed both the completeness and the failure modes of notifiable condition data.
Evaluation is not a matter of opinion here. There is a long-standing published framework for evaluating public health surveillance systems built around attributes: simplicity, flexibility, data quality, acceptability, sensitivity, predictive value positive, representativeness, timeliness and stability. Naming that framework, citing it properly and then applying two or three attributes with evidence is a far stronger paper than gesturing at all nine. The attribute most often written badly is representativeness, because it requires you to say who is missing from the data and why, which is the question this course keeps returning to.
Stewardship belongs in the same paper. Collection of identifiable health information for public health purposes rests on legal authority and carries confidentiality duties, disclosure limits, retention rules and small-number suppression practices designed to prevent re-identification in thin geographies. A submission that treats data governance as an afterthought has skipped a component of the system, and in a course about organizations that omission reads as not knowing what holds the system together.
The MPH-500 Week 6 method, step by step
Seven moves for describing and evaluating a surveillance system on paper.
-
State the purpose the system was built to serve
Detection of outbreaks, monitoring of trends, targeting of resources and evaluation of a program are different jobs, and a system built for one will look like a failure if you judge it against another. Purpose first, always.
-
Reproduce the case definition rather than paraphrasing it
Published definitions specify clinical, laboratory and epidemiologic criteria and separate confirmed from probable and suspect. Quote or cite the definition you are working with, because a system's numbers cannot be interpreted without it.
-
Draw the flow from event to action
Who observes, who is legally required to report, to whom, in what timeframe, into which system, and who receives the analyzed output. Write it as a sequence with named actors, and the weak link will announce itself.
-
Choose two or three attributes and evidence them
Take timeliness, representativeness or data quality, and support each with something measurable: median days from specimen to report, the proportion of records missing a key field, or which settings report and which do not.
-
Separate changes in the disease from changes in the system
An increase in reported cases can mean more illness, more testing, a broadened definition, a new automated feed or one facility that started submitting. Say which explanations you considered and how you ruled any out.
-
Write the legal and confidentiality layer as part of the design
Name the authority for collection, the limits on disclosure, and the suppression rule applied to small counts. Then say what that rule costs you analytically, because protecting identity in small populations genuinely reduces what can be published.
-
Recommend a change to the system, not to the report
The strongest close names one field, one workflow or one feedback loop that would improve a specific attribute, identifies who could change it, and states what it would cost the reporters in effort.
A layout and word budget for a surveillance system evaluation
Our frame for a system description with an evaluative component, sized for roughly 1,100 to 1,400 words. It is our own outline rather than anything the university issues, and your week's scoring guide outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| System and purpose | What the system is, who operates it, and the specific decision its output is meant to support. | 140 to 170 |
| Case definition and population | The definition with its source, the confirmed and probable tiers, and who is under surveillance. | 170 to 210 |
| Information flow | Observer, reporter, legal duty, timeframe, receiving system and the route the analyzed output takes back. | 230 to 270 |
| Attribute assessment | Two or three named attributes from a published framework, each supported by something measurable. | 250 to 300 |
| Governance and confidentiality | Authority to collect, disclosure limits, suppression practice, and the analytic cost of that protection. | 170 to 200 |
| System recommendation | One change to a field, workflow or feedback loop, with an owner and an honest account of the burden it adds. | 140 to 170 |
Evidence craft for surveillance writing
Cite the case definition to the body that publishes it, with its year. Definitions are revised, and a revision changes the count without changing the disease. Papers that report a trend across a definition change without saying so have made an error the grader can see from the outside.
Distinguish counts, rates and reported rates in your sentences. A count is what arrived, a rate divides by a population, and a reported rate divides what arrived by a population while carrying every gap in reporting with it. Using the right term consistently is the clearest signal in the paper that you understand what surveillance data is.
Measure timeliness between two named events. From symptom onset to report, from specimen collection to laboratory result, from result to entry in the system, from entry to public posting. Each interval belongs to a different part of the machine, and naming which one you measured is the difference between an assessment and an impression.
Name what suppression hides. Where counts below a threshold are withheld to protect identity, small jurisdictions and small subgroups disappear from published tables, which is exactly where inequity is most likely to sit. Stating that limitation is analysis, not a disclaimer.
Be exact about who is legally obliged to report. Duties fall on clinicians, laboratories and facility operators under different provisions and different timeframes, and long-term care and congregate settings frequently sit under separate requirements from the general clinical duty. Getting that mapping right is the kind of institutional precision this course grades.
Five mistakes that cost points in this week's territory
- Describing a dataset instead of a system. A file of records is the output; the graded object is the arrangement of people, duties and software that produced it.
- Reading case counts as incidence. Reported cases are a function of testing, reporting behaviour and definition as much as of disease, and treating them as incidence is the central error of the territory.
- Nine attributes at one sentence each. A list of framework terms with no evidence attached demonstrates that you read the framework, not that you evaluated anything.
- Privacy handled with a sentence. Data governance is a component of the system, and one line saying data is kept confidential is not a description of it.
- Recommending a dashboard. A visualization does not improve sensitivity, timeliness or representativeness; those are properties of collection and flow, and the recommendation has to reach them.
Before you submit
- The system's purpose is stated before any judgment about it
- The case definition is cited to its issuing body with a year
- The information flow names every actor and the legal duty at each step
- Two or three attributes are assessed with measurable support
- Suppression and confidentiality practice appears with its analytic cost
- Every reference appears in the text and every in-text citation appears in the list
Evaluating a surveillance system for MPH-500?
Send the prompt and the scoring guide out of Canvas. A premium original draft comes back in 24 to 48 hours with the flow drawn actor by actor, attributes evidenced rather than listed, and the governance layer written in, and revisions run until the grade lands.