Clinical messaging
Routing to a clinical role
When you need the on-call RN, you shouldn't have to know their name. Address the role, and Rounds resolves it to whoever is on call right now.
A clinician sending an urgent message often doesn't know — and shouldn't have to know — which person is on call. They know the role: "I need the on-call RN." Role-based routing lets you address a message to a clinical role, and Rounds delivers it to the right person automatically.
How to route to a role
-
Open a channel and click into the composer
From the chat workspace, click the channel in the list on the left, then click into the Type a message… box at the bottom. -
Type @ in the composer
The same@you use to mention a person also lists your agency's clinical roles, in their own Clinical roles section of the pop-up. -
Pick a role
Choose a role — say@On-call RN. The list marks it as routing to whoever is on call, so you know it follows the schedule. -
Send
Rounds resolves the role to the on-call person at that moment, notifies them directly, and renders the message so every reader sees both the role and the resolved name.
What a routed message looks like
A routed message carries a role chip — @On-call
RN — and, inline beside it, the person it resolved to: @On-call
RN → Dana Cole. Every reader sees who the message actually landed on,
not just the role that was addressed.
Roles versus user groups
A clinical role is dynamic
@On-call RN resolves fresh every time, to whoever holds the
on-call assignment at the moment you send. It follows the schedule.
A user group is static
@night-shift is a
fixed roster — these people, until an admin edits the set. It doesn't
follow the schedule.
When no one is on call
If you address a role that has no on-call coverage right now, the message still sends — but it shows a clear "no one is on call for On-call RN" warning, and the gap is recorded in the audit log. Rounds never silently misdelivers a routed message; if there's no one to route to, it tells you.