HLTH 3105 Week 3 planning manual

1. Capture the live Week 3

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 Interprofessional Teamwork in Healthcare, 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.

Making the mechanism visible instead of asserting it

Week 3 asks for reasoning a reader can follow, which in this course means writing the middle of the argument rather than only its ends. Weak drafts jump from a determinant straight to an outcome and leave the mechanism implicit. Force that middle open: name the determinant, name its immediate effect on how work is organized, name what that does to a specific role's ability to act, and only then name the outcome. Four short sentences in that order beat one confident sentence that skips two steps.

Run the same discipline on comparisons. When the live activity asks you to weigh options, declare the criteria before the options rather than after, and apply the same criteria to each. Effectiveness, feasibility, cost to the people who must carry the change out, and effect on the least-served part of the population are criteria the course method already puts in your hands. A comparison with unnamed criteria reads as preference; a comparison with declared criteria reads as analysis, and only the second can be scored as reasoning.

Reading the rubric row by row when the rows shift to analysis

The rows that separate a middling draft from a strong one are the ones whose verbs stopped being describe. Sort the live rubric into two piles: rows satisfied by accurate reporting, and rows that require a claim plus support plus interpretation. Draft the second pile first and give each of those rows its own visible passage, because an analysis row buried inside a description paragraph tends to be read as description.

For each analysis row, write in the margin the single sentence that would prove the row is met, then check whether that sentence actually appears in the draft. If you cannot write it, the reasoning is not finished. If you can write it but cannot find it, the reasoning is finished and hidden, which is a structural fix rather than a thinking one. Your classroom rubric decides which rows exist and how they are weighted, so run this sort against the version currently posted in your section.

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.

Using a source for its method, not only its number

Once the work is about visible reasoning, the design of a source becomes part of the argument. A surveillance report tells you how common something is and cannot tell you why. A policy document tells you what is required and cannot tell you whether the requirement is followed. An organizational report tells you how work is arranged in one setting and cannot be generalized without saying so. A study that compared two groups can support a claim about effect; a study that observed one group at one time cannot, however large it is.

Write that constraint into the sentence rather than hiding it. A sentence that says what kind of evidence is speaking gives a grader something to score and keeps you from overclaiming: report what the source is, what it found in whose population, and what it therefore can and cannot establish. Where two sources disagree, say so and explain the difference by design, date, or population rather than choosing the one that fits and quietly dropping the other. Handling a disagreement in the open is one of the clearest signals of analytical work a written draft can carry.

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

The first pitfall is description wearing an analysis label. A paragraph that defines a concept and then cites a source that also defines it has analyzed nothing, even under a heading that says analysis. The fix is the so-what test: after each paragraph, write one sentence beginning with which means, pointing at the population, the outcome, or a role's decision. If that sentence cannot be written, the paragraph is still description.

The second pitfall is the hidden middle step, where a determinant is joined to an outcome by an unstated assumption about how a system behaves. The fix is to read your own causal sentences backward and ask what has to be true between the two ends. Write that condition down; it is usually the most interesting sentence in the section and often the one the rubric was reaching for.

The third pitfall is a comparison whose columns are not parallel, so one option is judged on cost and another on acceptability. The fix is to fix the criteria as row labels first and to require every option to have a filled cell for every criterion, using an explicit note that the evidence you hold does not report it where that is the honest answer.

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 4. 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 3, 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 4.

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

Week 3 questions