• Checkbox - Response choices are shown in a list; multiple answers can be chosen.

• Continuous Slider - Participants slide their finger from left to right to choose a continuous response (e.g., 1-10 visual analog scale).
  

  

• Date - Participant uses a calendar to choose a date.

• Dropdown - Participants click a box to select from a long list of potential answer responses.
  

  

• Payment Log - This item type is used to display the number or percentage of surveys completed, requires HTML file. More information can be found here.
  

  

• Radio - Response choices are shown in a list; only one answer can be chosen.
  

  

• Rich Text - A block of text that can be used to provide messages or instructions in the app; rich text allows additional formatting that is not available with the Text Only item type. For example, this item type allows you to embed URL links, underlining, highlighting, and bolding into messages.

• Image Modified

• Slider - Participant slides their finger from left to right to choose a categorical response.
  

  

• Text Area - Participant uses their keyboard to type a longer response than the text field question type.

• Text Field - Participant uses their keyboard to type a short answer.

• Text Only - A block of text that can be used to provide messages or instructions in the app.

  

• Time - Participant uses a clock to choose a time.

  

• Timer - Participants see a configurable countdown timer.

  

We recommend that the first stage of any study be a “Start Study” Stage. The Start Study stage will standardize the study experience for all participants and will set the first day of your study for each participant. The Start Study stage should contain a Start Study assessment that includes the question: “Do you want to start the study now?” (Yes = 1; No = 0). The Formula stage change type should be used to move the participant to the first day of the study (type [start_study]==1 into the End Date Formula field). See video below to see an example for creating the Start Study stage.

Under Schedule Type, select Random. Random events can be scheduled for specific days of the week (i.e., Weekly) or they can be scheduled for specific days of a stage (i.e., Stage Offset).

• Weekly – Click the Weekly button, then click the checkbox next to the day(s) you would like the assessment to be prompted.

• Stage Offset – Click the Stage Offset button, then enter the specific day you would like the assessment to be prompted. For example, if you created a 14 day stage, and you want this assessment to be prompted on day 7 of that 14 day stage, you would type 7 into the Day of the Stage text field. 

Scheduling Features

• Assessments per Day – Type the number of assessments that should be randomly prompted per day in this text box. Each participant’s daily waking hours will be split into equal epochs and one random assessment will be prompted within each epoch.

• Time Buffer (minutes) – This setting prevents random assessments from occurring closer together than desired (e.g., it is technically possible for 2 random assessments to be just one minute apart). Type the minimum allowable number of minutes between the random assessments in this text box.

• Wake Time Offset – This setting prevents random assessments from being prompted too close to the participant’s wake time. Type the number of minutes after the participant’s wake time for the initial random assessment window to begin. See how Wake Times can be created here.

• Sleep Time Offset – This setting prevents random assessments from being prompted too close to the participant’s bedtime. Type the number of minutes prior to the participant’s bedtime for the final random assessment window to end. See how Sleep Times can be created here.

Reschedule Assessments - There are two ways to reschedule prompted events (e.g., Fixed Events, Random Events): Snooze and Event Reschedule Settings. These features give participants another opportunity to complete assessments that may be prompted at inconvenient times. 

• Snooze –This feature allows the participant to postpone prompted assessments for a specific amount of time. The researcher sets the duration of the snooze and the number of times the assessment can be snoozed. To access this feature, click “Reschedulable,” then click “Snooze.”

  • Snooze Time: Enter the number of minutes you would like the event to be prompted after the snooze button is clicked. For example, if the participant snoozes the assessment, prompt the assessment again 15 minutes later.

  • Snooze Limit: Enter the number of times the assessment can be snoozed by the participant. 

• Event Reschedule Settings – This feature allows prompted assessments (e.g., Fixed or Random Assessments) to be automatically rescheduled if the participant does not start the assessment when it is prompted. This feature is similar to snooze, but it does not require the participant to do anything (i.e., click Snooze) in order for the assessment to be automatically rescheduled. To access this feature, click in Settings. In the Setting Type dropdown menu, select “Event Reschedule Settings.” 

  • Reschedule Attempts: Enter the number of times the assessment should be automatically rescheduled.

  • Reschedule Minutes: Enter the desired delay (in minutes) between the initial prompt and rescheduled prompt. For example, if the participant does not respond to the first prompt, reschedule the prompt 15 minutes later.

• Event Resume -This feature allows Assessments in progress to be resumed at a later time. If the Participant closes the Insight app, accepts a phone call, or powers off their phone during an Assessment, they will be able to Resume the Assessment later. After the specified number of minutes have passed, the Event Resume feature will expire. To enable this feature, follow instructions below:

1. Select desired study > Click on the Events tab

2. Find the Stage desired > Click the button to open

3. Scroll down to Settings > Select to open

   

4. Click Setting Text

   

5. A dropdown will appear > Scroll until Event Resume is seen > Select it

   

6. Check the Allow Resume box > In the Resume Timeout Minutes field, input the desired minutes for an event to be resumed before it expires.

   

   1. Resume Timeout Minutes - determines the number of minutes that an Event can be Resumed, starting with the timestamp when the Assessment is started. The homepage of the app will show a “Resume XXXXXX“ Assessment (where XXXXXX is the name of the incomplete Assessment) message for an available Assessment until the Resume Timeout Minutes have elapsed.

   2. For example, if an assessment is started at 9:00 AM and the Resume Timeout Minutes is set to 60 then the participant is able to resume the assessment until 10:00 AM.

7. Click  Save on the Stage level

   

1. Download Wear OS from the Google Play Store

• Choose the Google Play Store app from the participant’s phone

• Search Wear OS by Google

• Choose INSTALL

2. Connect Wear OS Watch to Phone

This section will require both the watch and the phone.

1. Tap on the watch screen when it says Tap to begin

   

2. Select English (United States) as your language

   

3. Press the check mark to agree to the Terms of Use

   

4. The watch will then prompt you to open the Wear OS app on your phone. Scroll down and you’ll see the watch name. Take note of the watch name as you’ll use this as a reference to it later during the phone setup.

   

   
   

1. Press Start Setup

   

2. Press Agree for Terms of Service

   

3. Press Agree for Make Wear OS better

4. The phone will then attempt to link with your watch. Turn on Bluetooth if the phone prompts you to turn it on.

   

5. Match the watch name seen on the watch with the watch name on the phone and click on it.

6. A pass key will appear on the watch. Make sure it matches the one on your phone and press OK to pair the phone with the watch.

7. Under Choose which Google Accounts to copy to your watch, make sure the slider is on (slider will be blue if it’s set to on) next to the participant’s google account. Click on Next

8. Press Copy to copy the google account to the watch

9. Under Stay connected to Wi-Fi, press Connect

10. Press Next under Chat with your friends

11. Press Allow for all 4 of the permissions.

12. Under Check your calendar, press Next and press Allow for the calendar permission

13. Under Get notifications at a glance, press Allow

14. Tap on the slider next to Wear OS by Google (it’ll turn blue)

15. Press Allow on the Allow Wear OS by Google pop up

16. Press Next under Location notice

17. The phone will then continue to set up on its own (may take up to 5 minutes).

18. Once you see the You’re all set screen, press Done

3. Sign in to Google Fit on the Watch

• Swipe from right to left on the watch

• Tap the screen to sign in to Google Fit and use the Google account that you copied over to the watch

• Fill in all the details and accept all the permissions

4. Download Insight from the Google Play Store

• Choose the Google Play Store app from the participant’s phone

• Search for Insight mHealth Platform

• Choose Install

• After the app downloads, choose ACCEPT

• Open the Insight app

• Click Allow to all permissions

• At the “Do not optimize battery usage” prompt, choose YES

• Create a participant in the CMS and set up the participant on the Insight app. Click here for instructions on participant set up.

5. Download mHealth Outsight from Google Play Store

• Choose the Google Play Store app from the participant’s phone

• Search mHealth Outsight

• Click on Install

• Click on Open to open the Outsight app

• Press Allow on all the permissions

6. Download mHealth OutsightAndroidWear app on the Fossil Watch

• On the Fossil watch, press the middle dial to open up the watch’s list of apps.

  

• Click on Play Store

  

• Scroll down until you see Outsight under Apps on your phone and click on the download button

• Open OutsightAndroidWear in your list of apps, and accept the sensor permission

Troubleshooting

1. Ensure WEAR OS, Insight, and Outsight remain open and running in the background.

   1. If the app is open, Click the “Home” button (typically located at the bottom, center of the phone) to allow the app to run in the background. Example of a Recent window below:

      

   2. Note: If the app(s) are not displayed in the “Recent” window then the app(s) are closed; this prevents any background operations which hinder collecting sensor data.

2. Verify there is a connection between the smartwatch and phone.

   1. Open the WEAR OS app on the phone > under the watch name “connected” will appear if the phone and watch are paired.

      1. If WEAR OS signifies there is no connection, reestablish the connection by hitting reconnect

3. If there appears to be no connection, open Outsight and Insight on the phone.

   1. This can reestablish a connection between Outsight to Insight to allow sensor readings.

4. Restart the phone and watch if the above methods do not produce the expected results.

   1. Restarting Phone: hold down the power button (typically on the side of the phone) until Restart Phone appears > Click Restart Phone

   2. Restarting Watch: hold down the large middle dial on the side until Restart appears > Click Restart

5. Attempt to pair multiple phones and watches while thoroughly reading the instructions (starting from 1. Download Wear OS) to gain more experience; doing this can reduce quantity of errors when pairing the phone and watch.

Supported Devices:

• Fossil Smartwatch 5^th Generation

1. Create a new Event and set the Schedule Type to “Sensor Data“

   • Sensor Data can be scheduled to start at a specific time or any of the time offset (e.g., before sleep time)

2. Add a Setting ('+') to the “Sensor Data“ Event, also called “Sensor Data”

   1. Device: “Android Wear”

   2. Choose a Sensor Type

      1. Pedometer

      2. HeartRate

      3. Accelerometer

   3. Repeat Count and Sensor Read Frequency (milliseconds)

      • These values are tied with the Schedule Type/Time to schedule the start of sensor data collection and set how long the delay between readings should be, and how many times the readings should repeat (a repeat of 0 means there will be 1 reading, a repeat of 1 means 2 readings, …).

      • “Repeat Count“ is the number of times per day that this Sensor Event will trigger. The time increment between Sensor Events = T / 1440 (There are 1440 minutes in a day), where T is the value of the “Repeat Count“ field. T = 480 means that the Sensor Event triggers every 3 minutes for the entire 24 hour day.

      • Frequency is the length of time between Sensor Events, in milliseconds (0.001 sec). Repeat Count is the number of times that the Sensor Data event will trigger during each 24-hour cycle, based on the Select Time which is the start of the first Sensor Event. It is the responsibility of the Study designer to ensure that (Frequency * Repeat Count) total is less than or equal to 1440 minutes, which is 1 calendar day.

      • It is recommended to not have multiple sensors firing at the same time. If you need heart rate and pedometer readings, they should be set at least a minute apart as readings (particularly HR) may take time to complete and requests may be dropped if a service is busy with another reading.

      • There is a max of number of “events”, subdivided by day, that can be scheduled. This is a platform limitation, and may vary by vendor but any study scheduling more than 200 events per day should take caution. There is a convention that will leverage “repeating” sensor events and will allow more data to be collected. However, no assessments can be associated with a repeating sensor event (ie, follow ups).

      • If you wanted sensor readings every 10 minutes all day, you would set:

        1. Schedule Type = Specific Time

        2. Select Time = 12:01am

        3. Repeat Count = 143 ((60 mins * 24 hrs / 10) = 144 -1 for initial offset)

        4. Sensor Read Frequency = 600,000 (milliseconds)

3. Post-Sensor Reading Logic (cannot be used for “repeating events, see above)

a. If this formula evaluates to true, the Selected Assessments will trigger

• Events will only trigger if it is during the participant’s waking hours.

b. If left blank or if the formula evaluates to false, the event will passively collect sensor data.

c. This formula is not limited to sensor specific formulas. The usual question based formulas work here as well if you need to reference other data.

• Refer below for formula options.

Sensor Specific Formulas

• GetStepsPerMinute(n)

  • Gets the average steps per minute over a given duration

  • Ex: GetStepsPerMinute(30) < 8 would get the average steps per minute from the last 30 minutes and trigger an assessment if that value is less than 8. (less than ~8.33 steps per minute is sedentary)

Using Sensor Data in a Follow Up Event

• Additionally sensor readings can be generated through a “Follow Up” schedule type. For more information on how to setup Follow Up events, click here. Then start at the Step 2 of Creating a Sensor Event to configure the Sensor Data setting.