HLTH 3115 Week 6 planning manual

1. Capture the live Week 6

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 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 joining earlier concepts to the current problem

Integration means using an earlier concept as a tool, not restating that you met it. Work it as a two-column list. On the left, write the three or four concepts the course has established so far, each in one line and in your own words. On the right, write the specific question each one lets you ask about the current problem. Determinants let you ask which upstream condition produces the pattern. System constraints let you ask which part of the delivery chain limits the response. Stakeholder reasoning lets you ask who must act and who carries the cost of acting. Measurement lets you ask what would count as change and who would see it. Then answer only the questions the live activity actually requires, because integration that answers unrequested questions reads as padding and crowds out the rows that are scored.

The systems view is worth drawing before it is written. Sketch the chain from the population, through the condition or exposure, to the point where people meet a service, to the service itself, to the constraints on that service, to the outcome measure. Mark where each stakeholder sits on that chain and where the chain breaks. Reusing sentences from your own earlier submissions is not integration, and the method on this site is explicit that a later prompt requires new reasoning, evidence, and authorship even when the underlying concept returns.

A concept-to-heading map keeps integration honest. Write the headings you intend to use, then write beside each the concept that will do the work in that section and the sentence where the concept will first appear. Any heading with no concept beside it is a section that will drift into description, and any concept with no heading is one you are planning to mention rather than use. Fix both before drafting. The map also shows repetition early: when the same concept appears beside three headings, either the argument has a genuine spine running through it, in which case say so explicitly in the transitions, or two of those sections are the same section written twice.

Reading the rubric row by row when criteria span the course

Later rubrics tend to carry rows written in course-level language: apply course concepts, synthesize across topics, connect to professional practice. Rows like these are scored on whether a named concept does visible work, not on whether the concept is mentioned somewhere. Give each such row a home in the outline and name the concept in the heading or in the topic sentence, so the connection is made by you rather than inferred by the reader.

Watch for rows that quietly require both breadth and depth, such as several concepts with at least one developed in detail. Satisfying only one half of that pairing loses the whole row, and it is a common way for a well-written response to score partially. How many concepts, and how deep, are not things a general guide can tell you; your classroom rubric decides.

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.

Layering foundational and current sources in one argument

An integrative argument usually needs two layers of evidence doing two different jobs. Framework sources establish the concepts, definitions, and measures the argument uses, and these can legitimately be older when the concept or measure they define is still the one in use. Situational sources establish the present state of the problem, and these must be current because they carry levels, trends, and policy conditions that change. Signal which layer you are using inside the sentence itself: framework sources take defining language, situational sources take reporting language.

Then keep the two layers in proportion to what the activity is asking for. A response that cites five framework sources and one current figure has described a theory and attached an example to it. A response with six current figures and no framework has listed numbers without a lens to read them through. Both lose the same integration row for opposite reasons. When a framework source and a current figure disagree about how something behaves, that disagreement is worth a paragraph rather than a silent choice, and it is often where the strongest analysis in an integrative piece sits.

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 6 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 integration pitfalls and how to undo them

The first is the recap paragraph, which retells earlier course content without using any of it. It consumes length that a scored row needed. Undo it by deleting the recap and replacing it with one sentence per concept that applies the concept to the current problem and says what it reveals.

The second is reusing your own previously submitted sentences because the concept has returned. It is the wrong kind of efficiency, and the method on this site is explicit that a later prompt requires new reasoning, evidence, and authorship. Undo it by drafting from your ledger of lessons and sources rather than from the folder of earlier drafts.

The third is introducing an unfamiliar framework late, without support and without applying it. It signals breadth and delivers confusion. Undo it by choosing: either support it with a source and use it consistently through the rest of the argument, or drop it and develop a framework you have already established.

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 7. 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 6, 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 7.

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

Week 6 questions