Around the midpoint of a capstone practicum the data arrives and has to be reported. NR-643 Week 4 in our arc is the results section: presenting what the measures showed, with their bases and periods, in tables and figures that are readable, and in prose that describes rather than interprets. The discipline of this stage is restraint. Meaning belongs to the next section. Your section may print this as NR 643 or NR643; 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-643 Week 4 asks for
A run chart of barcode scan rates on a surgical floor is a strange object the first time you build one. Twelve weekly points, a centerline, and a step that appears three weeks after go-live rather than immediately, which is the part everyone wants to explain and nobody should explain yet. The results section reports that the step occurred, where, and by how much. Why it lagged is the next stage's work, and mixing the two is the single most common structural fault in practice project write-ups.
A results section in a practice improvement project has a predictable set of components. The population or denominator actually observed, which is often smaller than planned. The baseline. The post-change values. Process measures showing whether the change happened at all. Balancing measures. Any data that was missing, excluded or unavailable, with the reason. And presentation choices that let a reader see the pattern rather than take your word for it.
Time-series presentation deserves special attention in this specialty. Improvement data is usually a series rather than two points, and a run or control chart shows things a before-and-after comparison hides: whether the process was already moving before you touched it, whether the change held, and whether variation is ordinary or unusual. If your data has enough points, a series is almost always the more honest presentation and it is well established in the improvement literature.
Deliverables at this depth are typically a written results section with tables or figures, sometimes with a posted summary of the headline finding. Posts do not reopen in Canvas after submission, so report the figure you can defend rather than the one you hope holds when the last week of data arrives.
The NR-643 Week 4 method, step by step
Six moves for reporting results without interpreting them.
-
Report what you actually observed, not what you planned to
Open with the real denominators: how many administrations, records, encounters or staff were in each period. Planned samples and achieved samples differ in almost every practicum project.
-
Account for every excluded case
How many were removed, on what criterion, decided before or after you saw the data. Exclusions applied after looking are a genuine source of bias and readers ask about them.
-
Present the series before the summary statistic
Show the pattern over time first. A single before-and-after difference computed from a series that was already trending is a number that will not survive a careful reader.
-
Pair every rate with its numerator and denominator
In the table, not only in the text. Percentages alone conceal whether a change of eight points came from four cases or four hundred.
-
Report process and balancing measures alongside outcomes
Same section, same prominence. A results section that presents only the outcome measure has already begun making an argument, which is the next section's job.
-
Write the prose as description only
Increased from, remained at, varied between. No because, no suggests, no demonstrates. Save every causal word for the interpretation section where it can be defended.
A layout and word budget for a results section
Our frame for reporting practice project results, sized for roughly 1,000 to 1,300 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.
| Section | What belongs in it | Word target |
|---|---|---|
| Observed population | Actual denominators for each period, how they compare to plan, and any change in the population itself. | 150 to 190 |
| Data completeness | Missing, excluded and unavailable data with counts and reasons, and when each rule was decided. | 140 to 180 |
| Delivery results | Whether the change was delivered and used, reported before any outcome appears. | 190 to 240 |
| Primary outcome results | Baseline and post values with bases and periods, presented as a series where the data supports one. | 250 to 320 |
| Unintended-effect results | What was watched for unintended cost and what it showed, including where it showed nothing. | 140 to 180 |
| Tables and figures | Each one self-explanatory, with a caption stating what is shown, for whom, and over what period. | Captions plus 100 to 140 |
Evidence craft for reporting results
Every figure needs a period. Scan rate rose from 71 percent to 86 percent means nothing without knowing that the first covers eight weeks before go-live and the second covers six weeks after. Periods belong in the sentence and in the caption.
Make tables independent of the prose. A reader should be able to understand a table without the paragraph beside it, which means full column headers, units, denominators and a caption that says what is being shown and for which population.
Do not smooth the ugly weeks. If a measure dropped during a staffing crisis, the drop stays in the series. Removing inconvenient points is data manipulation, and the alternative is simply to note the event on the chart and address it in interpretation.
Be careful with statistical language. Most practicum projects do not have designs that support inferential testing, and applying a test to two convenience samples produces a number that misleads more than it informs. Where you do use statistics, name the test and say why it fits. Where you do not, descriptive reporting with a clear series is entirely respectable.
Suppress small cells. A breakdown that leaves a category with very few cases can identify a person. Collapse it or suppress it, and say in a note that you did and why.
Where help stops in a practicum course
NR-643 carries 72 clinical hours in a mentored capstone practicum and the boundary is absolute. Your hours, your logs, your activity records, your mentor's evaluation and every signature attached to any of it are your own record of your own work, never drafted, reconstructed, estimated or completed with outside help. Nothing on this page is a route to producing documentation a mentor, a site or the university verifies.
A second boundary is specific to this stage and is at least as important. Patient-level data, identifiable extracts, live system reports and credentials of any kind never leave your organization and are never shared with anyone outside it, including anyone helping with your writing. The written layer that can be supported is the presentation: how to structure a results section, how to build a table that stands alone, how to caption a figure, how to keep causal language out of descriptive prose. Any figures shared for that purpose should be aggregated counts and rates with no identifiers of any kind.
De-identification governs everything reported here. Report at the level of counts and rates, never records. No names, no record numbers, no dates of service, and no cell so small that an individual patient or staff member could be inferred from it. If a category cannot be reported safely, collapse it and note the suppression rather than publishing a number that identifies someone.
Five mistakes that cost points in this week's territory
- Interpretation inside the results. A single because sentence in a descriptive section collapses the structure the rubric is scoring.
- Percentages without bases. A fifteen-point change from a denominator of twelve is a very different claim from the same change across four hundred cases.
- Two points instead of a series. A before-and-after pair cannot show whether the process was already moving, and improvement readers assume the worst when a series was possible.
- Outcome-only reporting. Omitting process and balancing measures makes the section an argument rather than a report.
- Unexplained missing data. Counts that shrink between periods with no explanation are the fastest way to lose a reader's trust entirely.
Before you submit
- Actual observed denominators appear for every period
- Missing, excluded and unavailable data are counted with reasons and timing of the rule
- Process measures are reported before outcome measures
- Every rate appears with its numerator, denominator and period
- Time-series data is presented as a series wherever the points allow
- Balancing measures appear even when they showed nothing
- Tables and figures are readable without the surrounding prose
- No causal or interpretive language appears anywhere in the section
Reporting results for NR-643?
Send the rubric and your aggregated, de-identified figures out of Canvas, never patient-level data. A premium original draft of the written layer comes back in 24 to 48 hours with bases attached and interpretation kept out of the description, hours and logs left entirely to you, and revisions run until the grade lands.