PRAC 6547 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 The Aging Experience Practicum, 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 the criteria ask for synthesis

Integration criteria are worded in a way that hides what they want. They ask the writer to connect, relate, incorporate, or build on earlier material, and a student can satisfy the surface of that language while failing the row. Decide first whether a synthesis row is asking for breadth or for depth, because the tests are opposite: a breadth row wants several strands visibly present and correctly related, while a depth row wants one strand carried further than the earlier work took it. The performance-level language usually settles the question, so read it before planning the structure. Watch also for a row that scores originality or independent thought, which in practice is a rule against reusing previously submitted language and a requirement that this deliverable perform its own reasoning. Where a row lists elements to be integrated, turn the list into a checklist with a location column, since integration rows are commonly lost not because a strand was missing from the student's thinking but because it never appeared on the page. The live rubric in the registered classroom governs which reading applies.

Worked reasoning: writing the interaction rather than the inventory

Integration in this subject is rarely a matter of mentioning several topics in one document. It means holding more than one domain in a single argument and saying how they act on each other, which is exactly the demand that aging-focused work makes: function, concurrent conditions, medication burden, social and caregiving context, communication and sensory factors, and the person's own goals do not sit in separate paragraphs in reality, and an argument that treats them separately misses the point of the course. So write the interaction sentence first, before any of the sections it will connect. Name two or three strands, then state what changes when they are considered together rather than in sequence: what a conclusion drawn from one strand alone would get wrong, and what the combined view adds. Build the document outward from that sentence. Draw the map on paper first if it helps, with the strands as nodes and the interactions as labelled arrows, then convert each labelled arrow into a paragraph. The arrows are the deliverable; the nodes are only the setup.

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.

Bringing earlier sources back without recycling earlier work

An integration week naturally revisits material from earlier in the course, and there is a clean line between doing that legitimately and crossing into resubmission. Citing a source again is ordinary scholarship. Reusing sentences, paragraphs, or a structure already submitted for credit is a different act, and it is the thing an originality criterion is watching for. Return to the source itself rather than to your earlier paper, read the part of it that this week's question needs rather than the part the earlier week needed, and write new prose from that reading. If the earlier deliverable is genuinely relevant, refer to the idea and develop it, and follow the instructor's stated position on self-citation in the registered classroom.

Integration also changes what a good source looks like. A study that examines one domain in isolation is often too narrow to support an interaction claim, so look for work that models several factors together, for reviews that synthesize across domains, or for guidance documents that explicitly address the complexity of concurrent conditions. Where no source examines the interaction directly, say so, then build the connection yourself from two sources and mark clearly which part of the claim is yours rather than theirs. Record that division in the ledger so it survives revision.

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.

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.

Three integration pitfalls, and the fix for each

Pitfall: pasting or lightly reworking prose already submitted this term, on the reasoning that the concept has not changed. Fix: write every paragraph from the sources and from this week's question, keep earlier deliverables closed while drafting, and preserve the method you learned rather than the language you used.

Pitfall: integration performed as a roll call, where each earlier topic gets a respectful mention and nothing is related to anything else. Fix: apply the arrow test, and require every strand named in the draft to appear in at least one sentence that states how it acts on another strand.

Pitfall: connecting concepts so enthusiastically that the standard disappears and the argument floats free of any authority. Fix: after the interaction paragraphs are drafted, run a pass that attaches the governing guideline or evidence to each claim, and cut the connections that turn out to rest on nothing.

Integration is a writing operation only

Connecting the course's ideas is work done on the page. It does not connect to, substitute for, or evidence anything in the student's placement, and this manual keeps the two apart deliberately. Whatever the student is required to perform and document remains theirs to perform and document, under the program's own process, and nothing written here reflects on how much of it has been completed. No part of that record is drafted, sampled, or approximated on this page.

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