Artificial Intelligence

Edge AI in Hospitals

Why more inference is moving into the room itself, and what changes when it does.

11 min readUpdated July 2, 20263 topics

Why edge

Edge AI runs inference on hardware inside the room — a camera's on-board chip, a small appliance under the monitor, a GPU in the wiring closet — instead of a distant data center. Hospitals choose it for three reasons:

  • Latency. Fall detection is useless if the alert arrives ten seconds late.
  • Bandwidth. Streaming high-resolution video from every room is expensive and stresses the network.
  • Privacy. Raw video and audio never have to leave the room.

Edge–fog–cloud topology

Interactive diagram

Fig. — Where inference can live. Most durable deployments split the work.

Use the plus and minus buttons or the plus and minus keys to zoom. Drag with the mouse or use the arrow keys to pan. Press 0 to reset.

Where it shows up

  • Computer vision — fall detection, bed-exit prediction, hand-hygiene compliance, patient acuity signals.
  • Audio analytics — cough classification, distress vocalization, agitation detection, ambient documentation.
  • Physiological signals — arrhythmia detection at the monitor, ventilator asynchrony detection, contactless respiration.

Vision and audio benefit most from on-device processing because raw data is sensitive, voluminous, and expensive to move.

The operational cost

Edge AI is not free. Every device needs firmware and model updates, health monitoring, and a plan for what happens when it drifts, breaks, or is unplugged during a room turnover. Successful programs treat edge AI as fleet management, not a one-time install:

  1. Signed OTA updates with staged rollout.
  2. Continuous performance monitoring per device.
  3. Model versioning tied to the medical device software configuration.
  4. Documented shadow-mode period before clinical alerts are enabled.

Governance & standards

FrameworkRelevance
FDA Good Machine Learning Practice (GMLP), 10 principlesBaseline expectations for ML-enabled medical devices
FDA Predetermined Change Control Plan (PCCP) guidanceGoverns allowed model updates post-clearance
IEC 62304Medical device software lifecycle
ISO/IEC 42001AI management system
WHO Ethics & governance of AI for healthValues framework

References & further reading

  1. 1FDA/Health Canada/MHRA — Good Machine Learning Practice for Medical Device Development
  2. 2FDA Guidance — Marketing Submission Recommendations for a Predetermined Change Control Plan
  3. 3IEC 62304 Medical device software — Software life cycle processes
  4. 4ISO/IEC 42001:2023 AI management system
  5. 5WHO — Ethics and governance of artificial intelligence for health (2021)

Help us improve

Spotted something wrong, outdated, or unclear? Let the editors know.