In Phreesia, what is the relationship between a template and a form when building a check-in flow?

In Phreesia, what is the relationship between a template and a form when building a check-in flow?

• A. A template is a single field; a form is a template bank
• B. A template is a reusable group of fields; a form is a specific instance built from templates
• C. A template is a collection of forms; a form is a check-in screen
• D. A template stores patient data; a form stores appointment data

Answer: (B)

In Phreesia, the relationship hinges on reusable building blocks versus the actual screens patients interact with. A template is a reusable group of fields that defines what information to collect. From these templates you assemble a form, which is a specific check-in screen or instance used at a particular step in the flow. This setup lets you standardize data collection—create a template once and reuse it across multiple forms as needed. For example, you might have a demographics template containing name, date of birth, address, and phone number. You then build a patient intake form by using that template (and possibly adding another template for consent), resulting in a concrete screen shown during check-in. The form is the live interface, while the template is the reusable blueprint behind it. Other options don’t fit because a template isn’t a single field, it isn’t a collection of forms, and it doesn’t store patient data; it’s the reusable group of fields used to compose forms.

In Phreesia, the relationship hinges on reusable building blocks versus the actual screens patients interact with. A template is a reusable group of fields that defines what information to collect. From these templates you assemble a form, which is a specific check-in screen or instance used at a particular step in the flow. This setup lets you standardize data collection—create a template once and reuse it across multiple forms as needed.

For example, you might have a demographics template containing name, date of birth, address, and phone number. You then build a patient intake form by using that template (and possibly adding another template for consent), resulting in a concrete screen shown during check-in. The form is the live interface, while the template is the reusable blueprint behind it.

Other options don’t fit because a template isn’t a single field, it isn’t a collection of forms, and it doesn’t store patient data; it’s the reusable group of fields used to compose forms.