Do not use spaces for variable names. If needed, use an underscore. For example, “Question 1” will not be acceptable for a field name. Instead use Question1 or Question_1.

Additionally, variable names are case-sensitive. [FOR_EXAMPLE], [For_Example], and [for_example] would be considered 3 different variables.

In the CMS, the options for the LineChart appear as shown below.

The first option is to select a Question in the Study. The requirement for the LineChart is that the Responses from the Question have numeric values. If they do not, the Line Chart will show an empty graph.

The default Line Chart for a Question uses all Responses for the Question over the course of the entire Study.

Other options are as follows:

Show Axis Labels - This is an Enable / Disable slider. Data Labels will be visible along the Y-axis at fixed increments.

Y-Axis Increment Label - A typed-in element of units (such as “Drinks“ or “ppm“) will be added to the Y-axis increments if “Show Axis Labels“ is enabled. Does not show if “show Axis Labels“ is Disabled.

Show Threshold - sets a second line on the graph at a fixed Y-value. Displays the graph data value overlaid the Threshold value. If the Threshold is significantly higher than the highest point of Data, the graph is stretched vertically to show both the data and the Threshold.

Threshold Value - If “Show Threshold“ is Enabled, this is a number input for the Threshold Value to be rendered against the data values from the selected Question.

Show Cumulative Sum - The Linear Chart is able to show a linear sum of Question Data over multiple days, as opposed to showing a linear plot of data. Each Response value is summed with the previous data point value, starting with just the first point and ending with the Response value from the last Response.

Number of Days - Line Charts can designate a number of days to use instead of all Responses over the course of the Study. Inputting a positive number of Days, the displayed Cumulative Sum Line Chart will show the Response Data for the last number of allocated Days. Leaving the Number of Days blank will show all of the Responses over the course of the Study.

Single Line Chart Visible Axis labels Data collected > 30 days Y-Axis Label → Ppm	Line Chart w/ Threshold line No Axis label Data collected > 30 days	Cumulative Sum Line Chart Visible Axis labels Y-Axis → test	Cumulative Sum Line Chart with Threshold Line No Axis label

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.

1. 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.

1. 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

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

1. 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

Note: The Fossil Watch will need to update it’s Play Store. Ensure that there is a good Wi-Fi connection and allow it to update while the watch is charging. This process may take 5-15 minutes. Typically, OutsightAndroidWear will automatically download to it. If it does not, a search through the watch’s Play Store as described above will work.

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.