| Course | NU803 Change Management and Clinical Data Analysis |
|---|---|
| Unit | Unit 5 |
| Paper type | Measurement plan |
| Length | About 840 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | Doctor of Nursing Practice (DNP) |
| Updated | September 2026 |
Free sample paper for NU803 Unit 5
Down to the Edge Cases: A Measurement Plan Defining Seven Measures for Afternoon Glucose Checks on Steroid-Treated Inpatients, Each With a Numerator, Denominator, Source, Collector and the Situations That Break Most Definitions
[Student Name]
Purdue University Global
NU803: Change Management and Clinical Data Analysis
Unit 5 Measurement Plan
[Instructor Name]
[Date]
The units, systems and schedules are composite; thresholds and times are bracketed.
Why Edge Cases Matter
A measure is only as good as its definition in unusual situations. If two people counting the same week of data would disagree about whether a day counts, the measure cannot show change reliably. The plan uses Donabedian's categories of structure, process and outcome (Donabedian, 1988), adds a balancing measure, and for each measure states what counts, what does not and who decides.
Measure 1: Trigger Coverage (Structure)
Numerator: qualifying steroid orders, at [20] mg a day or more in prednisone terms, that generated glucose check orders within [one] hour. Denominator: all qualifying steroid orders on either unit, from the pharmacy's order file. Source: pharmacy and order-entry records. Collector: informatics analyst, weekly. Edge cases: a dose increased from below to above the threshold mid-stay counts as a new qualifying order on the day of the increase; orders from the oncology and emergency order sets are included in the denominator even though the trigger is not yet built there, so the measure shows the gap rather than hiding it.
Measure 2: Pre-Lunch Check Completion (Process)
Numerator: eligible steroid days with a capillary glucose reading between [1030] and [1200]. Denominator: eligible steroid days on which the patient was on the unit at [1100]. Source: glucometer export linked to bed census. Collector: project lead, weekly. Edge cases: patients discharged before [1100] are excluded that day; patients transferred onto the unit after [1200] are excluded that day; patients not eating still need the check, since the steroid effect does not depend on the meal.
Measure 3: Pre-Dinner Check Completion (Process)
Defined in the same way, with a window of [1500] to [1700] and presence on the unit at [1600]. Reported separately from Measure 2, because the change model and framework analyses predicted different barriers at the two times.
Measure 4: Escalation (Process)
Numerator: qualifying episodes followed by a page to a prescriber within [two] hours. Denominator: qualifying episodes, defined as two capillary readings above 216 mg/dL within [24] hours. Source: glucometer export, paging log and nursing notes. Collector: project lead, weekly. Edge cases: a repeat reading taken within [15] minutes of a high one to confirm it counts as one reading, not two, so a single confirmed high does not create an episode; an episode that spans midnight is assigned to the day of the second reading.
Measure 5: Scheduled Insulin After Escalation (Process)
Numerator: escalations followed within [24] hours by a new order for NPH or other scheduled insulin, or an increase in an existing scheduled dose. Denominator: escalations. Source: order records. Collector: project lead, weekly. Edge case: an escalation in a patient already on basal insulin counts as answered if the dose was increased.
Most disagreements about whether a change worked turn out to be disagreements about what was counted, and they are cheapest to settle before the first week of data.
Measure 6: Hyperglycemic Monitored Days (Outcome)
Numerator: monitored steroid days with any capillary reading above 250 mg/dL. Denominator: monitored steroid days, meaning eligible days with at least two readings, one of them after [1100]. Expressed per 100. Source: glucometer export. Collector: project lead, weekly. Edge cases: a reading uploaded late because a meter docked days after use is counted in the week the reading was taken, and weekly extraction therefore waits [three] days after the week closes; laboratory serum glucose values are not counted, because they are drawn at different times and would change the meaning of the measure; confirmatory repeats within [15] minutes count once.
Measure 7: Low-Glucose Days (Balancing)
Numerator: steroid days, plus the [two] days after the last steroid dose, with any capillary reading below 70 mg/dL. Denominator: the same days. Expressed per 100. Source and collector as for Measure 6. Edge cases: including the two days after the last dose captures lows caused by insulin that outlasts a stopped or tapered steroid, which is the harm the bundle is most likely to cause; a repeat reading within [15] minutes of a low counts once.
Displaying the Measures
All seven will be plotted weekly on run charts with baseline medians where baseline data exist, following the principle that data for improvement should be displayed over time rather than summarized as two averages (Provost & Murray, 2022). Rules for detecting change will be those set in the proposal's evaluation plan, drawn from published run chart guidance (Perla et al., 2011).
Testing the Definitions
Before implementation, two reviewers, the project lead and a clinical nurse specialist, will separately apply the definitions to the same two baseline weeks independently. Any day on which they disagree will be discussed and the definition sharpened until agreement is complete.
References
Donabedian, A. (1988). The quality of care: How can it be assessed? JAMA, 260(12), 1743-1748. https://doi.org/10.1001/jama.1988.03410120089033
Perla, R. J., Provost, L. P., & Murray, S. K. (2011). The run chart: A simple analytical tool for learning from variation in healthcare processes. BMJ Quality & Safety, 20(1), 46-51. https://doi.org/10.1136/bmjqs.2009.037895
Provost, L. P., & Murray, S. K. (2022). The health care data guide: Learning from data for improvement (2nd ed.). Jossey-Bass.
NU803 Unit 5 instructions, in plain terms
The Unit 5 assignment asks you to define exactly how each measure in your project will be produced. Most versions want, for each measure, a numerator and denominator, inclusions and exclusions, the data source, the person who collects it and the schedule, with attention to situations that could make counts inconsistent. Around 1,500 words, often with a table, is common. Faculty reward plans that anticipate edge cases before data arrive, report process measures separately where barriers differ, name a second collector or reviewer, and test the definitions on real data. A measurement plan differs from an evaluation plan: it settles how each number is produced, not which result would count as success.
How this NU803 Unit 5 example is built
The plan opens by explaining why edge cases matter and organizing measures by structure, process, outcome and balancing. Trigger coverage includes order routes the trigger does not yet reach, so the gap stays visible. Pre-lunch and pre-dinner checks are defined separately, with rules for discharges and transfers. Escalation treats confirmatory repeats as one reading and assigns midnight-spanning episodes to a day. Scheduled insulin counts dose increases. The highlighted sentence argues that disagreements are cheapest to settle before data arrive. The outcome handles late uploads and excludes serum glucose. The balancing measure extends two days past the last dose. Display rules and a two-reviewer test close the plan.
Reading the NU803 Unit 5 grading rubric
Measurement plans are generally scored on precision, completeness, feasibility, reliability and alignment. Precision earns credit when every measure has a numerator, denominator and explicit inclusions and exclusions. Completeness rewards coverage of structure, process, outcome and balancing. Feasibility is judged on named sources, collectors and schedules that a project can sustain. Reliability is credited when edge cases are defined and definitions are tested by more than one person. Alignment scores well when measures match those promised in the proposal and evaluation plan. A table summarizing each measure is expected in most sections, with the narrative reserved for edge cases.
NU803 Unit 5 help: mistakes that cost points
A common weakness is defining a measure in one sentence and leaving its edge cases to be decided later, when the data are already in. Another is combining process measures that face different barriers. Some plans rely on a single collector, so measurement stops when that person is busy or leaves. Others include sources that do not yet exist. Many forget to test definitions on real data. And balancing measures often stop at the last day of treatment, missing delayed harm. Write out each numerator and denominator, list the situations that could confuse a counter, name two people, and have them apply the rules to the same data before go-live. Finally, date each definition and record every change to it, so any shift on the chart can be checked against the rules in force that week.
Get an NU803 Unit 5 example written to your instructions
Whatever you know about where each number lives is enough to start, alongside your measures as they stand and the Unit 5 instructions and rubric. The first custom sample, free and back within 24-48h, turns them into a data dictionary with numerators, denominators, edge-case rules, sources and collectors, site specifics bracketed until you supply them. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More NU803 papers and DNP samples
- NU803 Unit 1: Change Model Application, Lippitt
- NU803 Unit 2: Readiness Assessment, Nine Conditions
- NU803 Unit 3: Discussion Post, A Change That Faded
- NU803 Unit 4: Stakeholder Analysis, Who Pays
- NU803 Unit 6: Baseline Data Summary
- NU803 Unit 7: Run Chart Interpretation
- NU803 Unit 8: Statistical Analysis Write-up
- NU803 Unit 9: Seminar Reflection
- NU803 Unit 10: Sustainability Plan
- NU800 Unit 5: Evidence Synthesis, Steroid Glucose
- NU753 Unit 5: Theory Application, Open Systems
- NU703 Unit 5: Literature Synthesis, DNP Role Use
- NU743 Unit 5: Decision Tree, Appendicitis
NU803 Unit 5 questions, answered
How is a measurement plan different from an evaluation plan?
An evaluation plan decides which measures matter and what result would count as success. A measurement plan decides exactly how each number is produced, down to exclusions, sources and timing. Many projects need both, and some sections merge them. The sample treats this unit as the second kind, inheriting its measures from the proposal and defining each one operationally.
Why do edge cases matter so much?
Because they are where rates quietly change. If one week's data pull counts a repeat reading as a second low and the next week's does not, the chart moves without anything on the units changing. Written rules for repeats, transfers and late uploads keep the number stable, which is why the sample spends a page on them.
Can the writer collect the observed measures personally?
Often, early on, but a plan that depends on one person tends to stop when that person leaves. Name a second collector wherever possible and check that the two agree. The sample pairs the writer with a trained peer auditor, scores ten meals together to compare timings, and names who continues the audit after the project ends.
Where can I find a free NU803 Unit 5 sample paper?
This page holds the full NU803 Unit 5 measurement plan, with seven measures each defined by numerator, denominator, source, collector and edge cases, display rules and a two-reviewer test, with three references. Drafting help for definitions of your own measures is available.
Why count a repeat reading once in NU803 Unit 5?
A second reading taken within fifteen minutes to confirm a high or low is not new information. Counting it twice would turn a single confirmed value into an escalation episode or a double low, moving the chart without anything changing on the unit.