| Course | PHLT 8520 Advanced Epidemiological Methods |
|---|---|
| Week | Week 2 |
| Paper type | Design selection paper |
| Length | About 1,150 words, 7 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for PHLT 8520 Week 2
Ranking Four Observational Designs Against a Trial Nobody Would Run: Choosing a Design for Night Rosters in Early Pregnancy and the Risk of Preterm Birth
Student Name
Walden University
PHLT 8520: Advanced Epidemiological Methods
Instructor Name
Month Day, Year
Ranking Four Observational Designs Against a Trial Nobody Would Run: Choosing a Design for Night Rosters in Early Pregnancy and the Risk of Preterm Birth
The Trial Nobody Would Run
The course question asks if working nights during the first half of pregnancy makes an early delivery more likely for women employed by a health system. The cleanest answer would come from a trial: at confirmation of pregnancy, employees in rostered jobs would be randomly assigned either to schedules that include night shifts between gestational weeks 4 and 20 or to day-only schedules, and all would be followed to delivery. Randomization would balance job grade, income, prior obstetric history and health on average, and follow-up from assignment would keep early losses and job changes inside the comparison.
No ethics board would approve that trial, and no employer could deliver it. Writing it out still matters, because it turns a vague preference for "a good design" into a list of specific departures that each observational design makes. Hernán and Robins (2016) describe this practice as specifying the target trial, then asking how closely the available data can emulate each element: eligibility, treatment strategies, assignment, start of follow-up, outcome and analysis.
Elements of the Target Protocol
Table 1
Target Trial Protocol for Night Rosters in Early Pregnancy
| Element | Target trial | What emulation requires | |
|---|---|---|
| Eligibility | Employees in rostered jobs with a confirmed pregnancy by week 6, singleton, no prior preterm birth | Records of job, roster eligibility and confirmation date | |
| Strategies | Night shifts permitted in weeks 4-20 versus day-only rosters in weeks 4-20 | Day-by-day schedules for the window | |
| Assignment | Random | Measured confounders sufficient for exchangeability | |
| Start of follow-up | Confirmation of pregnancy | A recorded confirmation date | |
| Outcome | Live birth before 37 completed weeks | Gestational age from early ultrasound | |
| Analysis | Intention to treat and per protocol | Data on roster changes after week 4 | |
Note. Protocol written for this composite example.
Design One: Prospective Recruited Cohort
A prospective cohort would recruit employees at their first prenatal visit, record schedules weekly and follow them to delivery. It matches the protocol on start of follow-up and lets the team collect confounders it chooses. Its departures are cost and size. Preterm birth affects roughly one pregnancy in ten, and an employer cohort might enroll a few hundred pregnancies a year, so a modest effect would need many years of recruitment. Participation also depends on choice, and women who enroll may differ from those who decline in ways tied to both shift work and obstetric risk.
Design Two: Record-Linked Retrospective Cohort
A record-linked cohort would use data the health system already holds: timekeeping entries for every shift, human resources files for job title and grade, and the system's own obstetric records for confirmation date, ultrasound dating and delivery. It approximates the protocol closely on exposure measurement, because timekeeping records shifts as they happen, before anyone knows how a pregnancy will end. Danish researchers used the same kind of payroll data to study night work and preterm birth among more than 16,000 public employees (Specht et al., 2019). Its departures are confounders the records do not hold, such as household income beyond salary, and pregnancies that happen outside the system's own clinics.
Design Three: Case-Control With Recalled Schedules
A case-control design would sample employees who delivered preterm and a set of controls who delivered at term, then ask each about her schedule in early pregnancy. It is efficient for a rare outcome, and with careful control selection it can estimate the same ratio as a cohort (Wacholder et al., 1992). Here, though, the outcome is not rare enough to make efficiency decisive, and the design swaps recorded schedules for recalled ones. Mothers of preterm infants may search their memories for causes, so the recall error could differ by outcome, a departure the protocol cannot tolerate.
Design Four: Unit-Level Comparison
A fourth option would compare preterm rates across hospital units with heavy and light night staffing. It is cheap and uses published unit data. It departs from the protocol at the level of assignment itself: the unit, not the woman, carries the exposure, so a night-heavy unit could have higher preterm rates because of who works there, not because of what any one employee did. Individual schedules within units would be ignored entirely.
Ranking the Departures
The record-linked cohort ranks first, not because it is free of bias, but because each of its departures has a name, a likely direction and a way to be examined. Missing confounders can be probed with sensitivity analysis. Out-of-system deliveries can be counted from insurance claims and described. The prospective cohort ranks second; it would be cleaner on confounders but could not reach a useful size within a doctoral timeline. The case-control design ranks third, since differential recall would sit inside the exposure itself, and the unit comparison is set aside because no adjustment can recover individual exposure from unit averages.
Table 2
Departures From the Target Trial, by Design
| Design | Exposure record | Start of follow-up | Main departure | Can the departure be stated and bounded? | |
|---|---|---|---|---|
| Prospective recruited cohort | Weekly report | Matches | Size, volunteer selection | Partly | |
| Record-linked retrospective cohort | Timekeeping | Close, from confirmation | Unmeasured confounders, out-of-system care | Yes | |
| Case-control with recall | Memory after delivery | After outcome | Recall differing by outcome | Poorly | |
| Unit-level comparison | Unit staffing | Not defined | Group-level exposure | No | |
Note. Rankings are judgments for the composite setting.
What the Chosen Design Must Still Prove
Choosing the record-linked cohort sets the agenda for the rest of the course. Its comparison group must be defended, since night workers differ from day workers in ways the records only partly capture. Its entry rules must be examined, because a pregnancy has to be confirmed in the system's clinics to appear at all. Its exposure record must be validated against a second source, and its estimate must be stress-tested against a confounder it could not measure. The protocol table becomes the checklist for those weeks: every later decision will be described as a step toward, or away from, one of its rows.
Two questions stay open. The first is whether follow-up should begin at confirmation or at week 4, since some pregnancies are confirmed after night shifts have already occurred. The second is how to treat women who move between schedules during the window. The emulation framework handles both by stating the strategy precisely, so the Week 4 proposal will define exposure across the whole window from week 4 through week 20 and treat roster changes as data rather than noise.
Summary
Four observational designs were compared against a written target trial of night rosters in early pregnancy. A record-linked retrospective cohort, built from timekeeping, human resources and obstetric records, departs least from that protocol in ways that can be stated and bounded, and it is chosen as the design for the remaining weeks. The departures it keeps become the agenda for the course.
References
Hernán, M. A., & Robins, J. M. (2016). Using big data to emulate a target trial when a randomized trial is not available. American Journal of Epidemiology, 183(8), 758-764. https://doi.org/10.1093/aje/kwv254
Specht, I. O., Hammer, P. E. C., Flachs, E. M., Begtrup, L. M., Larsen, A. D., Hougaard, K. S., Hansen, J., Hansen, Å. M., Kolstad, H. A., Rugulies, R., Garde, A. H., & Bonde, J. P. (2019). Night work during pregnancy and preterm birth: A large register-based cohort study. PLOS ONE, 14(4), Article e0215748. https://doi.org/10.1371/journal.pone.0215748
Wacholder, S., McLaughlin, J. K., Silverman, D. T., & Mandel, J. S. (1992). Selection of controls in case-control studies: I. Principles. American Journal of Epidemiology, 135(9), 1019-1028. https://doi.org/10.1093/oxfordjournals.aje.a116396
Reading the PHLT 8520 Week 2 instructions
Design selection weeks typically ask students to compare several study designs for their own research question and to justify one. Prompts often list cohort, case-control, cross-sectional and ecological options and ask for strengths, weaknesses and a final choice. Strong submissions use a consistent yardstick instead of reciting a textbook hierarchy; the target trial framework is increasingly expected at the doctoral level. A paper of roughly four pages, one design-by-design table and methods citations is the usual shape. Instructors want feasibility discussed alongside validity, since a design that cannot reach adequate size within a dissertation timeline is not a real option. Many also ask what the chosen design must still demonstrate, which links this week to later assignments on confounding, selection and measurement.
How this PHLT 8520 Week 2 example is built
The paper begins with the impossible protocol, written in plain sentences, and cites the framework for emulating a target trial. Table 1 lists the six protocol elements and what emulation would require for each. Four sections then treat one design apiece, naming its departures from the protocol: volunteer selection and size for the recruited cohort, unmeasured confounders and out-of-system care for the record-linked cohort, outcome-shaped recall for the case-control design and group-level exposure for the unit comparison. Table 2 lines the designs up by exposure record, start of follow-up, main departure and whether that departure can be bounded. A ranking paragraph explains the order. A closing section lists what the chosen design must still prove and two decisions left open.
Reading the PHLT 8520 Week 2 rubric
Design papers are scored on whether the choice follows from a stated criterion. The sample's criterion, closeness to a written target trial with departures that can be named and bounded, is applied to every design, which earns the analytic marks. Accurate characterization of each design, including the point that a case-control study can estimate the same ratio as a cohort, earns content credit. Feasibility is weighed honestly: the prospective cohort is cleaner but too slow. Graders reward the closing agenda because it shows the design choice creates obligations rather than ending the analysis. A readable comparison table, consistent terminology and correctly cited sources make up the remaining criteria. Pages that crown a design without naming what it still gets wrong tend to stall at the proficient level.
PHLT 8520 Week 2 help: mistakes that cost marks
Weak design papers repeat the evidence pyramid and pick a cohort study because cohorts rank higher. Your instructor wants a choice tied to your question. Write the ideal randomized protocol first, even if it is unethical, and then measure each design against it. Name the specific departure each design makes, not a generic weakness such as "bias." Consider whether exposure is recorded before or after the outcome is known. Discuss feasibility with numbers: how many outcomes per year could you realistically capture? Rank the designs and explain the order. End with what your chosen design must still show. If you would like the same comparison built for your own exposure and outcome, a first custom version is free on request.
Get a PHLT 8520 Week 2 example written to your instructions
Include your Week 2 prompt, rubric and research question, plus any dataset your section can already reach. The selection writes the ideal protocol for that question, sets each candidate design against it, and commits to the one whose departures can be named. Expect it within 24-48 hours; a first request costs nothing.
More PHLT 8520 papers and PhD in Public Health samples
- PHLT 8520 Week 1: Error Taxonomy Brief
- PHLT 8520 Week 3: Confounding Brief
- PHLT 8520 Week 4: Design Proposal
- PHLT 8520 Week 5: Selection Analysis
- PHLT 8520 Week 6: Peer Challenge Reply
- PHLT 8520 Week 7: Measurement Error Brief
- PHLT 8520 Week 8: Control Strategy Comparison
- PHLT 8520 Week 9: Sensitivity Argument
- PHLT 8520 Week 10: Validation Check
- PHLT 8520 Week 11: Final Methods Paper
- PHLT 8500 Week 2: Model Build
- PHLT 8450 Week 2: Stakeholder Analysis Post
- PHLT 8331 Week 2: Variable Distribution Brief
- PHLT 8270 Week 2: Case Definition Discussion Post
PHLT 8520 Week 2 questions, answered
Where can I find a free PHLT 8520 Week 2 sample paper?
The complete Week 2 design selection paper is published above, ranking four designs against a target trial of night rosters in early pregnancy, with two tables and verified sources.
What is target trial emulation?
It means writing out the randomized trial you would run if you could, then designing an observational study to copy each element as closely as the data allow, so every departure from the ideal is explicit.
Why not use a case-control design for preterm birth?
A case-control design can work, but preterm birth is common enough that efficiency is not decisive, and recalling schedules after delivery risks recall that differs between mothers of preterm and term babies.
Why was a unit-level comparison rejected?
Comparing hospital units by night staffing assigns exposure to the unit, not the woman, so differences in who works on each unit could produce the result. No adjustment recovers individual exposure from unit averages.
How long should a PHLT 8520 design selection paper be?
Most run three to five pages. The sample uses about four pages of text with a protocol table and a design comparison table.