BOSTON CHILDREN'S HOSPITAL - VIRTUAL CHECKLISTS
Pre- and post-virtual checklists to assist a parent persona with the required tasks.
BOSTON CHILDREN'S HOSPITAL - VIRTUAL CHECKLISTS
Pre- and post-virtual checklists to assist a parent persona with the required tasks.
Executive Summary
In this project, I undertook a dual role as both the UX researcher and designer, crafting a system tailored for a parent persona's use of pre- and post-virtual checklists in assisting with their child’s required tasks during virtual appointments; this process also helps the provider to ensure that all health data are collected for a thorough exam. This would be a new feature to the current health portal for Boston Children’s Hospital that provides comprehensive pediatric specialties and subspecialties to infants, children, and teen. The target user group are parents of these children whose goals are to manage essential aspects of the virtual healthcare for their children.
The prototype focuses on simple, clean, and no clutter design with functional consistency that aims at a user-friendly process for quick navigation. Four main color—blue, cyan, pink, and yellow—gathered from the Boston Children’s Hospital website were utilized to emphasize important actions. Color is an essential part of the interface and can influence the user’s mood while interacting with the app. If use appropriately, they can ease a systematic task to be more enjoyable.
A test was conducted to validate the usability of the user interface and provide evidence of usability for the prototype. For the test, two participants shared their screens as they were given 10 scenarios to accomplish from the Figma’s presentation link (shown on the title and reference pages). Both interviews were conducted within 30-minute time span and recordings were given consents by the participants. Both participants were tested from version 1 of the prototype.
The 10 scenarios are the possible features created to support the needs of the persona who would appreciate a mobile app with easy access to all virtual visit-related information. The scenarios for the usability test are as follows:
Pre-Visit |
1. User needs to complete an intake form to prepare for the virtual visit. |
2. User needs to complete home exam with the TytoCare device. |
3. User needs to upload lab results from UMaine Health. |
4. User needs to complete pre-checkin to provide patient’s background. |
5. User completed the pre-virtual checklist and ready to join virtual visit. |
Post-Visit |
6. User would like to check if the HPN clinical note is ready. |
7. User would like to view his child’s CAIR clinical note. |
8. User would like to renew a prescription. |
9. User would like to see what the required items for next visit are. |
10. User would like to schedule 30-minute for his child with Elizabeth Castle, NP. |
Pre-Visit | Post-Visit |
1. User needs to complete an intake form to prepare for the virtual visit. | 6. User would like to check if the HPN clinical note is ready. |
2. User needs to complete home exam with the TytoCare device. | 7. User would like to view his child’s CAIR clinical note. |
3. User needs to upload lab results from UMaine Health. | 8. User would like to renew a prescription. |
4. User needs to complete pre-checkin to provide patient’s background. | 9. User would like to see what the required items for next visit are. |
5. User ready to join virtual visit after completing the pre-virtual checklist. | 10. User would like to schedule 30-minute for his child with Elizabeth Castle, NP. |
Methodology
During the one-on-one usability test via Zoom, each participant was greeted by the moderator and asked for consent to be recorded; they were informed that they can stop for break at any time. Next, the participants were asked to share their screens and visit the Figma presentation link address that they were invited to test with; before clicking on anything, they were asked to observe the Home Screen and share their immediate impressions of it. The moderator then pasted the texts of 10 scenarios to the participants via chat and let them know that they would also be read those tasks aloud.
Participants
• Were encouraged to think aloud
• Were told that there is no wrong answers
• Asked to describe what they’re looking at or trying to do
Collected data
• Time to complete the task for the scenario
• Number of completed tasks
• Errors made were actions that veered from scenarios
Moderator
• Read tasks aloud and noted usability interactions
• Followed-up with post-scenario questions
• Asked for suggestions and recommendations
Resources used and time
• 35 screens of Figma wireframe: 30 hrs.
• Script for test and other preparation: 1 hrs.
• Usability test: 2 hrs.
• Analysis & report writing: 10 hrs.
Participants
• Were encouraged to think aloud
• Were told to be aware that there is no wrong answers
• Asked to describe what they’re looking at or trying to do
Collected data
• Time to complete the task for the scenario
• Number of completed tasks
• Errors made were actions that veered from scenarios
Moderator
• Read tasks aloud and noted usability interactions
• Followed-up with post-scenario questions
• Asked for suggestions and recommendations
Resources used and time
• 35 screens of Figma wireframe: 30 hrs.
• Script for test and other preparation: 1 hrs.
• Usability test: 2 hrs.
• Analysis & report writing: 10 hrs.
Results of the Usability Study
The objective of this test was to uncover areas where the prototype succeeded well and areas where it failed to meet the needs of the participants; this testing process identifies areas where improvements must be made to the design. During the usability test, each participant used the same prototype (V1) from the same Figma presentation link and was provided with the same instructions. The system was evaluated for effectiveness, efficiency, and satisfaction as defined by measures collected and analyzed for each participant.
• Task completion definitions
Pass - Completed task successfully.
Assist - Required hint(s) to complete task successfully.
Fail - Task not completed successfully even with hint(s).
• Task completion summary
Participant # | Task 1 | Task 2 | Task 3 | Task 4 | Task 5 | Task 6 | Task 7 | Task 8 | Task 9 | Task 10 |
---|---|---|---|---|---|---|---|---|---|---|
P1 | Assist | Pass | Pass | Pass | Pass | Pass | Pass | Pass | Pass | Pass |
P2 | Assist | Pass | Pass | Pass | Pass | Pass | Assist | Pass | Pass | Pass |
Participant# | P1 | P2 |
---|---|---|
Task1 | Assist | Assist |
Task2 | Pass | Pass |
Task3 | Pass | Pass |
Task4 | Pass | Pass |
Task5 | Pass | Pass |
Task6 | Pass | Pass |
Task7 | Pass | Assist |
Task8 | Pass | Pass |
Task9 | Pass | Pass |
Task10 | Pass | Pass |
• Usability severity definitions
Pass - Users completed task successfully.
Assist - Minor, an observed issue that delays the users briefly.
Assist - Minor, an observed issue that delays the users significantly but eventually allows them to complete a task.
Fail - Catastrophic, an observed issue which prevents the users from completing a task.
Scenarios of Task Completion, Usability Issues, and Demo Videos
Scenario 1
Success criteria for task completion: User needed to complete an intake form to prepare for the virtual visit. From the Home Screen, tap on ‘1. Complete intake form’ to begin questionnaire.
Usability issue 1: From V1 of the prototype, both participants hesitated where to tap on and both needed hints to take the first step. This issue needed a solution.
Scenario 2
Success criteria for task completion: User needed to complete home exam with the TytoCare device. From the Home Screen, tap on ‘2. Complete home exam’ to see instruction for measuring with TytoCare.
Scenario 3
Success criteria for task completion: User needed to upload lab results from UMaine Health. From the app’s Pre-Visit Home Screen, tap on ‘3. Upload lab results’ to see direct link and instruction.
Scenario 4
Success criteria for task completion: User needed to complete pre-checkin to provide patient’s background. From the app’s Home Screen, tap on ‘4. Complete pre-checkin’ for direct link.
Scenario 5
Success criteria for task completion: User completed the pre-virtual checklist and ready to join virtual visit with his child. From the app’s Home Screen, tap on ‘5. Join virtual visit’ for a link to the appointment.
Scenario 6
Success criteria for task completion: User would like to check if the HPN clinical note is ready. From the app’s Post-Visit Home Screen, tap on ‘HPN clinic note’ and scroll down to see the full message.
Scenario 7
Success criteria for task completion: User would like to view his child’s CAIR clinical note. From the app’s Post-Visit Home Screen, tap on ‘CAIR clinic note’ and scroll down to see the full message.
Usability issue 2: User would like to view his child’s CAIR clinical note. After viewing the HPN note, a participant was confused of how to get back to the home screen or proceed to to see CAIR note.
Scenario 8
Success criteria for task completion: User would like to renew a prescription. From the app’s Home Screen, tap on ‘Prescriptions/Medications’ and scroll down to see the full list and the ‘Request Renewal’ button.
Scenario 9
Success criteria for task completion: User would like to see what the required items for next visit are. From the main screen of Post-Visit Information, tap on ‘Required items for next visit’.
Scenario 10
Success criteria for task completion: User would like to schedule 30-minute for his child with Elizabeth Castle. From the app’s Home Screen for Post-Visit, tap on ‘30-minute with Elizabeth Castle, NP’.
Summary of Recommendations and Implementation
Minor issues that have been implemented
Issue# | Description |
---|---|
1 | Both participants hesitated of where to go for the first scenario, so an instruction was added to V3 that points to task 1 to be completed first. |
2 | Participant 2 was confused of how to navigate to the CAIR note, arrows were added in V2 to all Post-Visit Information screens for easy exit. |
Based on the lack of failures or task deviations, the prototype seems to be an effective system in the making of an app for the persona to help with the tasks for pre- and post-visit appointments. All the assigned tasks were completed quickly as the participants were able to navigate the tasks and completed the task flows. The users were satisfied with the easy testing experience.
Iteration for Pre-Visit Checklist
Below shows the iteration process for the Pre-Visit Checklist with minimal changes for V1, V2, and V3 that were implemented after the user testing.