# Care flow design with Hosted Pages
URL: https://docs.awellhealth.com/docs/embed-and-host/care-flow-design-with-hosted-pages

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



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 [#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 [#keep-system-activities-out-of-the-patients-path]

### Avoid unnecessary system activities [#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 [#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 [#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](/docs/embed-and-host/link-to-an-activity-from-email-or-sms).

## Next steps [#next-steps]

**Next:** [Link to an activity from email or SMS](/docs/embed-and-host/link-to-an-activity-from-email-or-sms).