| Course | DNP 805 Health Care Informatics |
|---|---|
| Topic | Topic 6 |
| Paper type | Usability and workflow analysis |
| Length | About 960 words, 4 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DNP |
| Updated | October 2026 |
Free sample paper for DNP 805 Topic 6
Eleven Medication Passes Watched: A Usability and Workflow Analysis of Bar-Code Administration for One Patient, With the Workaround Read as Evidence
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
DNP-805: Health Care Informatics
Topic 6 Assignment
[Instructor Name]
December 7, 2026
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Eleven Medication Passes Watched: A Usability and Workflow Analysis of Bar-Code Administration for One Patient, With the Workaround Read as Evidence
The Task and How It Was Observed
The task is bar-code medication administration for a single patient's scheduled morning medications on the composite medical-surgical unit I manage, chosen because it is the most frequent documentation task nurses perform and the one they most often describe as slow. I observed it 11 times across three shifts, four on days, four on evenings and three on nights, with eight different nurses who agreed to be observed. For each observation, I recorded every click, the elapsed time for each step with a stopwatch and every interruption, whether from the system or from people, with the step at which it occurred. I did not help or comment during observations. Figures below come from the observations, not from what staff said about the task.
Step-by-Step Figures
Table 1 gives the median for each step across the 11 observations.
Table 1
Median Clicks, Time and Interruptions by Step, 11 Observed Administrations
| Step | Median clicks | Median time | Interruptions, total across 11 |
|---|---|---|---|
| Open the patient's administration record | 4 | 0.3 minutes | 2 |
| Scan the wristband | 1 | 0.2 minutes | 1 |
| Scan each medication, median of five medications | 10 | 1.1 minutes | 4 |
| Complete required assessments linked to specific drugs, such as pain score or heart rate | 12 | 1.9 minutes | 9 |
| Acknowledge system alerts | 7 | 1.2 minutes | 37 |
| Document and sign | 3 | 0.4 minutes | 3 |
| Total | 37 | 5.1 minutes | 56 |
Where the Time Goes
Two steps account for more than 60 percent of the total time: completing the required assessments and acknowledging alerts, together 3.1 of 5.1 minutes. The scanning steps that the system was designed around are fast. The assessment step is slow because each required assessment opens in a separate activity; when the nurse finishes it and returns, the administration record reloads at the top of the patient's list, and the nurse must scroll back to the medication she was giving. The alert step is slow because of its volume, discussed below. Interruptions from people, such as a colleague's question or a call light, occurred 19 times across the 11 observations, most often during the assessment step, when the nurse was already out of the medication list. The step that feels slowest to staff, scanning, is in fact among the quickest.
The Workaround and What It Solves
In 8 of the 11 observations, the nurse opened a second window of the administration record before starting the required assessments, so that the first window kept her place while the second reloaded; this is a violation of the unit's one-window policy, and it is also the clearest evidence available of where the design fails. The nurses were solving the reload problem. Workarounds to bar-code administration systems are common, and they usually arise from mismatches between the system's design and the real sequence of work (Koppel et al., 2008). The second window creates its own risk, since a nurse could document in the wrong window if two patients' records were open, and one nurse did briefly have two patients open. Eliminating the workaround by enforcing the policy would restore the reload problem; eliminating the reason for it would make the policy unnecessary.
The Interruption Burden
System alerts interrupted each administration a median of 3 times, 37 alerts across the 11 observations. Of the 37, 26, 70 percent, were dismissed in less than two seconds, too fast to have been read; the most common were duplicate-therapy warnings for as-needed pain medications ordered in dose ranges, which fire whenever two range orders exist even when only one is being given. Interruptions matter for safety as well as speed: in an observational study of hospital medication administration, each interruption was associated with a 12.1 percent increase in procedural failures and a 12.7 percent increase in clinical errors (Westbrook et al., 2010).
Three Changes Aimed at Observed Steps
First, embed the drug-linked assessment fields directly in the administration record, so that a pain score or heart rate is entered in the row of the medication that requires it. This removes the separate activity and the reload. Expected saving: about 1.2 minutes and 8 clicks per administration, and the reason for the second-window workaround.
Second, if the first change cannot be built before the spring upgrade, fix the reload so the record returns to the medication the nurse left. Expected saving: about 0.5 minutes per administration.
Third, convert duplicate-therapy warnings for as-needed range orders to a passive indicator in the record, keeping interruptive alerts for combinations pharmacy has identified as high risk. Expected effect: about two fewer interruptions and 0.8 minutes saved per administration. Interface guidelines for electronic records recommend reducing unnecessary interruptions and supporting the user's actual sequence of work (Zahabi et al., 2015).
Together, at about 15 patient medication passes per nurse per shift, the first and third changes would return roughly half an hour to each nurse's shift. The figures will be rechecked with the same observation method after the changes.
What the Observations Cannot Show
Eleven observations of one task on one unit support the direction of the findings more firmly than their exact size. Being watched probably made nurses faster and more careful, so the true times may be longer and the workaround more common. The eight nurses who agreed to be observed may not represent the unit's 26, and the patients were all on medical regimens, not the heavier postoperative regimens of the surgical side of the unit. Night observations were fewer, three rather than four, and nights are when alert volume is lowest because fewer new orders are written. These limits argue for repeating the observations after the changes with the same method and the same balance of shifts, so that the comparison is fair even if the absolute figures are not exact.
References
Koppel, R., Wetterneck, T., Telles, J. L., & Karsh, B. T. (2008). Workarounds to barcode medication administration systems: Their occurrences, causes, and threats to patient safety. Journal of the American Medical Informatics Association, 15(4), 408-423. https://doi.org/10.1197/jamia.M2616
Westbrook, J. I., Woods, A., Rob, M. I., Dunsmuir, W. T. M., & Day, R. O. (2010). Association of interruptions with an increased risk and severity of medication administration errors. Archives of Internal Medicine, 170(8), 683-690. https://doi.org/10.1001/archinternmed.2010.65
Zahabi, M., Kaber, D. B., & Swangnetr, M. (2015). Usability and safety in electronic medical records interface design: A review of recent literature and guideline formulation. Human Factors, 57(5), 805-834. https://doi.org/10.1177/0018720815576827
DNP 805 Topic 6 instructions, in plain terms
Topic 6 in DNP-805 asks students to analyze the usability and workflow of a clinical system task. Strong analyses define the task, explain how it was observed and report figures for each step, so that the analysis can show where the time actually goes. A workaround deserves to be read as a sign of a design problem, not only as a policy breach, measure interruption burden, such as alerts per task and how quickly they are dismissed, and propose changes aimed at the steps observed. The analysis should state what a small number of observations can and cannot show, including the effect of being watched, and it should name the next observations that would confirm or weaken its findings.
How this DNP 805 Topic 6 example is built
The finished example is built on observation rather than opinion. One task, medication administration for a single patient, is watched eleven times across three shifts, and the paper reports what it took each time: the click count, the elapsed minutes, the number of interruptions and where in the sequence they landed. A workaround appears in eight of the eleven, where staff open a second window to avoid losing their place, and the example reads this as a signal about the design, not a breach of policy to be corrected. Alert fatigue is quantified rather than named, with the number of interruptions per administration and the proportion dismissed without reading. The recommendations that follow all target steps the observations identified.
Reading the DNP 805 Topic 6 rubric
Faculty reward time located step by step. An Excellent analysis observes one task 11 times and tables median times, showing assessments and alerts take 3.1 of 5.1 minutes. Credit goes to reading the second-window workaround, seen in 8 of 11 passes, as evidence of a slow reload, drawing on Koppel and colleagues. The rubric values counting 37 alerts and the 26 dismissed in under two seconds, with Westbrook and colleagues on interruptions. Strong analyses embed assessment fields in the administration record. Top marks go to stating that observation probably made nurses faster. Limits come last.
DNP 805 Topic 6 help: mistakes that cost marks
The weakest version here is a paper asserting that a system is cumbersome with no measurement behind the claim, which cannot be acted on by anyone. A second failure is treating a workaround as non compliance to be eliminated, when it is usually the clearest available evidence about where the design fails. Marks also go for describing alert fatigue without counting anything, since the burden is measurable and the count is what makes the argument. Recommendations aimed at the system in general, rather than at a step, cannot be implemented. Observations conducted once, on one shift, describe a quiet afternoon. Time savings claimed with no per case figure cannot be scaled to anything.
Get a DNP-805 Topic 6 example written to your instructions
Send the DNP-805 Topic 6 instructions and the rubric your classroom posts, with the task or system your section assigned. We write a custom example to those criteria, built on repeated observations, with clicks and interruptions counted per step and each recommendation tied to an observed stage, in 24 to 48 hours. The first is free.
More DNP 805 papers and DNP samples
- DNP 805 Topic 1: Informatics Competency Analysis
- DNP 805 Topic 2: Data Standards Analysis
- DNP 805 Topic 3: Decision Support Evaluation
- DNP 805 Topic 4: Data Integrity and Privacy Analysis
- DNP 805 Topic 5: Telehealth Access DQ Pair
- DNP 805 Topic 7: System Change Evaluation Proposal
- DNP 805 Topic 8: Informatics Governance Analysis
- DNP 810 Topic 6: Social Conditions Analysis
- DNP 801A Topic 6: Practice Problem Description
- DNP 815A Topic 6: Translation Framework Application
- DNP 966 Topic 6: Revised Timeline
DNP 805 Topic 6 questions, answered
How many observations are enough?
Enough to cross shifts and conditions, which usually means eight to twelve rather than two or three. A task watched once on a quiet morning produces figures nobody recognizes. Spreading observations across a busy shift, a quiet one and a change of staff is what makes the click and interruption counts credible to the people who do the work.
Should I report a workaround if it breaks policy?
Yes, and the example frames it as a finding about the system, not a fault in the staff. A workaround appearing in eight observations out of eleven is telling you that the sanctioned path does not fit the work. Reporting it as a violation ends the analysis; asking what problem it solves for staff usually locates the design failure faster than anything else in the study.
How do I measure alert fatigue?
Count interruptions per task and the proportion dismissed without a change in action. Both are observable and both are more persuasive than describing clinicians as overwhelmed. If system reports are available, override rates by alert type add a second source. The point is to convert a widely accepted claim into a figure this setting can act on.
Where can I find a free DNP 805 Topic 6 sample paper?
The usability analysis for DNP 805 Topic 6 covers the task and how it was observed, step-by-step figures, where the time goes, the workaround, the interruption burden, three changes and what the observations cannot show. Forward the DNP 805 Topic 6 prompt you received for a free analysis.
Why report a workaround that breaks policy in DNP 805 Topic 6?
Because it shows what the system fails to do. Nurses opened a second window so the first kept their place during a slow reload, which points to a design fix rather than a discipline problem.