Key concepts to understand

3 min read

While Videoreach is quite an intuitive tool to understand and use, the following concepts are important to understand to get full value from this tool:

Visit Type

Similar to other healthcare software, this functionality allows Videoreach users to specify the different types of Visits you want to track for your Patients/Members and based on which you want to engage with your Patients. For example: If you are a Cardiologist, you may want to build Videoreach engagement around

Visit

The Visit property is the actual Date/Time value for the Patient for a particular Visit Type. For example, for the above example, the Patient may have the following upcoming visits:

  • Heart Surgery: Jan 10, 2024 8 AM
  • Office Visit: Jan 30, 2024 2 PM

In this case, the Patient will be setup with the following Visits:

  • Visit Date of Jan 10, 2024 at 8 AM for Visit Type: Heart Surgery.
  • Visit Date of Jan 30, 2024 at 2 PM for Visit Type: Office Visit.

Patient

The Patient property represents just what it says- the Patient and/or the Member. This is an individual who will receive the Videoreach interactions OR Flows and Videoreach helps engage them and tracks the engagement level. The Patient summary tab provides insights into the various flows the Patients have engaged with. Learn about how to create a Patient here.

Flow

A flow in Videoreach refers to the interaction you want to setup with your Patients/Members. A flow is a combination of steps, where each step consists of:

  • A Video
  • Text that allows you to provide more information
  • A question (Optional)
  • Response Options (Optional)

This is your own way to engage your Patients/Members and replicate real life conversations or education sessions with them utilizing pre-recorded videos. You can have to up n steps in a flow, though we don’t suggest you have more then 5. Note that Flows can also be setup in different languages IE: You can have a flow in English with English videos and English questions and responses and you can also build flows in Spanish with Spanish videos, questions and responses.

Program and Schedule

A Program is the way you put together different interactions (IE: Flows) for your Patients. One Program is related to a Visit Type. IE: For all the Patients enrolled in that Program, it will refer to the Visit Date or Visit Dates for that Visit Type for that Patient. A Program contains different schedules that are a time based property based WRT the Patient’s Visit Date for the set Visit Type for the Program. You can setup n schedules for a given Program. A schedule allows you to dictate when A flow should be sent to the Patient based on their Visit Date and what should be the accompanying text message they get before they start the flow.

For example, if you want to connect with the Patient 1 day before their surgery to educate them about the procedure and then 2 days after you wanted to follow up with them. Then, you would setup the following in Videoreach: Visit Type: Heart Surgery Program: Engage Patients for Heart Surgery Flow 1: Educate Patient on procedure Flow 2: Check-in with Patient, Ask question of how they are doing, Responses: Doing Ok, Need help, Worried. Schedule 1: 1 Day before Heart Surgery Schedule 2: 2 days after Heart Surgery And, Videoreach would then orchestrate these interactions with the Patients based on their Heart Surgery date/time.

Program Minimum Date

Currently, there is a limitation as to the earliest date/time a Visit Date can be for a Patient. Essentially, the Visit Date can NEVER be earlier then the Program Minimum Date, where the Program Minimum date is:

Program Minimum Date: TODAY + (Max of the Before values for Program Schedule) + 1 Day.

IE: If a Program has the following schedules:

  • 2 Days before Visit Date
  • 3 Days before Visit Date

And, Today is Feb 1, 2024, then the Program Min Date will be: Feb 5, 2024 because:

  • Today= Feb 1, 2024
  • Max of Before values for Program Schedule= 3

So, Program Min Date = Feb 1, 2024 + 3 + 1= Feb 5, 2024.

This is currently used to help us ensure message deliverability. We will be removing this requirement in the future releases.

Did this answer your question?