A project with a strong intervention and a weak measurement plan produces a change nobody can demonstrate, which is the most disappointing way for doctoral work to end. This stage asks for the plan itself: each measure with a numerator rule, a denominator rule, inclusions, exclusions, a source field and a collection interval, written so that two people applying them to the same month would produce the same number. 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 2 asks for
Take a family practice implementing a structured medication reconciliation step. Reconciliation completed sounds like a measure. It is not, until someone decides what completed means. Does a note with a medication list count, or must the list have been verified against the pharmacy record? Does a visit where the caregiver did not bring the bottles count as incomplete, or as excluded? Does a telephone visit count at all? Every one of those questions has a defensible answer and a different number attached, and if the answer is not written down before data collection starts, the number you produce in week seven will not be comparable to the baseline you produced in week two.
Doctoral projects are expected to carry a measure set rather than a measure. An outcome measure says whether the thing you care about changed. At least one process measure says whether the intervention was actually delivered, and it is the measure that makes a null outcome interpretable, because without it a flat result cannot distinguish an intervention that did not work from one that never happened. A balancing measure says whether the change broke something else - visit length, staff time, another step in the workflow that quietly got dropped. A plan with all three reads as improvement methodology; a plan with only an outcome reads as hope.
A 256-hour term makes a stronger data foundation possible, and that is where the extra time should go. There is room to specify the extract properly, run it once as a test before the operating period starts, look at what the field actually contains, and discover that the reconciliation flag is populated by a template default rather than by a human. That discovery in week two is an inconvenience. The same discovery in week seven is a project.
Where the boundary sits. The practicum belongs to you. The 256 clinical hours, the log that records them, activity and encounter counts, evaluations completed by preceptors or site mentors, agreements and signatures are your own record and your own work, never written, reconstructed, back-filled or estimated with help from anyone. Nothing here is an offer to touch them. What written support covers is the scholarly and preparatory layer: structuring a measurement plan, writing operational definitions precisely, organizing a data section so it holds together. Project data you work with must be handled under your organization's rules and de-identified in anything you write - aggregate figures wherever possible, no dates of service, no detail that would let a reader place a family. The clinical work has no shortcut and none is offered.
The NR-705C Week 2 method, step by step
Six moves for a measurement plan that survives a real dataset.
-
Write the denominator before the numerator, every time
Who is eligible, by which field, over what period, with which exclusions. Numerators are easy and denominators are where projects go wrong, because an eligibility rule that shifts between baseline and follow-up quietly invalidates the comparison.
-
Define completed as an observable state in the record
Not a judgment. A specific field populated, a specific note element present, a specific flag set. If your definition requires someone to read a note and decide, say who reads, against what rule, and what happens when two readers disagree.
-
Build the measure set, not the measure
One outcome, at least one process, one balancing. Write each with the same fields so the set reads as a single instrument rather than as three separate ideas assembled at different times.
-
Name the source system and the exact field for each measure
Reports get run by other people. A measure that cannot be traced to a field cannot be reproduced, and reproducibility is the property that lets your site keep monitoring after you leave.
-
Test the extract before the operating period begins
Pull one historical month, look at the distribution, and check whether the field means what you assumed. Defaults, autopopulation and blank-versus-zero problems are all cheap to find now and expensive to find later.
-
Describe the baseline by length and variation, not by a single figure
A baseline of one month with wide week-to-week swings supports almost nothing. Say how many periods you have, what the variation looks like, and what comparison that baseline can honestly carry.
A layout and word budget for a measurement plan
Our frame for a measurement and data section at this stage, sized for roughly 1,600 to 2,000 words plus the measure table. 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 |
|---|---|---|
| Aim statement with a number in it | What will change, for whom, by how much and by when, written so that the measures below could confirm or refute it. | 120 to 160 |
| Measure set table | Each measure: type, numerator rule, denominator rule, exclusions, source field, collection interval, owner. | Table plus 160 |
| Operational definitions | Prose definitions of every term that could be read two ways, written to survive a change of reader. | 300 to 380 |
| Data sources and their limits | Where each number comes from, who can produce it, and what is known to be unreliable in that field. | 250 to 310 |
| Baseline description | Periods available, the figures by period, the variation, and what comparison this baseline can support. | 230 to 290 |
| Analysis approach | How the comparison will be made and displayed, in improvement terms, without borrowing inferential language the design cannot support. | 220 to 270 |
| Data handling | Where data lives, who has access, how it is de-identified, and how it is disposed of at the end. | 170 to 220 |
Evidence craft for measurement writing
Borrow measure definitions from published specifications where they exist. If a professional body or a national program already specifies the measure you want, use its numerator and denominator rules and cite the specification. A locally invented definition that differs from a published one without explanation looks like it was designed around the available data.
Write the aim with a number and a date in it. Vague aims produce vague measures. An aim that names a target and a window forces the measure set to be specific enough to test it, and it gives your later results section something concrete to be assessed against.
Use improvement language, not inferential language. Run charts, shifts, trends and special cause are the vocabulary of the design you are actually running. Significance testing on a single-site pre and post comparison is usually inappropriate and always invites a methodological argument you do not need to have.
State known data weaknesses before someone finds them. If the field is completed by a template default, if one site codes visits differently, if a report excludes same-day appointments, write it. A measurement plan that names its own weak points is far more credible than one that presents a clean surface.
Keep identifiers out of your working files and your writing. Work with the minimum data necessary under your organization's rules, aggregate in anything you write, and never carry a line-level extract with identifiers into a course submission. Say in the plan how de-identification is handled, because a doctoral reader will look for it.
Five mistakes that cost points in this week's territory
- A measure with no denominator rule. Numerators are easy. Without a written eligibility rule, your baseline and your follow-up are counting different populations and nobody will notice until it matters.
- Outcome only. Without a process measure, a null result cannot be interpreted, and interpreting it anyway is the most common overreach in DNP project reporting.
- Definitions that need a human judgment with no rule attached. Adequately documented is not a definition. If a reader is involved, specify the rule and what happens on disagreement.
- No test of the extract. Assuming a field contains what its label suggests is the single most expensive assumption available in a project like this.
- Statistical machinery bolted onto an improvement design. A p value on a two-point comparison at one organization does not strengthen the argument and will be challenged.
Before you submit
- The aim statement contains a target and a time window
- Every measure has a numerator rule, a denominator rule and written exclusions
- The set includes at least one process measure and one balancing measure
- Each measure names a source system and a specific field
- The extract has been tested on historical data and the result is described
- The baseline is described by periods and variation, not by a single figure
- Data handling and de-identification are stated explicitly
Building the NR-705C measurement plan?
Send the rubric, your aim and what you know about your data sources out of Canvas. A premium original draft comes back in 24 to 48 hours with operational definitions written to be reproducible and the measure set built properly, revised free until it lands. Hours, logs and site evaluations are never part of the work.