Your Hospital Bought AvaSure. Who Is Maintaining Everything Around It?

It is the middle of a night shift, and a virtual safety attendant is watching a grid of patient rooms on the AvaSure platform. In one tile, a patient at high fall risk starts to shift toward the edge of the bed — but the video stutters and freezes, and when the attendant keys the two-way audio to redirect him, the sound comes through thin and broken. The cart in that room is powered on and the platform shows it as connected, yet a weak wireless signal and a battery near the end of its life have quietly degraded exactly the two things that matter most in that moment: a clear view and a clear voice.

That scene is a composite, drawn to illustrate a failure mode rather than any real event. But it points to something true about virtual observation programs. AvaSure pioneered this category with its TeleSitter® solution more than a decade ago, and its platform lets a single virtual safety attendant monitor multiple at-risk patients from a central workstation using real-time video and two-way audio, with computer-vision alerts and an in-room alarm to prompt fast intervention. The vendor supplies the software, the cameras and carts and ceiling devices, and a clinical support team. What it does not own is the hospital environment those tools run inside — and that environment is where day-to-day reliability is actually won or lost.

What AvaSure gives you, and what your building still owns

It helps to be precise about the boundary. AvaSure provides the observation platform, its devices, and vendor support. Your organization provides the ground it all stands on: the wireless coverage in every monitored room, the switching and network path the video crosses, the segmentation and firewall rules, the bandwidth to carry many simultaneous streams, the monitoring workstations and their configuration, and the physical upkeep of the carts themselves. When a feed degrades, the cause frequently lives on that hospital-owned side of the line — which is also the side a software vendor is not positioned to manage shift by shift.

A cart can look fine and still fail

A TeleSitter cart can be online and still be quietly compromised. A weak access point, a battery that no longer holds a charge, a microphone or speaker that has started to fail, a smudged or damaged camera, or a workstation running a stale configuration each looks like nothing on a status screen. But each becomes a clinical problem the moment an observer cannot clearly see a patient, cannot redirect them through audio, or cannot reach the bedside team quickly. The equipment does not have to be "down" to fail the patient. It only has to be degraded at the wrong time.

Wireless, bandwidth, and the network path

Everything the attendant sees and says depends on the network beneath it. Wireless has to be engineered for genuine signal strength and clean roaming as carts move between rooms and units, not merely for general office coverage. The observation traffic needs its own place on the network — appropriate VLAN segmentation, firewall rules that permit the platform's required connections, quality-of-service treatment so clinical video is not starved by other traffic, and enough bandwidth to carry many persistent streams at once. A network that looks healthy on a routine dashboard can still deliver frozen tiles and lagging audio, which is why coverage and capacity have to be validated in the real rooms with the real devices.

The monitoring station is the observer's whole world

The workstation in the monitoring room is the single window through which an observer watches every patient, so its reliability is not a detail. Screen count and layout shape what gets noticed, and workstation performance, multi-monitor stability, current operating-system and application configuration, and sensible session handling all determine whether that window stays clear across a long shift. A sluggish or misconfigured station degrades observation for every room at once, not just one.

Test the alarms and the escalation path

An observer who spots trouble is only useful if the tools to act on it work. That means routinely testing the cameras, microphones, and speakers in each room; confirming the in-room alarm actually sounds; and verifying that the escalation path — from a spoken redirection to summoning the bedside team — reaches a real person who responds. These are the components most easily assumed and least often exercised, and a program should prove they work on a schedule rather than discovering a dead speaker during an event.

Batteries, inventory, and preventive maintenance

Mobile carts live hard lives, and the unglamorous logistics keep them dependable. Charging routines that keep batteries healthy, an accurate inventory of every cart and device and where it is, and a preventive-maintenance schedule that catches aging batteries, failing peripherals, and drifting configurations before they fail in a room — these are what separate a fleet that is ready every shift from one that degrades quietly until a bad night exposes it.

Have a plan for when the platform is down

Even a well-run program will eventually face an outage — a network event, a workstation failure, a platform or connectivity interruption. Because observation is now a patient-safety function, the response cannot be an ordinary IT ticket handled on the usual timeline; it needs a defined downtime procedure, an immediate fallback to in-person observation for the patients who need it, and clear ownership of who makes that call and how fast. We treat this scenario in depth in a companion piece on telesitter downtime and patient-safety planning.

A readiness checklist for the infrastructure around AvaSure

Before you count on the platform for the next shift, work through what surrounds it:

• Validate wireless coverage and roaming in every monitored room, using the actual carts.
• Confirm VLAN segmentation, firewall rules, quality of service, and bandwidth for concurrent video.
• Verify monitoring-workstation performance, multi-monitor stability, and current configuration.
• Test cameras, microphones, speakers, and the in-room alarm on a schedule.
• Exercise the full escalation path from audio redirection to bedside response.
• Maintain cart battery-charging routines and replace aging batteries proactively.
• Keep an accurate inventory of carts and devices, with a preventive-maintenance schedule.
• Establish downtime procedures and an immediate in-person fallback, with named owners.
• Define where vendor support ends and local infrastructure responsibility begins.

Where the infrastructure conversation starts

An AvaSure investment delivers on its promise only when everything around it is dependable — the wireless, the network path, the workstations, the carts, and the operational routines that keep them ready. Those pieces sit inside your hospital, and they need an owner who treats them with the seriousness a patient-safety system deserves.

That is where Metro Relay works. As a Dallas–Fort Worth technology infrastructure advisor and implementation partner, Metro Relay helps healthcare organizations maintain the network, workstations, mobile carts, connectivity, and operational processes surrounding AvaSure TeleSitter deployments — including wireless assessment and roaming validation, network segmentation and firewall configuration, bandwidth and quality-of-service planning, workstation performance and lifecycle, device testing and preventive maintenance, and downtime and escalation procedures. What stays with the healthcare organization is everything clinical — which patients are appropriate, how observers and bedside teams respond, and what the protocols require. Metro Relay keeps the surrounding infrastructure dependable; it does not replace the platform or make the clinical calls.

Is your TeleSitter infrastructure actually ready for the next shift? Request a virtual-care infrastructure assessment.