Hospitals and healthcare · Physical Operations Intelligence

At which configured physical handoff does operational flow begin to slow?

In a controlled pilot, supported non-clinical views can show waiting, occupancy, queue pressure, mapped operational flow, aggregate role-level coverage, and configured equipment or trolley movement. Clinical state and outcomes remain outside camera evidence.

Plan a Spatial Audit

First, we verify which camera views can reliably support each entrance, waiting area, room boundary, corridor, lift lobby, and equipment zone.

Evidence boundaryA camera can describe anonymous flow, waiting, covered room use, role-level presence, and equipment location in approved areas. Clinical context, appointments, verified room readiness, cleaning completion, equipment records, and transport jobs require an approved connected system.

Wide illustrative hospital operations scene connecting entrance, registration, waiting, triage, rooms, corridors, lifts, and an equipment bay without patient identity. — Illustrative operating view. No patient, customer, or performance result is shown.

Camera-native hospital operations scope

Build the non-clinical operating view from camera-verifiable physical signals.

This is a representative scope, not a fixed metric ceiling. A useful KPI starts with the physical handoff, operational role, facilities rule, and decision your team needs to understand.

Flow and occupancy

Entry, exit, footfall, occupancy, and density
Anonymous groups, peaks, area dwell, and mapped routes
Arrival, registration, and triage continuation
A supporting 2D heatmap and a primary 3D operating map

Waiting and handoffs

Queue, estimated waiting, and configured thresholds
Waiting pressure at registration, triage, and diagnostics
Covered room approach and room-use state
Physical route alignment across defined care stages

Rooms, transport, and equipment

Corridor and lift-lobby transfer pressure
Wheelchair, stretcher, and porter flow
Equipment location and availability in approved covered areas
Role-level team coverage without individual scoring

Facilities and response

Restroom entry and exit counts at the entrance boundary
Configurable use-count cleaning alerts and task rules
Configured pilot conditions with location, threshold, priority, and reviewed action
Hospital, region, department, and period comparison

Dashboard action signalsHospital network comparisonDashboardAPIsHospital-system context

Inside the physical hospital

At which configured operational handoff does physical flow become waiting?

Keep the hospital fixed. Change the question to see whether delay begins at arrival, registration, triage, a room boundary, a corridor, a lift lobby, equipment movement, or a facilities rule.

Hospital question

Comparison view

Registration to triage handoff

Read the selected question inside one mapped hospital.

Where does mapped registration flow become waiting at the triage handoff?

Connect registration departure, the triage approach, waiting pressure, and nearby role-level coverage in the same physical view.

What the camera can read

Registration departure
Triage approach and queue
Waiting pressure and role-level coverage

Camera reads

Suitable views can read entry and exit, footfall, anonymous groups, mapped routes, queue, estimated waiting, area occupancy and dwell, covered room-use state, corridor and lift-lobby pressure, role-level team presence, transport flow, equipment location in approved covered areas, and restroom entry and exit counts at the entrance boundary.

Connected systems confirm

An approved HIS, appointment, cleaning, room-status, equipment, or transport system confirms clinical or appointment context, task state, verified room readiness, cleaning completion, equipment records, and transport jobs. Camera observations are not matched to a medical record.

Cameras stay outside the restroom and read only its entrance boundary. The page does not identify patients, infer diagnosis or health status, interpret treatment, rank individual staff, or verify cleaning, hygiene, sterility, or room readiness. Hospital pilots require legal, information-security, and clinical-governance review.

Configured pilot condition

Registration to triage handoffQueue threshold and durationAttention

Registration departures continue while triage waiting remains above the configured threshold and the required operational role is not present nearby.

Manager-reviewed action

Review available triage support, routing, and the active waiting zone before pressure reaches the adjacent corridor.

Location-specific learning

Keep each facility’s configured operational context distinct.

In a standard deployment, camera images are processed on the on-site Edge PC. Continuous raw video is not sent over the WAN. Required anonymous operational metadata may synchronize to the cloud so model weights can learn recurring arrival, waiting, room, transfer, equipment, and facilities patterns for this hospital.

Learns local patterns

Keeps recurring flow, handoff, capacity, and facilities patterns specific to this hospital.

Presents a recommendation

Layout and operating recommendations go to manager review. Nothing is applied automatically.

Compares the network

Hospitals are compared under the same operating question while every location-specific model remains separate.

Start with camera suitability

Map the physical handoff you need to understand.

A Spatial Audit identifies usable views, blind areas, entrance and room boundaries, waiting zones, corridor and lift routes, equipment coverage, facilities rules, live conditions, connected-system requirements, and the first operating question worth measuring.

Plan a Spatial Audit

All six hospital questions remain available without interaction

Where does observable arrival flow begin waiting before registration?Read covered entrance flow, first direction, and the physical continuation to information or registration without identifying the person. Entry and exit by covered entrance · First mapped direction · Continuation to information or registration Arrival flow remains active while physical continuation to available registration points stays below the configured range. Review wayfinding and available registration coverage while the arrival condition remains live.
Where does mapped registration flow become waiting at the triage handoff?Connect registration departure, the triage approach, waiting pressure, and nearby role-level coverage in the same physical view. Registration departure · Triage approach and queue · Waiting pressure and role-level coverage Registration departures continue while triage waiting remains above the configured threshold and the required operational role is not present nearby. Review available triage support, routing, and the active waiting zone before pressure reaches the adjacent corridor.
Does operational waiting persist while a covered room-use state appears inactive?Read waiting demand, approach to the covered room boundary, and room-use state. The camera does not verify clinical readiness. Waiting at the covered department · Approach to the room boundary · Covered room-use state Waiting remains above the configured threshold while the covered room-use state appears inactive. Review the operational handoff and confirm room readiness in the approved room-status system before changing the flow.
Where do configured transport and visitor routes build corridor pressure?Read anonymous movement, corridor pressure, lift-lobby waiting, and role-level coverage across the defined transfer path. Corridor movement by direction · Lift-lobby queue and estimated waiting · Role-level transfer coverage Opposing route pressure and lift-lobby waiting remain above the configured threshold while transfer coverage is limited. Review the active route, lift allocation, and available transfer support before pressure spreads to the next handoff.
Where is supported equipment or trolley movement visible relative to the configured operational need area?Read wheelchair, stretcher, equipment, and porter movement inside approved covered areas. Equipment status and transport jobs require connected records. Equipment location in covered areas · Wheelchair, stretcher, and porter movement · Distance to the mapped demand zone The mapped demand zone is active while the required equipment category is not observed in the approved nearby coverage area. Review the equipment record and active transport jobs, then route available support through the approved workflow.
When does the entrance count reach the manually configured facilities review condition?Cameras stay outside the restroom. They count entries and exits at the entrance boundary and can apply a configurable rule, for example every 100 entries since the last confirmed clean. Restroom entrance and exit count · Entries since the last confirmed clean · Configured cleaning-task threshold Entries since the last confirmed clean have reached the configured threshold while the cleaning task remains unconfirmed. Review creating or routing the cleaning task. Reset the count only after an approved workflow or staff and manager confirmation.

Hospitals, regions, departments, and equivalent periods can be compared under the same selected operating question.

How does the same physical flow question change across a hospital network? Select a comparable entrance, department, waiting area, diagnostic zone, transfer path, facilities rule, or operating window. Compare the same camera-observed evidence across hospitals, regions, departments, and equivalent periods.

Camera reads: Suitable views can read entry and exit, footfall, anonymous groups, mapped routes, queue, estimated waiting, area occupancy and dwell, covered room-use state, corridor and lift-lobby pressure, role-level team presence, transport flow, equipment location in approved covered areas, and restroom entry and exit counts at the entrance boundary.

Connected systems confirm: An approved HIS, appointment, cleaning, room-status, equipment, or transport system confirms clinical or appointment context, task state, verified room readiness, cleaning completion, equipment records, and transport jobs. Camera observations are not matched to a medical record.

Build the non-clinical operating view from camera-verifiable physical signals. Entry, exit, footfall, occupancy, and density · Anonymous groups, peaks, area dwell, and mapped routes · Arrival, registration, and triage continuation · A supporting 2D heatmap and a primary 3D operating map · Queue, estimated waiting, and configured thresholds · Waiting pressure at registration, triage, and diagnostics · Covered room approach and room-use state · Physical route alignment across defined care stages · Corridor and lift-lobby transfer pressure · Wheelchair, stretcher, and porter flow · Equipment location and availability in approved covered areas · Role-level team coverage without individual scoring · Restroom entry and exit counts at the entrance boundary · Configurable use-count cleaning alerts and task rules · Configured pilot conditions with location, threshold, priority, and reviewed action · Hospital, region, department, and period comparison

You define the operating question. We shape the KPI with you. Define the important areas and the decision you need to make. We combine camera-verifiable signals into a tailored KPI and add approved hospital-system context only when the question requires it.

Location-specific learning: In a standard deployment, camera images are processed on the on-site Edge PC. Continuous raw video is not sent over the WAN. Required anonymous operational metadata may synchronize to the cloud so model weights can learn recurring arrival, waiting, room, transfer, equipment, and facilities patterns for this hospital.