PRAC 6587 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 Acute Care Immersion II, 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.

Integrating earlier Weeks without recycling them

Integration means an earlier concept doing work on a current problem, not an earlier paragraph appearing again. The reliable method is to state the current problem first, in one sentence, then walk back through the course asking a single question of each earlier concept: does this change what the current answer should be? Most will not, and the discipline is to leave those out.

For the one or two that do, write the change as a sentence of this form: because of this concept, the answer to the current problem shifts in this way. That sentence is the integration, and it is new writing by construction, since it did not exist in any earlier submission. Previously submitted language is not reusable, and a returning concept requires fresh reasoning, evidence, and authorship even when the underlying idea is familiar. How much integration the response should carry is still settled by the live prompt.

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.

Reading the rubric row by row in Week 6

Read this Week's rubric for the knowledge it assumes. Integration rows rarely use the word integrate; they say build on, connect, or draw from, and they quietly expect earlier course material to be visible in the response. Work through the rows and mark each one with the earlier Week it appears to reach back toward, then check whether the drafting plan actually reaches there.

Watch for the opposite trap at the same time. A row scoped narrowly to the current prompt is one where reaching back would push the response off task and cost coverage. Keeping both kinds of mark on the same page prevents the common midcourse error of writing a term review in place of an answer. What the rows genuinely require is a question only the registered classroom can settle, and only its current rubric version counts.

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.

Reopening earlier sources with a new question

Integration Weeks are the best time to reread rather than to search. A source read in an early Week was read to answer that Week's question, and it almost always contains more than was taken from it. Return to two or three load bearing entries in the working file and put the current question to them directly.

The recorded fields make this quick, because population, setting, and limitation are precisely where a source either does or does not reach a new problem. Record any new usable finding as a separate line rather than editing the old one, so the file preserves both readings and neither claim loses its provenance. Where an earlier source turns out not to reach, say so in the draft and add support that does. Assigned readings still come first where the live activity requires them, and a source reused across Weeks still has to be cited for the claim it supports here.

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.

Integration is not permission to fill gaps

A synthesis Week creates a specific pressure: the draft looks thin, and the missing material would be easy to invent. In this subject that pressure has to be refused outright. Any part of a response that draws on the student's own placement activity is limited to what the student actually did and recorded, and no gap in that record is ever filled by inference, approximation, or a plausible substitute.

This page contributes nothing to that layer. It supplies no scenarios, encounters, counts, hours, site or preceptor detail, or evaluation wording, and no examples of any of them, and it never implies that a requirement has been met. If the live activity cannot be answered without material the student does not have, the correct next step is a question to the instructor or the program, asked early and in writing, with the written work planned around the answer that comes back.

7. Run the Week 6 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.

Three Week 6 pitfalls and the fix for each

The first pitfall is integration by name-dropping. Earlier concepts are listed, and not one of them changes a conclusion. The fix is to delete any mention of an earlier concept that is not immediately followed by a sentence saying what it changes.

The second is reusing sentences from an earlier submission because the concept has returned. A later prompt asks for new reasoning and new authorship even when the idea is the same. The fix is to work from the earlier lesson and the earlier notes, never from the earlier document, and to keep submitted files closed while drafting.

The third is an integrated response that answers the course rather than the prompt. Coverage rows go unmet while the word count fills with history. The fix is to keep the current prompt at the top of the working file and to test every section against it before expanding any earlier thread.

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