It operates the system rather than only reporting it - accepting and routing calls, registering staff, configuring, and producing reports.

An annunciator panel's job is to show the state of the ward. Many panels also allow acknowledgement, but their purpose is indication.

A console is an interface. From it a member of staff can accept a call and assign it, escalate one that has waited, register presence in a room, adjust zone or routing configuration within permitted limits, and run the reports that ward management needs.

It is also where the system's administrative functions live: adding a room, changing a call type, updating staff records.

That difference means the console needs access control - not everything on it should be available to everyone - and it needs to remain usable when several calls are active, which is the condition under which its interface is really tested.

Because it is used hardest exactly when the user has least attention to give it.

A console is operated during a busy shift, often by someone who is simultaneously doing something else, and sometimes in an emergency. In those moments an interface that requires navigation, or that presents the important control alongside a dozen others, will be used wrongly or not at all.

The practical consequences of poor design are calls not acknowledged because it took too long, escalation not used because nobody remembers where it is, and staff developing workarounds that the reporting then fails to capture.

So the things to look for are: accepting a call in one action, the most urgent call unmistakably prominent, controls that are hard to trigger accidentally, and legibility at a glance rather than on inspection.

Have it demonstrated with several simultaneous calls of different types. Any console looks usable with one call on screen.

Mobile and DECT handsets, staff location or attendance systems, reporting platforms, and sometimes building management or access control.

Mobile alerting is the most common and the most valuable: calls are pushed to staff devices with room and type, and can be accepted from the device, so response does not depend on being near a display.

Staff location or presence systems let the console know who is where, which supports routing a call to the nearest available person and automatically registering attendance when someone enters a room.

Reporting platforms take the event data for analysis and for the response-time evidence.

Each integration is also a dependency. Establish what the console does when one fails - a system that stops signalling calls because a reporting server is unreachable would be unacceptable, and it is the sort of behaviour that only emerges under test.

Ask specifically about degraded-mode behaviour for each interface.

Operational functions to clinical staff, configuration and reporting to designated administrators - enforced by the system rather than by convention.

Accepting, routing and escalating calls is everyday clinical work and must be immediately available with no barrier.

Changing zones, call types, escalation timers or staff records affects how the system behaves for everyone and should be restricted to people who understand the consequences. A well-meant configuration change made during a busy shift is a realistic way to break a working system.

Reporting access needs its own consideration because the data identifies patients and staff, so it falls under data protection requirements.

Role-based access with individual logins is the normal arrangement, though the login must not obstruct the emergency operational functions.

Agree the roles at commissioning and review them, since shared generic logins tend to appear wherever the access control is inconvenient.

A member of staff registers their presence in a room, which tells the system the call is being attended and starts the attendance record.

Registration is done by pressing a presence button in the room, by presenting a badge, or automatically by a staff location system detecting the person entering.

The effect is that displays show the call as attended rather than waiting, so other staff do not divert to it, and the elapsed timer for response stops - which is what makes the response-time reporting meaningful.

Presence is also what allows a staff-assist call to be raised from that room: a nurse already in attendance who needs help presses a different button, and the system knows who and where.

The practical requirement is that registering presence must be quick and habitual. If it is fiddly it will be skipped, the reporting becomes inaccurate, and the staff-assist function is unavailable when it is needed.

The call points and displays should continue to function - and confirming that is one of the more important questions to ask.

A nurse call system has life-safety relevance, so the failure of a management interface must not take out the basic call-to-display path.

In a well-architected system the call points, room lamps, corridor displays and annunciators operate through the system's own controllers, and the console is a client. Losing it costs acknowledgement, routing and reporting, but calls still raise and still display.

In a poorly architected one the console is in the path, and its failure is a system failure.

Ask explicitly what is lost when the console is off, and test it at commissioning by removing it. Also establish whether a second console can take over, and whether configuration is held centrally or on the console itself - because a console holding the only copy of the configuration is a single point of failure with a long recovery.

Brief, repeated, and covering the emergency path rather than the full feature set.

Most staff need to do three things reliably: recognise what the system is telling them, accept a call, and raise a staff-assist or emergency call themselves. Those should be trained to the point of being automatic.

The remaining functions - reporting, configuration, administration - concern a much smaller group and can be trained separately and in depth.

The common failure is a single handover session at installation, after which staff turnover erodes competence until nobody remembers anything beyond the basics. Building brief refreshers into ward induction is far more effective than a longer initial session.

It is also worth testing understanding rather than attendance: ask a member of staff to demonstrate raising and clearing an emergency call. That reveals gaps a signed training record does not.