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:
Surveys/Forms - Learn about building surveys here: Building: Surveys
Devices - For physical devices
SMS/Other - For data sources that aren’t surveys or physical devices
Clarity -Cus Custom Data Source (via API)
Clinstream
PennchartX ADT feeds
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
Most interventions require actions or logic to be performed as a result of participant data. This can be for adherence tracking, messaging, or more. There are two main ways an intervention can be configured to be reactive to participant data.
Data Collection Events
One method for performing actions from data and tracking adherence is to use a Data Collection event. This is an event type which is used to process data that comes in for a specified window of time. You can read about how to set up a Data Collection event here: ⚠️ 'Collect Data' Event
The exact behavior of a Data Collection event is a combination of how it is defined on the event page, and how the device. In the Advanced Settings section of a device, there are a number of options around how we determine which piece of data is attached to the Data Collection event when it closes:
Selection Strategy determines which piece of data attaches to the event when there are multiple data points inside the event window.
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.
...
In general, “As soon as data is
...
Generally used for medication adherence devices
...
available” will be used when you are waiting for any user input, while “Wait until the end of the encounter
...
Ex: leave Fitbit encounter window open so that WTH attaches the maximum number of steps walked to the encounter.
...
window” will be used when you are going to look at all data in a given day.
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
whether new data replaces the previously attached data on a closed event.
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 the Collect Data event gets new data attached to it after it is closed.
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)Once data is attached to an event, it can be used in event logic to determine follow-up behaviors.
Data Variables
Another way in which Way to Health enables you to perform actions based on your collected data is through Participant Data Variable. Once you have one of these variables defined, you can use it in messaging, logic, or other variables.
Reasons for late data
...
didn’t sync watch to phone
...
Question | Answer | |
|---|---|---|
What’s the difference between “Timestamp” and “Received in W2H”? | How do I enable intraday data collect? | How do I change the field that attaches to a Collect Data event?Timestamp refers to when the vendor says the data is for. Received in W2H refers to when that data made it into the platform. Example: On 10/05/2023, a participant walked 8429 steps. On 10/06/2023, Way to Health asks Fitbit how far the participant walked the previous day. In Manage Data, the Timestamp will be some time during 10/05/2023 since that is when the data is for while Received in W2H will be some time on 10/06/2023 since that is when the data made it into W2H. |
If there are multiple rows in manage data for a Collect Data event window, how do I change which value attaches? | ||
What is device latency? |
...
How do we fetch data?
Difference in timestamp vs received in w2h
...
How does data attach?
last, max, attach early
latency
...
Device Latency is a period of time that Data Collection events will wait before closing to allow for data to be collected. This will usually allow a device to ensure all data for the previous day is in the platform before closing. | |
Why does data come in late? | There are a number of reasons that data may come in late, which depends on the device. Some common reasons for data to not come in, or come in late:
Both of these could cause delays in the data making it from the device to Way to Health. |