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

Worked reasoning: mapping earlier Weeks onto the current prompt

Integration is a relationship, not a recap. Before drafting, build a small map on one page. Down the left, list the concepts the course has already covered, written as you understand them rather than copied from a heading. Across the top, list the parts of the current activity. In each cell where a concept genuinely bears on a part, write one sentence naming the relationship: this concept constrains that decision, this framework explains that pattern, this earlier criterion settles which option applies here.

Most cells stay empty, and that is the point. The three or four that fill are the integration the response should carry. A draft that touches every earlier topic once produces a tour, and a tour scores as summary.

Write each filled cell as a sentence you could defend under challenge. If the relationship cannot be stated without leaning on the word also, it is adjacency rather than integration, and it will read that way.

Keep the map built from course material and published evidence. Integration in an immersion course can feel as though it should be built from experience, but the layer this page addresses is the argument, not the record. Whatever the live activity asks the student to draw from placement remains theirs to gather, verify, and present, and your classroom rubric decides its form.

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

Synthesis rows are the hardest to satisfy by accident, so read them with unusual care. The tell is a criterion naming two or more things joined by a verb that acts on the pair: integrates, connects, relates, builds on, situates. Such a row is not asking for both items to be present. It is asking for the joint between them to be visible.

Mark every row of that kind and decide, before drafting, which single sentence will be the joint. Write that sentence first, then build the surrounding paragraph so the joint has something substantial on each side of it.

Read the level descriptors for these rows especially closely, because the ladder usually climbs through specificity. Lower rungs accept a general connection. Higher rungs want the connection made to the particular case, population, or problem the prompt names. A linkage sentence that would fit any course in the program sits at the bottom of that ladder.

Finally, check whether any row rewards the student's own account of their reasoning or learning. Where it does, the account must be the student's own, written from their own understanding, and your classroom rubric decides what form of evidence the activity requires for it.

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.

Source work: re-cite freely, re-use nothing

Integration Weeks create one specific temptation: moving a paragraph from an earlier submission into the current one because it already says the thing well. Treat the two operations as completely different. Re-citing a source used earlier is ordinary scholarship and usually a sign the shelf is working. Re-using previously submitted prose is self-plagiarism under most academic integrity policies unless the instructor has explicitly permitted it, and the safe assumption is that no such permission exists.

The practical method is to return to the source rather than to the old paragraph. Reread the use note, check whether anything more recent has appeared since, and write the sentence fresh against the current prompt. The new sentence will almost always differ, because the claim it supports differs.

Integration also calls for a particular kind of source: one that speaks to the relationship rather than to either side of it. Search for work examining the two concepts together, or for guidance that positions one inside the other. A single well-chosen bridging source often does more for a synthesis row than three strong sources that each cover only one half.

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 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 recycled language. Reusing sentences from earlier submitted work, even the student's own, breaches originality expectations in most classrooms and is straightforward to detect. The fix is the rule above: keep the method and the lesson, return to the source, and write new prose for a new prompt.

The second pitfall is integration by list. A paragraph naming four earlier topics and moving on has demonstrated recall, not synthesis. The fix is the joint sentence: cut the list to two items and spend the paragraph on what holds them together and where that hold breaks down.

The third pitfall is treating placement experience as the evidence base for a scholarly claim. Personal observation is not published evidence, single instances do not generalize, and writing them up in coursework tends to carry detail that should never leave the official record. The fix is to anchor scholarly claims in the literature and course material, to let anything the student draws from placement stay within the form and channel the official process specifies, and to write nothing that implies an hour, an encounter, or a competency has been met.

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