NURS 6912 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 Symptom Management for the Hospice and Palliative Care Clinician, the durable class question is: What outcome is being chosen, for whom, under which constraints and trade-offs? 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.

Worked reasoning: integrating without recycling

Integration means earlier material shows up as working equipment inside a new problem, not as a recap. The class question is the joint that makes this possible: earlier Weeks supplied criteria, evidence habits, and constraint vocabulary, and the current Week supplies a fresh outcome to choose. Work it in three passes. In the first, list what the earlier Weeks actually produced, stated as capabilities rather than as titles: a way to name an option set, a way to weigh benefit against burden, a way to say how an outcome would be measured. In the second, ask which of those the current activity needs and which would only pad it, since integration that drags in everything is as weak as integration that drags in nothing.

In the third pass, write the connecting sentences, the ones that say why the earlier idea belongs here and what it changes about this analysis. Those sentences are usually where an integration row is decided. One boundary matters more here than anywhere else in the quarter: preserve the method and the lesson, never previously submitted language. A returning concept requires new reasoning, new evidence work, and new authorship, and the current activity's instructions decide what integration is supposed to mean for this response.

3. Build the work in proof order

Convert theory into criteria, compare options against evidence and constraints, quantify material effects where possible, then state implementation, ownership, and measurement.

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.

Reading the rubric row by row for integration language

Rubrics signal integration with a small set of words worth spotting: connect, relate, build on, apply course concepts, synthesize across, or draw on prior learning. Each is a request for a link, and a link has two ends. When a row uses that language, confirm both ends are visible in your draft: the earlier concept named specifically enough that a reader recognizes it, and the current problem stated specifically enough that the link is not generic. A sentence saying the course has emphasized the importance of holistic care has one end and nothing at the other. A sentence saying that a criterion developed earlier for weighing burden is what makes two of the current options separable has both.

Also read the rows that are not about integration, because an integration Week can quietly lose ground on ordinary rows while your attention is on connections. Give every row its proof shape as usual, then add the links on top. The weight given to integration varies by section and term, so read the live rubric rather than assuming this Week emphasizes what an earlier Week emphasized.

4. Use evidence deliberately

Combine relevant scholarly literature with current market, organizational, or policy evidence while labeling assumptions and protecting confidential information.

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.

Source layering when the Week spans several concepts

A Week that spans concepts tempts a source list that spans everything and supports nothing. Layer instead. The base layer is the small number of sources carrying the central claim, and it should stay small enough that you could defend every entry from memory. The second layer supplies criteria and measurement, which is what keeps an integrated argument auditable rather than letting it become a tour. The third layer is constraint material, including program, policy, or organizational documents where the activity permits them, and this layer is what keeps an integrated recommendation from floating free of the setting it would happen in.

Reuse from your shelf where a source genuinely fits, and resist citing an old favorite because it is familiar. When an earlier source returns, its job may have changed, so rewrite the one-line use note rather than copying the old one. Integrated writing fails most often at the seam, where a paragraph built on one layer hands off to a paragraph built on another, so read your transitions as though they were claims that need support. Permitted source types, counts, and citation style come from the live activity instructions.

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

Stress-test feasibility, incentives, ethics, risk, counterarguments, implementation ownership, and the metric that would show the decision worked.

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.

Two Week 6 pitfalls and the fix for each

Pitfall one: the survey response. Everything from the course is mentioned, nothing is used, and the draft reads as a tour of the syllabus. The fix is a use test applied to every earlier concept you name: point to the sentence where that concept changes a judgment in this response. If no such sentence exists, either cut the mention or write the sentence.

Pitfall two: self-reuse. An earlier submission contains a passage that fits, and copying it feels efficient. It is not, and it is not authorship in a new activity. The fix is to keep the lesson and rebuild the language: reread your earlier reasoning, close the file, and write the current analysis from the current prompt with current evidence. If the concept genuinely returns, its new job in a new problem will change how it should be expressed anyway. Rules on reusing your own work are set by Walden policy and by the instructor, and the registered classroom is where that answer lives.

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