Patient Message Routing and Nurse Handoff

In a clinic, the patient line fills with the same kinds of message every day: when to start bowel prep, where to park, whether a driver is needed after sedation, whether an appointment can move. Mixed in among them are the messages that should never wait in a general queue, such as a new symptom. This Botlit concept shows a patient assistant for healthcare providers that sorts each conversation from the clinic's website chat and messaging channels by what it needs: an answer drawn from the clinic's approved instructions, a scheduling action, or a nurse.

The illustration opens the Conversations view of a sample gastroenterology clinic's patient assistant. Its header carries an active status, a web chat and messaging channel badge and an Approved content only badge. A Today's conversations table lists each message with its time, a patient identifier masked to its last four digits, the topic, the route it took and its status. Logistics questions such as bowel prep timing, parking and arrival, and a driver requirement are routed as Answered and name the clinic document they cite, such as the colonoscopy prep instructions, a visitor guide or the sedation instructions. A reschedule request is routed to a FluidGrids workflow and shows a slot offered to the waitlist. Two clinical messages go to nurse triage: a medication question sits as Queued, and a message about new chest pain carries a red Urgent badge.

With the urgent row selected, a Handoff to nurse triage panel records the reason, symptom language detected; what the assistant replied, the clinic's urgent-care instruction; the destination queue, a triage nurse for gastroenterology; how many messages of the conversation are attached; and when it was handed off, with Open in inbox and Mark reviewed buttons. The urgent flag is designed as a sorting aid for the nurse queue, never a substitute for a nurse. Beyond showing the clinic's own urgent-care instruction, the assistant is designed to leave clinical questions to the nurse.

A strip along the foot of the page covers appointments: confirmations sent today, unconfirmed appointments for tomorrow with a warning marker, and a no-show trend line, beside a card noting the figures are sent through FluidGrids to BigConsole with clinic access. In the design, Botlit handles the conversation, FluidGrids is designed to run the reschedule and reminder workflows, and the reminder workflow is designed to pass no-show figures to a BigConsole datasink the clinic manager can review. The concept is meant for front-desk and patient access teams, triage nurses and clinic managers who share one view of the day's patient messages.