HLTH 3105 Week 10 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Use accumulated feedback to repair recurring reasoning, evidence, format, or submission weaknesses before the last registered work. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
1. Capture the live Week 10
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.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
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.
Revision as diagnosis rather than polish
Week 10 revision starts from the feedback ledger, not from the top of the document. Pull the recurring criterion-level gaps out of the ledger and rank them by how often they have cost credit. Then revise in that order, weakest pattern first, and stop treating page one as the natural starting point. A draft revised from the beginning gets a heavily edited opening and an untouched close, which is exactly the shape a careful reader notices.
Work at the right altitude in the right order. Structural problems come first: a missing section, a claim that never appears, a rubric row with nowhere to live. Paragraph problems come second: a claim without support, a support without interpretation, an interpretation with no consequence. Sentence problems come last, because time spent on wording inside a paragraph about to be cut is time spent twice. Between passes, reread the live prompt rather than your memory of it, since a revision that improves the writing while drifting from the task is a net loss.
Reading the rubric row by row as a self-scoring exercise
Score your own draft against the live rubric before anyone else does, and do it in writing rather than in your head. Take each row, choose the performance level you honestly believe the current draft earns, and write the one sentence from your own text that justifies that choice. Rows where you cannot find the sentence become the revision list, in priority order, with no further analysis needed.
Be careful about the rows you consistently score generously. Everyone has a criterion they believe they satisfy naturally, and it is usually the one their feedback ledger disagrees with. Cross-check the self-score against the ledger and trust the ledger where the two differ. Your classroom rubric decides the actual result; this exercise only shows where the gap between your reading and the posted criteria is widest while there is still time to close 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.
Repairing citations and replacing weak sources
Revision is the last practical moment to replace a source that has been doing work it cannot support. Look for three signatures of a weak entry: a claim resting on a source whose population does not match, a claim resting on a summary rather than the study itself, and a claim resting on a document whose date raises a question you have not answered. Each is a targeted search rather than a general reading session.
Then run the mechanical checks that are easy to postpone and expensive to skip. Every in-text citation has a matching reference entry. Every reference entry is cited at least once. Every quotation is exact and marked. Every paraphrase is far enough from the original in structure as well as in wording. Every finding attributed to a source is one that source genuinely reports. These checks are unglamorous, and they protect the parts of a draft that reasoning alone cannot save.
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 10 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 10 pitfalls and the fix for each
The first pitfall is surface editing that feels like revision. Two hours of word choice produces a cleaner draft with the same missing analysis. The fix is to require every revision session to open with a structural question from the self-score list, and to forbid sentence-level work until that question is answered.
The second pitfall is revising what is easiest rather than what is weakest. The rows you already satisfy are pleasant to improve and cannot move the result much. The fix is the ordered list from the self-scoring exercise, worked from the top, with the easy improvements taken only if time remains.
The third pitfall is the patch that breaks coherence, where a paragraph inserted to satisfy one row contradicts something three pages earlier or simply repeats it. The fix is a full read-through after the structural passes, checking that the claim stated at the start is the claim defended in the middle and the claim concluded at the end, and that the terms list still holds throughout.
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 10, 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 10 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.
Week 10 questions
What is assigned in HLTH 3105 Week 10?
Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.
How should I start HLTH 3105 Week 10?
Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.
Can a tutor perform the Week for the student?
No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.