HLTH 3105 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 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.

The last verification pass on the reasoning itself

The final Week has two jobs, and the reasoning job comes before the administrative one. Read the finished work once as a stranger would and answer four questions in writing: what population is this about, what determinant is being claimed to matter, which roles would have to act, and what measure would show whether anything changed. If any answer requires you to explain something that is not on the page, put it on the page. A course built on population and systems reasoning closes well when a reader who was never in the class can follow the argument without your help.

Then verify the boundaries one final time. Confirm that causal language matches the evidence, that every recommendation names an actor and a measure, that limitations appear where they belong rather than only at the end, and that nothing confidential, identifying, or protected has reached the document. Confirm that everything the course required the student to perform was performed by the student and recorded through the applicable Walden process. That confirmation is not a formality; it is the last checkpoint at which an omission can still be addressed.

Reading the rubric row by row one last time

The final rubric read is a literal audit, done with the document open beside the live criteria and a finger on each row. For every row, point at the passage that satisfies it. Not the section that probably contains it, and not the paragraph you remember writing: the sentences themselves. Anything you cannot point at is either missing or invisible, and both are fixable while the submission window is open.

Do this pass before the formatting pass rather than after, because a structural fix will move the formatting anyway. Then check the requirements living outside the rubric rows: length, file type, headings, citation style, and whatever the current activity specifies about submission. Your classroom rubric decides the outcome, so the version you audit against must be the one posted for this activity in your section, in its current revision, read alongside any instructor announcement that modified it.

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.

Closing the source log and keeping what transfers

Before the course closes, spend a short session turning the source log into something that outlives it. Mark the entries that proved genuinely useful and note why: a reliable surveillance series, a policy document you will need again, a study whose method you now understand well enough to recognize elsewhere. Those notes are the part of the quarter's reading that carries into the next course.

Do the same for the method itself. Write a short page recording what you learned about finding evidence at the right level, how you now decide whether a source is scholarly for a health systems argument, and which of the four kinds of evidence you reach for first for which kind of question. Keep the lesson and the method rather than the submitted text; a later course will ask for new reasoning, new evidence work, and new authorship even when the concepts return, and what is worth carrying is the way you work, not the words you used.

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.

Three Week 11 pitfalls and the fix for each

The first pitfall is submitting without opening what was submitted. Uploads fail quietly, files convert badly, and the wrong version is easy to attach at the end of a long Week. The fix is unchanged from the first Week and matters more now: submit, reopen the submitted artifact from the classroom itself, confirm the file and the timestamp, and save the receipt.

The second pitfall is letting fatigue set the standard for the last item. The closing deliverable is often the heaviest and receives the least energy, which is why final sections so often thin out. The fix is to schedule the last item's checking block on a different day from its drafting block, so the audit is run by a rested reader.

The third pitfall is discarding the feedback that arrives after the course ends. Those final comments are the only ones written about your finished work, and they are the most useful ones you will receive. The fix is to add them to the ledger anyway, classified by criterion, so the next course opens with a diagnosis rather than a blank slate.

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