Care flow design with Hosted Pages
How to design a care flow whose activities are completed on Hosted Pages, and why system activities in the wrong place make a patient wait.
A care flow completed on Hosted Pages needs more thought about timing than one completed inside Awell Care, because the patient is waiting while it runs.
System activities make the patient wait
A care flow contains both stakeholder activities and system activities:
- Stakeholder activities that a person does: a form, a message, a checklist.
- System activities that Awell does: a calculation, an API call.
On Hosted Pages, a system activity between two stakeholder activities becomes a pause the patient experiences; a call to a slow third-party system shows as a spinner.
Keep system activities out of the patient's path
Avoid unnecessary system activities
A system activity placed between stakeholder activities adds to the time the patient spends waiting. Ask whether each one has to happen now.
Run necessary system activities after or in parallel
If a system activity must happen, put it after the stakeholder has finished, or in parallel with their work, rather than between two of their steps. The patient then finishes their part without waiting for the calculation.
Send an activity page via a secondary channel
Rather than relying on the patient staying in one session, send a link by email or text message so they can return later. See Link to an activity from email or SMS.
Next steps
Set a custom domain for Hosted Pages
Serve Hosted Pages from a custom domain instead of Awell's, so links look like they come from the care organization.
Link to an activity from email or SMS
Put a link to a pending activity into an email or text message, so a stakeholder can act straight from the message.