NUR 675 Module 7 Milestone Three Example

Reviewed by Delia Ravenscroft, MSN, RN

This NUR 675 Module 7 Milestone Three sample shows how to plan a quality improvement project so that it can be carried out, measured and reported within a practicum. It is written for SNHU NUR 675 (NUR-675), the MSN seminar that prepares students for the practicum. A composite MSN student will test a scheduled toileting and medication review program on night shifts to reduce falls on a medical-surgical unit. The plan uses the Model for Improvement described by Langley and colleagues to state the aim, the measures and the change, then lays out a first Plan-Do-Study-Act cycle on two rooms followed by a larger cycle across the unit. Outcome, process and balancing measures will be tracked weekly on run charts using the rules Perla and colleagues explain. From day one, notes follow SQUIRE 2.0 headings.

CourseNUR 675 MSN Seminar: Preparation for Practicum
ModuleModule 7
Paper typemilestone project plan for a quality improvement practicum
LengthAbout 1,050 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMSN
UpdatedSeptember 2026

Free sample paper for NUR 675 Module 7

1

Milestone Three: A Practicum Project Plan Built for PDSA Cycles and SQUIRE 2.0 Reporting

[Student Name]

Southern New Hampshire University

NUR 675: MSN Seminar: Preparation for Practicum

Module Seven Milestone Three

[Instructor Name]

[Date]

What this page is doingThe title names the method for doing the work and the standard for reporting it, both of which shape the plan.
2

Milestone Three: A Practicum Project Plan Built for PDSA Cycles and SQUIRE 2.0 Reporting

Many practicum projects falter not because the idea is poor but because the plan is vague: no clear aim, no measures chosen in advance, a single large rollout that cannot be adjusted and a final report pieced together from memory. The student in this paper will test a change to reduce night-shift falls on a medical-surgical unit at a composite hospital, where most falls involve patients getting up alone to use the bathroom, often after sedating medications. The evidence review favored toileting schedules and medication review over bed alarms. This milestone presents the project plan. It argues that framing the project with the Model for Improvement, testing in small cycles, measuring process and outcome from the start and documenting according to a reporting standard will make the project achievable and its results credible.

What this page is doingThe introduction names common reasons practicum projects falter and states the plan's approach.
3

The Model for Improvement

Langley et al. (2009) set out an improvement approach built on three guiding questions, about the aim, the evidence that will show progress and the change worth trying, combined with rapid small-scale testing. Each test runs through a Plan-Do-Study-Act loop: the team writes down what it expects, tries the change on a handful of patients, compares the results with its expectation and then keeps, modifies or drops the change. The strength of the approach for a practicum is that small tests produce learning quickly and cheaply and let the team adjust before a larger rollout.

For this project, the aim is to reduce night-shift falls on the unit from a baseline of 4.1 per 1,000 night patient days to 2.5 by the end of the twelve-week practicum. The change is a program in which nurses offer toileting to every high-fall-risk patient at 10 p.m., midnight, 2 a.m. and 4 a.m. and in which the evening charge nurse, pharmacist and admitting provider review sedating medications on admission and each evening.

What this page is doingThe Model for Improvement's questions and PDSA cycles are explained and applied to state the aim and change.
4

Testing in Cycles

The first cycle will run for one week on four rooms with high-risk patients. The prediction is that nurses will complete at least 80% of scheduled toileting rounds and that no patient in those rooms will fall. The student will observe two nights, collect round completion sheets and interview the nurses at the end of the week. If completion is low, the cycle will study why, for example whether rounds collide with medication passes, and adapt the schedule. The second cycle will expand to the whole unit for three weeks with the adapted process, and the medication review will be added. A third cycle, if time allows, will test ways to sustain the process, such as adding the round schedule to the electronic task list. Each cycle's prediction, results and decision will be recorded on a one-page form.

Staff will be involved from the start. Before the first cycle, the student will meet with the night nurses on the four test rooms to explain the change, ask what might get in the way and adjust the round times if they clash with other work. Their suggestions, and the reasons behind any changes, will be recorded in the project log.

What this page is doingSpecific PDSA cycles are planned with predictions, data collection and decision points.
5

Measures

Table 1 lists the measures. The outcome measures reflect the aim, the process measures show whether the change is actually happening and the balancing measures check that the change is not causing harm elsewhere, such as interrupting sleep, which can itself increase delirium and falls.

Table 1. Project Measures and Operational Definitions

TypeMeasureOperational definitionSource and frequency
OutcomeNight-shift fallsFalls on the night shift, per 1,000 night patient daysIncident reports and chart review, weekly
OutcomeInjurious night fallsNight falls with any injury per 1,000 night patient daysIncident reports, weekly
ProcessToileting round completionCompleted rounds divided by scheduled rounds for high-risk patientsRound sheets, nightly
ProcessMedication review completionHigh-risk admissions with documented evening medication reviewChart audit, weekly
BalancingPatient sleep disruptionPatients reporting that rounds disturbed their sleepBrief morning survey, sample of five patients weekly
BalancingNurse workloadNurses rating the rounds as unmanageableEnd-of-shift question, weekly

Note. Balancing measures watch for unintended effects, such as disturbed sleep, that could undermine the change.

What this page is doingThe table defines outcome, process and balancing measures with sources and frequency.
6

Displaying and Interpreting Data

Because the unit has relatively few falls each week, weekly fall rates will vary a great deal by chance. Perla et al. (2011) describe run charts, which plot data over time around a median, and give a handful of simple rules, based on runs of points above or below the median and on steady climbs or drops, for telling a real signal from noise. The project will plot twelve months of baseline data and then weekly data during the practicum on run charts for each measure. Process measures, which change quickly, will be interpreted first; the outcome measure will be interpreted cautiously, since a twelve-week window gives a rare event little room to show a dependable shift.

Data collection has been kept light so that it does not become a burden that staff resent. Round completion sheets take seconds to mark, the morning sleep question is asked by the day nurse during routine rounds and the chart audit is done by the student.

What this page is doingRun charts and rules for signals guide interpretation, with caution about rare outcomes over a short period.
7

Documenting for SQUIRE 2.0

Ogrinc et al. (2016) produced SQUIRE 2.0, a consensus standard for writing up improvement projects. In plain terms, a SQUIRE report explains why the problem mattered and what was already known, why the team expected its change to help, what the local setting was like, what was actually done and how it shifted along the way, how the effects were studied and measured, what the numbers showed, including anything unexpected, and what the team concluded, with limits and ethical points. Knowing these elements from the start changes what the student records. She will keep a project log noting context, such as staffing changes and other initiatives on the unit, each PDSA decision and its reasons and any unexpected effects. At the end, the final practicum report will follow the SQUIRE headings, drawing directly on the log, run charts and cycle forms.

What this page is doingSQUIRE 2.0 elements shape documentation from the start, making the final report straightforward.
8

Conclusion

The project has a clear aim, a change grounded in evidence, small tests that allow adjustment, measures defined in advance with balancing checks, run charts to read the data honestly and documentation organized for a recognized reporting standard. With these in place, the practicum can produce both a useful test of change for the unit and a credible account of what was learned.

What this page is doingThe conclusion summarizes the plan's elements and what they allow the practicum to produce.
9

References

Langley, G. J., Moen, R. D., Nolan, K. M., Nolan, T. W., Norman, C. L., & Provost, L. P. (2009). The improvement guide: A practical approach to enhancing organizational performance (2nd ed.). Jossey-Bass.

Ogrinc, G., Davies, L., Goodman, D., Batalden, P., Davidoff, F., & Stevens, D. (2016). SQUIRE 2.0 (Standards for QUality Improvement Reporting Excellence): Revised publication guidelines from a detailed consensus process. BMJ Quality & Safety, 25(12), 986-992. https://doi.org/10.1136/bmjqs-2015-004411

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

What the NUR 675 Module 7 instructions ask for

Milestone Three in NUR 675 usually asks for a detailed plan for the project you will carry out in the practicum, including methods, measures and how results will be analyzed and reported. Expect five to seven pages in APA 7, often with a measures table. State a specific aim with a baseline and target, describe the change and how it will be tested in small cycles with predictions, define outcome, process and balancing measures precisely, explain how data will be displayed and interpreted given small numbers and describe how you will document context and decisions so that your final report meets a recognized standard such as SQUIRE 2.0. Keep data collection light enough for staff to sustain.

How this NUR 675 Module 7 milestone three example is built

This milestone plans a composite student's night-shift falls project. The Langley Model for Improvement frames an aim to lower night falls from 4.1 to 2.5 per 1,000 night patient days with scheduled toileting and evening medication review. A first PDSA cycle on four rooms predicts 80% round completion before expanding unit-wide. A table sets out outcome, process and balancing measures, among them patients' sleep. Run charts follow Perla and colleagues, with caution about a rare outcome over twelve weeks, and a project log is organized around the Ogrinc SQUIRE 2.0 headings. Data collection is designed to take staff only seconds. Night nurses shape the first cycle.

Where the NUR 675 Module 7 rubric puts the points

Grading of project plans commonly weighs the clarity of the aim, the rationale for the change, the design of tests, the quality and definition of measures, the analysis plan, documentation and APA 7 writing. Top-band plans state predictions for each test cycle, define every measure operationally and include balancing measures. Graders reward realistic interpretation plans that account for small numbers and short time frames, and documentation designed around a reporting standard. Plans that show how the change could be sustained after the practicum demonstrate awareness of what happens when the student leaves. Light, sustainable data collection is noticed and valued. Involving frontline staff in designing each test cycle is also valued by graders.

NUR 675 Module 7 help: the mistakes that cost points

Project plans lose points when aims lack baselines or targets, when changes are rolled out all at once without testing, when measures are named but not defined, when balancing measures are missing or when results will be judged by before-and-after comparison of a rare outcome. Another gap is starting documentation at the end. State a measurable aim, test in cycles with predictions, define measures, add balancing measures, use run charts and document context from day one. If your project involves education, a new workflow or a technology change, send it with your NUR 675 prompt so the plan fits. Keep data collection light. Involve the staff who will run the change.

Get NUR 675 Module 7 written to your instructions

Share your practicum project, site data and the NUR 675 grading criteria. The plan you receive will state a measurable aim, design PDSA cycles with predictions, define outcome, process and balancing measures and set up documentation for SQUIRE reporting, within 24 to 48 hours, free the first time. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.

More NUR 675 papers and related MSN samples

NUR 675 Module 7 questions, answered

Where can I find a free NUR 675 Module 7 Milestone Three sample?

This page carries the full plan: a falls project with an aim, PDSA cycles, outcome, process and balancing measures, run charts and SQUIRE 2.0 documentation.

What are the three questions of the Model for Improvement?

What are we trying to accomplish, how will we know a change is an improvement and what change can we make that will result in improvement?

What is a balancing measure?

It watches for side effects of a change, such as overnight rounding that disturbs sleep.

What is SQUIRE 2.0?

Guidelines for reporting quality improvement work, covering the problem, rationale, context, intervention, measures, results and limitations.

Why use run charts in a practicum project?

They show data over time and help distinguish real change from random variation, which matters when numbers are small.