How it works

Select a step to see what it does.

OtherwiseStop · can end the Journey at any step
  • Check
  • Email
  • Label

Label Members who asked for support and send a care-plan check-in to Members who did not. A Form and a draft Journey for care teams.

Who it is for

Care teams that record whether a Member in a care plan has asked for support.

What it does

  • The Treatment adherence Form has one Boolean field, Support requested, with no default value.
  • The Journey reads the field once, when a Member is enrolled. True adds the Support requested label. False goes to the check-in email step.
  • A Member with no recorded value gets the Review support status label. No email step runs on that path.
  • The Stop treatment support label ends the Journey at any step.

What it does not do

It does not measure adherence, assess treatment or make a clinical decision. The labels mark Members for a process your team monitors. They do not notify anyone. Keep urgent requests in your existing process. The build guide describes a different Journey: it emails every enrolled Member, waits for the answer and notifies a Support Coordinator. This Bundle reads a value your team has already recorded.

Before you turn it on

Installing adds the Form and a draft Journey to the workspace you choose. It does not enroll Members or send messages: automatic enrollment is off and each email step is inactive. Keep one current record per Member in the Form. Review the email text and the Inbox, and test with synthetic Members before you publish the Journey. Confirm PHI authorization for the workspace before you use real health data.

Included in the bundle

Forms

Treatment adherence

Holds one record

Record support requests alongside treatment adherence intake fields.

  • Support requested
    Yes or No

Journeys

Workflows