Patient rounds. Proof of presence.

Q15 checks are safety observations where staff see each patient at least every 15 minutes and document what they observe. Neither the Joint Commission nor CMS sets a specific check frequency for general inpatient psychiatric care. Facilities define observation levels and intervals in their own policies, and surveyors hold them to those policies.

The staff device detects the patient’s wristband and averages several seconds of signal readings into a distance. The observation is marked proximity-verified only when staff are within the unit’s configured range, and the record keeps that distance with the timestamp and the documenting staff member.

Staff can still document. They choose an override reason, such as no wristband assigned or a wristband malfunction. The observation is recorded as not proximity-verified, and the reason stays in the record and the audit log.

Your EMR records that a check was entered. Ward adds proximity verification at the bedside, real-time fall and elopement alerts, and environment-of-care rounds. Where your EMR supports it, Ward writes observation documentation back to the chart over FHIR, so it works alongside your EMR rather than replacing it.

Q5, Q15, Q30, and Q60 intervals, plus 1:1 continuous observation. Intervals run from the last observation, and overdue checks raise alerts. On a 1:1, staff get a continuous observation screen with a coverage timer and relief handoffs, and any gap over 5 minutes raises a critical alert.

Each unit sets its night hours and protocol: full room entry, or a doorway check that reduces sleep disruption. In both modes, staff see every patient and document each observation.

The on-site hub doesn’t store patient names, and wristbands broadcast only device identifiers. The link between a wristband and a patient exists only in the cloud. The hub makes outbound HTTPS connections only and accepts no inbound connections.

Staff keep documenting observations and vitals on their devices. Data is stored encrypted on the device and syncs when the connection returns. The hub keeps running fall and elopement detection and uploads buffered events when it reconnects.

Yes. Our BAA commits to breach notification within 5 business days and prohibits using patient data to train AI models. Security documentation is available on request.