HLTH 4115 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 Strategic Planning and Marketing 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.

Worked reasoning: connect earlier Weeks without repeating them

Integration is the point at which a course stops being a sequence of tasks and becomes a body of reasoning, and it has a technical meaning here. Take the population profile, the determinant ranking, and the evidence base built earlier and use them as inputs to the current problem rather than as content to restate. The test is simple: if a paragraph could have been written in an earlier Week without change, it is being recycled, not integrated.

Build a short integration map before drafting. In the left column list the concepts the course has covered. In the middle write what each contributes to the current activity: a constraint, a measurement definition, an alternative explanation, a stakeholder consideration. In the right write the sentence in the current draft where that contribution appears. Concepts with no landing sentence are decoration, and landing sentences with no concept behind them are usually where the reasoning thins.

Watch the joins. Integration lives in the connective sentences, not in the material being connected. After each borrowed idea, write one line saying what it changes about this problem: which option it removes, which assumption it undermines, which measure it makes possible. A draft that stacks concepts without those lines reads as coverage; a draft with them reads as analysis.

Reading the rubric row by row in Week 6

Look for the rows that reward synthesis, and be honest about how rarely they are satisfied by accident. They usually contain words such as integrate, connect, relate, or draw on, and they are scored on visible links rather than on the presence of both topics somewhere in the document.

For each synthesis row, decide where the link will be visible. A reader should not have to reconstruct your reasoning from two separate sections. Name the earlier concept in the sentence, apply it, and state the consequence, all in the same paragraph as the current problem.

Check the rows governing originality and independent work as well. Reusing your own previously submitted text is a policy question rather than a style question, and courses treat it differently. When an activity deliberately builds on earlier work, the live instructions say so and describe what may be carried forward. Where they are silent, write new prose and keep the method rather than the sentences. The registered classroom rubric and the current course policy decide this, not habit from another class.

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.

Reusing a source for a new claim

A source you have already cited is not automatically available for a new argument. Integration Weeks tempt students to reach for the familiar reference and let an old summary stand in for fresh reading. Go back to the source, find the passage that speaks to the current claim, and write a new use note in the ledger: same source, new job, new section, new limitation.

Then check the balance of the growing reference list. By this stage a strong list shows a mix of evidence families and a spread of dates, with the load-bearing claims supported by the family that can actually settle them. If several sections now depend on one document, find a second source that could confirm or complicate it. Convergence from independent evidence is worth more than volume from a single stream.

Integrate the reused source in a sentence that names the shift: what it established earlier, what it is being asked to establish now, and why that is a legitimate extension. That single move demonstrates exactly the reading a synthesis row is looking for.

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.

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.

Two Week 6 pitfalls and the fix for each

The first pitfall is the detached Week, in which the current activity is treated as a fresh topic with no relationship to the eleven Weeks around it. It produces a competent, forgettable draft that answers a narrower question than the one asked. The fix is the integration map, plus a rule that at least one paragraph must explicitly carry an earlier concept forward and say what it changes here.

The second is the opposite failure, where integration becomes a tour of everything covered so far. Long recap paragraphs consume the space the analytic rows need and delay the actual argument. The fix is a budget: one tight paragraph of setup, then a hard turn to the current problem, with each earlier concept appearing only at the moment it does work. If a concept has no work to do, leave it out and let the remaining ones carry more weight.

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