| Course | NR 721 Topics in Healthcare Systems Leadership II |
|---|---|
| Week | 5 |
| Paper type | Workaround case study |
| Length | About 1,120 words, 5 pages |
| Format | APA 7 student paper |
| School | Chamberlain University |
| Program | MSN, Nurse Executive |
| Updated | October 2026 |
Free sample paper for NR 721 Week 5
Workaround Case Study: The Paper "Keep on Tele" List at the Monitor Desk, Written Step by Step and Priced Against the Route It Replaced
Student Name
College of Nursing, Chamberlain University
NR 721: Topics in Healthcare Systems Leadership II
Instructor Name
Month Day, Year
Workaround Case Study: The Paper "Keep on Tele" List at the Monitor Desk, Written Step by Step and Priced Against the Route It Replaced
The Workaround in One Sentence
On 5 West, a handwritten sheet stuck beside the monitor station, titled "keep on tele," lets nurses answer the 07:00 telemetry discontinuation reminder with the default "continue, provider preference" for any listed patient, without assessing the patient or contacting a provider.
The Second Version, in Steps
The workaround runs alongside the designed protocol and has its own steps, which no document records.
1. At the evening huddle, about 19:30, the night charge nurse asks each nurse whether any monitored patient should stay on telemetry, and writes those names on the list.
2. During the night, a hospitalist who wants a patient kept on monitoring sometimes tells the nurse or adds a name directly.
3. At 07:00, when the reminder fires, the nurse answering it walks to the monitor desk or calls the technician and asks whether the patient is on the list.
4. If the patient is listed, the nurse selects "continue, provider preference" in about five seconds.
5. Names are crossed off when a patient is discharged or transferred; otherwise they stay, sometimes for several days.
The list needs a sheet of paper, a pen, tape and the evening huddle. It takes the charge nurse about two minutes a night and the answering nurse about ten seconds a reminder. What it produces that the designed route does not is a way to honor a hospitalist's wish to keep a patient monitored without paging the hospitalist at 07:00, when the hospitalists are themselves in handoff.
How the List Began
The list is about eleven months old. Night nurses date it to November 2026, when two hospitalists complained at a medical staff meeting that nurses were removing telemetry from patients the hospitalists had wanted monitored, and one removal had been followed, an hour later, by a run of atrial fibrillation that a box would have caught. The removal had met the criteria and the arrhythmia caused no harm, but the episode left night nurses wary. A night charge nurse started the list as a courtesy to the hospitalists, so their wishes would be visible at 07:00. Within a month it had become the default route for any patient anyone was unsure about. Its origin matters: it was built to protect nurses and to respect physicians, not to avoid work.
What Staff Said About It
Five nurses and two monitor technicians described the list when asked. All of them knew it was not part of the protocol. Three nurses said it saved them from paging a hospitalist at the worst moment of the morning. Two said they used it for patients they were unsure about, "to be safe." Both technicians said the list was often out of date and that they crossed off names only when someone told them a patient had left. Nobody described it as a shortcut; everyone described it as a safety measure.
Pricing the Designed Route Too
The designed route, for a patient a provider wants kept on telemetry, is longer. The nurse assesses the patient against the criteria, about two to three minutes; finds the criteria met but the provider's wish unclear; pages the hospitalist and waits for a reply, which in September took a median of 18 minutes at 07:00 and often arrived mid-medication pass; then documents the reason given. For the 81 September reminders answered by the list, the designed route would have cost roughly 81 pages to hospitalists during their handoff and about four hours of nurse assessment and documentation time, plus the interruptions of 81 replies arriving during medication passes. Pricing only the workaround's shortcuts and not the designed route's burden would make the list look like laziness. It is not; it is a cheaper route to an answer the designed route makes expensive (Debono et al., 2013).
What the Shortcut Gives Up
Three things are lost. First, the assessment: the patient is not checked against the criteria at all. Second, the documented reason: "provider preference" says who wanted monitoring, not why, so no one can later tell whether the indication still held. Third, expiry: names stay on the list until someone crosses them off. To test what this costs, the manager reviewed 46 patient-days in September on which a listed patient's reminder was answered with the default. On 19 of the 46, 41%, the patient met the protocol's criteria for stopping and the chart held no reason a provider had given for continuing. The national monitoring standards treat telemetry beyond its indication as overuse that adds alarm burden without benefit (Sandau et al., 2017).
Ward Currency
Table 1
Designed Route and Workaround Compared for a Patient a Provider Wants Kept on Telemetry
| Designed route, per listed reminder | Workaround, per listed reminder | |
|---|---|---|
| Nurse time | About 3 minutes plus documentation | About 10 seconds |
| Hospitalist pages at 07:00 | 1 | 0 |
| Interruptions during medication pass | Usually 1 | 0 |
| Patient assessed against criteria | Yes | No |
| Documented reason for continuing | Yes | No |
| Expiry | Reassessed at next reminder | None until crossed off |
Note. Note. Times from observation in September 2027; page reply time from the paging system log.
Three Possible Endings
The unit could forbid the list. That is the simplest ending and probably the least durable: the pressure that produced the list, pages at 07:00 and interruptions mid-medication pass, would remain, and a new informal route would likely appear.
The unit could formalize the list. A hospitalist who wants a patient kept on telemetry past 48 hours would enter a short order, "continue telemetry," with a required reason and a 24-hour expiry. The reminder would then show that order and its reason, and the nurse would neither page nor guess. This keeps what the list does well, letting a provider's wish travel without a page, and restores the reason and the expiry it lost.
The unit could redesign the moment that created the list. Moving the reminder from 07:00 to 10:00 would place it after handoff, after the medication pass and after hospitalists have started rounds, when a question can be asked in person.
The recommendation is to formalize and redesign together, and to remove the paper list only once both are in place, so that staff are never left without a route. Removing a practice works best when something fills the space it leaves (Norton & Chambers, 2020).
References
Debono, D. S., Greenfield, D., Travaglia, J. F., Long, J. C., Black, D., Johnson, J., & Braithwaite, J. (2013). Nurses' workarounds in acute healthcare settings: A scoping review. BMC Health Services Research, 13, Article 175. https://doi.org/10.1186/1472-6963-13-175
Norton, W. E., & Chambers, D. A. (2020). Unpacking the complexities of de-implementing inappropriate health interventions. Implementation Science, 15, Article 2. https://doi.org/10.1186/s13012-019-0960-9
Sandau, K. E., Funk, M., Auerbach, A., Barsness, G. W., Blum, K., Cvach, M., Lampert, R., May, J. L., McDaniel, G. M., Perez, M. V., Sendelbach, S., Sommargren, C. E., & Wang, P. J. (2017). Update to practice standards for electrocardiographic monitoring in hospital settings: A scientific statement from the American Heart Association. Circulation, 136(19), e273-e344. https://doi.org/10.1161/CIR.0000000000000527
NR 721 Week 5 instructions, in plain terms
Describe one workaround completely, the way a specification is written: what the staff-built route does, step by step, what it needs, how long it takes and what it produces that the designed route does not. Explain how it began and record how staff describe it, since a workaround is often seen as a safety measure rather than a shortcut. Price the designed route as carefully as the shortcut, in the same currency, such as minutes, pages or interruptions, so the comparison is fair. Then say what the shortcut gives up, and test that loss against records where you can. Avoid spending the paper on why staff ought not to do this. Close with possible endings, such as forbidding, formalizing or redesigning, and recommend one or a combination with reasons.
Inside the NR 721 Week 5 example
The sample states the workaround in one sentence and then in five steps, from the evening huddle to crossing off names, with the materials and times involved. A section traces the list to a medical staff meeting and an atrial fibrillation episode after a removal. Staff describe it as a safety measure. The designed route is priced at a 07:00 page with an 18-minute median reply and about three minutes of nurse time, about 81 pages and four hours a month. A review of 46 listed patient-days finds 19 met criteria with no reason recorded. A table compares the two routes on six points. Three endings are weighed, and the recommendation is to formalize the list as an expiring order and move the reminder to 10:00.
Where the points sit in the NR 721 Week 5 rubric
The biggest loss goes to a case study that spends its length on why staff should not be doing this, answering a question the assignment never asked. Next is a workaround described in summary rather than in steps, so no recommendation can be built on it. Marks are also lost for costing the designed route in the abstract while costing the shortcut precisely, or the reverse, since an uneven comparison decides the answer in advance. Graders take points when what the shortcut gives up is asserted rather than tested. Case studies score well when the workaround is specified step by step, both routes are priced in the same ward currency, the loss is tested against records and the endings are weighed fairly.
NR 721 Week 5 help: mistakes that cost points
A workaround usually exists because the designed route is expensive at a particular moment, and the case study has to show that fairly. Describe the workaround, how it began and what the official route asks of staff, and the paper can specify both in steps, price each in the same currency, test what the shortcut gives up and weigh endings that keep what the workaround does well. Recording how staff describe it often explains why forbidding it alone would fail. The workaround and the data are from your own unit.
Get a NR 721 Week 5 example written to your instructions
Send the case study instructions and rubric with a sketch of the workaround, even three lines of it. A custom Week 5 case study returns inside 24-48h with the second version written out as a procedure and the recommendation defended. A first request costs nothing, and a full scenario is available where the real one sits too close to your own unit.
More NR 721 papers and MSN samples
- NR 721 Week 1: Change Aftermath Post
- NR 721 Week 2: Post-Implementation Review
- NR 721 Week 3: Drift Analysis
- NR 721 Week 4: Unintended Consequence Memo
- NR 721 Week 6: Tradeoff Analysis
- NR 721 Week 7: Continue or Stop Recommendation
- NR 721 Week 8: Decision Communication
- NR 529 Week 5: Unit Budget Review
- NR 720 Week 5: Cross-Department Comparison
- NR 531 Week 5: Shared Governance Proposal
- NR 711 Week 5: Budget Variance Report
NR 721 Week 5 questions, answered
Is a workaround always a sign of a bad design?
Not always. Some appear because a design was right for most cases and wrong for a few, and the sensible ending is an exception route rather than a redesign. The case study earns marks for making that distinction, since a paper treating every shortcut as proof of a flawed change is as unhelpful as one treating it as misconduct.
Should I name the staff involved?
No, and rubrics rarely reward it. Describe the role and the shift pattern where those matter to the procedure, and leave individuals out entirely. The case is about a route through the work that anybody in that role would find, which is a stronger claim than one resting on what two particular people happened to do.
What if the workaround is unsafe?
Then say so plainly and early, and let it shape the recommendation rather than the whole paper. The structure holds: it still gets written out in steps, still costed, still compared. What changes is the ending, where making the designed route easier stops being one option among three and becomes the only one available to you.
Where can I find a free NR 721 Week 5 sample paper?
A full case study of a paper keep-on-tele list, priced against the designed route, can be read on this page.
What does the NR 721 Week 5 sample recommend for the paper list?
Turn it into an order that states why monitoring continues and lapses after a day, move the reminder to 10:00 and take the list down once both are live.