| Course | NURS FPX 6426 Nursing Informatics Life Cycle Management |
|---|---|
| Assessment | Assessment 4 |
| Paper type | System change evaluation |
| Length | About 1,070 words, 6 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | MSN |
| Updated | September 2026 |
Free sample paper for NURS FPX 6426 Assessment 4
Evaluation of an Information System Change: An Electronic Nursing Handoff Tool Six Months After Go-Live
Student Name
Capella University
NURS FPX 6426: Nursing Informatics Life Cycle Management
Instructor Name
Month Day, Year
Introduction
Information system projects often end at go-live, and their results are assumed rather than measured. This paper evaluates the electronic nursing handoff tool implemented on six inpatient units of a 280-bed hospital, six months after go-live. It returns to the needs identified before implementation, answers each with data, examines unmet needs, and considers what the change did beyond its intended effects. The evaluation uses the DeLone and McLean (2003) model of information systems success, which considers system quality, information quality, service quality, use, user satisfaction, and net benefits.
The Original Needs
Before implementation, stakeholders identified five needs: a consistent structure for handoff across units; automatic display of pending results and recent changes; fewer handoff-related errors; handoff that takes no longer than the current process; and a summary that fits on one printed page for nurses giving report away from a computer.
Answered Need by Need
Consistent structure: met. An audit of 60 handoffs found that the tool was used for 88% of them, and all used the same sections. Automatic display of pending results: met. The tool pulls pending laboratory and imaging results automatically, and nurses rated this the most useful feature. Fewer handoff-related errors: partly met. Event reports attributed to handoff fell from 11 in the six months before go-live to 6 in the six months after. The numbers are small, and reporting practices may have changed, so the reduction is encouraging but not conclusive. The direction of the change is plausible, since a multicenter study of a standardized handoff bundle found fewer errors and preventable harms after it was introduced (Starmer et al., 2014). No longer than the current process: not met. Timed observations showed that handoff took a median of 4.1 minutes per patient, compared with 3.2 minutes before. One printed page: met after revision. The first version printed on two pages; a revision in month two reduced it to one.
Why an Unmet Need Failed
The handoff time need was not met, and the evaluation looked for the cause. Observation showed that the extra time came mainly from two sources: nurses reviewing the free-text section, which some colleagues filled with long notes, and nurses reading the automatically displayed results aloud, including results that were not relevant. The tool made more information available, and nurses used the extra minute to read it, which is not necessarily a failure but was not what the need anticipated. Guidance on keeping free-text notes brief and on highlighting only abnormal or pending results could reduce time without removing information.
Work That Moved
Information system changes often move work rather than remove it. The handoff tool moved some work from the end of the shift to during it: nurses now update the tool's "to do" section throughout the shift, which spreads the work but adds small interruptions. It also moved work to charge nurses, who now review handoff summaries for completeness each morning. These shifts were not planned and should be considered in future revisions. Neither is necessarily harmful, but both consume time that the project's original business case did not count, and a fair evaluation must include them alongside the benefits.
Claimed Benefits Tested
Before go-live, the project team claimed three benefits: safer handoff, improved nurse satisfaction, and better communication with physicians. Safer handoff is partly supported by the event report data. Nurse satisfaction was measured by survey: 64% rated the tool better than the previous process, 21% rated it the same, and 15% rated it worse, mainly because of time. Better communication with physicians, the third claimed benefit, was not supported by any data collected; physicians rarely viewed the nursing handoff summary, and no change was found in physician-reported communication.
Adoption Is Context
Usage of the tool was high, at 88% of handoffs. But high use does not by itself show success, because use was required by policy. Adoption is context for the outcome data: because nearly all handoffs used the tool, changes in outcomes can reasonably be connected to it. Satisfaction and outcome data, not use, determine whether the change was worthwhile, and future reports to leadership should lead with them rather than with usage percentages.
System, Information, and Service Quality
The DeLone and McLean model also asks about the quality of the system, its information, and the support around it. System quality was generally good: the tool loaded quickly and was available during 99.8% of scheduled hours, with one outage during an electronic record upgrade. Information quality was mixed: automatically displayed results were accurate, but manually entered sections were sometimes out of date by the time of handoff, particularly the isolation status when precautions were discontinued during the shift. Service quality was rated highly by nurses, who valued the informatics team's rounding during the first month. Separating these dimensions shows that the tool's main weakness lies in information entered by people, which is a workflow and training issue rather than a technical one.
Voices From the Units
Nurses' comments added detail the numbers could not. A night nurse wrote that the tool meant she no longer had to hunt for pending cultures at 0300. A step-down nurse wrote that the free-text section had become a place for complaints about the previous shift, which the character limit and guidance should address. A newly graduated nurse said the structure helped her know what to ask in report, which suggests the tool may support newer nurses in particular. These comments will be shared with the nursing practice council along with the quantitative results.
Recommendations
The evaluation leads to four recommendations: add guidance and a character limit to the free-text section; configure the results display to highlight abnormal and pending results; clarify the charge nurse's review role or remove it if not needed; and drop the claim of improved physician communication unless a physician-facing feature is added.
Conclusion
Six months after go-live, the electronic handoff tool meets most of its original needs, has likely contributed to fewer handoff-related errors, and is used consistently. It has not met the need for faster handoff, and it has moved some work rather than removing it. Returning to the original needs, testing claimed benefits, and treating adoption as context provide a balanced account and a clear direction for revision.
References
DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information systems success: A ten-year update. Journal of Management Information Systems, 19(4), 9-30. https://doi.org/10.1080/07421222.2003.11045748
Starmer, A. J., Spector, N. D., Srivastava, R., West, D. C., Rosenbluth, G., Allen, A. D., Noble, E. L., Tse, L. L., Dalal, A. K., Keohane, C. A., Lipsitz, S. R., Rothschild, J. M., Wien, M. F., Yoon, C. S., Zigmont, K. R., Wilson, K. M., O'Toole, J. K., Solan, L. G., Aylor, M., ... Landrigan, C. P. (2014). Changes in medical errors after implementation of a handoff program. New England Journal of Medicine, 371(19), 1803-1812. https://doi.org/10.1056/nejmsa1405556
The Capella NURS FPX 6426 Assessment 4 instructions
The final assessment asks you to evaluate an information system change after implementation. You return to the needs and success criteria set earlier, measure whether each was met, analyze causes of shortfalls, identify unintended effects, assess quality using a recognized framework, gather user perspectives and recommend next steps. A widely used framework is the DeLone and McLean model of information systems success, which looks at system, information and service quality alongside use and net benefits. Usage data can show adoption, but adoption alone does not show success. The evaluation should be honest about what did not work. Evidence from the system, surveys and observation, in de-identified form, supports the findings.
Inside the NURS FPX 6426 Assessment 4 example
The evaluation is built as an answer sheet to the life cycle's first assessment. It opens by restating the original needs and the success criteria attached to them, then takes each need in turn and reports the data that show whether it was met. Where a need was not met, the paper looks for the cause, separating design, configuration and training. A section on work that moved asks whether the tool removed effort from handoff or simply shifted it to another time or person. Benefits promised before go-live are tested one by one, and adoption figures are presented as context, not as evidence of success. The paper then applies the system, information and service quality dimensions, adds quotations from nurses on the units, and ends with recommendations tied to specific findings.
Where the marks sit in the NURS FPX 6426 Assessment 4 scoring guide
The scoring guide rates the use of original criteria, the measurement, the analysis of shortfalls, the unintended effects, the framework and the recommendations. Measurement reaches Distinguished when each original need is answered with data. Shortfall analysis scores higher when causes are identified. The unintended effects criterion rewards noticing work that moved elsewhere. Framework use earns credit when dimensions are applied, not named. Treating adoption as context shows evaluative maturity. Recommendations should follow from findings. User voices add credibility. The annotations point to where claimed benefits are tested. APA formatting and writing quality are part of the grade.
NURS FPX 6426 Assessment 4 help from the desk
Students often measure success by how many people use the system, which says little about whether handoffs improved. Another frequent mistake is inventing new criteria at evaluation time instead of using the original ones. Unmet needs are sometimes glossed over. Work shifted to another role or time is easy to miss. Recommendations that say continue to monitor are too weak. Keep data de-identified and consistent with the earlier assessments. Include what nurses say, since their account often explains numbers that look puzzling, such as a tool used on every shift but trusted by few. A model evaluation of your own system change can be drafted to your instructions on request.
Get a NURS FPX 6426 Assessment 4 example written to your instructions
Send the Assessment 4 instructions and the scoring guide from your NURS FPX 6426 courseroom, plus the original needs and the post-implementation data your evaluation uses. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and answering each original need individually is what makes the evaluation useful rather than reassuring. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More NURS FPX 6426 papers and MSN samples
- NURS FPX 6426 Assessment 1: The Case That Starts a Life Cycle
- NURS FPX 6426 Assessment 2: Needs Assessment Meeting With Stakeholders
- NURS FPX 6426 Assessment 3: A Go-Live Walked Through on Paper
- NURS FPX 6620 Assessment 1: Coordination Models Compared Against Evidence
- NURS FPX 6424 Assessment 4: Practice Recommendation With Measure, Baseline, and Target
- NURS FPX 6622 Assessment 1: How a Real Setting Currently Moves Patients
- NURS FPX 6422 Assessment 4: Making Decisions to Use Informatics Systems in Practice
NURS FPX 6426 Assessment 4 questions, answered
How should I structure NURS FPX 6426 Assessment 4?
Evaluate the change against the needs defined at the start of the project, one by one, with data for each. Then address what did not work and why, and what the change did that was not intended.
Is high usage evidence that a system change succeeded?
No. Staff may use a system because they are required to, not because it meets their needs. Usage shows adoption; outcomes and user experience show whether the change worked.
Which evaluation framework can I use?
Information systems success models, such as the DeLone and McLean model, organize evaluation around system quality, information quality, service quality, use, user satisfaction, and net benefits.
Is high usage proof of success in NURS FPX 6426 Assessment 4?
No. Usage shows adoption, but success means the original needs were met, such as fewer handoff omissions or less time spent. Report usage as context and test the needs directly.
Where can I find a free NURS FPX 6426 Assessment 4 sample paper?
This page holds the full six-month evaluation of the handoff tool, with each original need answered, shortfalls, moved work, tested benefits, quality dimensions and recommendations. A free custom evaluation is available.