Good Health Hospital: the nosocomial infection report
A five to six page evaluation report on an E. coli outbreak at a regional hospital: itemising nosocomial infections by person, time, place, ethnicity and gender, proposing questions for the health department, and building a treatment contingency plan.
Editorial process
Last reviewed · August 7, 2026
The scenario is less settled than it sounds
Read the scenario for what it actually establishes, because it is written to look more settled than it is. It reports six cases, then supplies a table listing four; it says the outbreak *was in fact* caused by spoiled cafeteria food while also saying the litigation question is whether one patient was already symptomatic before admission; and it cites the recommendation to change vendors on the grounds that the present suppliers cannot verify sanitation, which is a procurement failure rather than a demonstrated source. Those are three different epistemic states — a count, a conclusion, and an unresolved question — presented in one paragraph. Noticing the gap between them is the first analytic move, and it is what an evaluation report is for. Opening the report by stating which of the three you are treating as established, and which you are treating as open, also tells the reader what kind of document they are about to read.
The parameters are named for you and they are the standard epidemiological descriptors: *person, time, place, ethnicity, and gender*. Categorising the data into those is not a formatting exercise. Person and time together give you the epidemic curve, which is what distinguishes a common-source outbreak from person-to-person spread; place localises exposure and, in a hospital, separates ward acquisition from community acquisition; and the demographic parameters matter mainly for whether the cases share anything beyond being in the building. With four ages and two sexes and nothing else, the honest finding is that the supplied data cannot discriminate between hypotheses — which is a result, and a defensible one to report. Saying what each parameter would show if the data supported it is worth doing even where it does not, since the report is assessing a compilation and not only reporting one.
The six questions you are asked to propose for the health department are the part where the report either shows method or does not. Good questions here are ones whose answers would change the conclusion: when did each patient's symptoms begin relative to admission, which is the litigation question stated as an epidemiological one; what did the four cases eat and where; were any staff affected; is there a shared ward, shift or procedure; was the organism typed and did the isolates match; and are there comparable cases in other Tampa Bay facilities. Each of those is answerable and each discriminates. A question that cannot change what you would conclude is decoration. A finding that the available records cannot settle the question is also the finding that most directly supports the request for a health department investigation.
Onset relative to admission is the hinge of the whole scenario and deserves its own section. A hospital-acquired infection is conventionally defined by onset after a defined interval from admission, and that interval is what separates an infection the hospital is responsible for from one the patient brought with them. The litigation issue the administrator raised is exactly this question, and the incubation period of the organism is what answers it — which is why the report cannot resolve liability without dates. Say so plainly. An evaluation report that adopts the scenario's own conclusion without noticing that the decisive datum is missing has evaluated nothing. Setting out the definitional interval explicitly also gives the six questions their most important member, which is simply when each patient's symptoms began.
The second deliverable is a contingency plan built from state and federal surveillance data, and it should be structured rather than listed. A workable plan states what triggers activation, who leads, what is done in the first twenty-four hours, how cases are found and defined, what control measures are applied and in what order, what is reported and to whom, and how the plan is stood down. National surveillance data earns its place by telling you which infections are actually common in facilities like yours, so the plan is proportionate to the real distribution rather than to the outbreak that happens to be in front of you. Three academic sources minimum, and five to six pages. Naming who owns each step is what turns a plan from a description of good practice into something an administrator could actually put into effect on the day.
Element of the report | The version that under-performs | What an evaluation requires |
|---|---|---|
The scenario's conclusion | Repeated as established | Separated into count, conclusion and open question |
Case count | Six, as stated | Six asserted, four tabulated — a discrepancy worth noting |
Person and time | Ages and dates listed | An epidemic curve distinguishing common source from spread |
Place | The hospital | Ward, unit and exposure location, separating acquisition from admission |
The six questions | Requests for background | Questions whose answers would change the conclusion |
Onset relative to admission | Not addressed | The definition that decides the litigation question |
Contingency plan | A list of good practices | Trigger, roles, case definition, control, reporting, stand-down |
Likely learning objectives
Inferred from the brief — check these against your own rubric.
- 01Distinguish what a scenario establishes from what it asserts.
- 02Use standard epidemiological descriptors to test hypotheses rather than to organise data.
- 03Frame investigative questions whose answers would change a conclusion.
- 04Build a contingency plan with triggers, roles and a stand-down.
Read the full question
Review every instruction before using the planning guidance that follows.
What the evaluation report must contain
- 01A 5 to 6 page evaluation report.
- 02An analysis of the hospital's records itemising nosocomial infections over the past year.
- 03The data categorised by person, time, place, ethnicity and gender.
- 04At least six proposed questions for the health department.
- 05An evaluation of state and federal data on common nosocomial diseases.
- 06A treatment contingency plan for hospital infections.
From the data's limits to an activated plan
Separate what is known from what is claimed
The count, the asserted cause, the open litigation question, and the procurement finding.
The five parameters as tests
Person and time for the curve, place for exposure, demographics for shared characteristics.
State the limits of the data
What four rows of age and sex can and cannot discriminate between.
Six questions that would change the answer
Onset timing, food exposures, staff cases, shared ward or procedure, isolate typing, regional comparison.
Onset relative to admission
The definitional interval, the organism's incubation period, and what that means for liability.
A contingency plan with structure
Trigger, roles, first day actions, case finding, control measures, reporting and stand-down.
Two agencies, and what their data can support
Recommended databases
- State health department surveillance reports
- Federal healthcare-associated infection reporting
- PubMed and PMC
- Health statistics tutorials and data locators
Search sequence
- 1.Find the national distribution of healthcare-associated infections before writing the plan, because a contingency plan should be proportionate to what actually occurs rather than to the organism in the scenario.
- 2.Look up how a healthcare-associated infection is defined by time from admission, since that definition is what the litigation question turns on.
- 3.Search the surveillance literature for what a functioning programme contains, so the plan resembles an established structure rather than an invented one.
- 4.Check your own state's reporting requirements, as the plan has to say what is reported to whom and that varies.
Programme infrastructure and surveillance practice
These are authoritative starting points, not a ready-made bibliography. A qualified reviewer must confirm that each source fits the assignment and supports the claim beside which it is cited.
Nothing here is cleared for citation until you have read it.
- 01
Necessary Infrastructure of Infection Prevention and Healthcare Epidemiology Programs: A Review
Infection Control and Hospital Epidemiology, via PubMed · 2016
What an infection prevention programme has to contain — surveillance, performance improvement, outbreak response, education, and reporting to the national network. This is the structure your contingency plan should follow, and citing it makes the plan an implementation of an established model rather than an invention.
- 02
The current scope of healthcare-associated infection surveillance activities in hospitalized immunocompromised patients: a systematic review
BMJ Open, via PubMed · 2019
How surveillance definitions and case-finding actually vary in practice. Useful for the parameters section, because it shows that what counts as a case is a decision rather than a given — which is directly relevant to a scenario reporting six cases and tabulating four.
- 03
Impact of electronic healthcare-associated infection surveillance software on infection prevention resources: a systematic review of the literature
American Journal of Infection Control, via PubMed · 2017
Evidence on automated case finding and what it does to detection and to staff time. Relevant to the contingency plan's case-finding step, where the practical question is how an outbreak would be noticed at all rather than what to do once it has been.
- 04
Finding and Using Health Statistics
National Information Center on Health Services Research, U.S. National Library of Medicine · 2024
A guide to locating and interpreting federal and state health statistics, including what each source can and cannot support. Use it for the data-gathering half of the assignment, where the task is to obtain figures from two agencies and then judge whether they answer the question you are asking.
Before the evaluation report is submitted
Common mistakes
- Accepting the scenario's stated conclusion about the cafeteria without examining it.
- Missing that six cases are asserted while four are tabulated.
- Treating the five parameters as headings rather than as tests.
- Omitting symptom onset relative to admission, which decides the central question.
- Proposing questions that gather background rather than discriminate between hypotheses.
- Writing a contingency plan as a list of good practices with no trigger or owner.
- Using national surveillance data as decoration rather than to set priorities.
- Confusing a procurement failure with a demonstrated source of infection.
Submission checklist
- The discrepancy between six cases and four records is noted.
- An epidemic curve or its equivalent is described from person and time.
- Place distinguishes ward acquisition from admission with infection.
- The limits of the supplied demographic data are stated.
- Onset relative to admission is identified as the decisive datum.
- Six or more questions appear, each capable of changing the conclusion.
- The contingency plan has a trigger, an owner, a case definition and a stand-down.
- Three or more academic sources are cited; the paper is 5 to 6 pages.
Use this guide to plan and review your own work. Follow your institution's rules and read our academic-integrity policy.

Written by
Aaron Bishop
MA, Education
assignment interpretation and research-methods coaching across disciplines
Aaron leads the EssayCrackers editorial desk. He works on how assignment briefs are read — what a rubric is actually asking for, and where students most often answer a different question than the one set.

Reviewed by
Dr. Nathan Cole
PhD, Rhetoric & Composition
Argumentation and thesis development
Nathan teaches first-year composition and directs a university writing center. He reviews EssayCrackers guides for argumentative soundness and citation accuracy.