| Course | PUBH 8501 Scholar-Practitioner Inquiry I |
|---|---|
| Week | Week 2 |
| Paper type | Observation memo |
| Length | About 680 words, 4 pages |
| Format | Memo, APA 7 citations |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for PUBH 8501 Week 2
Memorandum
To: Course Instructor and Practice Mentor
From: Doctoral Student, Harbor Street Sexual Health Clinic
Date: Month Day, Year
Re: Four weeks of observation on retest reminders, with inferences listed separately
Methods Note
I observed my own retest reminder work at Harbor Street, the composite walk-in sexual health clinic where I work, for four weeks. Each client treated for chlamydia about three months earlier was due a reminder, since guidance recommends retesting at roughly that interval (Workowski et al., 2021). I logged each event as it happened, in the past tense, one event per entry, recording only the date, what occurred, the channel and the time of day. No names, birth dates, phone numbers or other identifiers were written down at any point.
The log has limits. It covers only reminders I sent and visits on days I worked. Reminders sent by the two other outreach staff, and any client who walked in on my days off, are not included. Field researchers advise writing what was seen before deciding what it meant (Emerson et al., 2011), and I have tried to hold to that.
The Log
Of the 61 reminders I sent over the four weeks, 14 led to a booked retest and 9 to a completed one. Eleven failed at the first step because a number or address no longer worked. One client was in the building and still left without a test because nothing in the chart flagged the order.
Table 1
Selected entries from the four-week log
| Day | Event | Channel | Time | |
|---|---|---|---|
| 1 | Reminder text sent to a client treated 13 weeks earlier | Text | 9:10 a.m. | |
| 1 | Text returned as undeliverable | Text | 9:11 a.m. | |
| 1 | Call placed to the same client; number not in service | Phone | 9:20 a.m. | |
| 2 | Reminder text sent to a client treated 12 weeks earlier | Text | 9:05 a.m. | |
| 3 | Client from day 2 replied asking whether the test was needed if symptoms were gone | Text | 7:48 p.m. | |
| 4 | Reply sent explaining retest purpose; no further response | Text | 9:02 a.m. | |
| 6 | Client arrived for an unrelated visit; retest order not flagged in the chart; client left untested | In person | 2:30 p.m. | |
| 8 | Reminder letter mailed to a client with no phone on file | 11:00 a.m. | | |
| 11 | Letter from day 8 returned, no forwarding address | 10:15 a.m. | | |
| 12 | Client booked a retest after one text | Text | 12:40 p.m. | |
| 15 | Voicemail left for a client; mailbox full on second attempt | Phone | 4:10 p.m. | |
| 19 | Client booked, then did not attend | Scheduling system | 3:00 p.m. | |
| 22 | Walk-in client asked for a retest unprompted | In person | 10:20 a.m. | |
| 26 | Twenty reminder texts sent in one batch; three replies within a day | Text | 9:00 a.m. | |
Entries are illustrative and drawn from a composite clinic.
Inferences, Kept Separate
While writing the log I noticed explanations forming. I list them here, each marked unconfirmed, so they can be tested rather than assumed.
The first inference is the staff belief I wrote about in the first discussion. The log neither supports nor contradicts it. The second is new to me and may matter more. Reviews of rescreening programs have found reminder systems promising (Guy et al., 2012), but a reminder cannot work if it never arrives.
Table 2
Inferences noticed during observation
| Inference | Status | |
|---|---|
| Clients who miss retests are mostly students who have left town | Unconfirmed; the log does not record student status | |
| Outdated contact details cause more misses than client reluctance | Unconfirmed; suggested by 11 failed contacts | |
| Clients think a retest is unnecessary once symptoms are gone | Unconfirmed; one client asked this | |
| The chart fails to prompt staff when a client is already present | Unconfirmed; one missed opportunity seen | |
| Batch texts work less well than single texts | Unconfirmed; too few replies to compare | |
Each inference names what the log can and cannot show about it.
Next Step
I will check whether contact details recorded at treatment differ from those on file three months later, before treating any of these inferences as findings.
References
Emerson, R. M., Fretz, R. I., & Shaw, L. L. (2011). Writing ethnographic fieldnotes (2nd ed.). University of Chicago Press.
Guy, R., Hocking, J., Low, N., Ali, H., Bauer, H. M., Walker, J., Klausner, J. D., Donovan, B., & Kaldor, J. M. (2012). Interventions to increase rescreening for repeat chlamydial infection. Sexually Transmitted Diseases, 39(2), 136-146. https://doi.org/10.1097/OLQ.0b013e31823ed4ec
Workowski, K. A., Bachmann, L. H., Chan, P. A., Johnston, C. M., Muzny, C. A., Park, I., Reno, H., Zenilman, J. M., & Bolan, G. A. (2021). Sexually transmitted infections treatment guidelines, 2021. MMWR Recommendations and Reports, 70(4), 1-187. https://doi.org/10.15585/mmwr.rr7004a1
Reading the PUBH 8501 Week 2 instructions
Observation assignments in this sequence ask students to watch a piece of their own practice for a set period and write down what happened. Prompts usually require a short methods statement, a log or set of fieldnotes and a reflection. Many instructors stress that events and interpretations must be kept apart, often asking students to put interpretations in a separate section. Identifying details are usually prohibited. Memos that mix explanation into the log, such as writing that a client "didn't care" rather than that a client did not reply, tend to lose credit because the week is meant to show how quickly interpretation slips into description.
How the PUBH 8501 Week 2 example is put together
The memo opens with a methods note covering who observed, the four-week window and what was not captured, such as reminders sent by other staff. A table of selected entries follows, recording the day, the event, the channel and the time in plain past tense. A short paragraph sums up the month: how many reminders led to a booking, how many failed because contact details no longer worked, and one client who left untested while in the building. A second table lists five inferences with their status. A closing paragraph names the next check, comparing contact details at treatment with those on file three months later.
PUBH 8501 Week 2 rubric: what earns full marks
Graders typically assess the clarity of the methods note, the discipline of the log, the separation of inference from description and the absence of identifiers. Entries written as single events in the past tense score higher than narrative summaries. Saying what the log missed is rewarded, because one observer's view is always partial. A separate inference section, with each item marked unconfirmed, demonstrates the core skill of the week. Scholarly support for observation methods strengthens the memo. A next step that tests an inference, rather than acting on it, shows the inquiry stance the course rewards. Totals drawn from the log, such as reminders sent and retests completed, give the reflection a factual footing. A log that would let another observer repeat the exercise in the same clinic tends to be marked as methodologically sound.
PUBH 8501 Week 2 help: mistakes that cost marks
Set up your log before you start observing, with columns for date, event, channel and time, so you are not tempted to write stories. Write each entry as soon as the event happens. Keep a separate page open for explanations that come to mind, and move them there whenever you catch one in the log. Strip identifiers as you go. At the end, count what you can count and say what you could not see. If your observation period is over and your notes have turned into a narrative, we can help you rebuild them into a log and an inference list in this format.
Get a PUBH 8501 Week 2 example written to your instructions
Describe a setting you can watch directly and the weeks available to you, plus the memo instructions for Week 2 and how they are graded. What returns is a dated event log with inferences parked on their own page. The first memo costs nothing and arrives inside 24 to 48 hours; this callback desk and its queue are fictional.
More PUBH 8501 papers and PhD in Public Health samples
- PUBH 8501 Week 1: Discussion Post
- PUBH 8501 Week 3: Source Audit
- PUBH 8501 Week 4: Distribution Brief
- PUBH 8501 Week 5: Peer Critique
- PUBH 8501 Week 6: Burden Estimate
- PUBH 8501 Week 7: Counter-Evidence Check
- PUBH 8501 Week 8: De-Identification Pass
- PUBH 8501 Week 9: Scope Test
- PUBH 8501 Week 10: Problem Statement
- PUBH 8501 Week 11: Source List
- PUBH 8410 Week 2: Systems Map
- PUBH 8211 Week 2: Question Memo
- PUBH 8132 Week 2: Segmentation Memo
- PUBH 8048 Week 2: Framework Comparison Post
PUBH 8501 Week 2 questions, answered
Where can I find a free PUBH 8501 Week 2 sample paper?
The whole Week 2 observation memo is reproduced above, logging a month of chlamydia retest reminders at a composite clinic.
Why keep inferences on a separate page?
So explanations formed during observation can be tested later rather than slipping into the record as facts.
What did the log find most often?
Reminders failing because phone numbers and addresses no longer worked.
What limits does the methods note admit?
The log covers only the author's reminders and working days, not other staff or days off.
What is the next step after the memo?
Comparing contact details recorded at treatment with those on file three months later.