HLTH 6051 Week 4 planning manual

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.

2. State the Week's reasoning question

For Diversity, Human Rights, and Social Justice, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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.

Matching the level of the evidence to the level of the action

Week 4 turns analysis into a recommendation, and the most common failure is a mismatch of levels. Decide first where the proposed action sits: with an individual, with a program, with an organization, or with policy. Then check that the evidence in your hands was gathered at that level. A study of individual behavior change does not by itself justify a policy claim, and a policy evaluation does not by itself tell a health educator what to do in one session.

Write the recommendation as a sentence with four parts: who acts, what they do, for which population or setting, and what outcome the evidence predicts. If a part is missing, the recommendation is not yet scorable. Then add the sentence that names what would have to be true for the action to work, because a recommendation with stated conditions is stronger than one that pretends to be universal. How much of this the activity requires is decided by your classroom rubric.

3. Build the work in proof order

Define the required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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.

Reading the rubric row by row when a recommendation is scored

Recommendation rows are usually compound requirements wearing the costume of a single line. Break the row apart and check the pieces separately: is the action specific, is it supported, is it feasible in the stated context, does it align with the analysis earlier in the paper, and does it name who is responsible.

Many rows also require the justification to be tied to course material rather than to general reasoning, and that tie has to be visible in a sentence, not implied by the reference list. Mark which rows govern the analysis and which govern the recommendation, then verify that the two halves of the draft agree with each other; a recommendation that solves a different problem than the one you analyzed loses on both rows at once. Point values, row wording, and whether a recommendation criterion exists at all are decided by your classroom rubric.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to 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.

Sources that can carry an action claim

For an action claim, three families of support do the heaviest work. Evaluation studies and trials report what happened when something similar was tried, and the comparison group is the part to read closely. Implementation and program reports from agencies and established organizations describe what the work required in practice, which is where feasibility lives. Guidelines, position statements, and legal or regulatory texts establish what is permitted, expected, or mandated, which decides whether the action is even available to the actor you named.

Place these deliberately: the evaluation source next to the effect claim, the implementation source next to the feasibility sentence, and the guideline next to the authority sentence. A recommendation paragraph that cites only descriptive research about the problem has no support at the point where support is needed. Assigned readings remain mandatory wherever the live activity requires them.

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.

Discussion work when peers propose competing actions

Week 4 boards fill with recommendations, which makes comparison both easy and worthwhile. Take a peer's proposed action and test it against the four parts: actor, action, population, expected outcome. Supplying a missing part is a genuine contribution, and so is naming a constraint the peer has not addressed, such as who funds the action, who holds authority to approve it, or what the population would have to accept for it to work.

Where two classmates propose different actions for the same problem, name the criterion that would decide between them instead of announcing a preference. Keep examples at the level of programs, populations, and published cases, and never introduce identifying detail from a workplace or community you serve. Reply requirements, deadlines, and the number of peers you must engage are set by the live discussion instructions for this Week.

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

Check task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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 Week 4 pitfalls and the fix for each

Pitfall one: a recommendation with no owner, written in the passive voice so that nobody in particular is being asked to do anything. The fix: rewrite every recommendation sentence with a named actor as the grammatical subject, then check that the actor plausibly holds the authority to act.

Pitfall two: borrowing evidence from a different population or setting without saying so, which quietly overstates what the source supports. The fix: name the source population and setting in the sentence, then add one sentence on why the finding does or does not carry across.

Pitfall three: an action section that reads as a list of general good practices rather than an answer to your own analysis. The fix: for each proposed action, point back to the specific step in your pathway that it interrupts, and delete anything that cannot be traced there.

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