HLTH 3115 Week 3 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Move beyond definitions by making mechanisms, comparisons, calculations, or decision criteria visible in the order the current rubric can score. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
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.
| 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 Public and Global Health, 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.
A worked pass at making the pathway visible
Description earns little once a rubric asks for analysis, and the difference between the two is a visible pathway. A pathway names the determinant, the mechanism, the point where the mechanism touches people, the outcome, and the measure that would detect the change. Written out on parallel material, instead of stating that a transport constraint affects health, the chain reads: limited service in a defined area lowers attendance at scheduled preventive visits; missed preventive visits delay detection; delayed detection appears in the population as a shift in the stage at which conditions are found; the measure is that stage distribution for the same population and period. Each link is a sentence a reader can challenge, and being challengeable is what makes it analysis rather than assertion.
The same discipline governs comparison. When the live activity asks you to weigh interventions, fix the criteria before describing the options: reach, expected effect, resource burden, what implementation would require, effect on equity, and how the result would be measured. Hold those criteria constant across every option so that the comparison produces the recommendation rather than the writer's preference. Keep association and causation separate in the wording as you go, because a difference observed between two groups is not by itself a mechanism, and a row that asks for critical analysis is often asking you to say which of the two you actually have.
One test decides whether a pathway is finished: read each link as if a well-informed colleague were about to interrupt. For every step, ask what that colleague would demand before accepting it, and either supply it or mark the link as an assumption in the text. Links that survive become the structure of the section, and links that do not survive become the limitations paragraph, which is a better outcome than leaving them buried where a reader will find them first. Doing this before drafting also tells you where the evidence search should go, because the weakest link in the chain is the one that most needs a source, and it is rarely the link that felt most interesting to write about.
Reading the rubric row by row where reasoning is scored
Analysis credit hides inside verbs, so sort the rows into three kinds. Report rows are satisfied by accurate content. Relate rows require an explicit connector sentence that says how one thing bears on another. Judge rows require a stated criterion and a decision made against it. Most drafts that feel complete but score partially have answered relate and judge rows with report content, which reads as effort without argument.
Mark each row in your outline with its kind, then check that a sentence of the matching kind actually exists in the draft, not merely a paragraph on the right topic. Where a row escalates from present to accurate to explained to evaluated, find the word that marks the top level and write the sentence that meets it directly. Nothing here overrides the live sheet: your classroom rubric decides which level language applies to this activity.
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.
Matching source design to the claim it supports
Different claims need different kinds of evidence, and a strong source cited for the wrong kind of claim is still a mismatch. A claim about how common something is needs surveillance or a representative survey. A claim that one thing changes another needs a design capable of supporting that, an intervention study or a carefully controlled analysis, not a snapshot that only shows two things appearing together. A claim about what works at scale needs implementation or evaluation evidence rather than a single trial. A claim about what is permitted or funded needs the policy or regulatory text itself. Before adding any source, name which of these four claims it is being asked to carry.
Then work it into the draft in three sentences rather than one. The claim sentence states what you are asserting. The evidence sentence names the source, its population, its design, and its finding. The interpretation sentence says what that finding means for the population you are writing about, including what it cannot settle. Three sentences per evidence point keeps quotation low, keeps reasoning visible where an analysis row can score it, and makes it obvious when a source is doing no work at all.
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 reasoning pitfalls that cost visible credit
The first is stacking several citations behind one general sentence. It looks well supported and demonstrates nothing, because no single source is tied to a specific claim. The fix is to split the sentence into the claim, evidence, and interpretation pattern and give each source the one claim it can actually carry.
The second is naming a determinant in the problem statement and then never returning to it. The determinant disappears into a general discussion and the reader is left holding a promise. The fix is to require that the named determinant reappears in the comparison criteria and in the outcome measure, so the argument closes the loop it opened.
The third is using causal verbs for associational evidence. Words such as causes, drives, and leads to commit you to more than a cross-sectional finding can support. The fix is to match the verb to the design: associated with, more common among, or followed by, and then say directly what evidence would be needed to establish the stronger claim. Naming that gap reads as command of the material rather than as hedging.
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
What is assigned in HLTH 3115 Week 3?
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 3115 Week 3?
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.