HLTH 3105 Week 9 planning manual

1. Capture the live Week 9

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.

Building the closing map before the work concentrates

Week 9 is a planning Week disguised as a working one. Open the registered classroom, list everything still outstanding in the course, then convert the list into a dependency chain rather than a schedule. Mark each item with what it needs from someone else: a peer response, an instructor answer, an approval, a group contribution, a technical step, or nothing at all. Items needing nothing can be done at any time and should therefore be done last, not first.

Then work backward from each item with a real dependency and find the latest moment its request could be sent while still leaving room for a reply and a revision. Those moments, not the due windows, are the real deadlines of the closing stretch. Write them into the same ledger you have kept all quarter. For any element requiring an institutional step outside the writing, note that the step belongs to the student and to the official process, and that a polished draft cannot substitute for an unfinished approval.

Reading the rubric row by row for the largest remaining deliverable

Read the rubric for the biggest outstanding item now, well before you would normally open it. Early reading changes what you notice: rows requiring information you do not yet have, rows requiring a section type you have not written this quarter, rows needing a source at a level your log does not cover. Each of those is a lead time problem, and lead time only exists if you find them early.

Turn the rows into an outline immediately, one heading per row group, with a one-line note under each heading saying what will fill it. An outline built from rows makes gaps visible while they are still cheap to close. Where a row's meaning is ambiguous, ask now rather than in the final days, because the answer may reshape the plan. Your classroom rubric decides the requirements, and the version attached to the live item is the one to build the outline from.

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.

Freezing the source set and checking it end to end

The closing stretch is the wrong time to be discovering literature. Set a point this Week after which the source set is closed except for a specific, named gap you already know you must fill. Then audit what you hold: every entry retrievable, every citation matched to a reference entry and every reference entry cited, every date confirmed, every policy document current, and every finding traced to the source that actually reports it.

Check coverage against the argument rather than against a count. Walk the four slots one more time and ask which of them is carrying claims on thin support. In a systems argument the outcome slot is the usual weak point, because measures are harder to source than descriptions. Fill that gap deliberately rather than adding whatever is easiest to find. A source set that is small, current, level-matched, and fully used will read as stronger than a long list assembled to look thorough.

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

The first pitfall is planning by due date rather than by dependency, which puts every step requiring another person at the end of the queue where there is no room for a reply. The fix is the dependency chain described above, with requests sent in the first days of the closing stretch and independent writing scheduled around whatever comes back.

The second pitfall is discovering a submission or format requirement late: a file type, a length constraint, a template, an approval, or a technical route that behaves differently from the one you have used all quarter. The fix is a dry run this Week, opening the actual submission location and confirming what it accepts, so the last hours go to content rather than to conversion.

The third pitfall is leaving discussion replies for the end, when the remaining work is heaviest. Replies are small, repeatable, and easy to underestimate, and they are also part of the graded record. The fix is to keep the reply routine running unchanged through the closing Weeks rather than treating it as slack.

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 10. 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 9, 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 10.

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

Week 9 questions