D159 Evidence-Based Measures for Evaluating Healthcare Improvements, catalog number NURS 6435, is a two-CU course in the MSN Leadership and Management specialty on determining the key performance indicators and metrics that define success for a healthcare improvement project. It is the course that decides whether the capstone will have anything to report, because a project measured badly cannot be evaluated well no matter how successful it was.
What NURS 6435 is actually testing
A key performance indicator is not a hope with a number attached. It is a defined quantity, computed the same way every time, that moves when the thing you care about moves and does not move when it does not. Building one is a technical exercise, and this course is testing whether you can do it.
The core skill is specification. Numerator, denominator, inclusion and exclusion rules, data source, collection frequency, and who computes it. A measure that cannot be handed to someone else and computed identically is not a measure, it is a description. Most student measures fail this test on the exclusion rules, which is where the awkward cases live.
The second skill is choosing a balanced set. Improvement measurement uses several kinds at once. An outcome measure says whether the thing you wanted happened. A process measure says whether the change you made is actually being done. A balancing measure watches for harm caused by the improvement itself. Projects measured only on outcome cannot tell a failed intervention from an intervention nobody adopted, which is the single most common analytic failure in healthcare improvement.
The third is evidence. The catalog says evidence-based measures, which means your indicators should where possible be ones the field already uses, with published definitions and comparison data, rather than ones you invented. An invented measure is unbenchmarkable and usually harder to defend.
Turning scored aspects into a section plan
Rubric detail lives in your Course of Study rather than in the catalog. Count the aspects first. Each is scored on its own against a three-point scale and each needs a 2, so a well-specified outcome measure will not carry a missing balancing measure.
The word budget, worked. Assume five scored aspects and directions asking for roughly 1,500 words alongside any required measure table. Reserve 110 for an opening restating the project and its aim, and 90 for the close, leaving 1,300 across five aspects, or 260 each. Then weight it. The specification aspect deserves 380, since each measure needs its full definition. The analysis plan aspect deserves 300, because how the data will be examined over time takes room. That leaves 620 for three aspects at about 207 each.
Write the aim statement first and make it numeric. Reduce X from A to B among population C by date D. Every measure in the paper then has a clear job, and measures that do not serve the aim become visibly unnecessary.
A structure that fits a measurement plan
Task directions govern where they specify a format. Where they do not, this arrangement produces a plan the capstone can actually report against.
| Section | What belongs in it | What earns the aspect |
|---|---|---|
| Aim statement | The improvement expressed numerically with a population and a date | A number and a deadline, since an aim without both cannot be evaluated |
| Measure set | Outcome, process and balancing measures listed together | All three kinds present; outcome alone is not a set |
| Specification | For each measure: numerator, denominator, exclusions, source, frequency, owner | Sufficient detail for someone else to compute it identically |
| Evidence for the measures | Where each measure comes from and who else uses it | Published definitions preferred over invented ones |
| Baseline | Current performance, with the period it covers and its variation | Variation shown, since a single prior figure cannot establish a baseline |
| Target and rationale | The target value and why that value rather than another | A rationale from benchmark, evidence or capacity, not a round number |
| Analysis plan | How data is examined over time and what counts as a real change | Distinguishing signal from ordinary variation |
| Reporting | Who sees the data, in what form and how often | A cadence fast enough to influence behaviour |
| Limitations | What the measure set cannot see and how it could mislead | Gaming risk named, since every measure has one |
| References | APA list of measure specifications and improvement literature | Stewards named for any published measure used |
Baseline variation deserves particular attention. Two data points cannot tell you whether a change happened, because most processes move a little every month anyway. Where you can get several periods of prior data, use them, and say what normal fluctuation looks like before claiming a shift.
Evidence craft in measurement work
Measurement claims are checkable, so precision is protective.
- Use published measure specifications where they exist, cited to their steward with a version. Paraphrasing a national definition loosely breaks comparability with everyone using it.
- State the data source for every measure and whether it is collected automatically or by hand. Hand-collected measures decay when the project champion leaves.
- Give the baseline a period and a denominator, and show variation across periods rather than a single figure.
- Justify targets from benchmark data, from published effect sizes or from capacity, and say which.
- Report absolute change alongside relative change. A halving from four events to two is a real result and a fragile one, and the reader deserves both numbers.
- Quote sparingly. Measure definitions are heavily reproduced, and WGU runs submissions through a similarity check.
Attribution is the other honest difficulty in improvement measurement and it deserves a sentence in your plan. Healthcare systems change constantly, so a number that moves during your project may have moved because of a staffing change, a seasonal pattern, a national initiative or a different project running on the next corridor. You usually cannot rule those out, and the professional response is to say what else was happening during the measurement period rather than to claim the credit silently. Evaluators reward that restraint, and it protects the credibility of the result you do claim.
The habit that most improves a measurement plan is writing the gaming paragraph. For each measure, how could this number improve without the underlying problem improving. Documentation changes, patient selection, timing of when something is counted. Naming the risk and adding a control shows an understanding of measurement that goes well beyond definition writing.
What separates Competent from a submission sent back
Aspects score independently, and specification and balancing measures are the usual returns.
- The aim is numeric with a population and a date.
- Every measure has a numerator, a denominator, exclusions, a source and a frequency.
- The set includes outcome, process and balancing measures.
- Baseline shows variation across periods rather than one figure.
- The analysis plan says what would count as a real change rather than noise.
WGU performance assessment work can be revised and resubmitted with no grade penalty, so a return costs time rather than standing. Terms run six months at a flat rate, so closing courses inside a term is what lowers the effective cost of the degree. D159 also sits immediately before the field experience and capstone, and a weak measure set here produces a capstone with nothing to report, which is a much more expensive problem than a returned assignment.
Five mistakes that cost time in D159
- Measuring only the outcome. Without a process measure you cannot tell a failed intervention from one nobody used.
- Skipping the balancing measure. Every improvement takes something from somewhere, and the aspect is watching for whether you looked.
- Specification without exclusions. The awkward cases decide what the number means, and leaving them undefined makes the measure unrepeatable.
- Targets chosen because they sound good. Twenty percent is not a rationale. Benchmark, evidence or capacity is.
- Claiming a change from two data points. Ordinary variation looks like improvement roughly half the time.
How support works on this course
D159 is technical and short, which is a good combination when the work is done in the right order. Send the rubric out of your Course of Study with the task directions and the first pass is the numeric aim, because it tells you which measures are needed and which are decoration. From there you get each measure specified to the point where a colleague could compute it unaided, published definitions located and cited to their stewards, a baseline built from several periods, a target with a real rationale, an analysis plan that separates signal from variation, and a gaming paragraph with controls.
The boundaries hold. Objective assessments at WGU are proctored, so we prepare only, never sit them, and never ask for portal credentials. On the field experience we never complete practice hours, contact mentors or sites, sign placement paperwork or fill in hour logs.
Questions students ask about D159
Is D159 the same course as NURS 6435?
How many measures should a project have?
What if my organisation does not collect the data I need?
Specifying measures for D159?
Send your Course of Study rubric and the task directions. We fix the numeric aim first, then specify every measure to the point a colleague could compute it.
Where D159 sits in WGU's programs
The July 2026 catalog places this code in 3 current WGU programs. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.