NRNP 6567 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 Critical Care Immersion: Advanced Skills and Patient Management, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? 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

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

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: layering, not recycling

Integration means the current judgment visibly stands on earlier foundations, and the connection is written, not implied. In the draft, name the earlier concept doing load-bearing work and show in fresh syntax how it constrains or explains the current problem: the mechanism met early in the course sits underneath this Week's judgment, and one or two sentences make the dependency explicit. The reader should be able to see the course arc inside the deliverable without being told to look for it.

Re-reason rather than re-use. An earlier concept enters this Week through new sentences aimed at the current prompt; pasting previously submitted language answers an old task under a new heading and collides with originality expectations besides. A deliberate integration move that stays honest: write one short passage stating how this Week's problem would have been answered with only early-course understanding, and what the intervening Weeks changed about the answer. That passage demonstrates growth in a form a rubric can score, and it forces the student to locate the actual difference rather than gesture at accumulation.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

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.

Re-using sources honestly across Weeks

A strong source may serve several Weeks, but each appearance must be earned fresh. Return to the source itself for the new claim rather than paraphrasing the student's own earlier summary of it, because summary-of-summary drift compounds quietly until the citation no longer supports the sentence in front of it. Re-cite fully in the required style each time, and check what the new claim actually needs: a source that once warranted a definition may now be asked to warrant a management judgment it cannot carry, and the honest move is an upgrade, not a stretch.

Extend the evidence bank's ledger so each entry lists every claim it has carried across the course. An entry accumulating too many different claim types is being stretched, and the ledger makes the stretch visible before a grader finds it. Integration work also tends to need one or two genuinely new sources, because the connection between earlier and current material is itself a claim, and evidence that speaks to the connection, rather than to either part alone, is what separates synthesis from adjacency.

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

Check safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

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.

Reading the rubric row by row

In an integration Week, watch for synthesis rows: language about connecting, building on, integrating, or applying prior concepts to the current problem. Their top columns typically require the connection to be explicit, specific, and supported, which means an implied relationship, however real, scores as a partial one. Distinguish carefully between rows scoring the current content and rows scoring the connection, because both must be served by visible text and neither can substitute for the other.

The audit for this read is underlining: mark every sentence in the draft that performs connective work, stating how an earlier concept bears on the present analysis. If the underlining comes back empty, integration existed only as intention. A recycled paragraph fails both row families at once, stale for the current content and inert for the synthesis row, which is why the row-by-row read is where recycling gets caught before a grader catches it. End by checking that the connective sentences carry citations where they make claims, since synthesis without warrant is just narration of the syllabus.

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.

Week 6 pitfalls and the fix for each

Pitfall one: self-plagiarism by pasting from prior submissions. Re-submitted language misrepresents new work, can trip originality checking, and usually answers the earlier prompt rather than this one. The fix is closed-book re-derivation: work from the feedback ledger and the evidence bank, not from old files, and let the current prompt shape sentences that have never existed before.

Pitfall two: integration by name-dropping, a list of earlier topics with no connective work done. Naming is not linking. The fix is a consequence sentence for every named concept: what that concept changes about the current analysis, decision, or boundary, stated specifically enough that removing the concept would visibly weaken the passage.

Pitfall three: treating the Week as standalone and silently contradicting a position the student defended earlier in the course. Unacknowledged reversals read as inattention rather than growth. The fix is a consistency check against prior submissions before the gate: where the position genuinely changed because understanding improved, say so in one sentence and give the reason, which converts the contradiction into demonstrated learning.

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