Creating a Data Source

To create a new data source, you can go to the Data Sources tab under Manage Study, then create a data source from the following types:

1. Surveys/Forms - Learn about building surveys here: Building: Surveys

2. Devices - For physical devices

3. SMS/Other - For data sources that aren’t surveys or physical devices

   1. Clarity -Cus Custom Data Source (via API)

   2. Clinstream

   3. PennchartX ADT feeds

   4. CSV Uploads - Custom Data Source (Manual Upload)

Devices

For a list of our supported devices, look here: https://waytohealth.atlassian.net/wiki/spaces/BG/pages/2567110660/Supported+data+sources#%5BhardBreak%5DConnected-Devices

The first step to setting up a device integration is to select which device you are trying to collect data from:

Once a device has been selected, you will be presented with any additional pieces of information that may be required for Way to Health to interact with that device vendor. This is usually either a key provided by them for authentication or a username/password. Other devices may have custom configuration around what data they will ignore/process so that invalid data inputs do not cause issues.

Advanced Settings

There are advanced settings within each device that can impact how data is processed for the device on a more detailed level. Most devices have default values for these settings but there may be situations where you want to change them.

Collect Time Series Data enables intraday data collect for devices that support it.

Selection Strategy explanations can be found in How Device Data attaches to Events. However there are some general principles.. 

• First: used for medication adherence devices

• Last:

• Min: used for weight loss studies

• Max: used for physical activity studies 

Selection Field determines which field of data WTH should use for a particular device to determine whether a participant completed or was compliant to the encounter

• Ex: Clevercap pill bottle selection field should be IS_TAKEN, which will have the variables 0 and 1 for yes and no to determine encounter completeness and compliance 

Attach data and close encounter... indicates when the encounter should close.

• As soon data is available: will immediately close out the encounter once data is received and attaches to the open encounter.

  • Generally used for medication adherence devices

• Wait until the end of the encounter window: encounter will not close until the end of the encounter window.  This is ideal for devices where it may be typical to receive multiple data enteries throughout the course of the encounter.

  • Ex: leave Fitbit encounter window open so that WTH attaches the maximum number of steps walked to the encounter.

  • Ex: leave Withings Scale encounter window open so that WTH attaches the minimum weight value to the encounter, regardless of how many times the participant steps on the scale.

When an already-completed encounter gets new data... determines what to do with new data 

• Attach new data in place of the old: If new data comes in after an encounter is completed, it will switch out the new data with original data 

  • Ex: Fitbit participant doesn't sync their device until the following day, WTH will replace the '0 steps' with the # of steps that they walked

• Stick with our original data: WTH should leave the original data that attached to the encounter

  • Used for medication adherence devices

Apply feedback... indicates what action WTH should take following new data

• Only the first time data attaches: If any new data comes in during an encounter window that has already been completed, WTH will not do anything. 

• Each time a new data point attaches to an encounter: If any new data comes in during an encounter window that has already been completed, WTH will reapply feedback on the encounter for each data entry 

If data attaches late to an event... allows for creation of an incident in the case of late data.

Data Collection Events

One method for collecting data and tracking adherence is to use a Data Collection event:

Once you have selected the event type, you can choose which of your devices you want to attach to the event

Data Collection

There are two ways in which we collect data from a device. A vendor can either push data to Way to Health when they have something to provide to us (Push), or Way to Health can routinely ask the vendor if there are any updates (Pull).

• How do we fetch data?

  • Difference in timestamp vs received in w2h

• How does data attach?

  • last, max, attach early

  • latency

•  

• Reasons for late data

  • didn’t sync watch to phone

  • didn’t sync phone to server