| Course | NURS 6451 Evaluation Methods for Health Information Technology |
|---|---|
| Week | Week 6 |
| Paper type | Usability analysis |
| Length | About 810 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Master of Science in Nursing (MSN) |
| Updated | September 2026 |
Free sample paper for NURS 6451 Week 6
Where Nurses Got Stuck: A Think-Aloud Usability Analysis of the Secure Messaging App, Organized by Failure and Rated by Severity
Student Name
College of Nursing, Walden University
NURS 6451: Evaluation Methods for Health Information Technology
Instructor Name
Month Day, Year
Where Nurses Got Stuck: A Think-Aloud Usability Analysis of the Secure Messaging App, Organized by Failure and Rated by Severity
Methods
Six nurses from the two medical-surgical units already using the secure messaging app took part in individual sessions of about 40 minutes in a quiet room off the unit. Each used a test version of the app on a unit phone with made-up patients. Each completed four scripted tasks: send a non-urgent request about a pain medication to the covering prescriber for a named patient; forward a pharmacist's question to the prescriber; escalate a deteriorating patient to the rapid response nurse; and find a reply from earlier in the shift. Participants were asked to think aloud, saying what they were looking for and deciding as they worked, following established guidance on the think-aloud method for user interface evaluation (Jaspers et al., 2004). A facilitator read each task, did not help and prompted only with keep talking. Screens and voices were recorded with each participant's written consent, and sessions were reviewed by two analysts. Failures were matched to usability heuristics adapted for patient safety in health care devices (Zhang et al., 2003) and rated on a four-point severity scale: 1, cosmetic; 2, minor, slows the task; 3, major, causes errors or abandonment; 4, critical, could delay care for a patient. Six participants are enough for a formative analysis that aims to find problems, because the same failures recur quickly once tasks are realistic; the sample would not support comparing versions statistically.
Finding 1: The Recipient Directory Is Sorted by Name, Not by Covering Role (Severity 4)
Trying to: send a request to the prescriber covering a patient. Said aloud, in a composite of several participants: "Who's covering 14 today? I don't know the name, I know it's the orange team." Screen: the directory lists every prescriber alphabetically, with no indication of team, role or which patients they are covering; searching for the team name returns nothing. Five of six participants either sent the message to the wrong prescriber or left the app to find the name on the unit whiteboard. Heuristic violated: match between the system and the world, since nurses think in covering roles and teams, not names. This is the most serious failure, because a request sent to the wrong prescriber looks sent and may never be answered.
Finding 2: Every Message Is Flagged Urgent by Default (Severity 3)
Trying to: send a non-urgent request. Said: "It's red, so it must be urgent... I'll just leave it, I guess." Screen: the urgent toggle is on by default and sits below the text box, out of view until the keyboard closes. Four of six participants sent non-urgent requests as urgent. Heuristic violated: error prevention and visibility of system status. The effect falls on prescribers, who receive an urgent alert tone for routine requests, and it undermines the meaning of urgent for real escalations.
Finding 3: Forwarding Strips the Patient Context (Severity 3)
Trying to: forward a pharmacist's question to the prescriber. Said: "Does it keep the patient attached? I can't tell." Screen: forwarded messages arrive without the patient banner, so the recipient sees a question without knowing which patient it concerns. Three of six participants retyped the patient's name and room. Heuristic violated: consistency and minimizing memory load.
Finding 4: Earlier Replies Are Hard to Find (Severity 2)
Trying to: find a reply from earlier in the shift. Said: "I know he answered, it's in here somewhere." Screen: conversations are ordered by the most recent message, and a busy prescriber's thread drops below the screen within an hour. Participants scrolled for an average of about a minute; all eventually found it. Heuristic violated: recognition rather than recall.
Satisfaction Score, Read After the Failures
After the tasks, participants completed the System Usability Scale, a ten-item questionnaire that yields a score from 0 to 100 (Brooke, 1996). The mean score was 71, a result that would usually be read as acceptable. It is reported here after the observed failures deliberately, because it tells a different story from them. Participants rated the app positively overall while five of six had sent at least one message to the wrong prescriber. The score is useful as a summary that a later round can be compared against, but it did not detect the most serious failure. Read on its own, it would have supported a conclusion the observations contradict.
Recommendations and Next Round
Three changes are recommended in severity order: add covering-team and role search to the directory, showing which prescriber covers each patient on the unit; set the urgent flag to off by default and move it above the text box; and keep the patient banner on forwarded messages. After the vendor makes these changes, a second round with six different nurses will repeat the same four tasks, so the rate of misdirected messages can be compared directly.
References
Brooke, J. (1996). SUS: A "quick and dirty" usability scale. In P. W. Jordan, B. Thomas, B. A. Weerdmeester, & I. L. McClelland (Eds.), Usability evaluation in industry (pp. 189-194). Taylor & Francis.
Jaspers, M. W. M., Steen, T., van den Bos, C., & Geenen, M. (2004). The think aloud method: A guide to user interface design. International Journal of Medical Informatics, 73(11-12), 781-795. https://doi.org/10.1016/j.ijmedinf.2004.08.003
Zhang, J., Johnson, T. R., Patel, V. L., Paige, D. L., & Kubose, T. (2003). Using usability heuristics to evaluate patient safety of medical devices. Journal of Biomedical Informatics, 36(1-2), 23-30. https://doi.org/10.1016/S1532-0464(03)00060-1
The Walden NURS 6451 Week 6 instructions
The Week 6 prompt generally asks for a usability evaluation of your health IT system, using methods such as think-aloud testing, heuristic evaluation or standardized questionnaires, and reporting findings with recommendations. Many sections accept a planned study if running sessions is not feasible, as long as the method is described fully. Reports usually run three to five pages. Write realistic tasks that match how the system is actually used, describe how sessions were run and recorded, rate each finding's severity and connect it to a recognized heuristic. If you use a questionnaire score, interpret it alongside what you observed. Explain why your number of participants is enough for your purpose.
How this NURS 6451 Week 6 example is built
The methods section describes six participants from two units, a test version with made-up patients, four scripted tasks, think-aloud guidance, a facilitator who does not help, consented recording and review by two analysts, and explains why six participants suffice for a formative analysis. Four findings follow in severity order, from the name-sorted directory to hard-to-find earlier replies, each with the nurse's goal, words, screen and violated heuristic from a patient safety adaptation of usability heuristics. The satisfaction section reports a score of 71 and explains why it missed the most serious failure. Recommendations and a second round close the report. Each finding gives the count of participants who met it.
Reading the NURS 6451 Week 6 rubric
Usability rubrics usually score appropriateness of methods, realism of tasks, quality of findings, severity assessment, use of heuristics or standards, recommendations and writing. Methods earn credit when they are described well enough to repeat. Tasks should reflect real work. Findings are judged on specificity, with the user's goal and the screen's behavior both described. Severity ratings help decision makers and are often required. Heuristics connect findings to accepted principles. Recommendations should follow from findings in order of severity, and many rubrics reward a plan to retest after changes. Some rubrics also reward reporting how many participants met each failure, which helps readers judge how common a problem is.
NURS 6451 Week 6 help from the desk
The most common loss is reporting a satisfaction score as the main finding, which can hide serious problems. Another is findings written as opinions, such as the app is confusing, with no task or screen behind them. Some reports use tasks that do not match real work, or a facilitator who helps participants and hides failures. Others skip severity. Write tasks from real workflows, record what users say and do, describe each failure precisely, rate severity, link it to a heuristic and read any questionnaire score in light of what you observed. Also plan a second round after changes, since a fix that is never retested may not work. Keep participants' names out of the report.
Get a NURS 6451 Week 6 example written to your instructions
Which screen or task the analysis targets shapes everything, so say so alongside the Week 6 prompt and rubric; the failures are then built around that screen. Your first request is free and arrives in 24-48h, with every finding numbered so your own recommendations can reference them.
More NURS 6451 papers and MSN samples
- NURS 6451 Week 1: Discussion post
- NURS 6451 Week 2: Evaluation question memo
- NURS 6451 Week 3: Literature matrix
- NURS 6451 Week 4: Evaluation design
- NURS 6451 Week 5: Measurement plan
- NURS 6451 Week 7: Workflow impact analysis
- NURS 6451 Week 8: Stakeholder analysis
- NURS 6451 Week 9: Discussion post
- NURS 6451 Week 10: Evaluation plan
- NURS 6451 Week 11: Reflection
- NURS 6501 Week 6: Musculoskeletal mechanism concept map
- NURS 6441 Week 6: Risk register
- NURS 6512 Week 6: HEENT episodic note critique
- NURS 6421 Week 6: Swimlane diagram
NURS 6451 Week 6 questions, answered
How many participants does a usability analysis need?
Fewer than most authors expect for finding problems, since the same failures recur quickly once tasks are realistic. The sample uses a small group of nurses from two units and says why that suffices for a formative analysis, while noting that it would not support comparing versions statistically. Your prompt may set a number, and the analysis follows it.
Why report the SUS score at all if it misses the main failure?
Because it is a widely used, comparable summary, and a later round can be measured against it. The point is the order and interpretation: reported after the observed failures, the score is read as one signal among several rather than as the verdict. Sections that require SUS get it in full, with its limits stated beside the result.
Can I run think-aloud sessions for coursework?
Many prompts accept a planned analysis rather than one conducted, and the structure here works either way. If sessions are feasible, involve whoever at your organization approves observation of staff before recording anyone. If they are not, a heuristic evaluation of screens you can access, clearly labeled as such, carries the method argument without participants.
Where can I find a free NURS 6451 Week 6 sample paper?
The full usability analysis, methods, four findings, satisfaction section and recommendations, is posted here free. An analysis for the system your prompt names can be drafted on request.
Does a NURS 6451 usability analysis need real participants?
Many sections accept a planned study or a heuristic evaluation if sessions are not feasible. If you run sessions, get approval from whoever oversees observation of staff at your organization first.