NUR 633 Module 9 Final Project Example

Reviewed by Delia Ravenscroft, MSN, RN

This NUR 633 Module 9 Final Project sample assembles an informatics project into one proposal that a nursing and information technology steering committee could approve. It completes the final project of SNHU NUR 633 (NUR-633), the MSN informatics course. The proposal follows composite unit 6 West from its falls data, 38 falls and 9 injuries in a year, most at night after an unanswered call or alarm, through the evidence on call lights, bed alarms and patient-specific fall plans. It summarizes the work system analysis and presents an integrated design that carries fall risk from the electronic record to the nurse call system, badges and whiteboard. Privacy and usability safeguards follow, along with a budget of about $48,000 set against the published cost of an injurious fall. The proposal closes with the 16-week rollout, measures and a decision rule for keeping or retiring the system.

CourseNUR 633 Informatics and Communication Technology
ModuleModule 9
Paper typeFinal informatics project proposal
LengthAbout 1,190 words, 7 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMSN
UpdatedSeptember 2026

Free sample paper for NUR 633 Module 9

1

Final Project: An Informatics Proposal to Reduce Falls on 6 West by Integrating Fall Risk Across the Record, Nurse Call and Mobile Devices

[Student Name]

Southern New Hampshire University

NUR 633: Informatics and Communication Technology

Final Project

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title states the aim, the unit and the integration that defines the solution, which is what a steering committee needs to see first.
2

Final Project: An Informatics Proposal to Reduce Falls on 6 West by Integrating Fall Risk Across the Record, Nurse Call and Mobile Devices

Hospitals rarely lack information about which patients are likely to fall. What they lack is a way to get that information to the right person at the moment a high-risk patient tries to stand. This proposal closes that gap for the 32 beds of composite unit 6 West by connecting systems the hospital already owns. It asks the nursing and information technology steering committee to approve a modest integration project, and it argues that the project is justified by the unit's own data, supported by evidence, designed around the people who will use it and structured so that its value can be measured and its continuation decided on results.

What this page is doingThe introduction frames the problem as an information delivery gap and states what the proposal asks the committee to approve.
3

The Problem in the Unit's Data

Over the last year, 6 West recorded 38 falls and 9 injuries, among them a broken hip in a woman in her eighties who died after surgery. The usual safeguards, a validated risk scale, rounding every hour and bed sensors, have run for three years without bending the curve. Linking incident times with nurse call logs showed that 61% of falls occurred at night and that 45% followed within 10 minutes an alarm or call no one had yet answered. About 1,860 bed-exit alarms sound in a typical week, and most are canceled within half a minute because the patient only shifted in bed. The Morse score is charted for nearly every patient, yet it stays in a flowsheet that no responder sees. The problem is not missing information; it is information that stops short of the bedside.

What this page is doingThe section condenses Milestone One into the key figures, emphasizing the pattern revealed by linking data sources.
4

What the Evidence Supports

Three findings shape the design. A study of call light use found that units where patients called more often had less fall-related harm, suggesting that encouraging calls, not suppressing them, should be the goal (Tzeng & Yin, 2009). A cluster randomized trial found that increasing bed alarm use alone did not reduce falls (Shorr et al., 2012), and a review of alarm research reported that most clinical alarms are false or insignificant, leading to desensitization (Sendelbach & Funk, 2013). By contrast, a randomized trial of a toolkit that drew on the electronic record to produce an individualized fall prevention plan, shared with patients and posted at the bedside, reduced falls, particularly among patients 65 and older (Dykes et al., 2010). Together these suggest that targeted, patient-specific information delivered where decisions are made works better than more undifferentiated alarms.

What this page is doingThe evidence is summarized as design principles, contrasting approaches that failed with one that succeeded.
5

How the Work System Fails at Night

A work system analysis using the SEIPS model, which treats people, tasks, tools, environment and organization as interacting parts (Carayon et al., 2006), traced a typical night event. Five nurses and one assistant cover up to 32 patients on an L-shaped unit whose far rooms sit 60 meters from the station. A bed-exit alarm from a high-risk patient looks identical to one from a low-risk patient, sounds at a station that is often empty and never reaches a badge. Sensors default to their most sensitive setting. The patient's risk and prevention plan are visible to no one who responds. The analysis found four weak links: every alarm looked equally urgent, alarms went to a console instead of a caregiver, sensors were set too twitchy by default and the risk score never left the chart.

What this page is doingThe section condenses the systems analysis into the failure points that the design must correct.
6

The Proposed Design

The design corrects each failure point using existing systems. When a nurse documents a Morse score of 45 or higher, the integration engine sends a risk flag to the nurse call system, which marks the room. Bed-exit alerts from flagged rooms go to the badges of the assigned nurse and assistant with the room and risk level, and escalate to the charge nurse when a minute passes without a response. Sensors default to a middle sensitivity, raised only for a documented reason. Each flagged patient receives an individualized prevention plan on the whiteboard, reviewed with patient and family. Calls from unflagged patients continue to reach staff as they do now, and patients are encouraged, not discouraged, to call.

What this page is doingThe design is described as a set of changes that map one to one onto the failure points, using systems the hospital already owns.
7

Privacy, Usability and Documentation

Badge messages will display only the room number and a risk level, not names or diagnoses, applying the minimum necessary standard to information shown on mobile devices, and badges are hospital-managed and encrypted. The design adds no documentation: the risk flag comes from a score nurses already chart. Night nurses and assistants will test the design in scripted scenarios before go-live, and any step that adds clicks or alerts without benefit will be removed.

What this page is doingSafeguards address privacy on mobile devices, documentation burden and usability testing, which a steering committee will ask about.
8

Budget and Value

The project is inexpensive because it uses existing systems. Estimated costs are about $13,200 for 120 hours of interface build and testing, $9,600 for badge alert licensing for one year, $8,400 for staff time in scenario testing and training, $12,000 for informatics nurse support during go-live and $4,800 for whiteboard templates and printing, a total of about $48,000. Against this, a study at three hospitals found that falls with serious injury added about $13,800 in operational costs and nearly a week to the hospital stay (Wong et al., 2011). Preventing four serious-injury falls in a year would roughly repay the investment, before counting the harm to patients themselves.

What this page is doingThe budget itemizes costs and compares them with published costs of serious fall injuries, giving the committee a break-even frame.
9

Implementation

Implementation runs over 16 weeks. The first month builds and tests the integration in a test environment and on four beds. The second month runs scripted scenarios with night staff and fixes problems. In weeks nine and ten only half the unit switches over, giving a brief side-by-side comparison, and the remaining rooms follow from week eleven. Barriers identified with the Consolidated Framework for Implementation Research (Damschroder et al., 2009), such as thin night staffing and skepticism left by a faded 2022 pilot, are addressed with shift-based super users, 20-minute training at the start of each shift type, informatics support on nights during each go-live week and a downtime procedure that posts printed lists of high-risk patients if the interface fails.

What this page is doingThe implementation summary gives the phases and shows how framework-identified barriers are addressed.
10

Evaluation and Decision Rule

Success will be judged first by the fall rate per thousand patient days for the year after implementation compared with the year before, aiming for a drop of about 30%; falls that cause harm are tracked as the most important secondary result. Process measures from system logs include the share of flagged alerts acknowledged within a minute at night, weekly bed-exit alarm counts and the share canceled almost immediately. A balancing measure tracks response times for unflagged patients. A staff survey measures alarm burden. At week 16, the steering committee will choose among keeping, modifying or retiring the system, looking first at prompt acknowledgment of flagged alerts and at staff reports of alarm burden; the annual fall rate will guide the decision at one year.

What this page is doingEvaluation includes outcome, process, balancing and staff measures and an explicit decision rule at defined points.
11

Conclusion

6 West's falls continue not because nurses do too little but because the right information does not reach them at the right moment. For about $48,000, using systems the hospital already owns, this project would deliver patient-specific risk to the people who respond at night, cut unnecessary alarms and give patients an individual plan. It is designed to be tested honestly and kept only if it works.

What this page is doingThe conclusion restates the problem, the modest cost and the commitment to evaluation, which is the basis for approval.
12

References

Carayon, P., Schoofs Hundt, A., Karsh, B.-T., Gurses, A. P., Alvarado, C. J., Smith, M., & Flatley Brennan, P. (2006). Work system design for patient safety: The SEIPS model. Quality and Safety in Health Care, 15(Suppl. 1), i50-i58. https://doi.org/10.1136/qshc.2005.015842

Damschroder, L. J., Aron, D. C., Keith, R. E., Kirsh, S. R., Alexander, J. A., & Lowery, J. C. (2009). Fostering implementation of health services research findings into practice: A consolidated framework for advancing implementation science. Implementation Science, 4, Article 50. https://doi.org/10.1186/1748-5908-4-50

Dykes, P. C., Carroll, D. L., Hurley, A., Lipsitz, S., Benoit, A., Chang, F., Meltzer, S., Tsurikova, R., Zuyov, L., & Middleton, B. (2010). Fall prevention in acute care hospitals: A randomized trial. JAMA, 304(17), 1912-1918. https://doi.org/10.1001/jama.2010.1567

Sendelbach, S., & Funk, M. (2013). Alarm fatigue: A patient safety concern. AACN Advanced Critical Care, 24(4), 378-386. https://doi.org/10.1097/NCI.0b013e3182a903f9

Shorr, R. I., Chandler, A. M., Mion, L. C., Waters, T. M., Liu, M., Daniels, M. J., Kessler, L. A., & Miller, S. T. (2012). Effects of an intervention to increase bed alarm use to prevent falls in hospitalized patients: A cluster randomized trial. Annals of Internal Medicine, 157(10), 692-699. https://doi.org/10.7326/0003-4819-157-10-201211200-00005

Tzeng, H.-M., & Yin, C.-Y. (2009). Relationship between call light use and response time and inpatient falls in acute care settings. Journal of Clinical Nursing, 18(23), 3333-3341. https://doi.org/10.1111/j.1365-2702.2009.02916.x

Wong, C. A., Recktenwald, A. J., Jones, M. L., Waterman, B. M., Bollini, M. L., & Dunagan, W. C. (2011). The cost of serious fall-related injuries at three Midwestern hospitals. Joint Commission Journal on Quality and Patient Safety, 37(2), 81-87. https://doi.org/10.1016/S1553-7250(11)37010-9

What the NUR 633 Module 9 instructions ask for

The NUR 633 final project usually asks for a complete informatics project proposal: the problem and its significance, supporting data and evidence, a workflow or systems analysis, the proposed solution, privacy, security and usability considerations, costs, an implementation plan and evaluation. Some sections add a presentation for a steering committee. Expect eight to twelve pages in APA 7. Revise the milestones into one argument, keep numbers consistent, show how each part of the design answers a specific failure point, estimate costs against a credible measure of value and set a decision rule for continuing or stopping, because the final project is graded as a proposal a real committee could approve. Keep numbers consistent throughout.

How this NUR 633 Module 9 final project example is built

The sample proposes integrated fall risk alerts for a composite unit with 38 falls and 9 injuries in a year. It condenses the linked incident and nurse call data, summarizes the Tzeng, Shorr, Sendelbach and Dykes evidence as design principles and restates the SEIPS failure points. The design maps each failure point to a change in existing systems. Privacy safeguards limit badge messages to room and risk level, and the design adds no documentation. A $48,000 budget is set against the Wong estimate of about $13,800 in added cost per serious-injury fall. A 16-week CFIR-informed rollout and an evaluation with a week-16 decision rule complete the proposal, followed by a one-year review.

Where the NUR 633 Module 9 rubric puts the points

Final project rubrics in NUR 633 usually weigh the problem and significance, use of data and evidence, the systems analysis, the proposed solution, privacy and usability, cost and value, implementation, evaluation and APA 7 writing. Strong proposals present one coherent argument in which the design follows from the analysis, costs are itemized and compared with value, privacy is handled precisely and evaluation includes a decision rule. Graders reward proposals that use existing systems where possible and that avoid adding documentation burden. A proposal that commits to measuring honestly and retiring a tool that does not work reads as credible to decision-makers and often earns full marks for professionalism.

NUR 633 Module 9 help: the mistakes that cost points

Informatics proposals lose points when the solution appears before the problem is established, when sections contradict each other, when costs are missing or unsupported, when privacy is mentioned only in general terms or when evaluation has no decision point. A common gap is proposing new hardware when existing systems could be connected. Build one argument from data to design, show how each design element answers a failure point, itemize costs against a published measure of value, specify privacy safeguards, phase the rollout and set a decision rule. If your project addresses a different problem, send your milestones and final guidelines for a proposal built on them and your unit's data.

Get NUR 633 Module 9 written to your instructions

Send your milestones, your instructor's feedback and the final project guidelines. A proposal that builds one argument from data to design, itemizes costs against value, handles privacy precisely and sets a decision rule will be ready within 24 to 48 hours, and the first is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.

More NUR 633 papers and related MSN samples

NUR 633 Module 9 questions, answered

Where can I find a free NUR 633 Module 9 Final Project sample?

This page shows a complete informatics proposal: integrated fall risk alerts for a medical-surgical unit, with data, evidence, systems analysis, design, privacy, budget, rollout and evaluation.

What sections belong in a nursing informatics project proposal?

Problem and significance, data and evidence, systems or workflow analysis, proposed solution, privacy and usability, costs and value, implementation plan and evaluation with a decision rule.

How much does a serious fall injury cost a hospital?

A study at three hospitals found that falls with serious injury added about $13,800 in operational costs and nearly a week to the length of stay, compared with similar patients who did not fall.

How can informatics reduce inpatient falls?

By delivering patient-specific fall risk and prevention plans to the people who respond, routing alerts to the assigned caregiver and reducing nonactionable alarms, rather than simply adding more alarms.

What is a decision rule in a technology project?

A condition agreed in advance that determines whether the system continues, is adjusted or is stopped, based on specific measures at defined points.