NURS 6910 Week 4 planning manual

1. Capture the live Week 4

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 Introduction to Palliative Care: Principles of Hospice and Palliative Care, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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 required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to 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.

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 4 quality gate

Check task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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 5. 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 4, 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 5.

Turning a recommendation into an action statement

Week 4 asks for the move that separates a literature summary from usable graduate work: converting what the evidence says into what someone should do. A complete action statement in this subject names four things, the actor, the action, the trigger or timing, and the observable result that would show it worked. Worked out, a sentence saying that conversations about goals of care should happen earlier names nobody and commits to nothing. A sentence naming which role initiates, at what point in a trajectory as the source defines it, what gets documented, and what would be visible afterward is an action statement a rubric can credit. Write the four elements as a bare list first, compose the sentence second, then check that every element survived the composition. Elements usually disappear during the polish, not during the draft.

Reading the rubric row by row on evidence-to-application rows

Application rows have a specific shape: they credit the link, not the parts. A draft can present strong evidence and a sensible recommendation and still lose the row because the two never touch on the page. Highlight every rubric row containing words like apply, support, integrate, justify, or connect. For each one, find the single sentence in your draft where the link is actually made and mark it. If a row's sentence does not exist, write it before touching anything else. Then check whether the rubric separates quality of evidence from use of evidence, because those are frequently two rows and are lost in different ways. Your classroom rubric decides the row set and its wording, so read the live version rather than assuming this pattern holds in your section.

Citing guidance without overstating it

Guideline and consensus sources are unusually useful in hospice and palliative coursework and unusually easy to misuse. Three habits protect the citation. First, carry the conditions, since recommendations are almost always scoped to a population, a setting, or a stage, and a sentence that drops the scope has changed the source's meaning. Second, keep the strength language the source used; a suggestion is not a requirement, and a statement issued where evidence is limited is not equivalent to one built on consistent trial evidence. Third, do not let guidance stand in for a mechanism, because it tells you what a body recommends, and if the prompt asks why, you still need the study or review underneath. Where guidance and a primary study disagree, say so in the draft, since naming the tension is analysis and quietly choosing the convenient one is not.

Three ways evidence and action come apart in Week 4

The first is the actorless recommendation. Sentences built on should be considered or needs to be improved pass the eye and fail the row. Fix it by rewriting every recommendation in active voice with a named role as the subject.

The second is condition stripping. A recommendation copied without the population or setting it was scoped to becomes a claim the source never made. Fix it by writing the scope into the same sentence as the recommendation rather than leaving it in your memory.

The third is confusing how strongly something is recommended with how certain the underlying evidence is. These are separate axes, and collapsing them produces overclaiming. Fix it by stating each explicitly once, then choosing hedging language that matches the weaker of the two.

Keeping the action layer honest about what you did not do

This course sits close to practice, and Week 4 is where drafts start drifting toward implementation language the written layer cannot support. Keep the boundary visible. You are proposing, analyzing, and justifying on paper; you are not reporting that something happened. Where the activity asks for a plan, write it as a plan, with its assumptions and its unknowns stated. Where an element would require access, approval, or activity you have not completed, name that as a prerequisite instead of describing it as done. Readers in this subject watch that distinction closely, and a plan candid about its dependencies is stronger, not weaker, than one that reads as a finished account of work that has not occurred.

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

Week 4 questions