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 several ways an intervention can 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.
Attach data and close encounter... indicates when the encounter should close. In general, “As soon as data is available” will be used when you are waiting for any user input, while “Wait until the end of 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 whether new data replaces the previously attached data on a closed event.
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 if the Collect Data event gets new data attached to it after it is closed.
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.
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 or logic.
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).
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? | |
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? | |
Why does data come in late? | |
How do I create an incident whenever late data is attached to a Collect Data event? |
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