Messages

How a patient reaches their care team, with the SMS thread beside the secure one — two channels, one inbox.

Access

How a patient reaches the screen, and what has to be true for it to open.

Element What it decides Permissions

Navigation Bottom bar → Messages on a phone; side menu → Messages on a desktop. Client:conversations.on

Header

What the band states before anything below it is actionable.

Element What it decides Permissions

Title “Messages”, with how many are unread and how many threads there are. —

Main actions

What belongs to the page rather than to one thread.

Element What it decides Permissions

New message Opens a new message. On the SMS channel it reads New SMS, so the label always matches what will be sent. —

Form · New message

What a message needs before it is sent.

Field Validations Permissions

Recipient Required. Someone on the care team. —

Subject Required on a secure message; SMS has none. —

Body Required. —

Attachments Optional. Secure messages only. —

Filters

Which threads the list holds.

Element What it decides Permissions

Channel Messages · SMS. —

Folder Inbox · Sent. —

Search Sender, subject and body, within the channel chosen. —

Table

What one thread shows in a row.

Element What it decides Permissions

Sender Who wrote last, with their photo. —

Subject What the thread is about. —

Preview One line of the latest message. —

Date When it arrived. —

Unread A dot until the thread is opened. —

Opening a thread Beside the list on a desktop, in its place on a phone. —

Row actions

What can be done to one thread.

Element What it decides Permissions

Reply Inside the thread, with the composer at its foot. —

Mark read Per thread, or for every thread chosen. —

Archive Per thread, or for every thread chosen. —

Errors

Not yet written from the code.

API calls

Not yet written from the code.