PRAC 6577 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 Advanced Primary Care Immersion Practicum II, 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.

Reading the rubric row by row when a row says integrate

Integration rows are widely misread as summary rows. A row asking you to summarize wants earlier content restated accurately. A row asking you to integrate wants a claim that could not have been made from any single week alone, which is a much harder thing and a much easier thing to check. Read every integration row and write the claim type it implies: a comparison across two frameworks, a judgment that resolves tension between two standards, or an application that needs one concept to set up another. Then decide in advance where that claim will appear, because integration buried in a closing paragraph often reads as an afterthought. Watch also for rows that ask you to build on prior work, which is not an invitation to resubmit it. Your classroom rubric decides what integrate means in this activity, and if the row is ambiguous the instructor is the authority.

Mapping concept to concept before writing

Integration fails when a writer lists everything learned so far and hopes the connections are obvious. Build a small map instead. Left column: the earlier concepts, standards, or methods the course has covered. Right column: the specific demand of the current problem. Middle column, written last and hardest: the sentence that actually joins one to the other, stating what the earlier concept lets you do with the current problem that you could not otherwise do. Only pairs with a completed middle column earn a place in the draft. Two well-joined pairs beat six loose mentions every time, and the map makes the difference visible before any prose exists. Where a pair resists joining, that is useful information too, because it usually means one of the two is being remembered in a simplified form and needs rereading before it can carry weight.

Integration never means importing a narrative

Carrying your own reasoning and your own methods forward is exactly the point of an integration week. Carrying previously submitted language forward is a separate matter that your program defines, and a later prompt requires new reasoning and new authorship even when the underlying concept returns. Carrying in anyone's clinical narrative is out of bounds entirely. Your placement record stays inside your own documentation system and remains yours alone to gather, verify, and submit through the required process. No part of it may be reconstructed here, borrowed from a peer, generalized from what usually happens, or filled in from a published account to make a synthesis feel more grounded. The concepts integrate; the records do not travel.

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.

Carrying a source forward for a new claim

A source that supported one claim earlier in the course will not automatically support a different claim now, and this is the most common quiet error in an integration week. Reread before you re-cite. Check that the finding you remember is the finding the source states, that the population still matches, and that no newer edition or revision has appeared since you captured it. When a source is genuinely reusable, note the second job it is now doing in your source shelf, so the shelf records the range of each entry rather than a single use. When a source is being stretched, find one that fits instead. Integration weeks reward evidence that spans the course, but only when each span is real; a familiar citation working outside its actual scope is easier for a reader to spot than a new one.

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.

Three integration failures and the repair for each

The first failure is the recycled paragraph. Earlier language gets pasted forward because it was good and the concept is the same, and the response answers the earlier prompt rather than this one. The repair is to write from the map rather than from old files, and to check any passage that felt effortless against the current prompt word by word.

The second failure is a synthesis that is a list. Three concepts are introduced in sequence, each accurately, with no sentence joining them. The repair is the middle column of the map: no concept enters the draft without its joining sentence written first.

The third failure is inherited citations that were never rechecked. A reference travels forward with the text and now supports something it does not say. The repair is a rule that any citation reused from an earlier week gets reopened before it is reused, with the date and the specific finding confirmed again.

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