Heparin infusion starts mapped before and after pump integration on one unit show fewer keystrokes and faster starts, plus new failure points, in the NU515 Unit 2 workflow analysis. Searches like "nu 515 unit 2 assignment example", "nu515 unit 2 sample" and "nu515 unit 2 example" land here.
What a finished NU515 Unit 2 workflow analysis looks like
Six pages built on two swimlane maps set side by side, with lanes for the nurse, the second nurse, the pump, the electronic record and pharmacy. The before map shows thirteen steps: order review, bag retrieval, two scans, then manual pump entry of drug, concentration, weight and dose, an independent double check, and a flowsheet entry made later. The after map shows ten, with a pump channel scan added and manual entry replaced by parameters sent from the order. A timing table summarizes ten observed starts in each condition: median 7.4 minutes before and 5.1 after, and a median 41 minutes before the rate reached the record, now none. Three of the ten post-integration starts failed to auto-program, two with the pump offline and one on a mismatched library entry, and took 9.2 minutes by hand.
How a NU515 Unit 2 example is structured
Scope comes first and is narrow on purpose: one high-alert task, from order verification to a documented running rate, observed ten times in each condition on one unit. The current-state map precedes the new one so every change can be traced to a specific step. Steps are then sorted by type, care, verification and documentation, which shows that integration removed transcription while keeping the double check hospital policy still requires. The failure path gets equal weight with the success path, because three fallbacks in ten starts are where a nurse's time and a patient's risk move. Each fallback is traced to its cause: wireless dead zones in two rooms and a library entry whose units did not match the order. What the maps cannot show closes the paper: night staffing, multi-channel pumps and titrations.
One task, ten starts each way
A weight-based heparin infusion, from verified order to documented rate, observed before and after integration on one unit.
Thirteen steps, then ten
Manual entry of drug, concentration, weight and dose gives way to a channel scan and parameters sent from the order.
Twenty-three keystrokes to four
Pump entries counted at each start, the clearest measure of transcription removed and of errors that can no longer be keyed in.
The rate reaches the record
A median 41-minute delay before the rate appeared in the flowsheet disappears once the nurse validates the start at the pump.
Three starts that fell back
Two pumps offline in wireless dead zones and one mismatched library entry, each start finished by hand in a median 9.2 minutes.
What ten observations cannot show
Nights, multi-channel pumps and titrations sit outside the scope, and the paper lists them for later measurement.
Where marks go in NU515 Unit 2
The first test a grader applies is whether a stranger could trace one nurse's actual path through the task from these maps. Generic diagrams that could describe any hospital earn little, since the course argues that the same technology behaves differently in different workflows. Credit goes to observed steps, counted and timed, and to lanes that show which actor or system performs each one. Mapping the earlier path as carefully as the new one earns marks, because improvement can only be shown against a baseline. Graders look especially for the failure path; an analysis presenting only successful auto-programming has described the vendor's demonstration. Causes traced to specific conditions, such as dead zones, show analytic depth. Small samples should be labeled as small, and figures must agree between map and table.
Get a NU515 Unit 2 example written to your instructions
Pick one task a technology changed on your unit, or soon will, and describe how it runs now. Along with the Unit 2 prompt and rubric, that description becomes a model analysis with both maps, timings and the failure path, back in 24-48h and free the first time. The task you map, and what you see, stay yours.
NU515 Unit 2 questions, answered
Do I need to time real observations?
Where possible, yes, even a handful, but many sections accept estimated times if the basis is stated. The sample reports ten composite observations per condition and labels the sample as small. What matters most is that each step comes from the real workflow rather than the policy manual, since policies describe the path nurses are supposed to take, not the one they do.
Which mapping notation should the analysis use?
Swimlane diagrams work well because they show who or what performs each step, and handoffs between lanes are where delays and errors tend to occur. The sample uses five lanes, treating the pump and the record as actors. Some sections prefer flowcharts or value stream maps. Whichever notation is used, a legend and consistent symbols across both maps make comparison possible.
Why include failed auto-programming attempts?
Because the fallback path is part of the real workflow. When integration fails, the nurse programs manually, often under more time pressure than before, and the analysis would be incomplete without that path. The sample shows three failures in ten starts and traces each to a cause. Leaving them out would overstate the benefit and hide the problem later units try to fix.