NR-652 Week 4 Results Analysis and Findings: How to Write It

What NR-652 Week 4 asks for

On a subacute unit inside a hospital-affiliated skilled nursing facility, a student finished her measurement period with 63 eligible admissions, 58 of which had complete records, a delivery rate that started low and climbed, an outcome measure that moved in the right direction by an amount smaller than her aim, and a balancing measure showing that the new step added time at a shift where time was already scarce. All of that is a good results section. It is also, written badly, a paragraph of adjectives about how the project went well overall. The stage asks you to turn the first into prose that a stranger could audit.

The organizing principle is flow. A reader needs to know how many events were eligible, how many were included, how many were excluded and why, before any number about them can be interpreted. Improvement and evaluation reporting conventions put this first for good reason: a favourable outcome computed on a denominator that quietly shed a third of its cases is not a favourable outcome. Write the flow explicitly, in the text and ideally in a small table, and account for every case between eligible and analyzed.

The second principle is order. Results are reported in the order the evaluation questions were asked, which is usually delivery first, then process, then outcome, then balancing. This ordering carries an argument by itself: it tells the reader that the intervention happened before it tells them what followed, which is the only sequence in which the outcome number is meaningful. Reordering to put the best result first is the most common temptation at this stage and it is visible to any experienced reader.

The third is silence. No because, no suggests, no demonstrates, no unfortunately. A results section that contains interpretation forces the reader to evaluate your reasoning before they have finished absorbing your data, and it usually means the discussion section that follows will repeat itself. Deliverables at this stage typically include the written results with tables or figures, and where a discussion runs alongside, post final copy since contributions do not reopen after submission in Canvas.

Boundary setting: the numbers must be the numbers

Two boundaries govern a results stage. The first is unchanged from the rest of the practicum: hours, hour logs, activity or encounter documentation, attendance verification and every preceptor, mentor, sponsor or faculty evaluation are your own record, produced by you, and never drafted, reconstructed or estimated with outside help.

The second is about the data itself, and it is absolute. The figures in your results are the figures your project produced. Nobody supplies them, improves them, smooths them or fills a gap in them. Legitimate help at this stage is help with structure, table design, precision of language, ordering, and the discipline of keeping interpretation out of the results. Where a number is missing, the correct action is to report it as missing. Where a period was not audited, the correct action is to say it was not audited. A results section with an honest hole is a scholarly document; a results section with an invented figure is misconduct that follows a nurse a long way.

De-identification and data governance still apply. Report aggregates, suppress or combine any cell small enough to identify a resident or a staff member, keep identifiable data inside authorized systems, and describe cases by clinical relevance rather than by detail. If a single case must be described to illustrate a mechanism, alter every non-essential feature and say that details have been changed.

The NR-652 Week 4 method, step by step

Six moves for writing results that a careful reader can audit.

1. Write the flow before anything else

   Eligible events, excluded with reasons and counts, included, analyzed. Every case accounted for. If the flow does not add up, stop and reconcile before writing another sentence, because everything downstream inherits the error.

2. Report the period and the context in plain numbers

   Baseline dates, implementation dates, unit and setting, volume per week, and any external event that occurred inside the window. Context here is factual reporting, not explanation, so keep it to what happened rather than to what it might have caused.

3. Give delivery before outcome

   Fidelity by component with counts and denominators, and the trajectory over time if you have it. This is what allows a reader to weigh the outcome result correctly, and putting it first removes the need for you to argue the point later.

4. Report each measure the same way every time

   Numerator, denominator, period, and the value, with the same number of decimal places and the same units throughout. Consistent presentation lets a reader compare across measures without recalculating, and inconsistency reads as carelessness even when the numbers are right.

5. Build tables that stand alone, then describe them without repeating them

   A table needs a number, a title, defined column headers, units and a note explaining abbreviations. The text should point to the table and highlight the one or two features a reader might miss, not restate every cell in sentences.

6. Report the unfavourable results with the same care as the favourable ones

   Balancing measures, missed periods, components that were never delivered, and outcomes that did not move. Give them their own sentences in their proper place in the order. A results section that reports only good news is not read as good news; it is read as incomplete.

A layout and word budget for a capstone results section

Our frame for the results component of a capstone report, sized for roughly 1,100 to 1,500 words plus tables and figures. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.

Evidence craft for results writing

Counts first, rates second, always with the period. Eleven of 58 admissions over an eight-week implementation period gives a reader everything. Nineteen percent gives them a figure they cannot weigh, and in small settings the difference between those two presentations is the difference between honest and misleading.

Match precision to the data. Reporting a rate to one decimal place on a denominator of 58 implies precision the sample cannot support. Whole numbers or one decimal at most, applied consistently, and no percentages at all where the denominator is under about twenty.

Follow an established reporting structure for improvement work. Published reporting guidelines for quality improvement and evaluation projects exist and specify what a results section should contain, including context, flow, fidelity and unintended consequences. Naming the guideline you followed and citing it tells a graduate reader you know the genre.

Describe figures in words for the reader who cannot see them. A sentence saying that the measure held between two stated values across the baseline weeks and then ran above the baseline centre line for a stated number of consecutive weeks after go-live conveys the chart. Referring to the figure without describing it leaves your argument dependent on an image.

Keep every evaluative word out. Improved, disappointing, encouraging and unfortunately all belong in the discussion. The results section says what the number was and when, and its authority comes precisely from that refusal.

Five mistakes that cost points in this week's territory

• Interpretation inside the results. The most common structural error at this stage, and it costs points in two sections rather than one.
• An unexplained denominator. Cases that vanish between eligible and analyzed undermine every figure that follows them.
• Percentages on tiny numbers. A rate built on six events looks authoritative and is nearly meaningless without the count beside it.
• Tables that repeat the text. If the paragraph restates every cell, one of the two is wasted space and both will be read as padding.
• Balancing measures omitted. Leaving out what the change cost is the omission experienced readers look for first.

Before you submit

• Every eligible case is accounted for between eligibility and analysis
• Delivery and fidelity are reported before any outcome
• Each measure carries numerator, denominator, units and period
• Precision and decimal places are consistent and proportionate to the sample
• Tables are numbered, titled and self-explanatory, and the text does not repeat them
• Balancing measures and missing data appear in their proper place
• No sentence in the section explains, justifies or evaluates a result

Questions students ask about this stage

Keep going