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:
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).
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