NUR 633 Module 5 Milestone Two Example

Reviewed by Delia Ravenscroft, MSN, RN

This NUR 633 Module 5 Milestone Two sample does the analysis most technology projects skip: tracing exactly how the current work happens before designing anything new. It meets the second milestone of SNHU NUR 633, Informatics and Communication Technology, the SNHU MSN informatics course numbered NUR-633. Building on the falls data from Milestone One, it uses the SEIPS work system model to examine the people, tasks, tools, environment and organization involved when a high-risk patient on composite unit 6 West tries to get up at night. A step-by-step map follows a bed-exit alarm and a call light across the nurse call system, the bed sensors, the nurses' badges and the electronic record and finds four points where information is lost or delayed. The milestone ends with numbered requirements covering what the integrated system must do, the technical conditions it must meet and the human and privacy conditions for its use.

CourseNUR 633 Informatics and Communication Technology
ModuleModule 5
Paper typeMilestone: systems and workflow analysis with requirements
LengthAbout 1,040 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMSN
UpdatedSeptember 2026

Free sample paper for NUR 633 Module 5

1

Milestone Two: A Work System Analysis of the Night-Shift Fall Response on 6 West

[Student Name]

Southern New Hampshire University

NUR 633: Informatics and Communication Technology

Milestone Two

[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 names the milestone, the method and the specific workflow being analyzed, which keeps the analysis bounded.
2

Milestone Two: A Work System Analysis of the Night-Shift Fall Response on 6 West

Milestone One showed that most falls on 6 West occur at night, often soon after an unanswered call or alarm, and that the patient's fall risk never leaves the electronic record. Before any solution is designed, the project needs to know how the current system produces those results. Technology added without that understanding tends to create new work, new alarms and workarounds. This milestone analyzes the night-shift fall response as a work system. It argues that the problem arises from the interaction of several systems that were each designed separately and that the requirements for any solution must address people and workflow as well as software.

What this page is doingThe introduction links to the prior milestone, explains why analysis must precede design and states the systems-level argument.
3

The SEIPS Framework

The Systems Engineering Initiative for Patient Safety model describes a work system as five interacting components: the people doing the work, the tasks they perform, the tools and technologies they use, the physical environment and the organization, including staffing and policies. It holds that these components together shape care processes, which in turn shape patient and staff outcomes (Carayon et al., 2006). The model is useful here because falls are rarely caused by one component; they emerge when a tired nurse, an ambiguous alarm, a distant room and a staffing ratio combine at the wrong moment.

What this page is doingThe framework is explained with its source and justified for this problem, which sets up a structured analysis rather than a list of observations.
4

The Work System at Night

People: the night crew on 6 West is five RNs plus a single nursing assistant covering as many as 32 patients, a ratio of about one nurse to six or seven patients. Two of the five night nurses have less than a year of experience. Tasks: nurses are giving medications, managing admissions from the emergency department and answering calls, often simultaneously. Tools: four separate systems are involved. The nurse call system receives call lights and bed-exit alarms and displays them on a station console and a hallway dome light. Bed sensors trigger when weight shifts, at one of three sensitivity levels set by the nurse. Nurses carry wireless badges that receive voice calls but not alarm messages. The electronic record holds the Morse score and fall precautions in flowsheets. Environment: the unit is L-shaped, and rooms at the far end are about 60 meters from the station; bathrooms are across the room from the bed. Organization: policy requires bed alarms for any patient with a Morse score of 45 or higher, and the nursing assistant is expected to answer most calls.

What this page is doingEach SEIPS component is described with specifics, including numbers and physical details, so later findings can be traced to particular parts of the system.
5

Current Workflow Map

Tracing a typical night event shows the steps, and each one was confirmed by shadowing two night shifts and reviewing the nurse call log for the same hours. A high-risk patient in a far room wants to use the bathroom and shifts toward the edge of the bed. The bed sensor, set to its most sensitive level by default, triggers. The alarm appears on the station console and the hallway dome light over the room, with no indication of the patient's risk level, and sounds at the station. If no one is at the station, the alarm is heard only by staff nearby. The nursing assistant, often in another room, may not hear it. After 90 seconds without cancellation, the alarm repeats. No message reaches any nurse's badge. The assigned nurse, in a medication room, eventually hears it or sees the dome light. By then, a patient determined to reach the bathroom may already be walking. Meanwhile, the Morse score in the record has been documented but is visible to no one in this sequence. The same event during the day unfolds differently: more staff are present, the station is usually occupied and the alarm is often answered within two minutes. The contrast explains why the falls cluster at night. The technology is identical across shifts; what changes is the number of people available to hear an alarm that reaches only the station, which is itself a design flaw rather than a staffing problem alone.

What this page is doingThe workflow map follows one realistic event step by step, making the delays and missing information concrete.
6

Where Information Is Lost

The analysis identifies four failure points. First, the alarm carries no priority: a high-risk patient's bed exit looks the same as a low-risk patient rolling over, which contributes to the alarm fatigue documented in the literature, where most alarms are false or nonactionable (Sendelbach & Funk, 2013). Second, alarms route to a place, the station, rather than to a person, the assigned nurse or assistant. Third, the most sensitive sensor setting, chosen by default, produces many alarms for patients who are only moving in bed. Fourth, the patient-specific risk information in the record, and the individualized plan that could accompany it, never reaches the people responding. The Fall TIPS trial showed that making a patient-specific fall prevention plan visible at the bedside reduced falls (Dykes et al., 2010), which suggests that closing the fourth gap could matter as much as speeding response.

What this page is doingThe failure points are drawn directly from the map and linked to evidence, which justifies the requirements that follow.
7

Requirements

The analysis yields requirements, stated so that any proposed solution can be tested against them. Functional requirements: R1, a fall risk flag shall pass automatically from the chart into the call platform whenever the Morse score is documented at 45 or above; R2, bed-exit alarms from flagged patients shall route to the assigned nurse's and assistant's badges with the room number and risk level, escalating to the charge nurse if not acknowledged within 60 seconds; R3, bed sensors shall default to a moderate sensitivity, with the most sensitive setting chosen deliberately for patients who meet defined criteria; R4, a patient-specific fall prevention plan shall display on the room whiteboard and the badge. Technical requirements: R5, the interface between the record and the nurse call system shall use the hospital's existing integration engine and standard messages; R6, alarm and response times shall be logged for evaluation. Human and privacy requirements: R7, badge messages shall show only the minimum information needed, such as room number and risk level, not diagnoses; R8, no requirement shall add documentation for nurses; R9, night staff shall be involved in testing before go-live.

What this page is doingRequirements are numbered, testable and span function, technology, people and privacy, including a requirement that the solution add no documentation.
8

Conclusion

The night fall response on 6 West fails at four points where systems designed separately meet: alarms without priority, alarms routed to a place rather than a person, oversensitive defaults and risk information trapped in the record. Nine requirements, grounded in the SEIPS analysis and the evidence, will guide the design and the implementation plan in Milestone Three.

What this page is doingThe conclusion summarizes the failure points and links the requirements to the next milestone.
9

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

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

What the NUR 633 Module 5 instructions ask for

Milestone Two of the NUR 633 project usually asks for a systems or workflow analysis: describing the current processes, people, technologies and environment related to the problem, identifying gaps and stating requirements for a solution. Many prompts suggest a framework such as SEIPS or the systems development life cycle and ask for a workflow diagram or narrative map. Expect three to five pages in APA 7. Describe each component of the work system with specifics, trace the current workflow step by step, identify exactly where information is lost or delayed and write numbered, testable requirements that include people and privacy, since graders look for analysis that could guide a real design team and vendor selection. Validate the map by observation.

How this NUR 633 Module 5 milestone two example is built

This sample analyzes the night fall response on a composite 32-bed unit using the SEIPS model. It describes the people, tasks, four separate systems, the L-shaped layout and the bed alarm policy, then traces a far-room bed exit step by step, from an oversensitive sensor through an alarm that sounds at an empty station to a nurse who hears it late. Four failure points follow, each tied to evidence from Sendelbach and Funk on alarm fatigue and the Dykes Fall TIPS trial. Nine numbered requirements cover risk flags from the record, badge routing with escalation, sensor defaults, bedside plans, integration, logging, minimum necessary display, no added documentation and staff testing.

Where the NUR 633 Module 5 rubric puts the points

Systems analysis rubrics typically score the use of an appropriate framework, a thorough description of the current state, identification of gaps and root causes, clear requirements, attention to users and workflow and APA 7 writing. Top-band work traces the workflow in enough detail to reveal specific failure points, links those points to evidence and states requirements that are numbered and testable. Graders reward requirements that address privacy and documentation burden as well as function, and plans to involve end users in testing. Keeping the analysis separate from a specific vendor product shows sound informatics practice, which often earns credit under the analysis criteria of the rubric.

NUR 633 Module 5 help: the mistakes that cost points

Workflow analyses lose points when they describe technology without the people and environment around it, when the current state is summarized rather than traced, when gaps are not tied to evidence or when requirements are vague, such as the system should be user-friendly. Another common error is naming a product before stating requirements. Use a framework, describe each component with specifics, map the workflow step by step, identify failure points and write numbered requirements that can be tested, including privacy and burden. If your project involves medication administration, handoffs or discharge, send the milestone guidelines and a description of how the work runs on your unit, and the analysis will follow your systems.

Get NUR 633 Module 5 written to your instructions

Send the milestone guidelines, a description of your unit's current workflow and the rubric. A systems analysis that applies a framework, traces the workflow step by step, finds the failure points and states numbered, testable requirements will be ready in 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 5 questions, answered

Where can I find a free NUR 633 Module 5 Milestone Two sample?

This page holds the whole milestone: a SEIPS work system analysis of the night fall response on a medical-surgical unit, with a current workflow map, four failure points and nine requirements.

What is the SEIPS model?

The Systems Engineering Initiative for Patient Safety model describes a work system of people, tasks, tools and technologies, environment and organization, which together shape care processes and outcomes.

Why analyze workflow before choosing technology?

Because technology added without understanding the current work often creates new steps, alarms and workarounds. Mapping the workflow shows where information is actually lost.

How should informatics requirements be written?

As numbered, specific statements that a solution can be tested against, covering function, technical conditions, users and privacy, without naming a particular vendor product.

Why route alarms to a person instead of a station?

An alarm that sounds at an empty station may go unheard. Routing it to the assigned nurse's device, with escalation if not acknowledged, makes responsibility clear.