Installing a nurse call system in a live hospital environment is one of the most logistically complex IT projects a biomedical or facilities engineering team will undertake. Unlike office IT deployments, every installation decision has a direct clinical impact — a ward that goes offline for an afternoon is a ward that cannot call for help.
This guide walks through the complete installation process for an IP-based nurse call system in a hospital environment, from pre-installation network assessment to post-go-live validation. It is written for biomedical engineers, facilities managers and hospital IT teams.
Before You Begin: What This Guide Assumes
This guide assumes:
- You are installing an IP-based nurse call system (not analogue/hardwired)
- Your hospital has an existing Ethernet network infrastructure
- Installation will be done in a live clinical environment (wards remain operational during installation)
- You have received hardware and software documentation from your vendor
If you are replacing an existing analogue system, your vendor should provide a migration plan specific to your site. Do not attempt to run analogue and IP systems simultaneously without explicit vendor guidance — clock conflicts and wiring interactions can cause both systems to behave unpredictably.
Phase 1: Pre-Installation Planning (2–4 Weeks)
1.1 Network Infrastructure Assessment
The single most common cause of IP nurse call installation delays is inadequate network preparation. Complete this assessment before any hardware arrives on site.
Switch inventory. Identify every network switch that will serve nurse call devices. For each switch, confirm:
- Available POE (Power over Ethernet) port count and total POE budget (watts)
- Current firmware version (vendor will specify minimum requirements)
- VLAN configuration capability
- UPS (uninterruptible power supply) coverage
Bandwidth capacity. Nurse call systems generate modest but continuous traffic. A 200-bed deployment with two-way audio at every bedside will use approximately 2–4 Mbps of sustained bandwidth on its VLAN. Confirm your core switches and uplinks have sufficient headroom.
VLAN planning. Create a dedicated VLAN for nurse call traffic before installation begins. This isolates nurse call from general hospital IT traffic and allows QoS (Quality of Service) priority rules to be applied. Work with your network team to assign VLAN ID and IP address range before hardware arrives.
Wireless assessment (if applicable). If mobile app notifications will be used, conduct a site survey to identify Wi-Fi dead spots. Clinical corridors and ward bays must have continuous Wi-Fi coverage. DECT handsets require their own base station planning — typically one base station per 30–40 metres of linear coverage.
1.2 Device Placement Planning
Walk every ward with the installation team and mark device locations on floor plans. For each room, document:
- Bedside station position (headwall, bedside rail, ceiling-mounted)
- Call cord or pull cord routing (especially for bathroom/wet area positions)
- Room Terminal position (wall mounted at entrance)
- Door light position (standard is above door, outside room)
- Corridor display position (above nurse station, corridor junction)
- Ethernet cable routing path (from device to nearest network cabinet)
- Power source (most IP devices are POE-powered — confirm POE availability at each drop)
Photograph each planned location. Disputes about device placement are common once installation begins — photographs from the planning walk provide an agreed baseline.
1.3 Ward-by-Ward Installation Schedule
In a live hospital, you cannot take an entire building offline. Build a ward-by-ward schedule that:
- Starts with the lowest-acuity ward (day surgery, outpatient) as a pilot
- Allows 1–2 weeks per ward depending on bed count and complexity
- Schedules ICU and high-dependency units last (when the team has maximum experience)
- Avoids installation during peak shift change periods (typically 07:00–09:00 and 13:00–15:00)
- Includes buffer time for network issues, hardware DOA replacements and scope changes
Share the schedule with nursing management and the infection control team. Both will have requirements that affect your timeline — infection control may restrict drilling and dust-generating work to specific hours.
1.4 Stakeholder Communication
Before installation begins, brief:
- Ward managers on what will change, when and what downtime (if any) to expect
- IT/network team on VLAN requirements, switch configuration and firewall rules
- Clinical informatics / HIS team on integration requirements (ADT feeds, API credentials)
- Facilities/estates team on cable routing, wall penetrations and aesthetics
Phase 2: Network Configuration (1 Week)
Complete all network configuration before any physical hardware is installed. Trying to configure the network while devices are being installed adds confusion and extends the timeline.
2.1 VLAN Creation and Switch Configuration
On every switch that will serve nurse call devices:
1. Create VLAN [your assigned ID, e.g. VLAN 40]
2. Name it: NURSECALL
3. Set QoS: mark nurse call traffic as priority (DSCP EF or CS5)
4. Configure inter-VLAN routing to allow nurse call server communication
5. Apply POE budget limits per port if required by vendor
Save and document the switch configuration. You will need to replicate it on every access switch in the deployment.
2.2 Server Preparation
The nurse call management platform runs on a server (physical or VM) in your data centre. Standard requirements for a 200-bed deployment:
- CPU: 8 cores
- RAM: 16 GB
- Storage: 500 GB SSD (OS + application + 2 years of call data)
- OS: As specified by vendor
- Network: Static IP on management VLAN, firewall rule to allow nurse call VLAN traffic on required ports (vendor will specify)
- Backup: Daily automated backup of application data to separate storage
2.3 Firewall and Security Rules
Create firewall rules to allow:
- Nurse call devices (VLAN 40) → Nurse call server (management VLAN) on vendor-specified ports
- Nurse call server → HIS/EMR server on HL7 port (typically 2575 for TCP HL7 MLLP)
- Block all other traffic from nurse call VLAN to general hospital network
Phase 3: Hardware Installation (4–8 Weeks, Ward by Ward)
3.1 Pilot Ward Installation
Begin with your chosen pilot ward. Complete the full installation process on this ward before moving to the next.
Cable installation:
- Run CAT6 (minimum) from each device location to the nearest network cabinet
- Label both ends of every cable with a unique identifier matching your floor plan
- Test every cable with a cable tester before patching into the switch
- Failed cables must be replaced, not accepted — a marginal cable that passes today may fail in 6 months
Device mounting:
- Mount bedside stations at the height specified in your floor plan
- Ensure call cord/pull cord reaches the bed in every position (adjust bed position to test)
- Secure door light cables in trunking — exposed cables in clinical areas are an infection control risk
- Corridor displays should be at eye level, not mounted at ceiling height
Device connection:
- Patch each IP device cable into the switch on the nurse call VLAN port
- Patch each in-room auxilliary device to the room's Master IP device
- Confirm POE power-up — most IP devices have a LED status indicator
- Log MAC address and physical location for each device in your device inventory spreadsheet
3.2 Device Configuration
Once devices are powered and connected, configure them via the nurse call management platform:
- Device discovery — the platform should automatically detect devices on the nurse call VLAN
- Room assignment — assign each device to its room/bed in the platform
- Call type configuration — assign call types to each device (standard call, emergency, bathroom pull cord)
- Audio configuration — set call tone volume, two-way audio settings, night mode volumes
3.3 Pilot Ward Commissioning Test
Before going live on the pilot ward, complete a full commissioning test:
- [ ] Every call button tested individually — call reaches platform, notification sent
- [ ] Two-way audio tested from every bedside station
- [ ] Emergency call tested: reaches charge nurse immediately, does not wait for primary nurse
- [ ] Bathroom/pull cord tested: call type correctly identified in platform
- [ ] Door light tested: illuminates with correct colour on call, cancels on answer
- [ ] Corridor display tested: shows active calls, clears on answer
- [ ] Mobile notification tested: staff on test smartphones and DECT handsets receive calls
- [ ] Call cancel tested: nurse cancels call at bedside and from mobile
- [ ] Analytics tested: all call events appearing in dashboard with correct timestamps
Do not go live until every item on this list passes. Issues found after clinical go-live are significantly harder to resolve.
Phase 4: HIS Integration (Parallel with Phase 3)
HIS integration can be configured and tested in parallel with hardware installation, since it does not require physical devices.
4.1 ADT Feed Configuration
The minimum viable integration is an HL7 ADT (Admit, Discharge, Transfer) feed from your HIS to the nurse call platform. This ensures patient names and room assignments are automatically synchronised.
Work with your HIS vendor or clinical informatics team to:
- Configure an HL7 outbound interface from the HIS
- Point it at the nurse call server's HL7 listener (port specified by vendor)
- Test with a sample patient admission — confirm patient name appears in nurse call platform within 60 seconds
4.2 Integration Testing Scenarios
Test the following scenarios with your HIS team:
- Patient admitted → appears in nurse call platform in correct room
- Patient transferred between wards → nurse call platform updates room assignment
- Patient discharged → removed from nurse call platform, room shown as vacant
- Patient name change (edge case) → updates correctly in platform
Phase 5: Staff Training (1 Week Per Ward)
Training should happen immediately before each ward goes live — not weeks in advance. People forget, and live systems are more memorable than simulation.
Nursing staff training (60–90 minutes):
- How to receive and acknowledge calls on the mobile app and DECT handset
- How to respond to emergency calls vs routine calls
- How to cancel calls at the bedside station
- What to do if the system shows an error
Charge nurse training (additional 30 minutes):
- How to view and manage the live call queue dashboard
- How to reassign calls to different nurses
- How to access response time reports
IT/biomedical training (half day):
- Device replacement procedure
- Common fault diagnosis
- Remote diagnostics access (if enabled)
- Escalation path to vendor support
Phase 6: Go-Live and Post-Go-Live Monitoring
6.1 Go-Live Day Protocol
On go-live day for each ward:
- Vendor engineer and biomedical team member present for the full shift (at minimum)
- IT support on standby remotely
- Test all call functions at the start of the shift before patients are in beds
- Brief ward staff again on the day — a 5-minute reminder at handover
6.2 First-Week Monitoring
During the first week on each ward, review:
- Response time data daily: are calls being answered? Any unacknowledged calls?
- Escalation events: are escalations triggering correctly?
- Staff feedback: what is confusing or not working as expected?
- Device faults: any units not connecting, audio quality issues, LED indicators in fault state?
6.3 30-Day Review
After 30 days on each ward, conduct a formal review with the ward manager covering:
- Response time trend: improving, stable or worsening?
- Outstanding issues from go-live week
- Configuration adjustments needed (escalation timeouts, notification routing)
- Additional training needs
Common Installation Problems and Solutions
Problem: Devices power up but do not appear in the platform. Solution: Confirm the device is patched on the correct VLAN port. Check firewall rules allow VLAN traffic to reach the server.
Problem: Two-way audio is choppy or delayed. Solution: Check QoS configuration on all switches in the path. Audio packets must be prioritised. Also check for network congestion during peak hours.
Problem: Mobile notifications are delayed (>30 seconds). Solution: Check Wi-Fi coverage at staff locations. Check server load.
Problem: HIS ADT feed is not updating room assignments. Solution: Check HL7 interface is active in HIS. Check firewall allows HIS server to reach nurse call server on HL7 port. Check nurse call platform HL7 listener is running. Review HL7 message logs for errors.
Problem: Staff are not acknowledging calls. Solution: Usually a training issue, not a technical one. Run a brief refresher training session. Check that staff mobile devices have push notifications enabled for the nurse call app.
Frequently Asked Questions
Can we install a nurse call system without interrupting clinical operations? Yes, with proper planning. IP nurse call installation does not require taking wards offline. Cable installation creates dust and noise that requires infection control coordination, but devices can be installed during quiet periods and tested before going live. Patient care continues throughout.
Do we need to replace our existing network switches? Not necessarily. Most enterprise-grade switches installed in the last 10 years support the VLANs, QoS and POE required for IP nurse call. Your vendor will provide a compatibility specification. Switches that are end-of-life or lack POE capacity will need upgrading.
How many network drops do we need per patient room? A standard two-bed room typically requires 1 cable drop per bed if beds use VoIP bedside stations, plus 1 drop for the IP Room Terminal . Auxilliary devices within the room (batroom pull cord, or over door corridor light) requires patching to the IP Room Terminal. Confirm with your vendor's hardware configuration guide.
What is the typical warranty on nurse call hardware? IP nurse call hardware is typically warranted for 2 years by manufacturers. Extended warranties of 5 years are available from most vendors. Beyond warranty, a hardware maintenance contract covering parts and labour is standard practice for clinical equipment.
Who is responsible if a nurse call device fails and a patient is harmed? This is a question for your hospital's legal and risk management team. In practice, the maintenance contract and SLA with your vendor establish the commercial framework for device failure response. Clinical risk management should document the escalation procedure (backup communication methods) when nurse call devices are offline for any reason.
ZKR's implementation team has deployed nurse call systems in more than 1000 hospitals from 50 to 5,000 beds. Our engineers provide on-site support throughout installation and post-go-live monitoring. Contact us to discuss your project.