Halfway through the operating period the question stops being whether the change launched and becomes whether it is being delivered as designed, to whom, and how often. Fidelity, reach and dose are the three process constructs that make a later outcome interpretable, and the writing this stage asks for is a process analysis rather than an outcome report. A project without this section cannot tell the difference between an intervention that failed and one that never really ran. Your section may print this as NR 705B or NR705B; 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-705B Week 5 asks for
Return to the pediatric practice adding a structured screening step. Four weeks in, the practice manager reports that the team is doing it. The record says the form was completed at 78 of 143 eligible visits. Observation across five clinic sessions says that when the form is completed it is handed over correctly, but that same-day add-on appointments never trigger the schedule flag, which is where roughly a third of the eligible visits live. Three different sources, three different pictures, and the written task is to reconcile them into one honest account of how much of the intervention is actually reaching families.
Keep the three constructs separate in your prose, because students routinely collapse them. Reach is who received the intervention out of who was eligible. Dose is how much of it they received - all four elements of the step, or two. Fidelity is whether what was delivered matched the protocol in the ways that carry the mechanism. A practice can have high reach and low fidelity, which produces a null result for reasons that have nothing to do with the evidence base. Naming which of the three is weak is the analytic payload of this section.
This is also where a partially adopted intervention has to be written honestly. If one provider declined, your denominator is not the whole panel and your later comparison must respect that. If the schedule flag misses add-ons, then a named category of visits is structurally excluded and that is a finding about the workflow rather than about staff. Reporting reach against the true eligible population, and explaining any restriction of it, is one of the clearest markers of doctoral-level implementation work.
Where the boundary sits. The practicum is your own from end to end. The 192 clinical hours, the log that records them, encounter and activity counts, evaluations completed by preceptors or mentors, and any document a site or the university verifies are your record alone - never drafted, reconstructed or estimated with help of any kind, and no part of what is offered here. Fidelity observations of your own project's workflow are project data you collect yourself; they are not a substitute for anything a school verifies and they are not something anyone else can produce for you. What written support covers is structure and reasoning on the page: how to organize a process analysis, how to write about counts precisely, how to reflect analytically. De-identify every clinical detail that reaches your writing, and remember that the hours cannot be shortcut by anyone.
The NR-705B Week 5 method, step by step
Six moves for writing a process analysis that makes a later result interpretable.
-
Define the eligible population in one testable sentence
Which visit types, which ages, which exclusions, drawn from which field. If two people applying your definition to the same month would produce different denominators, the definition is not finished and everything downstream inherits the ambiguity.
-
Report reach as a count over that denominator, with the period
Screening completed at 78 of 143 eligible visits between the first and the twenty-eighth. Never a bare percentage. The base and the window are what let a reader judge whether the figure is stable enough to mean anything.
-
Break reach down by the category that explains it
By visit type, by day of week, by provider, by scheduled versus same-day. The disaggregation is where the actionable finding lives, and an undifferentiated total hides exactly the pattern you need.
-
Score fidelity against named protocol elements, not impressions
Pick the three or four steps that carry the mechanism, write them as observable behaviours, and record whether each occurred across a set of observed encounters. Say how many sessions you observed and when.
-
Reconcile your sources openly when they disagree
Record data, direct observation and staff report will not match. Write the discrepancy, say which source you trust for which construct and why, and never quietly pick the friendliest number.
-
Convert each weakness into one dated corrective action
A structural exclusion of same-day visits calls for a workflow change, not a reminder. Name the action, the owner by role, and the date it takes effect, because your final analysis will need to know which weeks ran under which conditions.
A layout and word budget for a fidelity and reach analysis
Our frame for a mid-implementation process analysis, sized for roughly 1,500 to 1,900 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 |
|---|---|---|
| Process constructs defined | Reach, dose and fidelity as you are using them here, each in two sentences, with the source of the framework named. | 170 to 210 |
| Eligibility and denominator rules | Inclusions, exclusions, the data field the denominator comes from, and any known limitation of that field. | 200 to 250 |
| Reach reported and disaggregated | The overall count over denominator with period, then the same figure split by the category that explains variation. | Table plus 200 |
| Dose delivered | Which elements of the step were delivered when the step occurred at all, and where the sequence gets truncated. | 200 to 250 |
| Fidelity observations | Method of observation, number and timing of sessions, the mechanism-carrying elements checked, and what was seen. | 250 to 320 |
| Source reconciliation | Where record, observation and report diverge, and your reasoned choice of which to rely on for each construct. | 200 to 250 |
| Corrective actions | One action per identified weakness, each with a role owner and an effective date, plus what you expect it to change. | 200 to 240 |
Evidence craft for process measurement
Name the framework you take your process constructs from. Implementation outcome taxonomies exist and are cited routinely in doctoral work. Borrowing the vocabulary without attribution reads as improvised; naming the source with its year lets your reader map your section onto a literature they know.
Write every proportion as a fraction first. 78 of 143 says how much data stands behind the figure. Fifty-five percent says nothing about stability, and in a small practice over four weeks stability is the whole question. Percentages can follow the fraction; they should not replace it.
Say how observation was conducted, not just what it showed. Number of sessions, days and times, whether staff knew you were observing, and whether you were also working clinically during the observation. Those conditions shape the finding, and stating them is standard practice rather than a confession.
Do not treat a process shortfall as a personal failing of anyone. A step delivered in half of eligible visits is a system finding. Write it as one, and trace it to the workflow feature that produced it. The same sentence written as staff compliance both misdescribes the cause and dates your project as pre-improvement-science thinking.
Keep every count clinically de-identified. Aggregate figures are safe by construction; illustrations are where risk enters. If you describe a particular encounter to make a point about dose, remove the date, the provider and any clinical detail that narrows it, and prefer a composite framing that no single family could be read into.
Five mistakes that cost points in this week's territory
- Reporting reach with no denominator rule. If the reader cannot tell who counted as eligible, the figure is uninterpretable and the rest of the section rests on it.
- Collapsing fidelity into reach. A step that happened is not a step that happened correctly, and projects with strong reach and weak fidelity produce the most misleading conclusions.
- Reporting only the total. The disaggregation is the finding. An overall figure with no breakdown leaves the actionable pattern buried.
- Choosing the friendlier data source silently. When record and observation disagree, using the higher number without saying so is the closest thing to a data integrity problem this stage offers.
- Corrective actions written as intentions. Will reinforce with staff is not an action. A workflow change with an owner and a date is.
Before you submit
- Reach, dose and fidelity are defined separately and used consistently
- The denominator rule is testable by someone outside the project
- Every proportion appears as a count over a base with a named period
- Reach is broken down by at least one explanatory category
- Observation method, session count and timing are all stated
- Discrepancies between sources are named and resolved with reasoning
- Each corrective action carries a role owner and an effective date
Writing the NR-705B process analysis?
Send the rubric, your protocol and your own aggregate counts out of Canvas. A premium original draft comes back in 24 to 48 hours with reach, dose and fidelity kept properly distinct and every figure written with its base, revised free until it lands. Hours, logs and site evaluations stay entirely yours.