| Course | HLTH 8475 Advanced Program Implementation and Evaluation |
|---|---|
| Week | Week 2 |
| Paper type | Discussion post |
| Length | About 630 words, 4 pages |
| Format | Discussion post, APA 7 citations |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for HLTH 8475 Week 2
Week 2 Discussion: When Is an Adapted Program Still the Program?
One Pharmacy Swapped In-Person PrEP Follow-Up Visits for Phone Calls: Still the Same Program Only if the Call Keeps the HIV Test Before Each Refill, Which Is What the Visit Was For
In our composite rural pharmacy PrEP program, clients are supposed to return to the pharmacy every three months for a follow-up visit. At the visit, the pharmacist reviews side effects and adherence, screens for symptoms of acute HIV infection, orders an HIV test and tests for other sexually transmitted infections, checks kidney function at the intervals the protocol sets and refills the prescription only after the HIV test is negative. The Seattle pharmacy clinic that pioneered this model managed follow-up through its own collaborative agreement and on-site care (Tung et al., 2018). One of our four pharmacies, in the smallest town, has replaced the in-person visit with a phone call. The pharmacist calls the client, reviews adherence and side effects and asks about symptoms, then sends a lab order to the regional hospital's outpatient lab, where the client gets blood drawn. The refill is sent once the result arrives.
My position is that this change breaks the program only if it removes what the visit was for. The visit's core function is to make sure that every refill follows a negative HIV test, because starting or continuing PrEP in someone with undiagnosed HIV can lead to drug resistance. Its secondary functions are catching side effects, supporting adherence and finding other infections. A phone call can do most of the secondary work. Whether it preserves the core function depends on one condition: does the pharmacy hold the refill until the lab result is in hand?
The FRAME poses a short series of questions about any modification: what changed, at which level of the program, whether it was planned in advance or made in reaction to events, who decided, and whether it preserved fidelity to the program's core elements (Wiltsey Stirman et al., 2019). Applied here, the content changed in format, from face to face to phone; the change was made by one pharmacist at one site; it was reactive, prompted by clients who said they could not take time off work to visit during pharmacy hours; and fidelity to core elements is preserved if the refill rule holds.
I asked the district's program coordinator how the pharmacy handles refills. The answer was mixed. Most refills waited for results, but in a few cases, when the hospital lab was slow, the pharmacist sent a refill so the client would not run out. That is the version of the adaptation that breaks the program. Pressman and Wildavsky (1973) would have expected this: the program changed at the point where one more link, a slow lab, entered the chain. A phone call is a defensible change in delivery; a refill without a current negative test is a change in the program's core.
The evaluation should therefore record this site separately, count how many refills had a negative result logged inside the allowed window and treat the phone format as a planned variation to compare, not as noise.
Question for the board: in your program, which component carries the core function, and could it survive a change in delivery?
Reply to Owen
Owen, you argued that any change to a tested protocol makes the program a different program. I see why, but that standard would also rule out the phone call, which may reach clients who would otherwise drop out. Would you accept the change if the refill rule were enforced?
Reply to Grace
Grace, you suggested home HIV test kits as a further adaptation. That might help, but the protocol would need to say which test types count before a refill, since some home tests detect infection later than lab tests.
References
Pressman, J. L., & Wildavsky, A. (1973). Implementation: How great expectations in Washington are dashed in Oakland. University of California Press.
Tung, E. L., Thomas, A., Eichner, A., & Shalit, P. (2018). Implementation of a community pharmacy-based pre-exposure prophylaxis service: A novel model for pre-exposure prophylaxis care. Sexual Health, 15(6), 556-561. https://doi.org/10.1071/SH18084
Wiltsey Stirman, S., Baumann, A. A., & Miller, C. J. (2019). The FRAME: An expanded framework for reporting adaptations and modifications to evidence-based interventions. Implementation Science, 14, Article 58. https://doi.org/10.1186/s13012-019-0898-y
HLTH 8475 Week 2 instructions, in plain terms
The Week 2 thread asks students to judge whether a change made at one site still counts as the program being evaluated. Faculty expect the post to identify the component's core function, test the adaptation against it and use a framework for describing modifications. The post should take a position that depends on a condition rather than a blanket yes or no. Recommendations for how the evaluation should treat the adapted site are valued. Sources should support both the clinical reasoning and the framework, and two replies are expected, each narrowing or extending a classmate's view of adaptation. Faculty also like a post that checks the site's actual records rather than its written protocol, since the two can differ.
How the HLTH 8475 Week 2 example is put together
The opening describes what a follow-up visit contains and how the small-town pharmacy changed it, with a sentence citing the Seattle clinic in Tung and colleagues. The second paragraph names the visit's core function, a negative HIV test before every refill, and its secondary functions. The third applies Wiltsey Stirman and colleagues' FRAME to the change: format, level, reactive origin and fidelity to core elements. The fourth reports that some refills went out during lab delays and, citing Pressman and Wildavsky, calls that the change that breaks the program. The fifth recommends recording the site separately and tracking refills against results. The reply to Owen narrows the disagreement to the core function. The reply to Grace raises which home test types would count.
Reading the HLTH 8475 Week 2 rubric
Posts this week are graded on whether they distinguish a change in delivery from a change in a program's core. A post that calls every modification a different program, or treats every modification as acceptable, tends to earn middle marks. The rubric rewards naming a component's function precisely, testing the adaptation against it and using a modification framework accurately. Faculty value posts that check what actually happened at the site rather than assuming the protocol was followed. A recommendation for how the evaluation should record the adapted site shows the author is thinking ahead to later assignments. Replies earn credit for sharpening a classmate's standard or adding a practical detail.
Common HLTH 8475 Week 2 mistakes, and how to avoid them
Discussions of adaptation often stop at whether a change is good or bad. The more useful question is what the original component was for and whether the change keeps that function. To write a stronger post, list everything the original component does and decide which part is essential. Ask whether the adapted version still does it, and check the records rather than the plan. Use a framework to describe the change. Say how the evaluation should treat the site. In replies, look for the function a classmate's argument overlooks. Our writers can model a post on an adaptation from your own program.
Get a HLTH 8475 Week 2 example written to your instructions
Paste the thread prompt, the Week 2 rubric and any classmate posts already up, and the replies are aimed at those arguments. If your section supplies its own program or site change, the post is built on that change. Turnaround runs 24-48h and a first request costs nothing; the rural clinic stays fictional unless you name a published case.
More HLTH 8475 papers and PhD in Public Health samples
- HLTH 8475 Week 1: Clearances Framing Post
- HLTH 8475 Week 3: Implementation Logic Model
- HLTH 8475 Week 4: Staged Implementation Plan
- HLTH 8475 Week 5: Pre-Set Measurement Plan
- HLTH 8475 Week 6: Reach Measure Peer Critique
- HLTH 8475 Week 7: Six-Month Process Evaluation
- HLTH 8475 Week 8: Rival Explanations Post
- HLTH 8475 Week 9: Site-Level Outcome Analysis
- HLTH 8475 Week 10: Program Failure Counterargument
- HLTH 8475 Week 11: Utilization-Focused Evaluation Report
- HLTH 8402 Week 2: Training Versus Practice Post
- HLTH 8392 Week 2: Merger Talk Rhetorical Analysis
- HLTH 8317 Week 2: Restricted Award Fungibility Post
- HLTH 8247 Week 2: No-Show Attribution Analysis
HLTH 8475 Week 2 questions, answered
Why cite a modification framework in a discussion post?
Because this course treats a change at a site as data the evaluation will need later. Naming a reporting method shows the author knows the change has to be written down when it happens, with its reason and its author, not reconstructed from memory at the end. A sentence is enough on the board; the implementation plan develops it.
Can a program from my own agency replace the composite one?
Yes, if what you describe is already public: a published program manual, a report, a funder summary. Internal staffing notes and anything about named colleagues stay out. The sample keeps its rural clinic invented, which lets it describe the adaptation in the detail the argument needs without pointing at anyone's workplace.
Where can I find a free HLTH 8475 Week 2 sample paper?
This page shows the full Week 2 discussion post, testing whether phone follow-up at one pharmacy keeps a PrEP program's core function, with two replies and three references.
When does the phone adaptation break the program?
When a refill is sent before a current negative HIV test is in hand, because that removes the follow-up visit's core function of preventing PrEP use in someone with undiagnosed HIV.
What is the FRAME?
Wiltsey Stirman and colleagues' tool for recording changes to an evidence-based program: what was modified, by whom, when and why, and whether the parts that make it work were kept.