HLTH 6205 Week 11 planning manual

1. Capture the live Week 11

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 Assessing Health and Wellness Needs for Communities, 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.

Worked reasoning: closing with implementation and evaluation that hold together

A recommendation is incomplete until someone could act on it. Give the closing proposal five elements: the organization or role that owns it, the first concrete action, the resources the action assumes, the sequence and rough timeline in which effects would appear, and the evaluation plan that would detect whether it worked. Then anchor the evaluation to the baseline established when the population was defined, because an evaluation with no baseline can report activity but cannot report change.

Separate the two measurement layers explicitly. Process measures describe whether the work happened as designed, such as reach into the intended population, participation, or delivery fidelity. Outcome measures describe whether the population changed on the indicator you defined. Early evaluation almost always sees process before outcome, and saying so protects the plan from being judged against a timeline it never claimed. Finish with the falsification sentence: what result would count as evidence the approach did not work, and what would be done then. A closing argument that names its own failure conditions demonstrates the reasoning this course question asks for. What the final registered work actually requires is set by the classroom, and the live rubric decides the form.

Reading the rubric row by row for the final registered work

Closing rubrics often reach back across the whole arc, scoring the population definition and the evidence handling alongside the conclusions, so read every row rather than only the ones that look new. Rows that were never tested earlier in the term deserve the most attention, since there is no returned feedback to calibrate them. Where a row scores reflection on learning or professional application, note that it is still evidence-scored: it asks what changed in your reasoning and how you would apply it, not how the course felt.

Run a final literal audit against the live instructions and the current rubric together. Every prompt part answered, every row visible in a locatable place, every figure verified, every citation matched, headings and format correct, exhibits interpreted, accessibility checked, confidential material removed, and the file opened after upload. Compare against the rubric posted now rather than a saved copy from an earlier Week. Weights, criteria, and requirements for the final activity are determined by your registered classroom.

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.

The evidence record worth keeping after the course

Most of what makes the next course easier is procedural rather than topical. Preserve the ledger structure you built, with its columns for publishing body, data year, publication year, geography, population, usable finding, limitation, and supported claim, because that template transfers to any population problem. Preserve your search strategy as well: which families of evidence answered which kinds of question, which agencies published usable local data, and which searches wasted time. Preserve the level-matching rule that kept claims and sources at the same geography, since that discipline is the one most often lost under deadline pressure.

Do not preserve submitted prose for reuse. A later course asks a different question, and the method rather than the paragraph is what carries forward; new prompts require new reasoning, new evidence handling, and original authorship even when a familiar concept returns. Keep the criterion-level feedback ledger alongside the source ledger so the recurring weaknesses named this term become the first things you test next term. Retention, reuse, and originality expectations are set by Walden policy and by the registered classroom.

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 11 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.

Pitfall: an evaluation plan with no baseline

Plans that propose measuring an outcome after implementation without stating what the indicator read before it cannot demonstrate change, and the gap usually appears only in the closing section. Carry the baseline figure forward from the population work, state its data year and denominator, and write the evaluation against that specific number rather than against a general improvement.

Pitfall: a recommendation with no named owner

Passive closing sentences about what should be done leave no one accountable and no path to implementation, which is exactly what a feasibility criterion looks for. Name the organization, role, or partnership that would act, and state the authority or resources that make action possible. If no plausible owner exists, that is a finding about feasibility and belongs in the text.

Pitfall: closing the course without harvesting the method

When the final submission clears, the reasoning built over the term is easy to lose because nothing forces you to write it down. Spend a short session capturing the method: how you defined a population, chose a comparison, tested a pathway, compared options, and set an evaluation. Record the criterion-level lessons alongside it. That record, not the returned file, is what the next course will actually use.

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 11. 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 11, 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 11.

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 11 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 11 questions