HLTH 3115 Week 4 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Use evidence for a stated analytical purpose and explain what the source changes about the case, audience, problem, or decision. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
1. Capture the live Week 4
Open the registered classroom and create one row for every visible activity. Record its exact name and type, complete action verbs and questions, rubric or scoring criteria, points and course weight, due date and time zone, required and permitted resources, length and format, discussion reply rules, dependencies, attempt limits, submission location, and instructor announcements. Save the rubric version beside the working file.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
2. State the Week's reasoning question
For Public and Global Health, the durable class question is: Which population, determinant, stakeholder, and measurable outcome define the problem? Translate the live activity into one sentence that names the decision or explanation, the required evidence, the audience, and the expected output. If that sentence cannot be written, return to the prompt instead of guessing from a prior Week or third-party example.
3. Build the work in proof order
Define the population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.
Make a rubric-to-evidence matrix before prose: one row per criterion, the evidence or reasoning needed, where it will appear, what the student must personally do, and the test that will prove completion. Draft the highest-risk row first, not necessarily the introduction. Protect time for replies, calculations, format conversion, approvals, and the final upload.
A worked pass from finding to recommendation
A finding becomes a recommendation only through stated criteria, and skipping them is what makes a strong analysis end weakly. Work the sequence in five sentences. Write the finding with its population and measure. Write the gap sentence that says what the current level is being compared against. Write at least two option sentences naming candidate actions at different levels, such as an individual-level response, an organizational one, and a policy or system one. Write the criteria sentence that names how the choice will be made: reach, feasibility, effect on equity, measurability, and resource burden. Then write the choice with its reason attached. A recommendation that arrives without the criteria sentence reads as preference no matter how much evidence preceded it.
Then check the level match. An action aimed at a different level than the determinant you identified cannot close the gap you described, and a rubric row that asks for justification usually catches the mismatch. If the determinant is a system-level access constraint, an education-only response is aimed at the wrong level, and saying so explicitly is stronger than quietly proposing it. For each option, name the stakeholder who must act: the person or body holding the decision, the budget, or the delivery. Naming that stakeholder converts a wish into a proposal, and it is often the sentence a stakeholder-analysis row is looking for.
Feasibility deserves its own sentence rather than an adjective. Write it as a statement about resources, authority, and time: what the action would require, who controls that requirement, and how long it would take before the outcome measure could move at all. A recommendation that would take several years to register any change is not disqualified by that fact, but a reader needs to be told, and saying it protects you from a reasonable objection that you would otherwise appear not to have considered. Where the live activity asks for a short-term and a longer-term option, the feasibility sentence is what distinguishes them, and it is usually more persuasive than the strength of the underlying evidence.
Reading the rubric row by row on the evidence criteria
Evidence rows are rarely satisfied by counting citations. The distinction they are usually testing is between cited and supported: cited means a source appears, supported means a reader can trace the specific claim to the specific source and see why that source can carry it. Read each evidence row for three requirements that tend to sit inside it without headings: how many and what type of sources, how recent they must be, and whether a source must be applied rather than mentioned.
Then read the row that governs the recommendation, which normally asks for justification and sometimes for a measurement or evaluation element as well. Map every one of those requirements to a labeled place in the draft, and keep a short list of the rows that cannot be satisfied by prose at all, such as those requiring a table, an appendix, or a citation format. How many sources and which kinds are not general facts; your classroom rubric decides.
4. Use evidence deliberately
Use current surveillance, policy, organizational, and peer-reviewed evidence at the same geographic and population level as the claim.
For every source, write a one-line use note before drafting. Distinguish direct evidence from interpretation and local observation. Quote sparingly, paraphrase from understanding, and cite the claim actually supported. If the activity requires current evidence, confirm publication dates and whether an older foundational source is still appropriate.
Matching evidence to the geographic and population level
The method on this site asks for evidence at the same geographic and population level as the claim, and this is the stage of the course where that rule does most of its work. Using a national figure to describe a county, or a study of one age band to support a statement about all adults, weakens an argument even when every source is respectable. When level-matched evidence genuinely does not exist, the professional move is not to substitute quietly. Say what does exist, state the direction and the uncertainty it supports, and label the step from the wider evidence to your population as an inference rather than a finding.
Keep the roles of your source families separate as you attach them to actions. Policy and organizational documents are not peer reviewed and should not be presented as if they were, but they are frequently the only authority for what a jurisdiction requires, funds, or reports, and they are the right citation for the feasibility and authority parts of a recommendation. Peer-reviewed literature carries relationship and effect claims. Evaluation reports carry claims about what happened when something was tried. When a recommendation rests on all three, cite all three, each for the part it can support.
5. Complete discussions and collaborative work
When the live Week contains a discussion, schedule the initial post by its own deadline and each reply by the response window. A useful reply does more than agree: compare evidence, apply the peer's idea to a different context, identify a boundary, or ask a focused question supported by the course material. The student writes and posts every contribution; a tutor may critique clarity and reasoning before submission.
6. Protect identity, practice, and research boundaries
Do not share protected health information, employer secrets, client identities, private peer content, assessment security material, or unauthorized research data. Clinical encounters, field hours, simulations, observations, interviews, group participation, proctored work, residencies, approvals, attestations, and original data collection must be completed and recorded by the student under the applicable Walden process.
7. Run the Week 4 quality gate
Test equity, feasibility, stakeholder effects, measurement validity, unintended consequences, and the boundary between association and causation.
Then perform a literal instruction audit: every prompt part answered, rubric row visible, calculation reproducible, citation matched, heading and format correct, accessibility checked, file opened successfully, and confidential material removed. Compare against the current rubric, not a saved rubric from another section or term.
Three evidence-to-action pitfalls and their fixes
The first is recommending something the cited evidence never evaluated. The sources establish that a problem exists, and the recommendation then arrives from elsewhere. The fix is to either find evidence for the action itself or present it explicitly as an untested option with a proposed way of evaluating it, which is an honest and scorable move.
The second is a reference list that grows while the analysis does not. Sources accumulate because they were found, not because they are used. The fix is a single rule applied before submission: any source that does not carry a sentence in the draft comes out of the list.
The third is a recommendation with no measure attached. It ends the paper without saying how anyone would know whether it worked. The fix is to attach four things to every recommendation: the outcome measure, the population it applies to, the time frame, and the data source that would report it. Whether an evaluation element is required at all is a classroom matter, and your classroom rubric decides.
8. Submit and close the loop
The student performs the final upload or entry, opens the submitted artifact, confirms the timestamp and file, and saves the receipt. When feedback arrives, record each criterion result, instructor comment, correction, and lesson for Week 5. Contact the instructor or official support channel promptly for a missing, late, or technically failed submission.
9. Defend the learning before moving on
Before closing Week 4, the student should explain the live task, central claim or decision, strongest evidence, method or calculation, important limitation, and next action aloud without reading the submitted artifact. For a discussion, explain what the peer exchanges changed. For clinical, field, research, group, or proctored work, identify which parts the student personally performed and how they were verified. Any point that cannot be explained becomes the first short practice item for the next study session. This oral defense tests understanding more honestly than another formatting pass and turns the finished Week into preparation for Week 5.
Source boundary
Walden's current catalog verifies this Course-Based class context, and the quarter calendar supports positional Weeks. The public catalog does not identify the student's Week 4 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.
Week 4 questions
What is assigned in HLTH 3115 Week 4?
Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.
How should I start HLTH 3115 Week 4?
Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.
Can a tutor perform the Week for the student?
No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.