By the middle of a 256-hour block the change is running and the written task is an account of how much of it is actually reaching people, where, and in what form. This is the implementation narrative: delivery described by site and by period, deviations named and classified, and the first weeks of collected figures reported without being interpreted as results. A heavier hour load means more surface area to describe, and more places for delivery to differ. Your section may print this as NR 705C or NR705C; 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-705C Week 4 asks for
Two locations of the same pediatric group start the same reconciliation step in the same week and behave nothing alike. At the smaller site the step is completed in most eligible visits within days, because one medical assistant does all the rooming and learned it once. At the busier site completion sits far lower, and observation shows the reason is structural: three staff rotate through rooming and two of them work evenings, when the briefing was never repeated. That contrast is the most valuable content your project will produce this term, and it exists only because the implementation was described per site rather than pooled.
Keep the constructs clean. Reach is who received the intervention out of who was eligible. Dose is how much of it they received. Spread, in a multi-site or multi-unit project, is where delivery has extended to and where it has not. Fidelity, which the next stage will take up in depth, is whether what was delivered matched the design in the ways that carry the mechanism. Students who use these words interchangeably produce narratives that sound thorough and cannot support a conclusion.
Numbers at this point are operational, not evaluative. Report them with bases and periods, split them by site, and say plainly that no comparison against baseline has yet been made. A mid-term narrative that starts claiming improvement has changed genre, and doctoral readers who see a premature result claim tend to read the rest of the document more sceptically.
Where the boundary sits. The practicum is entirely yours. The 256 clinical hours, the log that records them, encounter and activity counts, evaluations completed by preceptors or mentors, site agreements and every signature the university verifies are your own record and your own work - never drafted, reconstructed, back-filled or estimated with help of any kind. Nothing here is an offer to touch them. What written support covers is the written layer: organizing an implementation narrative, turning observations into analysis, writing scholarly prose about a change you personally led. De-identify everything clinical that reaches your page - roles rather than names, no service dates, nothing that would let a reader place a family or a colleague. The clinical experience has no shortcut, and clearer written reasoning about work you genuinely did is the entire offer.
The NR-705C Week 4 method, step by step
Six moves for an implementation narrative that holds up under questioning.
-
Establish the delivery state per site in the opening paragraphs
Which sites are live, from which date, in which visit types, under which protocol version. A reader should be able to draw the current footprint from your first two paragraphs without reconstructing it from later detail.
-
Report reach as counts over site-specific denominators
Never a combined figure alone. Completed at 84 of 112 eligible visits at one location and 63 of 229 at the other, over the same window, is the sentence that makes the rest of your analysis possible.
-
Explain the between-site difference structurally
Staffing pattern, volume, rooming design, shift coverage, template build. Structural explanations generate fixes. Explanations that reach for engagement or culture generate nothing you can act on before the term ends.
-
Classify every deviation and trace it to a plan element
Preparation gap, resource gap, workflow collision, communication failure, deliberate adaptation. Then name which part of your plan failed to anticipate it. The trace is the analysis; the list alone is a chronicle.
-
Date every correction and note what period it changes
Corrections mid-implementation are expected. Undated ones make your later analysis cover a period during which the intervention silently varied, which is a problem no statistical care can repair.
-
Label all figures pre-evaluation, in the sentence
Operational counts to date, no baseline comparison performed. That clause costs six words now and protects the credibility of everything you report at the end of the program.
A layout and word budget for a mid-term implementation narrative
Our frame for a delivery account written to be reusable in a final manuscript, sized for roughly 1,600 to 2,000 words plus tables. It is our own outline rather than anything the university issues, and your chair's direction and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Delivery state | Sites live, start dates, visit types included, protocol version in force at each, and anything still not launched. | 200 to 250 |
| Reach by site | Counts over site-specific denominators for the same window, with the combined figure only after the components. | Table plus 180 |
| Dose completed per encounter | Which elements of the step were completed when the step occurred, and where the sequence truncates in practice. | 220 to 270 |
| Between-site analysis | The structural differences that explain divergent delivery, evidenced by observation and by counts rather than asserted. | 320 to 400 |
| Deviations and corrections | Each departure with its class, its trace to a plan element, the correction made, and the date it took effect. | 320 to 400 |
| Data collection status | Whether the procedure is running as written, any gaps in the series, and what has been verified so far. | 170 to 220 |
| Live risks | What could still derail the remaining weeks, at which site, and the specific signal you are watching for each. | 180 to 230 |
Evidence craft for an implementation narrative
Give observation its conditions. Six clinic sessions across both locations, on different days and shifts, with staff aware of the observer. Those conditions shape what you saw and stating them is standard practice. Observation without conditions is an impression presented as data.
Never pool sites into a single reach figure without the components. A combined number in a two-site project conceals the only comparison that makes the project interesting, and a reader who has to ask for the split has already formed a view about the analysis.
Cite implementation literature for the pattern you are seeing. Rotating staff, evening coverage and multi-site variation are all well described. One or two citations show that you recognize a general phenomenon rather than a local accident, and that recognition is what makes a single-organization project translatable.
Write staff behaviour as system output. The step was completed in most observed morning encounters and in a minority of observed evening encounters is evidence about coverage design. Evening staff are less consistent is a characterization of colleagues that explains nothing and ages badly in a document your site may read.
Keep every count and illustration de-identified. Aggregates are safe by construction; the risk enters with examples. Where you illustrate a dose problem with an encounter, remove the date, the location and any clinical specificity, and prefer a composite framing no single family could be read into.
Five mistakes that cost points in this week's territory
- Pooled figures with no site breakdown. In a multi-site project the split is the finding, and a combined number hides it while appearing complete.
- Interpreting mid-term counts as improvement. No baseline comparison has been performed, the series is short, and a claim made here will be quoted back at you.
- Cultural explanations for structural problems. Buy-in and engagement as causes usually mean the staffing pattern or the workflow has not been examined yet.
- Deviations listed without a trace. A departure that is not connected to the plan element that missed it teaches your reader nothing and teaches the next site less.
- Silence about the data process. If collection has slipped, say so now. A gap in the series discovered at the end is far worse than one reported while it can still be filled.
Before you submit
- Delivery state is stated per site, with dates and protocol versions
- Every reach figure has a site-specific denominator and a named window
- Between-site differences are explained structurally with evidence
- Each deviation carries a class, a trace and a dated correction
- All figures are explicitly labelled operational and pre-evaluation
- Observation conditions - sessions, days, shifts - are stated
- No individual staff member or family is identifiable
Writing the NR-705C mid-term narrative?
Send the rubric, your protocol versions and your own aggregate counts out of Canvas. A premium original draft comes back in 24 to 48 hours with delivery reported per site and every deviation classified and traced, revised free until it lands. Hours, logs and evaluations remain entirely yours.