HLTH 3105 Week 2 planning manual

1. Capture the live Week 2

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.

Turning the reasoning method into a weekly cadence

By Week 2 the four-part class question should stop being a discovery exercise and start being a routine. Build the week as four working blocks rather than one long session: a reading block that ends with notes tied to the population and the determinant, a research block that ends with a source log entry, a drafting block that ends with one claim per paragraph, and a checking block that ends with a rubric pass. Blocks that end with a product are finished; blocks that end when you get tired are not.

The cadence needs a content test as well as a time test. Every working session in a population and systems course should move at least one of the four slots forward: sharpen the population, name a determinant more precisely, add a stakeholder role along with what that role actually controls, or make the outcome measurable. Write one line at the end of each session recording which slot moved. Two sessions in a row that move nothing means the problem statement, not the schedule, is the bottleneck.

Reading the rubric row by row before the cadence sets

The second Week is the right time to convert the rubric into a permanent worksheet you will reuse all quarter. Copy each row onto its own line, then add four columns of your own: the action the row demands, the evidence or reasoning that action needs, the section of the draft where it will live, and the check that proves it is done. Build this once and it carries forward, with the only maintenance being a version check each Week.

Pay attention to how the rows relate to each other. Rows are not independent: an analysis row usually depends on a description row being accurate first, and a recommendation row usually depends on an evidence row being level-matched. Sequencing rows by dependency tells you what to draft first. Where a row rewards stakeholder reasoning, plan a section that names roles and what each role can decide rather than a paragraph about cooperation in general. Your classroom rubric decides the wording and the weights, so read the live version each Week instead of trusting the copy you saved.

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.

Setting up a source log you can keep all quarter

A cadence needs a source log, not a folder. Give each source a single row with seven fields: full citation, date, issuing authority or study design, population and setting, the one usable finding, the limitation you would have to state, and the exact claim it supports. Filling that last field is the discipline that matters, because a source with an empty claim field is not ready to appear in a draft.

Scholarly in this subject means traceable to a method or a mandate. Surveillance summaries carry weight because someone counted. Policy documents carry weight because someone is bound by them. Organizational and professional reports carry weight because they describe how work is genuinely arranged. Peer-reviewed studies carry weight because a method was declared and reviewed. Opinion pieces, vendor material, and course-note aggregators carry none of that, however confident they sound.

Work a source into the draft the same way every time so the move becomes automatic: state your claim, deliver the finding with its population attached, then say what the finding does to the claim. That third sentence is what turns a citation into evidence, and it is the sentence most early drafts skip.

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

The first pitfall is a cadence built around due dates instead of dependencies. Work scheduled backward from a deadline collapses the moment one step waits on someone else, and in a course about interprofessional work the waiting steps are the ones that count. The fix is to list every step that depends on another person or an approval, start those first regardless of when they are due, and let independent writing fill the gaps.

The second pitfall is posting every discussion contribution in one sitting at the end of the window. A reply written in the same hour as the initial post cannot respond to anything, so it defaults to agreement and adds no reasoning. The fix is to separate the two by at least a day and to enter each reply with a specific job: compare two pieces of evidence, apply a peer's point to a different population, name a boundary condition, or ask a question the course material can actually answer.

The third pitfall is collecting sources faster than you read them. A log with twenty entries and four claim fields filled is a stalled project wearing the costume of progress. The fix is a cap: no new source until every existing row has a usable finding and a limitation written in your own words.

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

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

Week 2 questions