Staff
How the front desk knows who has arrived and what is still missing before a visit starts.
Access
How a member of staff reaches the screen, and what has to be true for it to open.
Client:new_dashboard.onMe:dashboard.access
staff app, at /intake.
Client:new_dashboard.onMe:dashboard.access
Header
What the band states before anything below it is actionable.
Main actions
What belongs to the day's list as a whole rather than to one visit.
Summary card actions
Where the day stands, and the quickest way to narrow the list to one part of it.
Filters
Which visits the list holds.
Client:departments.on
Client:appointments.locations
Form · Save preset
What a saved preset needs before it is kept.
Table
What one visit shows in a row.
Client:dashboard.show_insurance
Client:dashboard.show_eligibility
Client:dashboard.show_balanceClient:dashboard.show_copay
Workspace · Patient
Everything the desk needs about one visit, without leaving the list.
Client:dashboard.show_email
Client:dashboard.show_insurance
Client:dashboard.show_eligibility
Patient · Appointment
When and where the visit happens.
Patient · Billing
What is owed for the visit, and the way to ask for it.
Client:dashboard.show_copay
Client:dashboard.show_balance
Data:sms_thread_payment
Patient · Intake forms
What the patient still has to complete before the visit.
Client:custom_forms.forms_completed
Data:update_form_steps_on_demand
Data:intake_notification
Patient · Activity log
What staff has already done on this visit.
Client:sms_threads.onMe:sms_threads.access
Patient · Messages
The text conversation with the patient, beside the visit it is about.
Client:sms_threads.onMe:sms_threads.access
Client:sms_threads.onMe:sms_threads.access
Client:sms_threads.onMe:sms_threads.access
Client:sms_threads.onMe:sms_threads.access
Client:sms_threads.onMe:sms_threads.access
Client:sms_threads.onMe:sms_threads.access
Row actions
What can be done to one visit, and what each needs before it is offered.
Data:arrived_action
Data:checked_in
Data:send_to_tablet
Data:generate_intake_qr
Data:confirm_notification
Data:unchecked_in
Data:intake_notification
Data:intake_zero_login_notification
Data:sms_thread_payment
Client:eligibility.onClient:dashboard.show_eligibilityData:eligibility_rerun
Data:update_form_steps_on_demand
Client:billing.enabled_paymentClient:eligibility.onClient:dashboard.show_eligibility
Client:appointments.onMe:appointments.access
Client:custom_forms.forms_completed
Data:manage_payment_profile
Client:conversations.onData:view_messages
Client:billing.enabled_paymentClient:billing.show_payment_logs
Record · Intake QR code
A code that starts the patient's intake on their own phone.
Form · Steps on demand
Which form steps the patient is asked for outside the usual flow.
Errors
What the screen can fail at, and what the desk sees when it does.
GET /dashboard/all → any failure
An empty table, the same as a day with no visits: no message, and no retry until the next refresh. Not yet told apart.
GET /options/… → any failure
That filter offers nothing to choose, with no message. Not yet told apart.
GET /dashboard/:id → 403 or 404
The workspace closes, so the patient's details do not stay on screen. Any other failure keeps what it already shows.
GET /sms-threads → any failure
A notice where the messages would be. The next minute's refresh tries again.
POST /sms-threads → any failure
A notice saying it was not sent; what was typed stays, ready to send again.
API calls
What the screen asks the backend for, and what makes it ask.
datedepartment_ids[]location_ids[]doctor_ids[]
On confirming Download CSV.
datedepartment_ids[]location_ids[]doctor_ids[]pageper_pageadmission_statusneed_attention
When the screen opens, on choosing a status card, a filter or a page, every five minutes, and after every action on a visit. A status card adds either admission_status or need_attention.
date
When the screen opens and on changing the date, where departments are shown.
date
When the screen opens and on changing the date, where locations are shown.
date
When the screen opens and on changing the date.
patient_id
When the conversation opens, and every 60 seconds while it is open.
user_id
When the conversation opens.
patient_idphone_idmessage
On sending a message, or on sending the consent request, which carries no message.
appointment_idinsurance_id
On confirming Run Eligibility Report.
appointment_id
When Steps on demand opens.