Monitoring Patient Responses
After appointments have been uploaded and matched to a reminder template, the reminder messages are automatically sent to patients. Users can then monitor patient responses as they come in.
Optimizing Interfaces for User Goals
See the most important patient response information at a glance.
List the most recent patient responses in a split screen layout with the ability to see additional details and take appropriate action, all on the same page.
Without navigating away from the page, users can monitor recent patient responses, see the key details for each appointment, and take follow-up actions if needed. This makes it is easy for users to accomplish their goals while reducing their cognitive load and number of clicks.
Reminder Status at a Glance
Know the status of an appointment's reminder messages.
Use icons to designate the scheduling and delivery status of a reminder.
I used simple colored icons with symbols to help users quickly identify the status of an appointment reminder. This allowed users to easily know how many reminders had been sent, if they were successfully delivered, and if there were more scheduled to go out.
Showing Relevant Actions
1. Edit or delete an appointment before reminders have been sent.
2. Cancel or reschedule an appointment after reminders have been sent.
Update the key action buttons shown for each appointment based on the status of the reminders.
Before appointment reminders have been sent, the main user actions are deleting or editing the appointment, so those buttons are shown on the appointment summary screen. Once reminders have been sent, those actions are no longer viable and are replaced with cancelling or rescheduling the appointment. This ensures the buttons users see are always the most useful and relevant to their workflow.
Classifying Unusual Responses
Know whether an unusual patient response requires follow-up.
Allow users to manually update a patient's RSVP to "Going" or "Not Going" to signal that their response does not require additional action.
Common patient responses (Yes, Y, Si, No, N, etc.) are automatically mapped to "Going" or "Not Going," but if a response is less clear, users can manually map the response to identify messages that do not require follow-up. To ensure transparency for accounts with multiple users, an activity log entry is generated to show the staff member who made the update.