A 256-hour block is one of the few practicum stages with enough time for a change to stabilize in one place and then be offered to a second, and the written work at this point is about that extension: what transfers, what has to be rebuilt locally, and how the evaluation has to change once two settings are involved. This is a judgment about capacity as much as about method, and the document should argue for extending or for declining to. Your section may print this as NR 707C or NR707C; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-707C Week 4 asks for
A post-discharge telehealth outreach that works beautifully for a cardiology population is offered to the clinic that follows chronic respiratory patients, and it fails in the first week for reasons that have nothing to do with the intervention. The respiratory clinic schedules its own follow-ups already, its patients answer the phone at different times of day, and its nurses have a different relationship with the referring physicians. The mechanism was sound. The context was different, and nobody had written down which parts of the original success came from the change and which came from the setting it was born in.
The boundary that governs this manual. Practicum hours, hour logs, encounter counts, site paperwork, and preceptor or mentor evaluations are your own record of work you personally performed and are never drafted, reconstructed, or estimated by anyone else. What can be supported is the written layer: how a transfer decision is argued, how contextual differences are analyzed, how a second setting is described without inventing data. Every encounter that informs your writing is de-identified, and access to any second setting's records follows that setting's own authorization route, not the first one's.
The analytic core of this stage is separating mechanism from context. The mechanism is the element that produces the effect: a structured review at a defined interval, a hard stop in a workflow, a named person owning an escalation. The context is everything around it: staffing, schedules, relationships, population, technology. Transfer works when the mechanism is preserved and the context-dependent parts are rebuilt locally. It fails when the whole package is copied on the assumption that the second setting is a smaller version of the first, which it never is.
Expect the deliverable to be an analytic write-up of the extension, its rationale, and the adjustments it required, sometimes with a comparison table, often inside a mid-block progress document, and frequently a posted discussion about what did or did not travel. If your project is not extending anywhere, this stage is still worth writing as an analysis of transferability: which parts of your change would travel and what a second setting would need. That is a legitimate and well-scoring version of the same intellectual task.
The NR-707C Week 4 method, step by step
Six analytic moves for arguing an extension rather than assuming one.
-
1. Isolate the mechanism from its packaging
Write the one or two elements you believe actually produce the effect, and separate them from the artifacts that carry them: the form, the script, the meeting, the reminder. Artifacts are local. Mechanisms travel.
-
2. Compare the two contexts on named dimensions
Population, volume, staffing model, existing workflow, technology, and relationships with referring or receiving services. Six dimensions in a table beats a paragraph asserting that the settings are similar.
-
3. Verify stability before you extend anything
Write the condition that says the first setting is stable: adoption at a level you name, fidelity verified, no unresolved balancing signal. Extending from an unstable base doubles a problem instead of spreading a solution.
-
4. Rebuild the context-dependent parts locally
Say which elements you are deliberately not copying and what the second setting builds instead. A local rebuild that preserves the mechanism is transfer done properly; a copied artifact that nobody there helped design is transfer done badly.
-
5. Restate the measures for the second setting
Numerator, denominator, and clock all need checking against the new context, and at least one usually needs changing. Say which definitions are identical and which had to be adjusted, and never report a pooled figure across settings whose definitions differ.
-
6. Argue the decision, including a decision not to extend
Declining to extend because the first setting is not stable, or because 256 hours cannot support two implementations honestly, is a defensible doctoral judgment. Write the reasoning either way; the reasoning is the graded content.
A layout for an extension and transferability write-up
Our frame for this stage's document, sized for roughly 1,200 to 1,500 words plus a context comparison table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Stability of the first setting | Adoption, fidelity, and balancing status with counts, plus the stated condition for extending. | 200 to 240 |
| Mechanism and artifacts | The elements believed to produce the effect, separated from the local materials that carry them. | 190 to 230 |
| Context comparison | The two settings across population, volume, staffing, workflow, technology, and relationships. | 230 to 280 |
| What is copied, what is rebuilt | Element by element, with who in the second setting is building each local piece. | 200 to 250 |
| Measures in the second setting | Definitions that hold, definitions that changed, and why pooling is or is not appropriate. | 180 to 220 |
| Decision and its reasoning | Extend, defer, or decline, with the capacity analysis behind it and what it means for the block. | 190 to 230 |
Evidence craft for transfer writing
Context differences need evidence, not assertion. Say how you know the second setting's volume, staffing, or workflow differs: a report, a period of observation, a conversation with a named role on a date. Comparisons built on impression are the weakest paragraphs in an otherwise strong document.
Never pool across settings without saying so. A combined rate that blends two populations with different definitions or wildly different volumes will be read as a claim about both, and the larger setting will dominate it. Report separately, then pool only if the definitions are genuinely identical, and say explicitly that they are.
Draw on the spread and scale-up literature. There is a substantial body of published work on why improvements fail to travel, and citing it with a year converts your context analysis from local observation into scholarship. Use its distinctions rather than inventing your own vocabulary for the same ideas.
Keep the improvement frame in both settings. Two sites do not make this research, and a second setting does not create a comparison group. It creates a second local evaluation with its own limitations. Where your organization requires a determination about human subjects oversight, describe the process you followed and its date rather than characterizing an outcome.
De-identify each setting proportionally. A small specialty clinic is far easier to identify than a large inpatient service, and a description that names a population, a volume, and a schedule can locate a specific team. Aggregate more heavily where the setting is smaller.
Five mistakes that cost points in this week's territory
- Extending from an unstable base. If fidelity is unresolved in setting one, setting two inherits the problem and the evaluation loses both.
- Copying artifacts instead of mechanisms. A form built for another team's workflow is the most common thing that travels and the least likely thing to work.
- Contexts declared similar without evidence. Two clinics in the same organization can differ more than two hospitals, and the write-up must show it knows.
- Pooling incompatible measures. A single combined figure across settings with different definitions is not a result; it is an average of two different questions.
- Treating the second setting as free. Every extension consumes hours you already allocated, and a capacity analysis is part of the argument.
Before you submit
- Stability in the first setting is demonstrated with counts before extension is discussed
- Mechanism and artifacts are separated explicitly
- The context comparison covers named dimensions with evidence for each
- What is copied and what is rebuilt locally is listed element by element
- Measure definitions for the second setting are stated, with pooling justified or refused
- The decision, including a decision to decline, is argued with a capacity analysis
Writing the extension analysis for NR-707C?
Send the rubric and your setting data out of Canvas. A premium original draft comes back in 24 to 48 hours with mechanism separated from artifact, contexts compared on evidence, and the decision argued, and revisions run until the grade lands.