| Course | NR 500 Foundational Concepts and Applications |
|---|---|
| Week | 5 |
| Paper type | Practice problem brief |
| Length | About 1,120 words, 3 pages |
| Format | APA 7 student paper |
| School | Chamberlain University |
| Program | MSN |
| Updated | October 2026 |
Free sample paper for NR 500 Week 5
Practice Problem Brief: Vital Signs Entered Twice on a 32-Bed Medical Unit, Set Beside What Is Published About Nurses' Documentation Time
Student Name
College of Nursing, Chamberlain University
NR 500: Foundational Concepts and Applications
Instructor Name
Month Day, Year
Practice Problem Brief: Vital Signs Entered Twice on a 32-Bed Medical Unit, Set Beside What Is Published About Nurses' Documentation Time
The Problem, in One Sentence
On my 32-bed adult medical unit, nurses enter every set of vital signs twice, once in the flowsheet and again in a free-text shift note, because the note template does not pull the flowsheet values, and this double entry consumes time and produces records that sometimes disagree.
Enough About the Unit to Place It
The unit is an adult medical floor in a community hospital, staffed on day shift with six registered nurses for 32 beds and four hours of nursing assistant time per nurse. Most patients have vital signs taken every four hours, and those on the unit's early-warning protocol every two. The hospital moved to its current electronic health record five years ago. The shift note template was built at go-live, and nurses were told at the time to "summarize the vitals" in it. The instruction has never been removed, so nurses copy the latest numbers from the flowsheet into the note, often by memory, sometimes by retyping.
The Local Half
To make the problem concrete, I reviewed 20 shift notes from one week, with my manager's permission and with identifying information removed, and compared the vital signs typed into each note with the flowsheet values closest in time. In 7 of the 20 notes, at least one value in the note differed from the flowsheet: a heart rate of 88 typed as 83, a blood pressure from the previous set, a temperature rounded differently. None of these led to a wrong decision that I could find, but each is a place where a reader could. I also asked five nurses how long the vitals portion of the note takes them; their estimates ranged from 2 to 5 minutes per patient per shift. For a nurse with five patients, that is 10 to 25 minutes a shift spent retyping numbers the record already holds.
These are small samples, and nurses' time estimates are not measurements. The brief uses them to describe the problem, not to prove its size.
The Published Half
The published evidence frames the local picture in two ways. First, documentation takes a large share of nurses' time. Hendrich et al. (2008) followed 767 medical-surgical nurses in 36 hospitals with time and motion methods and reported that documentation accounted for 35.3% of nursing practice time, about 147 minutes of a shift, more than any other activity, against just 7.2% for assessing patients and taking vital signs. That study predates widespread electronic records in many hospitals, so its figures may not describe current practice, but it establishes documentation as a major use of nursing time.
Second, the burden is hard to measure well. Moy et al. (2021), reviewing 35 studies of documentation burden among physicians and nurses using electronic records, concluded that nobody yet agrees on how to measure it, and that validated instruments are missing. That finding matters for this brief: it means that a hospital wanting to show the effect of removing double entry will need to choose and define its own measure, and should say which one it chose.
Why the Problem Has Lasted Five Years
A problem this visible has survived for a reason, and the brief would be incomplete without it. No one owns the shift note template. It was built by the implementation team, which disbanded after go-live; the unit's educators assume it belongs to informatics, and the informatics team assumes the units would have asked for changes if they wanted them. Nurses, meanwhile, have absorbed the double entry into their routine and no longer notice it as a separate task, much as a detour becomes the route after enough time. When I asked colleagues why the vitals are in the note, the most common answer was "that's how we were taught."
There is also a quieter reason. Some nurses told me they like typing the vitals because it makes them look at the numbers once more before writing their summary, a kind of informal double check. That is a real benefit, and a redesign should keep it. A template that pulls the values automatically and then asks the nurse to confirm or comment on them would keep the second look while removing the retyping and the copying mistakes it invites.
What This Specialty Would Add
A bedside nurse can see the problem. What the informatics specialty adds is the ability to change the tool and to measure the change. An informatics nurse could redesign the shift note template so that it pulls the most recent vital signs automatically, remove the outdated instruction to summarize them, and test the change with nurses before it goes live. The same nurse could define the measure in advance, such as the proportion of notes with values that disagree with the flowsheet, and time spent in the note from audit data where the record provides it, and compare before and after. That combination of clinical knowledge, system knowledge and measurement is the specialty's particular contribution.
What Is Not Known
Three things are not known. How often, if ever, a disagreement between note and flowsheet has changed a clinical decision on this unit; my review found none, but 20 notes is too few to rule it out. How much time the double entry actually takes, as opposed to nurses' estimates; the record's audit data might answer this, but I have not had access to it. And whether nurses read the vital signs in the note at all, or go straight to the flowsheet; if no one reads them, the case for removing them is stronger still. Each of these is a question the redesign project would answer as part of its measurement, rather than an assumption the brief can make now.
The Size of the Ask
The change this brief points toward is small by informatics standards: a template edit, a short test with nurses on one unit, a one-page education note, and a before-and-after measure. It does not require new software or a vendor contract change. That matters for whether it will happen, because problems with small, owned solutions are far more likely to be fixed than problems that need a committee. The brief's recommendation is therefore modest and specific: assign the shift note template an owner, pilot the automated vitals pull on this unit for one month, and measure disagreement and time as defined above.
References
Hendrich, A., Chow, M. P., Skierczynski, B. A., & Lu, Z. (2008). A 36-hospital time and motion study: How do medical-surgical nurses spend their time? The Permanente Journal, 12(3), 25-34. https://doi.org/10.7812/TPP/08-021
Moy, A. J., Schwartz, J. M., Chen, R., Sadri, S., Lucas, E., Cato, K. D., & Rossetti, S. C. (2021). Measurement of clinical documentation burden among physicians and nurses using electronic health records: A scoping review. Journal of the American Medical Informatics Association, 28(5), 998-1008. https://doi.org/10.1093/jamia/ocaa325
What the NR 500 Week 5 assignment asks for
The Week 5 brief asks you to describe a practice problem related to your specialty and support it with evidence. The checklist generally covers the problem, the setting, local evidence, published evidence, why the problem persists, how your specialty can help and APA. State the problem in one sentence. Give just enough about the setting to place it. Present local evidence with its limits, such as a small review, and label estimates as estimates. Set it beside published figures from outside your unit. Explain why the problem has lasted, including any benefit people see in the current practice. Say what your specialty adds and what remains unknown. Size the change you are pointing toward.
How the NR 500 Week 5 example is put together
The problem sentence explains that the note template does not pull values from the flowsheet. The unit section describes day staffing. The local section reports a review of 20 deidentified notes from one week, with 7 disagreeing with the flowsheet, and nurses' estimates of time spent, noted as estimates. The published section cites Hendrich and colleagues' 36-hospital time-and-motion study on documentation time and Moy and colleagues' finding that burden is measured inconsistently. The persistence section explains that no one owns the template and that some nurses use retyping to review the numbers. The specialty section describes an informatics nurse redesigning and measuring the template. Unknowns follow, and the ask is a template edit and a short test.
NR 500 Week 5 rubric: what full points look like
Practice problem rubrics in NR 500 typically weigh a clear problem statement, local evidence, published evidence, analysis of causes, the specialty's contribution and APA. Combining local and published evidence is the row that decides this paper, and it earns it by setting 7 of 20 disagreeing notes beside a national time study. The problem is credited for one clear sentence. Local evidence scores for stated limits. Causes earn points when ownership and a hidden benefit are both named. The specialty row is credited because informatics can change and measure the tool. Unknowns show honesty. The ask is sized realistically. Hendrich and colleagues and Moy and colleagues complete the evidence.
NR 500 Week 5 help: mistakes that cost points
The largest loss on this brief is having no outside figure at all, with every claim about size or consequence resting on the writer's experience. Another is local data presented as proof rather than description. Students also skip why the problem persists, ignore any benefit of the current practice or propose a solution far larger than the problem. If you have no access to unit data, use published figures and describe the local problem qualitatively. The problem should be local enough to change but connected to published evidence. A practice problem is not yet a research question. Send your problem and an NR 500 brief can be built with a local half and a published half.
Get a NR 500 Week 5 example written to your instructions
Send the assignment instructions and the rubric and a custom NR 500 Week 5 brief comes back written to them inside 24-48h, the first one free. Describe your setting in general terms and lean on published figures; internal audit reports, incident data and unit dashboards belong with you and your employer, and the example is built so you can drop your own numbers in afterwards.
More NR 500 papers and MSN samples
- NR 500 Week 1: MSN Specialty Introduction Post
- NR 500 Week 2: Informatics Nurse Role Analysis
- NR 500 Week 3: Informatics Standards Review
- NR 500 Week 4: Sepsis Alert Source Evaluation
- NR 500 Week 6: Technology in Practice Brief
- NR 500 Week 7: Professional Goals Statement
- NR 500 Week 8: Closing Reflection
- NR 500NP Week 5: Case-based Application Paper
- NR 669 Week 5: Progress Brief
- NR 501 Week 5: Theory to Practice Write-up
- NR 662 Week 5: Integration Paper
NR 500 Week 5 questions, answered
Where do the outside figures come from if I have no access to unit data?
Public material carries more of this brief than most students expect. National quality reporting, professional body publications and published studies in similar settings will each support a statement about size or frequency. Your own numbers are not required, and a brief built on public material plus honest local description marks perfectly well.
How local does the problem have to be?
Local enough to describe in specifics, which usually means one unit, one clinic or one program rather than a whole health system. A problem you have only read about tends to produce a brief that repeats its sources. If you are between settings, choose the most recent one you know well and say which it is.
Is a practice problem the same as a research question?
Not at this stage, and treating the two as one is the commonest structural mistake in the genre. The brief argues that something is happening and that it deserves attention. Turning it into a question with variables and a design comes later in the program. Where your prompt does ask for a question, keep it to a line at the end.
Where can I find a free NR 500 Week 5 sample paper?
The complete Week 5 brief on vital signs entered twice, with the local review, the published evidence, why the problem persists, what informatics adds, the unknowns and two references, is on this page.
What did the local review in the NR 500 Week 5 brief find?
In 20 deidentified shift notes from one week, the vital signs typed into the note disagreed with the flowsheet in 7, a small sample the brief uses to describe the problem, not prove its size.