| Course | NUR-6310 Nursing Informatics Systems Life Cycle |
|---|---|
| Module | Module 3 |
| Paper type | Informatics paper: design phase and usability |
| Length | About 1,053 words, 6 pages |
| Format | APA 7 student paper |
| School | Thomas Edison State University |
| Program | M.S. in Nursing, Nursing Informatics |
| Updated | October 2026 |
Free sample paper for NUR 6310 Module 3
Seven Fields Instead of Twenty-Two: Redesigning a Nursing Sepsis Screen at an Englewood Hospital for Usability
Student Name
M.S. in Nursing, Nursing Informatics, Thomas Edison State University
NUR-6310: Nursing Informatics: Systems Life Cycle
Mentor Name
Month Day, Year
Seven Fields Instead of Twenty-Two: Redesigning a Nursing Sepsis Screen at an Englewood Hospital for Usability
The Problem
The hospital and every figure in this paper are invented. Two years ago a 360-bed hospital in Englewood added a sepsis screen to the nursing admission and shift assessment. The screen had 22 fields, including vital signs that were already charted elsewhere, a list of infection sources and a free-text comment. When certain combinations were entered, a pop-up alert told the nurse to notify the provider. Nurses described the screen as slow, and an audit found that 31 percent of screens were left incomplete. The alert fired on about one in five patients, and nurses said most of those patients did not have sepsis. In the past year, two patients with sepsis were recognized late on units where the screen had been completed but the alert dismissed.
The informatics nurse leading the redesign was asked to make the screen faster without making it less safe.
What Usability Means
Zhang and Walji (2011) proposed TURF as a unified framework for usability of electronic health records. In their definition, usability has three parts: the system must be useful for the work, usable in practice and satisfying to the people who rely on it. Useful means the system supports the work that needs to be done. Usable means it is easy to learn, efficient to use and error tolerant. Satisfying means users have a good subjective impression of it. TURF analyzes four parts of a system: the tasks it supports, its users, how information is represented on the screen and the functions it offers. The framework separates the work the domain requires from the extra work a poorly designed interface adds, which the authors called overhead.
Applied to the sepsis screen, the TURF view showed a large overhead. Re-entering vital signs that were already charted added work without adding information. The infection source list asked nurses to make a judgment better made by a provider. The free-text comment was rarely read.
Why Usability Is a Safety Issue
Howe et al. (2018) reviewed patient safety event reports from three health care systems over several years and identified reports that mentioned an electronic health record product and described a usability problem. Most involved medications, and a share of those reports described events that may have reached the patient and caused harm. The study showed that usability is not a matter of convenience alone: confusing screens, poor layout and hard-to-find information contribute to events that hurt patients. The authors argued for better usability testing by vendors and by the hospitals that configure their systems.
Heuristic Evaluation
Nielsen (1993) described heuristic evaluation, in which a few evaluators independently examine an interface against a short list of recognized usability principles, such as consistency, error prevention, keeping users informed of system status, minimizing what users must remember and avoiding unnecessary information. He reported that a small group of three to five evaluators finds most usability problems, making the method inexpensive enough to use early and often.
The informatics nurse, an informatics pharmacist and a usability analyst from the vendor each reviewed the current screen. They found 17 problems. The most serious were the duplicated vital signs, an alert with no explanation of why it fired, a dismiss button placed where the acknowledge button sits on other alerts and no way to see the patient's trend in heart rate or temperature on the same screen.
| Heuristic | Problem found | Redesign |
|---|---|---|
| Error prevention | Dismiss and acknowledge buttons in different places than other alerts | Standard button layout across all alerts |
| Recognition rather than recall | Trends not visible; nurse must remember earlier values | Last three values shown beside each field |
| Minimal design | Vital signs re-entered; infection list; free text | Vital signs pulled from the flowsheet; list and free text removed |
| Visibility of system status | Alert gives no reason | Alert names the criteria met |
The Redesigned Screen
The new screen has seven fields. Temperature, heart rate, respiratory rate, systolic pressure and mental status are pulled from the flowsheet, with the last three values shown beside each so the nurse sees trends. The nurse answers two questions only: whether infection is suspected and whether the patient looks worse than at the last assessment. If criteria are met, the alert explains which ones and offers two choices, notify the provider now or document why not. The dismiss option was replaced by a required reason, chosen from a short list.
The informatics nurse tested the new screen with eight nurses from three units using ten written patient scenarios, five with sepsis and five without. Nurses completed the screen in a median of 40 seconds, compared with more than two minutes for the old one, and correctly escalated all sepsis scenarios. Two nurses found the reason list confusing, and it was reworded before go-live.
Working With the Vendor
Not every change was within the hospital's control. Pulling vital signs automatically required a configuration change that the vendor supported, but standardizing alert button layout across the whole record required a request to the vendor's product team, which will take a later release. In the meantime, the hospital changed the layout of its own locally built alerts and documented the inconsistency in its training materials. The informatics nurse also shared the heuristic findings with the vendor's usability team, since other hospitals using the same product likely face the same problems.
Design Rules for Future Screens
The project produced five rules for future nursing screens at the hospital: never ask a nurse to re-enter data the record already holds; show trends beside values; explain every alert; use the same button layout on every alert; and test with at least five nurses before go-live.
Limits
Scenario testing is not real practice, and nurses may behave differently at the bedside under pressure. The safety report study described possible harm but could not measure how often usability problems cause it. Fewer fields may miss rare presentations of sepsis.
Conclusion
The old sepsis screen carried a heavy overhead of unnecessary work and an alert that explained nothing. TURF showed where the overhead lay, Nielsen's heuristics found specific problems quickly and evidence from safety reports showed why usability matters for patients. The redesigned screen asks less of nurses and tells them more, and the design rules carry the lessons into future work.
References
Howe, J. L., Adams, K. T., Hettinger, A. Z., & Ratwani, R. M. (2018). Electronic health record usability issues and potential contribution to patient harm. JAMA, 319(12), 1276-1278. https://doi.org/10.1001/jama.2018.1171
Nielsen, J. (1993). Usability engineering. Academic Press.
Zhang, J., & Walji, M. F. (2011). TURF: Toward a unified framework of EHR usability. Journal of Biomedical Informatics, 44(6), 1056-1067. https://doi.org/10.1016/j.jbi.2011.08.005
NUR 6310 Module 3 instructions, in plain terms
The design stage of a system's life cycle is part of the sequential process in TESU's catalog description of NUR-6310, and because TESU shares the syllabus only with its students, module three becomes a design paper focused on usability. Expect to write an informatics paper that describes a screen, form or tool and its problems with data, defines usability with a recognized framework, explains why usability matters for safety with evidence, evaluates the current design with a structured method such as heuristic evaluation, presents a redesign with its reasoning and reports a test with users. Some sections ask for a mock-up or wireframe instead of a full paper. Check whether images of screens may be included and whether a usability test is required or only planned, and keep any screenshots free of patient data. Describe what was removed as carefully as what was added.
How this NUR 6310 Module 3 example is built
An invented Englewood hospital's 22-field sepsis screen, its incomplete rate and its noisy alert open the paper. The TURF framework defines usability and exposes the screen's overhead. A study of safety reports links EHR usability problems to possible harm. Heuristic evaluation by three reviewers finds 17 problems, and a four-row table matches the key problems to the principles they break and the redesign. The seven-field screen and its test with eight nurses follow, then design rules, limits and a conclusion. Annotations note the reasoning behind each change and testing with users before launch. A section on the vendor separates what the hospital could change from what it had to request.
Where the marks sit in the NUR 6310 Module 3 rubric
Design papers earn credit for a problem described with data, an accurate usability framework applied to the design, evidence linking usability to safety, a structured evaluation method, a redesign whose choices are explained and a test with real users. Mentors notice when a redesign removes work rather than adding features. Matching each problem to the principle it breaks shows disciplined thinking. Testing with scenarios that include both positive and negative cases shows care about safety. Framework terms should be used as their authors defined them, and studies cited accurately, with any figures from user testing labeled as illustrative.
Common NUR 6310 Module 3 mistakes, and how to avoid them
Design papers often add fields and alerts to solve every concern; ask what can be removed. Another frequent problem is skipping user testing because of time; even five nurses and a few scenarios reveal problems. Use a framework to explain why each change helps. Explain every alert to the user. Keep the layout of buttons and warnings consistent across screens, and tell the vendor about problems you cannot fix locally. Model your work on the Englewood redesign if useful; the desk drafts your own screen or tool paper free.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Thomas Edison State University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More NUR 6310 and M.S. in Nursing, Nursing Informatics sample papers
- NUR 6310 Module 1: Project Charter Paper: Planning Smart Pump and EHR Integration
- NUR 6310 Module 2: Current-State Analysis Paper: Medication Reconciliation Workflow Through a Sociotechnical Lens
- NUR 6310 Module 4: Testing Paper: Pediatric Weight-Based Dosing Scenarios Before an Order Entry Upgrade
- NUR 6310 Module 5: Implementation Paper: Go-Live, Superusers and Unintended Consequences in a Three-Hospital System
- NUR 6310 Module 6: Evaluation Paper: Drug Interaction Alerts and the DeLone and McLean Success Model
- NUR 7110 Module 5: App Privacy Paper: Reviewing Mental Health Apps Before Recommending Them
- NUR 7010 Module 3: Data Quality Paper: Testing Flowsheet Data on Restraint Use Before Reuse
NUR 6310 Module 3 questions, answered
Where can I find a free NUR 6310 Module 3 sample paper?
The usability design paper for an invented Englewood hospital's sepsis screen, from 22 fields to seven, appears in full above.
What is the TURF framework?
Zhang and Walji's framework that defines usability as useful, usable and satisfying and analyzes tasks, users, representations and functions.
Can EHR usability problems harm patients?
A study of safety reports from three health systems found reports linking usability problems to events that may have harmed patients.
What is heuristic evaluation?
A method in which a few evaluators examine an interface against recognized usability principles; three to five evaluators find most problems.
How should a nursing screen be tested before launch?
With a small group of nurses working through written scenarios that include both positive and negative cases, timing them and checking their decisions.