| Course | HI501 Health Informatics |
|---|---|
| Unit | Unit 5 |
| Paper type | Usability walkthrough |
| Length | About 1,180 words, 7 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Health Informatics |
| Updated | October 2026 |
Free sample paper for HI501 Unit 5
A Bedtime Glucose of 247 and a Scale on the Wrong Tab: A Unit 5 Usability Walkthrough of Correctional Insulin Documentation, Rated Against Nielsen's Heuristics
[Student Name]
Purdue University Global
HI501: Health Informatics
Unit 5 Usability Walkthrough
[Instructor Name]
[Date]
The ward, the nurses and the screens are composite; the methods and sources cited are real.
Introduction
Correctional insulin, given before meals and at bedtime when blood glucose is above target, is one of the most frequent medication tasks on a medical ward. It is time-sensitive, it depends on a number the nurse must look up, and it is easy to get wrong by one row of a scale. That combination makes it a good task for a usability walkthrough: small enough to bound, common enough to matter and risky enough to justify attention.
Method
The task was bounded tightly: from a point-of-care glucose result of 247 at 21:30 to a documented correctional insulin dose. I performed a cognitive walkthrough in the training environment, answering at each step the four questions the method asks: will the user try to achieve the right effect, will the user notice the correct action is available, will the user associate the action with the effect, and will the user see progress after acting (Polson et al., 1992). I then observed two nurses completing the same task on a live unit at bedtime, recording steps and seconds, with no patient identifiers collected. Problems were rated against Nielsen's ten usability heuristics using his five-point severity scale, from 0 for no problem to 4 for a usability catastrophe (Nielsen, 1993). One walkthrough and two observed nurses are enough to find problems and judge their seriousness. They are nowhere near enough to estimate how often errors occur, and this paper makes no such claim.
The Step Sequence
1. Open the patient's chart from the unit list. Screen 1.
2. Open the medication administration record. Screen 2.
3. Find the correctional insulin line among the scheduled medications.
4. Select it to administer, which opens the dose window. Screen 3.
5. Scan the patient's wristband.
6. Scan the insulin pen.
7. Read the dose window, which shows "Dose: per scale" and an empty units field.
8. Look for the glucose result, which the dose window does not show; open the results tab. Screen 4.
9. Return to the dose window, which now asks for units.
10. Look for the scale, which is not in the dose window; open the order details tab. Screen 5.
11. Find the bedtime scale, read the row for 201 to 250, and remember the number.
12. Return to the dose window, rescan the pen after a timeout, and type the units.
13. Sign the administration.
In the walkthrough, the task took 13 steps across 5 screens and about 96 seconds. At steps 8 and 10, the answer to the walkthrough's second question was no: nothing on the dose window tells the nurse where the glucose or the scale can be found. The two numbers the nurse needs to choose a dose, the glucose and the scale, are both missing from the one screen where the dose is entered.
Findings
1. Recognition rather than recall, step 10, severity 3. The dose window asks for units while the scale sits on another tab. The nurse must carry the number in memory across a screen change. One observed nurse avoided the problem by writing the scale on a paper towel at the start of the shift, a workaround that will go out of date if the order changes.
2. Error prevention, step 12, severity 3. The units field accepts any number, including decimals such as 2.5, although insulin pens deliver whole units, and it does not check the value against the scale row for the documented glucose.
3. Consistency and standards, step 11, severity 3. The mealtime and bedtime scales are both titled "Correctional insulin" and differ only by a small "HS" at the end of the bedtime line. At 247, the bedtime scale calls for 2 units and the mealtime scale for 4. The second observed nurse first read the mealtime row, then corrected it after a second look.
4. Visibility of system status, step 12, severity 2. The dose window timed out after 60 seconds while the nurse was on the order details tab, cleared the pen scan without saying so, and required a rescan.
5. Flexibility and efficiency, step 8, severity 2. The glucose result, already in the record from the connected meter, is not shown in the dose window, so every nurse makes the same detour.
Usability problems in clinical software are safety problems as well as efficiency problems, which is why heuristic methods developed for general software have been adapted to medical devices and patient safety (Zhang et al., 2003). Three of these five findings could produce a wrong dose.
What the Two Observed Nurses Did
The live observations added what a walkthrough cannot: the strategies people invent to cope. The first nurse, with eleven years on the unit, opened the order details tab before scanning anything, read the scale, then went to the dose window, so the timeout never caught her. She described this as "doing it backwards so the system cannot rush me." The second nurse, three months out of orientation, followed the screens in the order they appear and was caught by every problem in turn: the detour to results, the timeout and the near miss with the mealtime row. Her task took 141 seconds. Experience did not make the design safer; it taught one nurse to work around it, and the workaround depends on a habit that new staff do not yet have.
Recommendation
One change addresses findings 1, 2, 3 and 5 together. The dose window should show the most recent glucose with its time, the name of the active scale in full words, and the scale row that matches that glucose, with the corresponding dose prefilled and editable. The units field should accept whole numbers only and ask for a reason when the entered dose differs from the scale row. With those changes, the task would take about 8 steps on 2 screens, and the nurse would never need to remember a number across screens. The timeout in finding 4 should be lengthened for the dose window, or the scan should survive a tab change.
Limits and Next Steps
This walkthrough studied one task in one record design with one evaluator and two nurses. A heuristic review by two or three additional evaluators would find problems this one missed, and a test of the redesigned window with five to eight nurses would show whether it works as intended. A measure for after the change would be the share of correctional doses that match the scale row for the documented glucose, taken from administration records. The finding most likely to change practice, though, is already clear from this small study: the dose window asks the nurse for an answer while hiding both of the facts the answer depends on.
References
Nielsen, J. (1993). Usability engineering. Academic Press.
Polson, P. G., Lewis, C., Rieman, J., & Wharton, C. (1992). Cognitive walkthroughs: A method for theory-based evaluation of user interfaces. International Journal of Man-Machine Studies, 36(5), 741-773. https://doi.org/10.1016/0020-7373(92)90039-N
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
What the HI501 Unit 5 assignment asks for
The fifth unit generally asks for a usability evaluation of one clinical task in an information system. Expect to name the task and why it matters, describe your method and its limits, record each step with screens and time, and report problems against a recognized set of heuristics with a severity rating. Many prompts combine a cognitive walkthrough with observation of real users, even just two or three. Findings should say what happened, where, which heuristic applies and why it matters for safety or efficiency. Recommendations should target the specific screen or field involved. Cite the walkthrough or heuristic method you used and a source applying usability to patient safety. Keep users and settings composite, and avoid presenting a few observations as an error rate. A step table and numbered findings make the work easy to grade.
How this HI501 Unit 5 example is built
An introduction explains why correctional insulin suits a walkthrough. The method section names the four walkthrough questions, the two observed nurses and the severity scale, then states the limits in the same paragraph. Thirteen numbered steps follow, marking where the walkthrough questions fail, and the highlighted sentence observes that both numbers needed for the dose are missing from the screen where the dose is entered. Five findings are each tied to a step, a heuristic and a severity. A section on the observed nurses contrasts an eleven-year nurse's workaround with a newer nurse caught by every problem. The recommendation proposes one dose window that shows the glucose, the named scale and the matching row with the dose prefilled. Limits and a follow-up test close the paper.
HI501 Unit 5 rubric: what earns full points
Usability evaluations are typically marked on method, the step analysis, findings, recommendations and limits. Method points reward a bounded task and a named technique applied consistently. Step analysis earns credit when each step, screen and time is recorded so a reader could repeat it. Findings carry the largest share: each should name the heuristic, the step and a defensible severity, with a sentence on consequence. Students lose points by listing general complaints about the system rather than specific, located problems. Recommendations score well when one targeted change addresses several findings. A limits section that refuses to turn a handful of observations into a rate earns credit for rigor. Citations of the method and of usability research in health care, plus clear tables, complete the rubric.
Common HI501 Unit 5 mistakes, and how to avoid them
The commonest problem in Unit 5 is a walkthrough of a task so broad, such as admitting a patient, that no step table can capture it. Another is findings with no heuristic or severity attached, which reads as opinion. Some students report what users said rather than what they did. Others recommend replacing the whole system when one field or window is the problem. Severity ratings often inflate every finding to the top of the scale, which undermines the ranking. Presenting two observed users as proof of how often errors occur draws deductions. To get a walkthrough started on a task you know, list its steps as they happen on your screens and the prompt's requirements, and the findings can be rated against the heuristics your course names.
Get an HI501 Unit 5 example written to your instructions
Usability tasks differ widely: some sections name the system and the task, others let the writer choose. Either way, include what Unit 5 hands out, the rubric and any screenshots or descriptions supplied. Expect a step table, rated findings and one redesign sketch within 24-48h, and no fee for a first custom sample. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More HI501 papers and MS in Health Informatics samples
- HI501 Unit 1: Discussion Post
- HI501 Unit 2: Capture Workflow Analysis
- HI501 Unit 3: Structured Data Memo
- HI501 Unit 4: Decision Support Rule Design
- HI501 Unit 6: Adoption Evaluation
- HI501 Unit 7: Workflow Redesign Proposal
- HI501 Unit 8: Patient Engagement Analysis
- HI501 Unit 9: Seminar Reflection
- HI501 Unit 10: Informatics Project Brief
HI501 Unit 5 questions, answered
Where can I find a free HI501 Unit 5 sample paper?
The finished Unit 5 walkthrough appears in full here, following a bedtime glucose of 247 to a documented insulin dose.
What is a cognitive walkthrough?
An evaluation in which the analyst steps through a task asking four questions at each step about whether a user would know and see what to do.
How are usability problems rated?
Against heuristics such as recognition rather than recall, with a severity from 0 to 4; the sample rates three findings at 3.
Can two observed nurses show an error rate?
No. They show problems and their seriousness; measuring how often errors occur needs a larger study.
What change did the sample recommend?
A dose window that shows the latest glucose, the named scale and the matching row with the dose prefilled, plus whole-number validation.